Finally got around to writing the firmware changes needed to support Amiga and Atari ST via the Imperium Solo USB adapter.
Here’s a video of Amiga version:
Will update soon with an Atari ST video too.
When I release the firmware updates, you can re-program the existing Imperium Solo C64 hardware with them, but not the Imperium Solo Amstrad CPC, as there is jumper settings via 0 ohm smd resisters that needs to be changed to be used on other hardware than the Amstrad CPC.
Notice that I made a seperate site for Imperium Solo, here:
Where you can see the database of tested Game controllers and mice, along with their button mapping (I still need to update this for Amiga and Atari ST).
Small update on the Imperium Solo project initially released for the Amstrad CPC. Made some changes to the firmware and changed two 0 ohm SMD resistor settings to support Commodore 64 and probably many other retro computers with my modern USB controllers to joystick adapter.
For now I used an external 5V powersupply, as you can only draw a limited amount of current over the C64 joystick port* and power usage will depend on the controllers plugged into the adapter (the adapter itself uses very little). Will see first if there is interest at all for this adapter (maybe something similar already exist?). Anyway here is a video of the C64 prelimary version.
*It turns out the 100mA limit per Joystick port (200mA total), is a limit of what the stock powersupply can deliver safely while keeping the system stable. Otherwise the 5V on the joystick port is directly connected to the PSU input with a nice fat trace. So if using a better powersupply or the devices connected to the joystick port use less than 200 mA current, there is no need for external powersupply.
About mouse support. It is just joystick mode (1350). I cannot support the analog mouse mode (1351) with current PCB layout atleast.
Imperium Solo is a USB to joystick adapter, intended for using USB gamepads, like DualShock 3/4, XBOX One controller on retro computers. It’s also possible to use USB mouse. For now the project only supports the Amstrad CPC range of computers, but I plan to make firmware updates for use with other retro computers.
The firmware is updatable by pluggin in an USB stick/drive (FAT32) with the correct file when the adapter is powered on.
Special supported controllers are only DualShock 3, DualShock 4, XBox One controller and SNES USB controller. Other USB HID controllers should work by using my generic HID parser, but controller mapping may not be ideal for those. So I hope to add more controllers with the help of feedback from users.
USB Mouse is also using my generic HID parser, which atleast works with the 5 different USB mice I had laying around. At a point I made a custom mouse mode, with 5 bit resolution for delta values making it possible to get much better mouse feeling(proportional mode). This may be implemented to a later firmware update, if there is demand (it will need adapted software to be usable).
Below you can see a video of :
Installation/Connecting (notice most other retro computeres have power on the joystick port, so will not need DC splitter cable like the Amstrad is using)
Playing a game with USB controller
Playing a game with USB mouse
Playing a game with TWO usb controllers
Will update later with documentation (controller mapping, firmware upgrade etc).
Lastly expect another update, when I add firmware for the next retro computer.
The M4 board for the Amstrad CPC computer series has now surpassed more than 600 shipped units. And I expect to pass 700 units this year, if things continue as now.
Though there hasn’t been any recent updates on this blog for the M4 board, I have released some firmware updates adding new features.
The biggest update came last year, when I added Hack Menu which is NMI triggering with ROM/RAM remapping. Making it possible to have “Multiface 2” like features.
For existing users it can be launched via the web-interface or by manually soldering a switch onto the board.
As can be seen on the video above, it is now possible to save game progress and re-load it again, using the popular .SNA format, which is compatible with many emulators aswell.
However it is still in beta so it can crash under some circumstances. I expect to do some major software improvement to this Hack menu.
How to add the Hack button to existing PCB’s.
Meanwhile I updated the PCB once again to have this new Hack button.
The PCB now being version 2.5C.
So what about M7 / Galaxy Board / Zen80 board ? It’s not cancelled, but I haven’t really worked on it for a long while, I do have some overall changes in mind and hope to pick it up again.
Imperium Solo – USB joypads
I also made a USB to joystick adapter called Imperium Solo, which is also partial functionality of the Galaxy board. Its intended use is to be able to connect USB joypads and mouses to the joystick port. For now it supports CPC, but later it’s meant to be working with ZX Spectrum +2/+3, C64, Atari ST and Amiga. Or well lets wait and see 😉
Video showing the use of Dualshock 3/4 controllers on an Amstrad CPC!
I will update more on this soon, as I am awaiting the final PCB.
Another board I started a long time ago, but due to time/life, has been on the shelf.
M7 board is connected between a Z80 and it’s dil socket.
For starters aimed at the Amstrad GX4000 console (and of course the other Amstrads), boosting it to be a full blown CPC+ computer. But maybe later other Z80 based computers.
It gives similar features of M4 board ie.:
SD card as mass storage
and much more.
However due to the design it will be able to offer more than the M4 board.
The Z80 datalines can be intercepted, so technically any hardware can be emulated on the Cortex M7 chip (disc drives, tapes, keyboard), providing the Cortex-M7 can keep up.
The design is:
STM32F7 mcu handling the Z80 address, data and control lines, SD card.
STM32F1 mcu being USB host, interconnected to the Cortex-M7, via 8 datalines and 4 address lines (covering the keyboard matrix).
ESP8266 handling the WiFi, connected via SPI to the Cortex-M7
Level converter between Z80 datalines to STM32F7 with OE signal
And a bus switch to seperate the Z80 datalines from the motherboard, this way any response on an I/O port for example can be “replaced”.
Planned features for starters is, expanding ram, probably I will spare 256KB + the internal 64 KB for starters.
Add key+mouse option (via ie. logitech unified) through the USB socket.
Debugging signals on a CPC464 and physical layout.
Description and purpose of the “M4 board”.
The M4 board, features as previously described a ST32F407 Cortex M4 MCU, connected via SPI to a ESP8266 WIFI module, and 18 GPIO’s routed via a GTL2000 voltage translator chip.
It was meant to be connected to the old the Amstrad CPC (z80 based) computer via it’s expansion port.
As with most old age computers, it runs with 5V I/O, here is where the GTL2000 chip came in handy.
The signals driven through the GTL2000 are output signals and the bi-directional data bus (D0-D7).
Input signals are connected directly to the ST32F407 Cortex M4 as it is 5V tolerant.
The idea was to provide WiFi to the Amstrad CPC, for easy and fast data exchange between it and a PC, but also direct internet access.
ROM BOARD emulation
First prerequisite was the ability to run code on the Amstrad via the M4 MCU so no additional loading (i.e. disc) would be needed.
It would be done by mapping a ROM in the Amstrad addressable space, this ROM would be in the M4 ram.
IORQ and WR will occur when a ROM is selected, data lines will contain the ROM number.
ROMEN and RD will occur when a read is happening from the currently selected ROM, address lines have the address, ROM data will be send back over the data lines.
A fairly trivial task, but the timing is tight having to bit bang the gpio, do direction changes on gpio’s mapped as data lines, even when the bus runs at only 4MHz.
Much time spent optimizing the handler in ARM assembler, it finally worked.
SD card storage
Being able to run code via the ROM board emulation, it would be nice to have native r/w storage.
A micro SD card slot connected to the M4 SDIO lines, was meant for this purpose.
An transfer interface from the Amstrad CPC to the M4 was designed.
Two I/O ports were assigned when an IORQ happened, one for receiving data on the M4 and one for telling it data was send, so it could process.
This was done as it’s easy to store data (low clock count), but takes additional time to process them.
When the 2nd port is written, the MCU sends BUSRQ signal to the Z80 CPU, which will ‘freeze’ the z80 CPU at the end of the current cycle, now the M4 has the time it needs to process the incoming data, before resuming the Z80 CPU and responding.
Responses are done in the ROM space, which of course is read only on the CPC, but R/W on the M4, as it is kept in the M4 ram!
Next up, was to hook the system bios/firmware functions, that do file related I/O to tape and disc on the original system and re-directing them to the sdcard.
Thus native file access from the SD card is possible, providing the CPC with up to 32GB (or more) of storage via SD card.
WiFi & Internet
In short the connection between ESP8266 and the M4 was done via SPI as IPC.
To allow internet/WiFi access from the Amstrad CPC itself, it sends a command to the M4, which again sends an IPC call to the ESP.
The ESP8266 hosts a WEB server, where various settings can be altered.
A battery mount was put on the board, making it possible to provide Real time clock as well via the RTC in the ST32F407.
What it does
Emulate Romboard, currently up to 16 roms, can be uploaded/removed via Web Interface.
Download files from internet via WiFi.
Mass storage to SD card, via native file I/O. R/W support. Emulated as drive A.
Can use DSK files on the SD card too, but only for file read access and sector reading via firmware call.
Upload files via web interface.
See a short demonstration here:
Lots of error checking.
Should anyone be mad enough to want a similar interface for their Amstrad CPC (or other suggestions), don’t hesitate to put a comment.
If enough are interested, I will run a batch + it’ll motivate me to finish and polish things up.
A little progress on the M4 Board, I managed to get the IPC (inter processor comms) system between the Cortex-M4 and the ESP8266 going.
It uses HSPI interface + GPIO0 on the ESP and SPI1 interface + a gpio on the M4.
SPI comms from ESP to Cortex-M4
Cortex-M4 acts as spi-slave, it will listen to the any incoming HSPI command from the ESP, via SPI_RXNE interrupt (on SPI1 irq handler, max. 42 MHz).
The irq handler is done with some very optimized assembler code and simply buffers whatever is send from the ESP, whenever there is something in the rx buffer. It also deals with sending any data if there is something in the transmit buffer to send.
HSPI CS will trigger an external interrupt on both edges on the M4.
When HSPI CS goes low, it will clear the index of the spi1 rx buffer.
When HSPI CS goes high, it will process the command/data received in the spi1 buffer.
Cortex-M4 to ESP
GPIO0 is set as input on the ESP and the M4 will pull this low whenever it wants to send command/data to the ESP. Prior to that command and data is written to the transmit buffer of the SPI IRQ handler.
This triggers an interrupt on the ESP, which will then start clocking dummy data out on the SPI to read/process the responses (full duplex).
This wont come in any faster than the ESP is driving the clock. The HSPI clock is set to 40 MHz.
This system works pretty well now. It’s not as fast as I’d like. Currently transfer is about 500 KB/s, while I can download to the ESP with about 900KB/s under optimal conditions.
So the SPI IPC is a bottleneck, however there is still room for improvement.
As the clock speed is really fine on the SPI, the problem is the delay between each byte write from the ESP which is done via CPU writes.
Ideally I could use DMA, but there seems to be no info on this anywhere in regards to the ESP.
Another option is to use 16 bit read/writes instead of 8 bits and probably almost double the speed.
Or I could use the entire 64 byte buffer of the ESP HSPI interface and clock them out nicely without delays 64 bytes at a time.
On the hardware side, I have re-designed the board and ordered new pcb’s. I screwed up the footprint of the GTL2000 chip and there simply was no way about. Obviously other improvements & fixes were added.
After ages of waiting for components to arrive from China (and some didn’t, so I had to reorder).
I was finally ready to assemble the M4 board. After applying the solder mask and doing pick and place, I found the GL2000 bi-directional level converter was the wrong package :/ – Oh well added the other components as there is enough work to do without it for now. Also a couple of other screwups, ie. swapped miso and mosi on the flash, used wrong SCK pin on ESP-12E (notice it is PIN 12 that’s spi-clock). So eventually I will have to re-do the PCB. Update: It’s not entirely true, it is because there is two (known) different ESP-12E modules in existence, see here http://www.esp8266.com/viewtopic.php?f=5&t=3163 My initial layout wasn’t wrong, I just got a 12E module with a different pin layout :/
For now, the MCU, SD and SPI flash is working, I can access the ESP8266 wifi chip and read/write the spi flash from the Cortex M4 (keep the ESP in reset state and do spi access) and obviously send serial commands.
However the plan is to make an IPC interface via SPI between the Cortex M4 and the ESP-8266 to get proper performance.
I will update on this as I get along.
A side project to log industrial robots via their PLC (24V) interface.
The PCB consists of:
ST32F407VGT (Cortex M4) as the MCU.
SD card for storing detailed logs.
DP83848 ethernet PHY hooked up to the M4 RMII interface, connecting it to the LAN, so logs can be downloaded, statistics viewed, live view, settings and more.
Using netbios names and DHCP by default, so easily accessible without pre-setting.
Optocouplers to completely seperate the PLC signals from the board.
Battery backup for SRAM and RTC, even poweroff’s are logged.
Status leds for Power On, SD card OK, Ethernet OK, MCU running (flashing).
Firmware upgradable from LAN/Internet or microSD.
The PCB was designed to fit a compact DIN rail case and using screw terminals for power and PLC signals.
For once it was a really smooth experince, only screwed up the battery polarity, which was easily fixed by using another holder.