[sorry for posting this in English]
after nearly 2 years of research and prototyping (every now and then) my biggest SHARP project so far is at the finishing line:
The SHARP PC-1600 Modular Extension Platform (MEP):
Some additional technical info:
The USB-keyboard use case comes "out of the box" - no programming required!
If you want to program your own application you need to do this:
- Program respective code in C for the ATmege328P. Therefore you can use my predefined API for I/O-port communcation with the PC-1600.
Write the compiled code via the on board SPI-interface to the ATmega.
- Program a respective PC-1600 ROM extension (Z80-Assembler). E.g. you may want to provide a custom BASIC token table and its implementation. Use an external EEPROM burner.
- Flash the USB-host controller (on board, utilizing a FTDI-USBtoUART cable) with a different application provided by the manufacturer
or build your own frontend hardware (UART communication with the ATmega on the backend)
When that is done, I'd might be ready to produce a small batch for the community:
- Assembled module (Backend + USB-Frontend), preconfigured with USB-keyboard software: 145,-EUR
- Shell/housing for the module (to come - probably 3D-printed body with aluminium cover): 20,-EUR
This is a pre-order poll. Please answer to this post, if you are interested in 1 or 1+2 (no binding order, but first come first serve).
Thank you for your interest!
I found that there is too much preprogramming and testing involved for a kit option, so I have to skip that offer.
The batch is limited to 10 units. Below I'll maintain a waiting list.
A remark on PC-1500 compatibility:
My initial thought was to design a module that has a PC-1500 compatibility mode. But it soon turned out that the PC-1500 would require 2-3 more ICs for buffering and sync, because the 1500-CPU cannot be haltet from peripheral devices in order to wait for complex processing within the device.
Another issue is the injection of transmitted key codes into the 1500 OS. There is no key ringbuffer or similar like the PC-1600 has and the respective OS-routines cannot be hooked like with the 1600.
I do like the 1500, but because of these shortcomings I decided to skip compatibility (at least for now).
But I want to thank Christophe (aka cgh) for his in depth help with this machine.
All the best
- ROM1500: 1x module+housing
- torgramm: 1x module+housing
- doum-doum: 1x module+housing
- Torsten Mücker: 1x module+housing
- Harald Richter: 1x module+housing
- Burhard Eicke: 1x module+housing
- Falkayn: 1x module+housing
- JPC69: 1x module
- Kai Schädel: 1x module