I’m getting this message when I boot EMX module:
EMX TinyBooter Mode Version: 184.108.40.206 Debug: COM1 LCD: 320x240 IP: 0.0.0.0 MAC: 00.00.00.00.00.00 Managed heap size: 1048580 Custom heap size: 0 TinyBooter v4.1.2821.0 EMX Build Date: Jun 30 2011 11:00:00 ARM Compiler version 410561 MSdbgV1O© Ô@ *** nXIP Program found at 0x00004000
I booted into the “Emergency Bootloader” but I’m still getting the error after resending TinyBooter.GHI. What’s the problem here and how to fix?
Force Boot Loader detected GHI loader commands are now active BL BL 1.02 BL Erase all memory! Are you sure? BL X11 BL Start File Transfer CCCCCCCCCCCCCCCCCCC File Transfer Finished Successfully EMX TinyBooter Mode Version: 220.127.116.11 Debug: COM1 LCD: 320x240 IP: 0.0.0.0 MAC: 00.00.00.00.00.00 Managed heap size: 1048580 Custom heap size: 0 TinyBooter v4.1.2821.0 EMX Build Date: Jun 30 2011 11:00:00 ARM Compiler version 410561 MSdbgV1z^ü¢a2**** nXIP Program found at 0x00004000
I’d like to point out that I didn’t do anything extraordinarily unusual here. I am turning up a set of new boards for a small production run and the previous board with EMX module was just fine.
The steps I followed were to deploy CLR, CLR2, Config - that worked fine - and then followed by deploying my application. Deploying my application resulted in an error message “check signature failed” after which the module went into this mode that I can’t seem to recover by redeploying TinyBooter.GHI.
This is the first time I tried to deploy my application using a file created with application deployment rather than using Studio to deploy. This is going to be important as I can’t have my production guys hitting F5 on Studio to deploy firmware.
I should point out that the deployment file was created with the exact same board previously turned up that is working great.
Any suggestions or ideas here on how to prevent this from happening again and/or recover from this state?