Recovery process:
Re-flashing or recovery can be done if the EP is in recovery mode.
You would need to setup a TFTP server with the the correct IPv6 address.
This package is needed to recover endpoints:
TRIAX have created a Raspberry Pi image, that can be used to recovery update following EoC devices:
- Coax endpoint: EPC1W
- Ethernet endpoint: EPE1W
- EoC controllers: CT32 / CT64 / CT32-B / CT64-B / CT32-MC / CT64-MC
Below folder contains the Raspberry Pi image and a guide, describing how to use the image, and how to determine what state/mode an EPC/EPE is in. Additionally, there is a folder with videos that can be used for reference.
EoC_Troubleshooting_and_Recovery
The Raspberry Pi will run a TFTP server, hosting the images needed for the EPC/EPE and EoC controller.
Mentioned EoC devices will automatically try to download the software from a TFTP, if they are in one of below listed states/modes:
(Use the guide and videos to determine what state/mode the device is in.)
- Software 2.x recovery mode
(Device may enter this mode if power is lost during the software update process. If the device is unable to download the recovery image from the EoC controller, a TFTP server may then be used instead.) - Software 2.x intermediate mode
(This is the transitional state for endpoints when updating from software 1.x/2.x to 3.x. If the endpoint does not automatically complete the update process, while connected to an EoC controller, a TFTP server may be used instead.) - Software 3.x recovery mode
(Device may enter this mode if both software partitions A and B become corrupted. A TFTP server can then be used to recover the device. Note that it is much less likely that a device will enter this mode, compared to the software 2.x recovery mode, i.e. power loss during software update will not make the device enter software 3.x recovery mode.)
Additional Notes on LED Status useful when performing the Recovery Process above:
Signal (G.hn) LED behavior SW 2.x and 3.x:
When power is connected to the EPC, the G.hn Signal LED must light up orange (possibly flash once) and then turn off again. If the EPC is connected to an EoC controller, the G.hn Signal LED must then again shortly after start blinking green/orange/red depending on the G.hn signal quality.
Status LED :
Shortly after the power is connected:
- If the Status LED starts blinking slowly (500ms on/off):
Linux is booting. (normal good scenario)
After a while the Status LED must either
- Turn solid on meaning startup has finished and the devices is running and ready.
- Start blinking fast (100ms on/off) meaning it is either SW updating or re-configuring.
If it keeps blinking slowly, the EP could either be running the 'Intermediate SW' (see further down) or the flash could have "minor" corruption, that would need me to recover it. - If the Status LED turns solid on only after a few seconds:
The EPC is in SW 2.x recovery mode. - If the Status LED stays off:
The main CPU is not running, or flash is severely corrupted,
or for SW 3.x the EPC may be in recovery mode.
Intermediate SW:
The intermediate SW is a special version, automatically installed on the endpoints, during the process of upgrading from SW 2.x to 3.x.
Be aware that if the EPC is running the intermediate SW, the Status LED will keep blinking slowly (500ms on/off) as in scenario A), until it starts updating the SW.