vv222 / u8glib

Automatically exported from code.google.com/p/u8glib
Other
0 stars 0 forks source link

u8g_WriteEscSeqP() not working with USMP-P19801 (SEPS114A) #311

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
Have successfully brought up the SEPS114A by pasting SPI commands into into a 
file named u8g_dev_USMPP19801.cpp with suitable header files. Of course, have 
successfully brought up the display with a simple test sketch as well.

However, running the same initialization sequence through u8g_WriteEscSeqP() is 
not bringing the device up. Oscilloscope tests seem to confirm at least the CS 
pin is toggled during the process, though the timing may be wrong.

This is a rather nice wristwatch-sized full-color OLED module. Would be neat to 
properly support u8glib's fonts and graphics support.

Please examine the following code.

http://pastebin.com/6NLW4hiK

Note the rawDispInit() and dispCommand() functions do work in this context when 
uncommented.

Original issue reported on code.google.com by spamfree...@gmail.com on 20 Jan 2015 at 5:31

GoogleCodeExporter commented 8 years ago
The sequence is empty:
tatic const uint8_t u8g_dev_usmpp19801_init_seq[] PROGMEM = {
        U8G_ESC_END
};
So it will not work. Also such displays (SSD1351) are better supported by 
uCglib.

Original comment by olikr...@gmail.com on 20 Jan 2015 at 5:54

GoogleCodeExporter commented 8 years ago
Thanks for the quick reply!

That sequence is just a commented out empty test sequence. The real sequence is 
above, and uses a preprocessor macro to abstract the comm_write() statements.

Original comment by spamfree...@gmail.com on 20 Jan 2015 at 5:58

GoogleCodeExporter commented 8 years ago
Also, uCglib seems to use very similar constructs to manage displays. Not sure 
I will find it easier to port SEPS114A support there.

Original comment by spamfree...@gmail.com on 20 Jan 2015 at 6:06