I still haven’t gotten the OLED display working. I am beginning to question Pinouts and even if the driver IC listed by the seller(s) is correct. At this point I can’t even tell if the device is seeing my commands. I checked the board for shorts/solder bridges and even replaced the OLED display. I still can’t get anything to show up on the display.
I think a reasonable test would be to measure current to the display and send it a power on command. If I am sending commands correctly, I should see a change in current draw. After that, I will try working through the commands available in the datasheet for a SSD1332 chip looking for a change in the display or the current draw.
Just like refactoring the code, It’s time to refactor the electronics design. I checked on my feature request on the Espressif forum. Nothing new has happened. So I am considering adding an external ADC to measure voltages.
Planning and Research:
No new information on the ADC feature request on Espressif”s forums.
I have started layout of the SSD1332 Breakout PCB. I finished the layout and ordered PCBs from OSHPark. Based on the datasheet for the SSD1332, I can get significantly better performance by using it in one of the 8 bit bus modes. Someone suggested that I look at STM32 processors to drive the display with. I will be considering that option this week.
I decided that the code that interacts directly with the hardware registers can’t be rewritten to be much clearer to read. There should be a lot of commenting in the code explaining why the registers need to be set that way. That is a big project and since I didn’t write most of that code, I don’t understand a lot of it. I am choosing this week to just make sure this code is formatted in the Allman style and leave commenting for later.
I have now worked through all the .c and .h files in the project to made sure they are formatted in the Allman style. I decided to go back through all the names used for variables, functions, constants, and macros and format them all the same. Since Espressif named all the system calls in lowercase underscore separated, system calls will follow that format.
The rest of the naming I decided as follows:
Macro: All caps with underscore separation followed by ()
Constant: All caps with underscore separation
Variable: Lower camel case
Non System functions: lower camel case with ()
I used Eclipse’ refactor feature to make these changes to all the files at once.
I had a couple of .h files that didn’t refactor correctly, but once i got those fixed, the code compiled and ran just like before.
The firmware is getting easier to maintain and edit. I hope to move forward with the electronics design again soon. I bought and received a new mixed signal oscilloscope and received it this last week, I plan on doing a review of it next week. I have uploaded these changes to Github, click the link in the right hand column to get the firmware source.
Have you used Eclipse’ refactor function before? Did you have similar problems?