All ePMP radios, except the Connectorized Radios with Sync, have a single flash bank. There is a high probability that the flash bank can get corrupted when power to the radio is interrupted during a flash write, i.e. software upgrade. This is not an issue with the Sync radio since there are two flash banks in them – one active and the other inactive. The inactive bank will take over if the active bank is corrupted.
Beginning with Release 2.6.2, it is now possible to recover an ePMP radio’s corrupted flash. In order to perform the recovery, the ePMP radio MUST be running Release 2.6.2 or newer. Recovery is not supported on devices running earlier releases or on Connectorized Radio with Sync (GPS radios).
To perform the recovery procedure, the following is needed:
- ePMP radio (non-GPS radio) with corrupted flash, i.e. there was a power interruption during a software upgrade and the device is no longer accessible or boots up.
- The ePMP radio must have already been running Release 2.6.2 (or newer).
- Laptop or PC with a 3rd party TFTP server (ex: Free TFTP server for Windows)
- Connect the PC/Laptop to the ePMP device (non-GPS radio).
- The PC/Laptop must be deployed in the same network as the ePMP device.
- TFTP Server IP address must be set to 192.168.1.10/255.255.255.0.
- Extract the ePMP recovery image (firmware.bin) from the ePMP software bundle (ePMP-NonGPS_Synced-v2.6.2.tar.gz) and place it in the TFTP Server’s root directory.
- Reboot the ePMP device.
- After successful boot-up, the ePMP device will perform the recovery procedure. The procedure will take approximately 5 minutes. Once done, the ePMP device will reboot automatically.
- After boot-up, the ePMP device will be accessible using the last configured IP address or default local IP of 192.168.0.2 or the fallback IP of 169.254.1.1.
- IMPORTANT: Software Upgrade through the GUI must be performed one more time for successful recovery in order to reflash broken image.
NOTE: This recovery procedure will work in cases where the u-boot of the radio is intact. In rare cases where the u-boot may also be corrupted, recovery is not possible.