Update:

I started the upgrade to the newest version of the SDK.

Process:

Upgrading went pretty smoothly.  I had previously downloaded the newest SDK. So I made sure there wasn’t a newer version.  Next I extracted the SDK folder from the downloaded zip file.  I renamed the old folder to indicate it’s version number. I renamed the new SDK folder to Uprogrammer. I copied the code folder (Uprogrammer Firmware) from the old SDK folder into this new one.

Then I compiled (Success), Uploaded (also success after I copied esptools folder), and interacted with the application over serial (again success). Everything seemed to be going great.

Then I opened Eclipse… It didn’t find the project.  So I set my file manager to show hidden files.  I noticed the .metadata folder was not in the new directory. I copied it and still no joy.  I did this for all of the hidden files and it still didn’t work.  I then realized I must not have gotten the spelling of my folder correct.  I checked, the ‘p’ in the folder name needed to be capitalized.

Finally, I checked Git-Cola to see if it worked correctly.  It came up and showed me a bunch of untracked files that were generated by the build I had just done (another success).

This was a very easy upgrade.

The request:

I am not satisfied with the ADC implementation in the SDK.  Also, there is no documentation that I could find to control the ADC directly.  I suspect the WiFi engine needs to have full control of the ADC to work correctly.

I registered with Espressif forums. Then I went to the Report Bugs area.  I searched the forums for ADC to see what I could find.  I found lots of posts about the ADC, but most were complaining about it’s accuracy when the modem is active.  I wrote my own post requesting a new way to access the ADC.  I will post a link to it  in the comments when it becomes available on the forum.

No change to the firmware this week.

The Side Project:

I haven’t had time to work on the Arduino compass I mentioned a few weeks ago.  I hope to design a small test PCB this week for the Display.  I have very little information on the OLED display.  The pin pitch of the flex cable is not specified from the vendor, the manufacturer is Ritdisplay, but the part number isn’t listed on their website.  I measured from the center of Pin 1 to Pin 27 and found 21 mm.  Since that represents 26 spaces, I divided the 21 by 26 and go 0.81mm pin pitch.  0.8mm is a common pitch used in electronics So that is what I will try first.

Your Feedback:

Have you had a similar experience changing to a new version of a SDK?  How about horror Stories? Is there something you would like me to discuss on this blog?