ESP32C3-mini-1 problem with strapping pins
Posted: Wed Jul 05, 2023 10:15 am
Hello,
We are using a lot of ESP32C3-mini-1 modules. We used to have modules with Package Code XXN4 but on our latest purchases we have Package Code M4N4. We are noticing that these two batches of mini-1 modules behave differently on boot-up.
We are using USB to connect and flash (Not uart).
We are unable to flash the M4N4 modules unless there is 0V on GPIO2 and GPIO3. If the module is started up with other combinations of
3V and 0V on GPIO 2 and 3 the esptool errors out: "[Errno 71] Protocol error"
(esptool version 4.5.1)
With 0V on GPI0 2 and 3 esptool reports:
"
esptool.py v4.5.1
Serial port /dev/ttyACM0
Connecting...
Detecting chip type... ESP32-C3
Chip is ESP32-C3 (revision v0.4)
Features: WiFi, BLE
Crystal is 40MHz
MAC: XXXXXXXXXXX
Uploading stub...
Running stub...
Stub running...
Warning: ESP32-C3 has no Chip ID. Reading MAC instead.
MAC: XXXXXXXXXXXX
Hard resetting via RTS pin..
"
This behavior is clearly different between revision v0.3 and revision v0.4 of of the esp32c3 chips we have in our modules (XXN4 v0.3, M4N4 v0.4).
Thank you and best regards
We are using a lot of ESP32C3-mini-1 modules. We used to have modules with Package Code XXN4 but on our latest purchases we have Package Code M4N4. We are noticing that these two batches of mini-1 modules behave differently on boot-up.
We are using USB to connect and flash (Not uart).
We are unable to flash the M4N4 modules unless there is 0V on GPIO2 and GPIO3. If the module is started up with other combinations of
3V and 0V on GPIO 2 and 3 the esptool errors out: "[Errno 71] Protocol error"
(esptool version 4.5.1)
With 0V on GPI0 2 and 3 esptool reports:
"
esptool.py v4.5.1
Serial port /dev/ttyACM0
Connecting...
Detecting chip type... ESP32-C3
Chip is ESP32-C3 (revision v0.4)
Features: WiFi, BLE
Crystal is 40MHz
MAC: XXXXXXXXXXX
Uploading stub...
Running stub...
Stub running...
Warning: ESP32-C3 has no Chip ID. Reading MAC instead.
MAC: XXXXXXXXXXXX
Hard resetting via RTS pin..
"
This behavior is clearly different between revision v0.3 and revision v0.4 of of the esp32c3 chips we have in our modules (XXN4 v0.3, M4N4 v0.4).
Thank you and best regards