![]() Maybe he has some extra ones he can sell to save yourself some time? Latest gerbers: Re: Native PS/2 mouse implementation for 386/486 boards using the keyboard controller Re: Native PS/2 mouse implementation for 386/486 boards using the keyboard controller I think maxtherabbit made his own and posted the gerbers, but I haven't tried this myself. Keropi made another: Re: Native PS/2 mouse implementation for 386/486 boards using the keyboard controller I made these which took some time: Re: Native PS/2 mouse implementation for 386/486 boards using the keyboard controller Option F is to use a device that plugs into your KBC socket to allow for native PS/2 mice to plug in. The two options couldn't be more different. I personally don't use serial mice on any system these days. It is also in Mouse.rarį) try a modified KBC circuit and switch to a PS/2 mouse. Also, I always use Test.exe to test my mice. Edit the mouserdrv.ini as appropriateĮ) If you don't have a Logitech mouse, try my fallback driver located in Mouse.rar. Do all testing from from a floppy disk, andĭ) Use a Logitech trackball mouse with their driver package 7.3. I can imagine a) failing if it is a hardware issue/conflict with the motherboard, but b) would likely still work.Ĭ) Disable (via jumper) everything on your multi I/O card except for COM1 and floppy. If your board was in my hands and I was having your issues, the first few things I would have tried were:Ī) see if I can get Rio444's PS/2-serial emulator card working with a PS/2 mouse Another PS/2 Mouse ISA (ISA8) card adapterī) see if I can get a bus mouse working with a bus mouse card, e.g. I never heard of dos navigator, so can't help ya there, but if it's for serial/modem communication it should be usable. back in the day we used telemate or terminate, or telix, or. Probably some telnet and ssh ports for dos.Įrhm. It was not obvious what i have to do really.Ĭannot even remember what DOS terminals i used back in the day. I dont remember ever using it in the distant past. The second approach with female connector will wait for the connector to arrive. Will run the suggested loopback tests soon. The one with terminal +2 connected pins will be first. If something else on the mainboard is causing the signal to stay stuck high or low, no interrupts can be handled by the mainboard. Reason is, interrupts on ISA are edge triggered. So it's best tested together with the loopback. ![]() ![]() I'm not asking for a voltage or frequency test on pin B24, There should be activity, signal going from low to high and high to low whenever there is serial data coming in. I have replaced the ic to rule out the possibility of a faulty chip.I mentioned in my first post that the controller and mouse are fully working.Ĭhecked the isa pins - voltages and frequencies check-out. I have tried removing the microcontroller out of the picture by doing a hardwired loopback but i dont get any echo. I have experimented with different baud rates and tried various combinations of decoupling caps on the vcc to check if this is a power stability of signal integrity issue. Any suggestions or tips would be greatly helpful as this is my first project with any FTDI chip. Maybe the USB cable is bad?Īlso I have configured the CBUS0 pin for VBUS_SENSE via the FT_PROG utility. usb 2-1.1: device descriptor read/64, error -32 usb 2-1.1: new full-speed USB device number 45 using ehci-pci Connecting 2x 100nF and 1x 4♟ caps on this pin was causing an error where the chip couldn't be read by the Linux kernel. You might notice that there are no decoupling caps on the VCC pin as shown in the datasheet. I have basically copy-pasted the self-powered USB design from the datasheet for FT230XS. I have attached the relevant schematic here. ![]() Inited Can Bus at bitrate 125000 bps turns to Initd aus a birate 500 ps. For example Helloworld\r\n turns to ellwold\r\n. The problem is that when I use GTK terminal, putty, or moserial to view the datastream, the data is always jumbled up and has missing fields. usb 2-1.1: FTDI USB Serial Device converter now attached to ttyUSB0 ftdi_sio 2-1.1:1.0: FTDI USB Serial Device converter detected usbserial: USB Serial support registered for FTDI USB Serial Device usbcore: registered new interface driver ftdi_sio usbserial: USB Serial support registered for generic usbcore: registered new interface driver usbserial_generic usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 2-1.1: New USB device found, idVendor=0403, idProduct=6015 usb 2-1.1: new full-speed USB device number 7 using ehci-pci When I connect the board the FTDI chip is recognized and proper kernel modules are loaded. I'm working with a custom STM32F429 board, I am using serial-USB port (USART1-PA9,PA10) for debug output and diagnostics. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |