-
Notifications
You must be signed in to change notification settings - Fork 7.7k
Description
Board
ESP32 Dev Module
Device Description
ESP32 Development board (ESP WROOM 32)
Installed board support Arduino IDE: esp32 by Espressif Systems version 3.3.0-alpha1
Hardware Configuration
Yes, a variable resistor to pin 34
Version
latest stable Release (if not listed below)
IDE Name
Arduino IDE
Operating System
Win10
Flash frequency
80
PSRAM enabled
no
Upload speed
921600
Description
Running the example https://github.com/espressif/arduino-esp32/blob/master/libraries/ESP32/examples/AnalogReadContinuous/AnalogReadContinuous.ino works, but gives the following errors:
E (12579) adc_cali: adc_cali_raw_to_voltage(41): invalid argument: null pointer
E (12579) adc_cali: adc_cali_raw_to_voltage(41): invalid argument: null pointer
E (12582) adc_cali: adc_cali_raw_to_voltage(41): invalid argument: null pointer
E (12589) adc_cali: adc_cali_raw_to_voltage(41): invalid argument: null pointer
The errors are a pain, since they mess up the serial monitor with tons of error messages when reading results in continous mode using analogContinuousRead. This basically renders the serial monitor useless for other debugging purposes.
Since the errors cannot be supressed by the chosen debug level in the IDE, it is a blocker for me.
Sketch
See your own code: https://github.com/espressif/arduino-esp32/blob/master/libraries/ESP32/examples/AnalogReadContinuous/AnalogReadContinuous.ino
Debug Message
E (12579) adc_cali: adc_cali_raw_to_voltage(41): invalid argument: null pointer
E (12579) adc_cali: adc_cali_raw_to_voltage(41): invalid argument: null pointer
E (12582) adc_cali: adc_cali_raw_to_voltage(41): invalid argument: null pointer
E (12589) adc_cali: adc_cali_raw_to_voltage(41): invalid argument: null pointer
Other Steps to Reproduce
Even commenting out "analogContinuousStop(); ... Serial.println ... analogContinousStart()" in loop() does not make a difference: The error seems to be caused by analogContinuousRead solely..
I have checked existing issues, online documentation and the Troubleshooting Guide
- I confirm I have checked existing issues, online documentation and Troubleshooting guide.To pick up a draggable item, press the space bar. While dragging, use the arrow keys to move the item. Press space again to drop the item in its new position, or press escape to cancel.
Activity
PaulChristopher commentedon May 25, 2025
Workaround: In C:\Users\XXX\AppData\Local\Arduino15\packages\esp32\hardware\esp32\3.3.0-alpha1\cores\esp32\esp32-hal-adc.c, function AnalogContinousRead comment out the call of adc_cali_raw_to_voltage (line 629) and work with raw values only.
lbernstone commentedon May 25, 2025
I'm not using the packaged 3.3.0, but current master is not giving me this error. Did you try changing the adc_pins[] line to just have pin 34 in the list?
PaulChristopher commentedon May 26, 2025
Yes, I tried to use pin 34 only. It gives me the same error. The error occurs for each pin - it does not matter, whether something is connected to the pin or not. It is a software issue, since something in adc_cali_raw_to_voltage is considered as a null pointer...
PaulChristopher commentedon May 26, 2025
Steps to reproduce the issue:
-Dowload Arduino legacy IDE https://downloads.arduino.cc/arduino-1.8.19-windows.exe and install it.
-Run the IDE, choose "Tools > Board > Boards Manager…". Search for esp32 by Espressif Systems, choose 3.2.0, and install it.
-Close and restart IDE
-Choose "Tools > Board > ESP32 Arduino > ESP32 Dev Module. Connect the devboard and make sure the correct port is selected using "Tools > Port > COM??"
In the output, you see the above mentioned errors:
P-R-O-C-H-Y commentedon May 27, 2025
@PaulChristopher Will test and reach back.
P-R-O-C-H-Y commentedon Jun 10, 2025
Hi @PaulChristopher I did test on 3.2.0 and also 3.3.0-alpha1 and both versions works for me. tested on ESP32-WROOM
PaulChristopher commentedon Jun 10, 2025
Thanks your testing and having a look at it! If you cannot reproduce the issue, let's close it!? I does not work for me, but I have found a workaround as described above. It is now documented in the bug tracker and other people might reopen this issue in future.
Thanks and all the best!
Paul