In the February 22 release we got ESP-IDF framework updated to 3.1.3.
Is it safe to assume that the issue found with the GPIO is fixed now and I don’t have to go look around for tools/sdk/ld/esp32.peripherals.ld and modify the aforementioned values ?
Or do I still have to get in there and change those values ?
The workaround seems to be to write to the different series of addresses, if the issue wasn’t resolved in your ESP32’s silicon revision. I can’t comment as to whether the issue is fixed or not, or still relevant.
However, the path to tools/sdk/ld/esp32.peripherals.ld using your platformio.ini config on windows is (just add %localappdata%\.platformio\packages\framework-arduinoespressif32 to what you had before):
I don’t know if the issue was resolved. Also I am using Linux and I have a hard time finding .platformio\packages\framework-arduinoespressif32\tools\sdk\ld\esp32.peripherals.ld
On Linux, you’ll want the ~/.platformio/packages/framework-arduinoespressif32/tools/sdk/ld folder… Sorry, for some reason I thought you were on Windows so gave you the Windows-style path…
If I’m reading the errata right, the fix would mean that this workaround would not need to be applied… but it is board specific because it is a update to the actual processor revision.
I really don’t know which revision I have.
I found PROVIDE ( GPIO = 0x3ff44000 ); and I thought that the correct value should be PROVIDE ( GPIO = 0x60004000 ); and so I changed it accordingly.
You can follow this if you want to find out which revision you have … 0, or 1… but if you need that workaround, it’s most likely you have revision 0.