I tried the same sequence of steps within the /blink/ directory, expecting to see one or more LEDs to begin blinking (I'm unclear how long to hold SW7; I release before executing 'make dfu_flash'). However, when the device reboots, it still appears to have the conference code installed (showing a splash screen followed by the menu listing the elf files). I believe I have failed to upload the blink bit file.
I have successfully loaded in a modified "Hello World" elf with my name, so I appear to have good communication with the unit (the unit also reboots itself after I run 'make dfu_flash').
Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2019 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/
Invalid DFU suffix signature
A valid DFU suffix will be required in a future dfu-util release!!!
No DFU capable USB device available
make: *** [Makefile:31: dfu_flash] Error 74
Scott@Laptop MINGW64 ~/hadbadge/hadbadge2019_fpgasoc/blink (master)
$ make dfu_flash
dfu-util -d 1d50:614a,1d50:614b -a 2 -R -D blinky.bit
dfu-util 0.9
Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2019 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/
Opening DFU capable USB device...
ID 1d50:614b
Run-time device DFU version 0101
Claiming USB DFU Interface...
Setting Alternate Setting #2 ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 0101
Device returned transfer size 4096
Copying data from PC to DFU device
Download [=========================] 100% 1032329 bytes
Download done.
state(2) = dfuIDLE, status(0) = No error condition is present
Done!
Resetting USB to switch back to runtime mode
Invalid DFU suffix signature
A valid DFU suffix will be required in a future dfu-util release!!!
I've followed the instructions here: https://github.com/mohitbhoite/hadbadge2019_fpgasoc/blob/master/doc/soc-dev.md On reboot, it appeared nominally the same, so I'm not sure how to tell if I was successful with uploading the latest build (my badge had the original image from the conference already installed).
cd .. cd blink
I tried the same sequence of steps within the /blink/ directory, expecting to see one or more LEDs to begin blinking (I'm unclear how long to hold SW7; I release before executing 'make dfu_flash'). However, when the device reboots, it still appears to have the conference code installed (showing a splash screen followed by the menu listing the elf files). I believe I have failed to upload the blink bit file.
I have successfully loaded in a modified "Hello World" elf with my name, so I appear to have good communication with the unit (the unit also reboots itself after I run 'make dfu_flash').
I'm running Windows 10.
git terminal output after running 'make', then 'make dfu_flash': Info: [ 81394, 81549) |** Info: [ 81549, 81704) | Info: [ 81704, 81859) |** Info: [ 81859, 82014) |**** Info: [ 82014, 82169) |*** ecppack --svf-rowsize 100000 --spimode qspi --freq 38.8 \ --svf blinky.svf --input blinky_out.config --bit blinky.bit dfu-util -d 1d50:614a,1d50:614b -a 2 -R -D blinky.bit dfu-util 0.9
Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc. Copyright 2010-2019 Tormod Volden and Stefan Schmidt This program is Free Software and has ABSOLUTELY NO WARRANTY Please report bugs to http://sourceforge.net/p/dfu-util/tickets/
Invalid DFU suffix signature A valid DFU suffix will be required in a future dfu-util release!!! No DFU capable USB device available make: *** [Makefile:31: dfu_flash] Error 74
Scott@Laptop MINGW64 ~/hadbadge/hadbadge2019_fpgasoc/blink (master) $ make dfu_flash dfu-util -d 1d50:614a,1d50:614b -a 2 -R -D blinky.bit dfu-util 0.9
Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc. Copyright 2010-2019 Tormod Volden and Stefan Schmidt This program is Free Software and has ABSOLUTELY NO WARRANTY Please report bugs to http://sourceforge.net/p/dfu-util/tickets/
Opening DFU capable USB device... ID 1d50:614b Run-time device DFU version 0101 Claiming USB DFU Interface... Setting Alternate Setting #2 ... Determining device status: state = dfuIDLE, status = 0 dfuIDLE, continuing DFU mode device DFU version 0101 Device returned transfer size 4096 Copying data from PC to DFU device Download [=========================] 100% 1032329 bytes Download done. state(2) = dfuIDLE, status(0) = No error condition is present Done! Resetting USB to switch back to runtime mode Invalid DFU suffix signature A valid DFU suffix will be required in a future dfu-util release!!!