
Chapter 35 File Manager
NXC CLI Reference Guide
231
35.8 Notification of a Damaged Recovery Image or Firmware
The NXC’s recovery image and/or firmware could be damaged, for example by the power
going off during a firmware upgrade. This section describes how the NXC notifies you of a
damaged recovery image or firmware file. Use this section if your device has stopped
responding for an extended period of time and you cannot access or ping it. Note that the NXC
does not respond while starting up. It takes less than five minutes to start up with the default
configuration, but the start up time increases with the complexity of your configuration.
1 Use a console cable and connect to the NXC via a terminal emulation program (such as
HyperTerminal). Your console session displays the NXC’s startup messages. If you
cannot see any messages, check the terminal emulation program’s settings (see Section
1.2.1 on page 16) and restart the NXC.
2 The system startup messages display followed by “Press any key to enter debug mode
within 3 seconds.”
Do not press any keys at this point. Wait to see what displays next.
Figure 21 System Startup Stopped
3 If the console session displays “Invalid Firmware”, or “Invalid Recovery Image”, or the
console freezes at "Press any key to enter debug mode within 3 seconds" for more than
one minute, go to Section 35.9 on page 232 to restore the recovery image.
Figure 22 Recovery Image Damaged
4 If “Connect a computer to port 1 and FTP to 192.168.1.1 to upload the new file”
displays on the screen, the firmware file is damaged. Use the procedure in Section 35.10
on page 234 to restore it. If the message does not display, the firmware is OK and you do
not need to use the firmware recovery procedure.
Komentarze do niniejszej Instrukcji