ESP32 Forum

ESP32 Official Forum
http://esp32.io/

esp32c3 revisions

http://esp32.io/viewtopic.php?f=13&t=21040

Page 1 of 1

esp32c3 revisions

Posted: Thu May 20, 2021 3:33 pm
by citoyx
Good afternoon,

After two months delay, i just received my esp32c3 devkitC 02v1.1
Sadly after trying to flash blink exemple i got this message:
E (38) boot_comm: This chip is revision 2 but the application is configured for minimum revision 3. Can't run.


I understand there is a workaround with modifying some files, but what is the difference between rev2 and rev3 ? does it have an impact on code ? will there be some structural change between revisions ?

and most important, where can i get latest revision chip devkit ?

***addons***

Just to let you know, and in case someone face the same issue. Just idf.py menuconfig -> component config -> esp32c3 specific -> Minimum supported esp32-c3 revision : choose 2 (or whatever your revision is).

here is the output of blink :
Code: [Select all] [Expand/Collapse]
  1. Serial port COM22
  2. Connecting....
  3. Detecting chip type... ESP32-C3
  4. Running idf_monitor in directory d:\work\esp\examples\get-started\blink
  5. Executing "C:\Users\plonky\.espressif\python_env\idf4.4_py3.8_env\Scripts\python.exe D:\work\esp\tools/idf_monitor.py -p COM22 -b 115200 --toolchain-prefix riscv32-esp-elf- --target esp32c3 --decode-panic backtrace d:\work\esp\examples\get-started\blink\build\blink.elf -m 'C:\Users\plonky\.espressif\python_env\idf4.4_py3.8_env\Scripts\python.exe' 'D:\work\esp\tools\idf.py'"...
  6. --- WARNING: GDB cannot open serial ports accessed as COMx
  7. --- Using \\.\COM22 instead...
  8. --- idf_monitor on \\.\COM22 115200 ---
  9. --- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
  10. ESP-ROM:esp32c3-20200918
  11. Build:Sep 18 2020
  12. rst:0x1 (POWERON),boot:0xc (SPI_FAST_FLASH_BOOT)
  13. SPIWP:0xee
  14. mode:DIO, clock div:1
  15. load:0x3fcd6100,len:0x1654
  16. load:0x403ce000,len:0x8c0
  17. load:0x403d0000,len:0x2928
  18. entry 0x403ce000
  19. I (32) boot: ESP-IDF v4.4-dev-1404-gc13afea63 2nd stage bootloader
  20. I (32) boot: compile time 17:40:37
  21. I (32) boot: chip revision: 2
  22. I (35) boot.esp32c3: SPI Speed      : 80MHz
  23. I (40) boot.esp32c3: SPI Mode       : DIO
  24. I (45) boot.esp32c3: SPI Flash Size : 2MB
  25. I (50) boot: Enabling RNG early entropy source...
  26. I (55) boot: Partition Table:
  27. I (59) boot: ## Label            Usage          Type ST Offset   Length
  28. I (66) boot:  0 nvs              WiFi data        01 02 00009000 00006000
  29. I (73) boot:  1 phy_init         RF data          01 01 0000f000 00001000
  30. I (81) boot:  2 factory          factory app      00 00 00010000 00100000
  31. I (88) boot: End of partition table
  32. I (92) esp_image: segment 0: paddr=00010020 vaddr=3c020020 size=07640h ( 30272) map
  33. I (105) esp_image: segment 1: paddr=00017668 vaddr=3fc8ae00 size=0145ch (  5212) load
  34. I (110) esp_image: segment 2: paddr=00018acc vaddr=40380000 size=0754ch ( 30028) load
  35. I (123) esp_image: segment 3: paddr=00020020 vaddr=42000020 size=178b0h ( 96432) map
  36. I (141) esp_image: segment 4: paddr=000378d8 vaddr=4038754c size=03724h ( 14116) load
  37. I (144) esp_image: segment 5: paddr=0003b004 vaddr=50000000 size=00010h (    16) load
  38. I (150) boot: Loaded app from partition at offset 0x10000
  39. I (153) boot: Disabling RNG early entropy source...
  40. I (169) cpu_start: Pro cpu up.
  41. I (177) cpu_start: Pro cpu start user code
  42. I (177) cpu_start: cpu freq: 160000000
  43. I (177) cpu_start: Application information:
  44. I (180) cpu_start: Project name:     blink
  45. I (185) cpu_start: App version:      v4.4-dev-1404-gc13afea63
  46. I (191) cpu_start: Compile time:     May 20 2021 17:40:32
  47. I (197) cpu_start: ELF file SHA256:  78cbbe885cdab963...
  48. I (203) cpu_start: ESP-IDF:          v4.4-dev-1404-gc13afea63
  49. I (210) heap_init: Initializing. RAM available for dynamic allocation:
  50. I (217) heap_init: At 3FC8D0E0 len 00032F20 (203 KiB): DRAM
  51. I (223) heap_init: At 3FCC0000 len 0001F260 (124 KiB): STACK/DRAM
  52. I (230) heap_init: At 50000010 len 00001FF0 (7 KiB): RTCRAM
  53. I (237) spi_flash: detected chip: generic
  54. I (241) spi_flash: flash io: dio
  55. W (245) spi_flash: Detected size(4096k) larger than the size in the binary image header(2048k). Using the size in the binary image header.
  56. I (258) sleep: Configure to isolate all GPIO pins in sleep state
  57. I (265) sleep: Enable automatic switching of GPIO sleep configuration
  58. I (272) cpu_start: Starting scheduler.
  59. I (276) example: Example configured to blink addressable LED!
  60. I (276) example: Turning the LED OFF!
  61. I (1286) example: Turning the LED ON!
  62. I (2286) example: Turning the LED OFF!
  63. I (3286) example: Turning the LED ON!
  64. I (4286) example: Turning the LED OFF!
  65. I (5286) example: Turning the LED ON!
  66. I (6286) example: Turning the LED OFF!
  67. I (7286) example: Turning the LED ON!
  68. I (8286) example: Turning the LED OFF!
  69. I (9286) example: Turning the LED ON!
GeSHi © Codebox Plus Extension

Re: esp32c3 revisions

Posted: Fri May 21, 2021 5:43 am
by ESP_Sprite
citoyx wrote: ↑
Thu May 20, 2021 3:33 pm
 I understand there is a workaround with modifying some files, but what is the difference between rev2 and rev3 ? does it have an impact on code ? will there be some structural change between revisions ?
There's some minor changes in the radio/MAC logic between eco2 and eco3, and USB-to-JTAG-serial doesn't work in ECO2. No structural changes otherwise.
and most important, where can i get latest revision chip devkit ?
Any mass market devkit you get at this point should have ECO3 on it. ECO2 and earlier was only given out in sample quantities.

Re: esp32c3 revisions

Posted: Fri May 21, 2021 7:54 am
by chegewara
ESP_Sprite wrote: ↑
Fri May 21, 2021 5:43 am
 Any mass market devkit you get at this point should have ECO3 on it. ECO2 and earlier was only given out in sample quantities.
I have bought esp32 C3 from mouser. My order was delayed about 5 weeks due to shortages and production, but thats not the point. My order was sent about 6 weeks ago, so not that long time ago and it was not sample. All 5 devkit boards are with eco2, at least esp-idf reports it is revision 2.

Re: esp32c3 revisions

Posted: Fri May 21, 2021 8:03 am
by citoyx
chegewara wrote: ↑
Fri May 21, 2021 7:54 am
ESP_Sprite wrote: ↑
Fri May 21, 2021 5:43 am
 Any mass market devkit you get at this point should have ECO3 on it. ECO2 and earlier was only given out in sample quantities.
I have bought esp32 C3 from mouser. My order was delayed about 5 weeks due to shortages and production, but thats not the point. My order was sent about 6 weeks ago, so not that long time ago and it was not sample. All 5 devkit boards are with eco2, at least esp-idf reports it is revision 2.
Yeah my order from mouser was made 23th of march.
4xESP32-C3-DevKitC-02 and 4xESP32-C3-DevKitM-1

So far i received devkit 02 last Wednesday an all are sample (rainmaker version) rev2.

devkitm-1 is delayed to mid june again with resupply status.

WHERE can i buy mass market version ?

Re: esp32c3 revisions

Posted: Fri May 21, 2021 8:06 am
by chegewara
Dont take this wrong, i do not complain, i knew exactly what i am buying and i am happy with that. Even without USB/JTAG i can work with new chip, test BLE5 or other API compatibility, which is good, but i am just a programmer.

Re: esp32c3 revisions

Posted: Thu Jul 08, 2021 4:32 am
by DoctorDan
Well, I do want to complain. I am new to these products. I also ordered esp32-c3 from mouser. The units were shipped with notes on the esp32-c3 idf. It describes the commands that should be run to test the installation (blink)

I followed these instructions step-by-step and got
E (36) boot_comm: This chip is revision 2 but the application is configured for minimum revision 3. Can't run.

This is pretty unacceptable. As a newcomer I have no idea if this error can be corrected or how to do that but it certainly does not appear that the merchandise that I received is what appears on my order. If the C3 modules are/were not ready the shipping should have been postponed until the correct items became available.

I don't know what to do next but I am one very unhappy camper.

Thank you,
de

Re: esp32c3 revisions

Posted: Thu Jul 08, 2021 10:39 am
by chegewara
@DoctorDan, dont worry, you can still use it and have a lot of fun. All you have to do is to change 1 option in menuconfig.

Code: Select all

idf.py menuconfig
Then search for revision keyword and change it from version 3 to version 2.

Re: esp32c3 revisions

Posted: Thu Jul 08, 2021 7:17 pm
by DoctorDan
Thanks, I'll take a look

Re: esp32c3 revisions

Posted: Fri Dec 24, 2021 12:36 pm
by PoClab
Seems like I have 1-st revision of ESP32-C3 that works not as expected. I am interested in how I can understand by marking on-chip that I am buying revision higher than 3?

Re: esp32c3 revisions

Posted: Sat Dec 25, 2021 11:20 am
by axellin
chegewara wrote: ↑
Thu Jul 08, 2021 10:39 am
 @DoctorDan, dont worry, you can still use it and have a lot of fun. All you have to do is to change 1 option in menuconfig.

Code: Select all

idf.py menuconfig
Then search for revision keyword and change it from version 3 to version 2.
This is no longer true, you will hit link error if rev < 3.
https://github.com/espressif/esp-idf/is ... -978774224
All times are UTC
Page 1 of 1
Powered by phpBB® Forum Software © phpBB Limited
https://www.phpbb.com/