Firmware Update Error with FTDI

After a lot of work to get the FTDI to actually work ( OSX drivers need uninstalled and updated in 10.10 for anyone who has issues ) I now have a more fatal error. Which has killed my tides!

Write 256 bytes at 0x8001A00
Traceback (most recent call last):
File “stmlib/programming/serial/stm32loader.py”, line 428, in
cmd.writeMemory(conf[‘address’], data)
File “stmlib/programming/serial/stm32loader.py”, line 307, in writeMemory
self.cmdWriteMemory(addr, data[offs:offs+256])
File “stmlib/programming/serial/stm32loader.py”, line 188, in cmdWriteMemory
self._wait_for_ack(“0x31 programming failed”)
File “stmlib/programming/serial/stm32loader.py”, line 69, in _wait_for_ack
raise CmdException(“No response to s” info)
main.CmdException: No response to 0x31 programming failed

Is there any way to slow the transfer? This unit’s been a total pain in a#!e for firmware. Audio’s never worked from the off, but now nothing does :frowning:

No idea which module it is. Certainly not a Shruthi :slight_smile:

Sorry it’s a tides, the one that I’ve posted before about in the past… thankfully it seems like there’s a few threads like this on muffs with people having the same issue and it suggested trying the audio update. I did and finally I have sheep on it So I can safely say, it’s fixed in a weird and long chain manner.

However, it does seem like this is an issue that is occurring more often with the ftdi interfaces in the vagrant environment. Possibly something to do with the VB usb? Not throttling or adhering to the rates required?

Anyway … I’ve got a bootloader and wavetables and a big big smile :smiley: