FAQ:"Bricked" LokSound Decoder
| See more FAQs | |
|---|---|
| General information | |
| DCC Categories | Multifunction Decoder |
| Related Articles: | |
| Manufacturers | |
Bricked refers to an incident occurring during the software update of an electronic device, rendering it unresponsive.
After updating the firmware in a LokSound decoder using the LokProgrammer, the decoder may be unresponsive. It is possible some Configuration Variables have been altered.
- Before allowing a firmware update, read and save the decoder configuration to your computer.
- Upon completion of the firmware update write the saved configuration back to the decoder.
There is a possibility when the firmware update was performed some CVs were changed and those have now become the defaults. A reset will not fix that.
Recovering a Bricked Decoder
In some cases the decoder will require return to the manufacturer for reformatting.
- The following suggestions are not guaranteed to work.
Firmware Reload
Before making plans to return the decoder, attempt to reload/update the decoder's firmware. Several attempts may be required. If successful, the next step would be to reload the sound project.
Firmware Downgrade
Another method would be to attempt to load an older version of the firmware. Sometimes the LokProgrammer will refuse to update the firmware, stating it is the current version.
Downgrading is done using an older version of the LokProgrammer software. If successful it will downgrade the firmware on the decoder. It can then be updated to the current firmware using a newer version of the LokProgrammer software
Decoder Swap
Sometimes the decoder does not acknowledge the LokProgrammer, which is the root of the issue.
Using an identical decoder, let the LokProgrammer initialize using it, then swap the new decoder for the faulty one. This will fool the LokProgrammer, getting around the issue of the decoder not being recognized.
Additional Resources
See the LokProgrammer page for more details and videos regarding its usage.