RE: Sample code for using OLED-C with Azure Sphere

Fred27 — Thu, 10 Oct 2019 13:09:57 GMT

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.