Show Posts
1
OLEDs / Re: damage from reversed power supply?
« on: December 30, 2014, 06:52:28 AM »
I tried implementing the example code Michael has posted on the forum but these displays seem to be very sensitive to timing and the platforms he develops on seem to have the timing characteristics necessary to make the displays work. They haven't worked for me.
After quite a bit of trial and error I've gotten this display to work in the default parallel 6800 mode and I've attached a logic analyzer capture file showing signal timing that works to initialize the display and write "Hello" in the middle of the second line of the display. This file was captured with the Saleae Logic 1.1.34 Beta, which can be downloaded from the Saleae website (http://support.saleae.com/hc/en-us/articles/201589175). I've had to rename it with a .jpg extension to get the forum software to accept it. Change it to .logicdata to open it.
You'll notice there is no checking of the busy flag. I tried but was not able to work out whatever timing is necessary to get a response from the display. This works without it and unless I run into problems I'm sticking with it.
You'll also notice this allows a lot of time between writes (~1.2 ms). I'm using the same delay for all commands, so it's likely these times can be shortened for everything except Clear Display. It's mainly good to know I have a working display.
[attachment deleted by admin]
After quite a bit of trial and error I've gotten this display to work in the default parallel 6800 mode and I've attached a logic analyzer capture file showing signal timing that works to initialize the display and write "Hello" in the middle of the second line of the display. This file was captured with the Saleae Logic 1.1.34 Beta, which can be downloaded from the Saleae website (http://support.saleae.com/hc/en-us/articles/201589175). I've had to rename it with a .jpg extension to get the forum software to accept it. Change it to .logicdata to open it.
You'll notice there is no checking of the busy flag. I tried but was not able to work out whatever timing is necessary to get a response from the display. This works without it and unless I run into problems I'm sticking with it.
You'll also notice this allows a lot of time between writes (~1.2 ms). I'm using the same delay for all commands, so it's likely these times can be shortened for everything except Clear Display. It's mainly good to know I have a working display.
[attachment deleted by admin]