3B1 Unix PC emulator -- keyboard driver (half) done

On 10/02/11 07:18, SPC wrote: The easiest way I can think of to get a keyboard-data dump would be something along the lines of: - Attach an RS232 protocol analyser (or a logic analyser with RS232 decoding, e.g. the Salae Logic) to the RX and TX pins on the 6850 ACIA chip. - Plug the keyboard in, insert the Diagnostics disc (Foundation set disc 1), and boot the 3B1. - Wait for the memory check screen, count to five, then press SPACE. - Pick one of the sub-menus (e.g. the Subsystem menu) -- type in its number, followed by RETURN. - Press 0 <RETURN> to get back to the main menu - Type p4test <RETURN> to get to the Expert screen - Exit the Expert screen and reboot (7 <RETURN>). - Stop the logic analyser and remove the Diags floppy. This should give me more than enough information to fix the bugs in the keyboard driver... The reason I suggested the Saleae Logic was because it stores transition data to the host PC, and has onboard RS232 decoding (not to mention the fact that the Logic software will run without the hardware and still allow you to use the protocol decoders...) A HP analyser should serve the same purpose -- set it to Transitional Timing mode (so it doesn't waste all the ACQ memory on blank space), trigger on falling edge, pre-trigger buffer to 1% (which if memory serves is the minimum on the 16500B), and save the output as a CSV. I've got an app (somewhere!) which can convert a HP 16500B CSV to a VCD file which I can then load into GtkWave to analyse. Thanks, -- Phil. classiccmp at philpem.me.uk http://www.philpem.me.uk/