Side Project:
I got the parts to build the OLED breakout PCB this week. I got them assembled and connected to my test STM32 Arduino device. Unfortunately, I didn’t get anything to show up on the display. I did measure the 13.8 volts on the high voltage part of the circuit. (I wasn’t sure if the inductor I chose for this voltage could handle the current. I am still not sure)
The STM board got hot quickly when trying to drive the OLED. This leads me to believe that the OLED is drawing too much current. I expect this display to work as well as the test display I have been using. It should draw about the same amount of current. My first guess is I have a solder bridge somewhere on the PCB.
Research:
I created a C project with multiple files and it worked without any problems. So I did a little research and found that when I add C into a C++ project I need to tell the compiler which functions are written in C. I found that I can wrap the #include in an extern “C”{} declaration.
Still Looking for a Fail:
Once I figured out how to make the new file I had created link. I re-created the CUTE tutorial project. I made sure it would run and test as expected and then re-created my clearFrameBuffer() function in it’s own file FrameBuffer.c. Before I included the new header file, added a test to verify the value of the function. The test is called testClearFrameBuffer(). This test attempts to call clearFrameBuffer. It fails to build of course because that hasn’t been written yet.
I did a lot of tinkering with the test to make it work right. Mostly I had made some logic errors and fixed them one by one. Now I have a successful test of clearFrameBuffer. I finally have tested and written my clearFrameBuffer function. I made more mistakes in the test code than the functional code.
The Cute tutorial was frustrating. It seems to be out of date. The IDE features don’t seem to work.
Have you used Cute? Have you had the same problems with the IDE? I could use some help with accessing the IDE features, am I trying to use them wrong?