Was working with it in icestorm just fine for the past few days. Out of nowhere it stopped letting me program it.
Hitting reset or unplugging/replugging results in a flashing boot light as expected.
TinyProg CLI ------------ Using device id 1d50:6130 Only one board with active bootloader, using it. Boards with active bootloaders: COM7: No metadata
TinyProg CLI ------------ Using device id 1d50:6130 Only one board with active bootloader, using it. All connected and active boards are up to date!
Attempting to program via apio gives: “Error: board TinyFPGA-BX not connected”
Attempting to program with ice storm gives a similar inability to find the board.
I’ve tried different USB ports, drivers install and setup correctly each time, shows up in device manager as “USB Serial Device (COM7)”
compiling with apio and attempting to write using tinyprog gives:
TinyProg CLI ------------ Using device id 1d50:6130 Only one board with active bootloader, using it. Programming COM7 with hardware.bin Traceback (most recent call last): File "c:\python38\lib\runpy.py", line 193, in _run_module_as_main return _run_code(code, main_globals, None, File "c:\python38\lib\runpy.py", line 86, in _run_code exec(code, run_globals) File "C:\Python38\Scripts\tinyprog.exe\__main__.py", line 9, in <module> File "c:\python38\lib\site-packages\tinyprog\__main__.py", line 334, in main addr = fpga.meta.userimage_addr_range() File "c:\python38\lib\site-packages\tinyprog\__init__.py", line 182, in userimage_addr_range return self._get_addr_range(u"userimage") File "c:\python38\lib\site-packages\tinyprog\__init__.py", line 188, in _get_addr_range addr_str = self.root[u"bootmeta"][u"addrmap"][name] TypeError: 'int' object is not subscriptable
Running “tinyprog -b” works correctly and causes my last programmed image to start up and fucntion correctly.
Any ideas? This issue does seem similar to TinyFPGA-BX Won't Program Anymore from 2 years ago, but I was hesitant to start hacking around with that.