FPGA Replay Board

[mikej]

Sounds like typical production woes... keep at it Mike!

Thanks Jim. Nothing unexpected - especially with Chinese suppliers. I deal with this sort of thing in my day job, but it's even less fun when it's your own toy.

"* So boards without the new bootloader works out of the box but without the features of said option?"

The revised bootloader code works on both old and new boards. It hasn't been shipped yet as it is part of the new firmware. The change is to correctly set up the internal memory controller as a result of an errata.

"* This new batch of ARM cpus only has slightly slower flashmemory write cycle? not slower flashmemory read accesstime?"

it's still in spec - just the old chips worked with the faster setting. It's only really read that's interesting from the flash in our case

"* Does the dead 1.2 V supply mean that you have to check and replace this on all boards?"
All power rails are checked on each board as part of the test suite. If it's out of spec the regulator is replaced.

"* How is the DDR memory self calibration going?"
Done, works like a charm.

"Whats VNC2?, If I recall it correctly, the ARM cpu is the USB-host and sends this to the FPGA via i/o. I like the everything-on-one-board-solution Perhaps an option would be to handle other USB devices by just forwarding the raw data and let the Amiga side deal with the configuration of endpoints etc."

This ARM cannot be used as a USB host. The VNC2 is an optional module which fits on the board instead of the PS2 connector and provides two USB host ports, and all the software muscle to drive them. It speaks mouse/keyboard SPI back to the FPGA which feeds it into the Amiga core.

"What I would like is to be able to just plug the board via USB ethernet to the local network and run with it, without messing with any pc-2-sd-2-arcade-repeat. Firmware updates would be just a matter of pressing a key. "

You can with the ethernet adapter on the daughterboard.

Firmware updates for the FPGA are as simple as copying the file on the SD card.
For the ARM code you push the menu button while powering on the board, and run an update program on your PC. The two will talk, the ARM flash is reprogrammed and you are good to go.

You can also update the bootloader this way too.
If you mess it up, there is a link on the board to reload a default boot loader.
/MikeJ

[freqmax]

Daughterboard is nice for extras lik a CPU but for Ethernet I would prefer it to be on the main board ie KISS.

Seems I misstok the P13 micro USB conncector for the PS/2 connector in USB mode. But if the FPGA has the electrical control of the PS/2 port + adapter to USB. Extended device support is only .bit file away

[psxphill]

Daughterboard is nice for extras lik a CPU but for Ethernet I would prefer it to be on the main board ie KISS.
 
Seems I misstok the P13 micro USB conncector for the PS/2 connector in USB mode. But if the FPGA has the electrical control of the PS/2 port + adapter to USB. Extended device support is only .bit file away

You'll almost certainly have to write the code for this too (assuming that it can actually be flashed in place)
 
http://www.ftdichip.com/Products/ICs/VNC2.htm

[mikej]

You'll almost certainly have to write the code for this too (assuming that it can actually be flashed in place)
 
http://www.ftdichip.com/Products/ICs/VNC2.htm

I have written all the code for the mouse/keyboard bridge already.
The VNC2 can be updated from a USB stick, and I need to add this before release.
Otherwise, you need to use the programmer - there is a connector on the module.

http://apple.clickandbuild.com/cnb/shop/ftdichip?op=catalogue-products-null&prodCategoryID=118&title=VNC2-Debug-module
/MikeJ

[psxphill]

I have written all the code for the mouse/keyboard bridge already.
The VNC2 can be updated from a USB stick, and I need to add this before release.
Otherwise, you need to use the programmer - there is a connector on the module.
 
http://apple.clickandbuild.com/cnb/shop/ftdichip?op=catalogue-products-null&prodCategoryID=118&title=VNC2-Debug-module
/MikeJ

I meant to enable the VNC2 to allow USB Ethernet. If the only way to update it without a programmer is to have it update itself and it needs to work for that, then there is no way I'll be messing with mine.
 
But it does sound at least doable. It's likely to be pig slow though.

[freqmax]

AT91SAM7S256-AU-001
CPU: ARMv4T (ARM7TDMI)
Freq: 18.432 MHz (max 55 MHz)
RAM: 64 kB
ROM: 256 kB

VNC2
CPU: 16-bit Harvard
Freq: 12 MHz
RAM: 16 kB
ROM: 256 kB

I think I know which MCU chip that would be tasked to handle the USB hodepodge.

[mikej]

The VNC2 runs the entire USB stack, the ARM is running the menu system and file IO to the SD card.
/MikeJ

[freqmax]

I know it was a mere suggestion on which one that has the most CPU power.

Btw, how much code size and MIPS does it require to use a USB device like a Ethernet dongle? (estimate), perhaps this estimate at 300 kB of RAM is realistic? in addition to the on board 4 MB flash.

Anyway at present an external USB/Disc/Ethernet solution is the required path.

[freqmax]

Are these "features" incorporated into the core?
abime.net: Undocumented Amiga hardware stuff

[psxphill]

I know it was a mere suggestion on which one that has the most CPU power.
 
Btw, how much code size and MIPS does it require to use a USB device like a Ethernet dongle? (estimate), perhaps this estimate at 300 kB of RAM is realistic? in addition to the on board 4 MB flash.

The VNC2 has to at least be involved, because it's the only chip that has a USB host port on the board. It then uses SPI to get the data elsewhere. I imagine putting in something that allowed more than keyboards and mice to work (ideally making it subway compatible) is doable but it'll be a lot of work.

[freqmax]

Well because the FPGA i/o goes straight to the PS/2 data+clock is available, one could use them as D+/D- and with the right core you can bang USB right there.

[mikej]

Well because the FPGA i/o goes straight to the PS/2 data+clock is available, one could use them as D+/D- and with the right core you can bang USB right there.

yes, but the electrical levels are wrong - ideally you still need an external phy. The VNC2 is cheap and means reduced software effort.
For high performance the normal USB and Ethernet PHY/MACs hanging off the processor databus are the way forward. It is already running with the USB stack.

Board testing continues, I've replaced a few of the 1.2V regulators without any trouble and the boards work fine.
/MikeJ

[freqmax]

Signal levels can be set with FPGA configuration, and if not one can fix that externally. Less electronics than another MCU.
Two 3,3V level signals that forms a differential signal together shouldn't be that hard to accomplish. Ofcourse it won't be 100% to specification but that hasn't hindered Amiga fans before

[mikej]

Signal levels can be set with FPGA configuration, and if not one can fix that externally. Less electronics than another MCU.
Two 3,3V level signals that forms a differential signal together shouldn't be that hard to accomplish. Ofcourse it won't be 100% to specification but that hasn't hindered Amiga fans before

You need an external pull-up still, and it would not be standards compliant. The VHDL to run the USB would take about 5% of the FPGA, but you would still need an on-board micro to run the USB stack for ps/2 mouse and keyboard.

/MikeJ

[psxphill]

You need an external pull-up still, and it would not be standards compliant. The VHDL to run the USB would take about 5% of the FPGA, but you would still need an on-board micro to run the USB stack for ps/2 mouse and keyboard.

Are hubs and usb game pads also supported?

[cunnpole]

The previous answer to game pads was "The current core is very close to the original hardware, so only 9PIN digital.
There are analog inputs on the ARM which can be used in future.
The USB adapter adds keyboard and mouse, and can be extended to all sorts of stuff in future."