Screen gone Black after Firmware Update - Solved

[Jesse Johannesen]

Hi, I ran into the same problem. Tried installing firmware 1.1.063 using teensy on Mac OSX with a USB connection.

First I got the message in teensy that the hex file was too large and I followed the instructions on the firmware installation webpage, and clicked on the Auto button and then the FW button. It ran for a brief instant and then teensy hung with a line at the bottom that says 79% used.

The NDLR has now gone black and cannot restart (tried the Shift-Menu held down and reboot method but didn't work also). I deleted and re-installed teensy hoping to reload the hex file and re-try but teensy still has the 79% used text at the bottom each time it is opened and after reloading the hex file.

Is there any way I can revive the NDLR? Any advice will be much appreciated by this fragile soul.

Thanks.

Hi browndwarf, I'll see if I can offer you some assistance with this. Good news, the 79% is just showing how much of the total space the hex file will take up on the device, so it's not a progress indicator.
Ok, now to get it working! The first thing I recommend is lets download the firmware again just in case there was an issue with that, then open that in the Teensy loader. Connect the NDLR to the computer via USB, be sure to press the small button inset in the case between the MIDI din connectors, this will reset the NDLR into bootloading mode at which point the screen will be black, but the Teensy loader should recognize The NDLR at this point and stop prompting you to press the button, and show new options available which were greyed out before.

At this point if all went well we should be able to load the newly downloaded firmware hex file, press program (curved green arrow), and get our progress bar. Once  finished it says "programming complete", but the screen remains black. at this point the green arrow next to the program button will reboot the device, and the programmer should say "reboot OK", and the screen should light up.
If this doesn't work, the next thing I would do is attempt the same process on another computer if that is a possibility.

Let me know if any of these solve our problem, and I will reach out to the rest of the team.
Jesse