Being able to recover your device is an important part of the development process. The MODM7AE70 has multiple paths to recovery, depending on the state of the device at any given time. Below, we cover the to main paths to recovery for devices that are stuck in a trapping loop, or are completely unresponsive.
For devices that are trapping repeatedly, the easiest method of recovery is to load a new program onto the module. In order to do this, it will be necessary to stop the device from running the user's application. We can accomplish this by interupting the application from executing right after the config server has started. From here, a new application can be uploaded through the config page on the browser, or through a serial terminal.
To prevent the user's application from running, and instead stop right after the configuration server has been started follow the steps below:
Type "A" to Abort boot
is displayed.>
prompt to display.At this point, you can either load the application through a browser from the configuration page (located at <device ip>="">:20034), or through a serial terminal, such as MTTTY. The steps below outline how to load an application from a MTTTY serial terminal.
>
prompt, type fla
into the serial prompt and then hit enter.F5
..bin
application file that you want to load.In a situation where the module becomes completely unresponsive, such as when the device is unable to boot properly, you will want to force the device into a default, recoverable state. The MODM7AE70 is able to do this by completely errasing the flash memory, and then loading a very small, internally stored factory application onto the device. This process is started by using the module's recover jumper. The steps to do this are listed below.
The boot jumper is a pair of circular pads located near the middle line of the board near the connector.