I had the exact same Error exit code 127 and display of the System32 folder when show logfile was selected. Screenshot 2024-04-25 004535.png Error during this operation: Screenshot 2024-04-25 004621.png Started the installation " esp-idf-tools-setup-online-2.24.exe " again with " Run As Administrato...

In the esp32_technical_reference_manual_en page 384, section 14.2.3 Channels it says LEDC_DUTY_HSCHn[3..0] can be used to dither the output. If this value is non-zero, with a statistical chance of LEDC_DUTY_HSCHn[3..0]/16, the actual PWM pulse will be one cycle longer https://www.espressif.com/sites...

If you are interested in the last output state of a pin you can read from either GPIO_OUT_REG (31..0) or GPIO_OUT1_REG (32..39). To detect if port is input or output you can read the GPIO_ENABLE_REG (31..0) or GPIO_ENABLE1_REG(32..39) If you are sure the direction is not changed outside your control...

The classic delay fix Not ESP32 Arduino code but a hint what is going on With an ESP32 connected as STA if I attempt to close wifi in one fast sequence: esp_wifi_disconnect(); esp_wifi_stop(); esp_wifi_deinit() There are no STA events. If I add 100ms delays between commands when disabling wifi the ...

To show the PWM is not unlinear a 0.5X voltage divider using 220k resistors feeding the ADC input. As seen the lower half scale in Range 3 is pretty straight. And this is also serves as a demonstration of the 12-bit ADC used for 6.4V full scale input, where the ADC does not producing readings >0 unt...

A closer look at the large ADC offsets

About the offset you can see the PWM to DC signal has the ouput at 150 ticks before the ADC Range=3 reading bcomes > 0.

A closer look:

High offset levels needs fixing. The high offset levels of the ADC makes it difficult to read lower voltages. As the ADC lowest range starts from zero at appr 70-100 mV you need external signal conditioning to lift the signal into "view". Also noticed the ADC 12-bit, Range 3 is exremely unlinear. S...

This is strange, because i dont have any issues with disconnecting client from esp32 and reconnecting it using nRF connect or even app written with app inventor 2. Yes I also found it strange and had to peer review myself and found out my app inventor log was wiped on each BLE "devicefound" event. ...

I have identical issue when connecting using the BLE extension in app inventor . It normally works for the BLE devices I have tested from Nordic Semiconductor (nordicsemi) like the nRF52840. Interestingly the nRF Connect for Mobile from nordicsemi is able to connect and disconnect from the ESP32 gat...

I hope some compiler expert will come forward and tell us this was fixed way back in 1972.