I called SystemUpdate.AccessBootloader() on the EMX module while running from the VS2010 debugger.
This seems to have completely ruined my EMX module.
I was able to ping the EMX module in MFDeploy, but VS Studio constantly reports “an error occurred please check your hardware”
I booted into the GHI Bootloader and re-transmitted the TinyBooter.GHI, them with MFDeploy all the CLR.hex, CLR2.hex, and Config.hex files, but VS2010 still reported the “please check your hardware” message even though MFDeploy could ping the module.
I just repeated this process now and can’t even get into the GHI Bootloader to respond (pressing Up/Dn/Select + Reset or sending % over COM1) by any means.
Any ideas how to recover the EMX module?
I had been able to call PowerState.RebootDevice(true) in the debugger and although I couldn’t trace from the beginning of the reboot process, the debugger did seem to “re-attach” to the process after 30 seconds or so, so I thought it’d work for AccessBootloader() also.
Since I’d like to eventually get the in-field update working, for future reference, is it a bad idea to call SystemUpdate.AccessBootloader() while running in the debugger?