Group Actions
Engagement
  • Author Author: Fred27
  • Date Created: Date Created
  • Views 731 views
  • Likes 9 likes
  • Comments 1 comment
Related
Recommended

Sample code for using OLED-C with Azure Sphere

Fred27

I've managed to get the OLED-C Click board working with the Avnet Azure Sphere Starter Kit. It will work with the OLED-C in mikroBUS #1 or with a few changes in a header file it will work in mikroBUS #2. I would include a photo, but it seems that the display and my smartphone camera do not get along!

https://github.com/FredMurphy/AzureSphereOLEDC

 

There were a few bumps along the way - not least the fact that there are 2 versions of the board that use completely different drivers. This is for the v1.01 which uses the SSD1351 driver. The initial documentation I found was for the v1.00 using the SEPS114A and I initially went off on a dead end with that! It's basically a port of the Libstock code supplied by MikroElectronica, alhough the SPI and GPIO configuration is done a little differently.

 

Let me know if you find it helpful.

  • It turns out that the Click OLED-C board uses pin 2 of the mikroBUS socket as its enable pin. Nothing wrong with that. It's connected to GPIO2 on the MT3620 and it works just fine. However, it seems that both mikroBUS sockets on the Avnet Azure Sphere Starter Kit share GPIO2 in this position.

     

    This means that any other Click board that uses pin 2 may not play nicely with the OLED-C. I've got a few other Click boards and this is what I found:

        Heart Rate 4 - this uses pins 2 as to signal data is ready to be read over I2C. You can't use it alongside to the OLED-C

        NFC click - this also uses pin 2 as an interrupt. It won't play nicely.

        OLED-B - This is OK, but I'm not sure why you'd want 2 OLED displays.

     

    I'm not going to go through the range of Click board and work them all out, but beware of any that use pin 2 - the second one down from the top on the right hand side. If there's consistency between boards then I'd hazard a guess it's any that use I2C.