Some code was built and deployed that had a serious bug, the Raptor is now inaccessible via USB and reboots continually.
MFDeploy seems to try to talk to the device but cannot because once it reboots it behaves well for a seond or two then crashes again before MFDeploy can get much info, no hope of erasing the app this way.
I next ran FEZ Config and this too is transiently able to “see” the board but it becomes inaccessible shortly after every reboot, its rebooting over and over.
I have the LCD attached so can see what’s it doing:
It reboots:
G400
Version 4.3.6.0
Debug: USB
LCD: 480x272
After 1 or secs it crashes with:
[b]ABORT Data
Build Date:
Oct 21 2014
13:05:18
cps=
pc=
lr=
sp=[/b]
After about 15 seconds it repeats.
The image show FEZ Config, the device gets reset and I press ‘Check for device update’ over and over rapidly, as you can see there’s a brief interval where FEZ Config successfully communicates then the device crashes.
I’d like to know the exact steps to take next in order to reload whatever needs to be reloaded!
Frustrated because I’ve just started a short vacation and had planned to spend quite a bit of time learning more of Gadgeteer and .Net MF!
Please Help !!
Korp.
PS: Because the device briefly communicates this suggest that an enhancement could be made in which we ask FEZ Config to freeze the loading of apps after reboot, that is FEZ Config could assert some flag/value etc and as the device reboots it checks/looks for this flag/value - like saying “Hey, I know your rebooting but DONT go any further” with the device saying “OK I’m rebooting, first let me see if FEZ Config is alerting me”.
Perhaps this could be a FEZ Config button “Intercept on reboot” or something…