Welcome to the Parallax Discussion Forums, sign-up to participate.
Heater. wrote: »
Given the amount of stuff you have there for the Propeller and the Pi there is no way you are going to be able to check it all out first. It would take ages. Building, compiling, testing everything.
Good luck anyway.
Cluso99 wrote: »
I have never used the 1pin for a mouse. Not sure if it possible.
Some keyboards are outside the speed specs hence I used a test to determine the speed and then programmed it in, since there is no clock for the data shifting.
There is a circuit on my RamBlade thread for connecting the keyboard and video. See link in my signature.
Best of luck while off-line :)
Current files (bleeding edge) Dropbox files and binaries
The new Tachyon Forth Glossary of words (Kernel, Extend, Filesystem) --- Introduction to TACHYON Forth (+links to files)
Propeller Hardware Explorer and debugger (with VGA)
Watch Easynet in operation --- Build Tachyon V4 video
Peter Jakacki wrote: »
SD card clock and data in can be shared with the EEPROMs I2C lines SCL and SDA as there is no conflict and I have done it heaps of times although there was a Verbatim brand card that liked to clock the data in line at power-up but SanDIsk always works. PS/2 data rate can be automatically adjusted too by the data pattern as PS/2 is in the 10kHz to 16.7kHz range and essentially asynch serial. I already have all this O/S, FAT32, Ethernet, "scripts" and language tools in Tachyon bar some form of screen editor but that's easy enough. A basic 80x25 video screen needs at least 2k of buffer plus attributes but I either reuse the hub memory from the cog image as buffers or load "ROMS" from upper EEPROM. Good luck trying to get it all working in 32k of hub RAM and 32 I/O!
Cluso99 wrote: »
After power up where the prop may send data to the ps2 keyboard (with clock out from prop), the lines turn around and the keyboard outputs data together with the clock. When using 1pin only the data pin is connected so you don't see the clock to get the timing from the keyboard. The downside is that you have to time the keyboard. I found that some keyboards were not within the timing specification. I solved this in two different ways.
1: I required the user to press a space and timed this to set my timer in the prop. Ie autoboard.
2: Do part 1, getting the timing output. Then feed that into the code as a fixed constant.
Both these work.
As for sharing with SD, how do you ensure that no key is pressed/released while accessing the SD Card?
While I have never tested or researched this, I presume the keyboard is working as open collectors, as there are 10K pull-ups to 5V on both pins.
What you cannot do with the 1pin solution is send data to the keyboard, such as lighting the numlock etc leds. This really isn't a problem. The keyboard sends 2 characters every time a key is pressed and also when released.