@ MRTFEREN this produces the same problem as a reboot.
@ Mike clearing the display is the first thing that I do when the program starts. Can I do it earlier than that?
@ Architect the display is connected to gadgeteer socket 3 and I’m using SDK 4.2. I should probably add that my application is NETMF, not gadgeteer. However, I have some applications where the display is working fine all the time and, in the current project that I am working on, I am not doing anything differently.
Also, I have tried re-flashing tinybooter and the firmware.
I just don’t understand what is different between sending the application to the Bee during debugging and rebooting/resetting the Bee! :wall:
I’m not particularly happy with this though as it adds another 10ms to the process of displaying something which could be bad for this particular application. In fact it is 20ms to use both lines of the display. Fortunately, no delay is needed for the Putc method.
Also, I still don’t get why this application needs this at as none of my other apps do.
So all of this leads me to ask if anyone knows of a display that is faster and doesn’t have issues like this?