Follow

What can we do if a device is in bootloader mode?

While an SSI device that is blinking a “Bootloader status” error code is bricked and must be replaced, that is not necessarily true of nLight devices.  Using SensorView to attempt a firmware update to the device may result in good success.

Example with an nPP16: Intentionally disconnecting the Cat5 cable in the middle of a firmware update resulted in the SensorView message below.

1b_disconnected_cat5_during_fw_update.jpg

2_reports_the_failed_update.jpg

 

MOVE AWAY FROM THE UPDATES TAB AND THEN BACK TO IT, WE SEE THE DEVICE SHOWING THIS STATUS

3B_refresh_UPDATES_tab_and_view_device_status.jpg

Meanwhile the LED’s of the device itself are blinking as seen in the attached video (not a slow-steady blink in this case).

Proceed with another attempt at updating the device firmware and observe if firmware update process this time completes with success.

4b_subsequent_fw_update.jpg

5_reported_completion.jpg

 

6b_reported_completion_b.jpg

If the subsequent attempt(s) at updating firmware fail(s), then consider troubleshooting the Zone(s) the devices are in.  If the databus on a daisy-chain of Cat5 cable is noisy or has frequent corrupt messages, that condition may prevent successful firmware updates.  Troubleshoot the Cat 5 with Bus-Splitting similar to what is done when there are comm errors.

 

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request