The MicroPython.org esp32c3 and esp32c3-usb download pages appear to have incorrect instructions.
Necessary changes
- The
--chip flag should have a value of esp32c3.
- The flash offset should be
0x0.
- The bin file name should be updated to include
c3 after esp32, for completeness.
Discussion
The symptom of the wrong flash offset was that after flashing, which appeared to be successful, I could not connect to the board with ampy, mpfshell, or rshell. I stumbled across this forum which had the answer. And indeed the bootloader documentation for the esp32c3 states that it should be 0x0.
Most people who use MicroPython on an esp32, if like myself, only use esptool to flash MicroPython have no concept of flash offsets and how to choose them so it would be good to fix this and maybe add a page to the MicroPython docs.
I would be happy to make these changes / pull request but did not see the website source in this repository.
The MicroPython.org esp32c3 and esp32c3-usb download pages appear to have incorrect instructions.
Necessary changes
--chipflag should have a value ofesp32c3.0x0.c3after esp32, for completeness.Discussion
The symptom of the wrong flash offset was that after flashing, which appeared to be successful, I could not connect to the board with ampy, mpfshell, or rshell. I stumbled across this forum which had the answer. And indeed the bootloader documentation for the esp32c3 states that it should be
0x0.Most people who use MicroPython on an esp32, if like myself, only use esptool to flash MicroPython have no concept of flash offsets and how to choose them so it would be good to fix this and maybe add a page to the MicroPython docs.
I would be happy to make these changes / pull request but did not see the website source in this repository.