I posted the below on the announcements page, but think its better suited to here:
I am trying the new code, but my FiPy is constantly rebooting with trace errors. I have tried to update/change the firmware on both Windows and Mac, but having the same issue once I have had sucess..
Here's the output from the logs:
I had to revert to using a USB CP2102 module as I couldn't get the tool to work with a PyTrack Module and the two PINs connected.
Is there a way I can flash an older version of code just to rule out the device? Also, is there a way to "reset" the firmware updater software as it could have been that I selected the wrong board when updating.*
Just updated to latest version and exactly the same issue again...
I tried the new version, but still getting the same issues:
I decided to wait for the latest SW rather than downgrade, so maybe a downgrade is the next step.
Is anyone else seeing this issue?
robert-hh last edited by
@pymiom There are quite a few discussion around on this board. There is a hint about downgrading here https://forum.pycom.io/topic/517/downgrading-firmware-advanced-users/17, using the basic tools. Erasing flash always brings you back to the start, but that is to be taken with care, since also erase registering information.