It appears there’s something in the HD44780 PrintString() that is causing a corruption of the TinyBooter and/or firmware on my Cerberus. Before I remembered the SetCursur(), I attempted to use “\n\r” notation to get to a new line. What I discovered is that if you send either of these escaped characters to PrintString() then it will corrupt your firmware. I’ve tried just doing an erase from MFDeploy and MFDeploy no longer recognizes the Cerberus once this code has been executed. I can reproduce this 100% of the time.
display.PrintString(_displayLine + "\r" + _displayLine);
I don’t think it matters what _displayLine[n] values are but in my test they were…
_displayLine = “Good morning!”
_displayLine = “”
It would be nice to harden the driver a bit to handle this better.