Running The TestBed
The instructions below refer to the two Goteks as follows:
- Device-Under-Test (DUT): Runs the FlashFloppy firmware to be tested.
- TestBed: Runs the TestBed firmware against the DUT.
Jumper for S0 only and with cleared Flash config (power on and then hold both buttons for a few seconds with no USB stick inserted until display changes).
Prepare a blank formatted USB stick by running make images and then mount the stick and copy the contents of the
images/ folder to the root of the USB stick.
Insert the USB stick into the Gotek DUT.
Build the firmware and then program the
TestBed with the FF.hex file, either by USB-TTL serial adapter or by
ST/Link. Examples of each for Linux are given in the flash and
ocd targets of the Makefile.
Configure jumpers as shown in Modifying A Gotek.
Connect the TestBed to the DUT using a straight ribbon cable. You can power the DUT from the TestBed using a Berg-Berg straight power cable.
You will want to collect serial logs from the TestBed using a USB-TTL adapter, and this can also be used for powering the TestBed. Connect to the 5V, GND, USART1_TX, USART1_RX pins on the Gotek programming header.
Tests will now start as soon as the TestBed is powered on. You can collect serial output from the USB-TTL adapter at 3Mbaud.
Sending a byte via serial resets the TestBed.
On Linux you may additionally log to a file in the usual way, for example:
# sudo miniterm.py /dev/ttyUSB0 3000000 | tee log.txt