Closed GoogleCodeExporter closed 8 years ago
maybe a hardware issue?
Original comment by olikr...@gmail.com
on 26 Aug 2014 at 5:28
I can rule out hardware as I have a testing board and the display works
fine. I probably haven't interfacing correctly, thank you though.
Original comment by omar.aljadda@gmail.com
on 26 Aug 2014 at 3:55
How did you connect your display? How does your constructor look like? What
exactly do you see?
Original comment by olikr...@gmail.com
on 26 Aug 2014 at 5:06
I connected it as follows as per the data sheet on the link above and got
no output:
(I also have the other pins wired as per datasheet for 4-wire SPI)
OLED PIN -> Arduino PIN
DC - 18 - A0 - 9
CS - 19 - CS - 10
SCLK - 13 - SCK - 13
SDIN - 12 - MOSI - 11
I tried these constructors, is this meant for 4-wire or 3-wire?
//U8GLIB_NHD31OLED_BW u8g(13, 11, 10, 9); // SPI Com: SCK = 13, MOSI = 11,
CS = 10, A0 = 9
//U8GLIB_NHD31OLED_2X_BW u8g(13, 11, 10, 9); // SPI Com: SCK = 13, MOSI =
11, CS = 10, A0 = 9
//U8GLIB_NHD31OLED_GR u8g(13, 11, 10, 9); // SPI Com: SCK = 13, MOSI = 11,
CS = 10, A0 = 9
//U8GLIB_NHD31OLED_2X_GR u8g(13, 11, 10, 9); // SPI Com: SCK = 13, MOSI =
11, CS = 10, A0 = 9
Original comment by omar.aljadda@gmail.com
on 26 Aug 2014 at 5:12
I agree, this looks correct. 4-Wire-Spi include the A0 line. For 3-Wire-Spi, A0
can be ignored.
Did you add proper caps? Unless you use an Arduino Due, do you have properlevel
shifters?
Original comment by olikr...@gmail.com
on 26 Aug 2014 at 6:48
In the display board itself - you need to set the 2 jumpers for your connection.
Those are SMD zero value resistors BS0,BS1. figure out how to set them
correctly.
No need for level shifters - it work fine on 5VDC.
Original comment by raanan.s...@gmail.com
on 27 Nov 2014 at 12:50
I used the display with built in electronics
http://www.buydisplay.com/default/spi-3-2-inch-oled-module-display-256x64-panel-
screen-yellow-on-black
Original comment by raanan.s...@gmail.com
on 27 Nov 2014 at 12:51
no further response... closing
Original comment by olikr...@gmail.com
on 13 Dec 2014 at 5:05
Original issue reported on code.google.com by
omar.aljadda@gmail.com
on 25 Aug 2014 at 10:57