OLED!!!

Hey all,

Having seen a nice-looking teensy OLED display (0.96”) somewhere, I decided to get one too, so I ordered an SPI version off of Electrodragon (no, I am not marketing for them). The instructions on their Wiki were somewhat vague, so I decided to post a short version here for whom it may concern:

1) The modules are apparently 5V-tolerant and are rated to work between 2.7V to 5.5V, so I’m figuring you can use this with a Pi/other SBC as well.

2) The line called “D0” is actually the SPI SCK line, which for hardware SPI on the Arduino Uno is Pin 13

3) The line called “D1” is actually the SPI MOSI line, which for hardware SPI on the Arduino Uno is Pin 11

4) The other lines (RES, DC and CS) can be assigned arbitrarily and specified in the sketch.

To actually drive the display, I used the Adafruit_SSD1306 library (which depends on the Adafruit_GFX library) so you’ll want to grab those using the Arduino IDE library manager (which is really nifty actually). Once that’s done, you’ll want to run one of the provided example sketches.

I followed the wiring given at the top of the ssd1306_128x64_spi example and tried to upload that, then got some error about having to fix the Adafruit_SSD1306.h file – that’s expected if you have a 128x64 OLED, so you’ll need to find the file (it should be in your “libraries” folder in your sketch directory i.e

<sketch directory>/libraries/Adafruit_SSD1306/Adafruit_SSD1306.h

And comment/uncomment the appropriate #define for your particular OLED. Once that was done, I hit the “Upload” button and it worked!

But I wasn’t satisfied. Because I wanted to get it working with hardware SPI instead.

So I followed the instructions in the example sketch once again, but simply adjusted the wiring for D0 and D1 as described above, and since the other pins were specified in the sketch nothing else was needed. Uploaded that and it worked equally as well.

Happy OLEDing!

Comments

Post a Comment

Popular posts from this blog

Bitbanging SPI on the Raspberry Pi (via spi-gpio)

Image
Hello all and happy holidays to everyone! I’m taking a break off work for the holidays so I have a little bit of time on my hands. I will therefore regale you with tales of my exploits! From my last post, I talked about the somewhat “edge” case where you’d want to add (cheap) Ethernet to a Raspberry Pi, probably the A+ or Zero as the case may be. I haven’t figured out the fixed MAC thing just yet, but I’m working on it. Anyways, after some time, another edge-edge case came to me: The ENC28J60 takes up the only SPI peripheral available on the Pi, so what if you needed to use both the ENC28J60 AND some other SPI device? The Pi’s SPI peripheral has two chip selects, so it is theoretically possible to use the exact same bus while using the first chip select for the ENC28J60 (which it uses by default) and using the second chip select for the other device. However, it goes without saying that network communications require some serious computing firepower so it might cause a bit of a perfo
Read more

Getting Started with Logic Analyzers and Pulseview

Image
Hey all, Been a while. Hope you’ve been up to no good, hm? A couple of days ago, I had to do some low-level I2C work on a bare-metal ATMega328P. Digging out the datasheet, I cobbled a simple I2C driver together, the purpose of which was to permit me write a driver for the particular peripheral which would call the lower-level functions the driver provided (i.e things like i2c_start(), i2c_stop(), i2c_address(), etc etc). When I finished the I2C driver, I tested it out with an MMA8452Q I had lying about and it seemed to work just fine. Believing everything to be dandy, I went ahead and wrote the peripheral driver for the component I was working with. And that was when the funny stuff started. To cut that long story short, it wouldn’t work right when deployed to the hardware. At all. I was in a bit of a bind – the code looked great, no errors no nothing, so it was time to look at the hardware/wire-level end of things. Logic analyzers (in my limited understanding) are tools/instrume
Read more

Enabling SPI1 on the Raspberry Pi B+/Zero/2/3

Image
Me hearties, Let us plunder and pil.. Sorry, wrong blog. Ahem. Hey all, Its been a while. Been busy at work as usual, and haven’t really had much time to write much. As penance, I will post not one but two updates! This particular post is in relation to Raspberry Pi users specifically. I had earlier talked about the vagaries involved in emulating SPI over GPIO in order to get an additional SPI peripheral. It was a moderately involved process, but the rewards were great With the most recent release of the Raspbian Jessie distribution (2016-05-10), a number of improvements have been made to both the desktop parts and the “under-the-hood” parts, perhaps most significantly the kernel. This new release uses Kernel version 4.4, which now adds the ability to use the second hardware SPI peripheral, SPI1, on the Raspberry Pi. This is only available to devices with the 40-pin header (as seen from the title of this post) so users of the original model A and B will probably need to turn to
Read more