ESP32 Forum

Posted: **Sat Oct 12, 2024 1:44 pm**

Hi,

After reaching the limit of ram capacity of my esp32-s3 N16R2 , i meet issue by being not able to boot anymore:

The program is flashed properly, but after reset, i have this console:

--- WARNING: GDB cannot open serial ports accessed as COMx
--- Using \\.\COM7 instead...
--- idf_monitor on \\.\COM7 115200 ---
--- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x15 (USB_UART_CHIP_RESET),boot:0x0 (DOWNLOAD(USB/UART0))
Saved PC:0x40041a76
waiting for download

I thought the device was locked aven after playing with boot pin , so i deicded to change the 2Mb version for a 8Mb.

Again, i can flash it , but i'm still facing the same issue again, same console...

I have no more idea, is it possible that probleme comes from my project ?

Thanks a lot for you help.

Posted: **Sun Oct 13, 2024 1:30 am**

Can you show the schematic of whatever you're putting the module onto?

Posted: **Sun Oct 13, 2024 8:16 am**

Hi,

Thanks for the reply.

The boot pin is tied to 3.3 through a 100kohm resistor.
The EN is directly connected to 3.3v. I have seen in the datasheet after ordering the pcb that it is advised to use a rc cicuit on EN pin with 10kohm and 1uF but I dont know if it is is the cause.

Other straping pin left open.

Posted: **Sun Oct 13, 2024 10:05 am**

here the schematics.

I will try to add the rc circuit to be sure it deson't come from this.

Posted: **Sun Oct 13, 2024 10:31 am**

Before to add the rc circuit to EN pin, i tried to force boot gpio0 pin to 3.3v, and it seems to pass.

It is not in download waiting state now, but the program seems to not fully start :

PS C:\Users\Flo\esp\project_test\lvgl3\lvgl3>
& set IDF_PATH='C:\Users\Flo\esp\esp-idf'
PS C:\Users\Flo\esp\project_test\lvgl3\lvgl3> & 'C:\Users\Flo\.espressif\python_env\idf4.4_py3.8_env\Scripts\python.exe' 'C:\Users\Flo\esp\esp-idf\tools\idf_monitor.py' -p COM7 -b 115200 --toolchain-prefix xtensa-esp32s3-elf- --target esp32s3 'c:\Users\Flo\esp\project_test\lvgl3\lvgl3\build\ots_dm.elf'
--- WARNING: GDB cannot open serial ports accessed as COMx
--- Using \\.\COM7 instead...
--- idf_monitor on \\.\COM7 115200 ---
--- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x15 (USB_UART_CHIP_RESET),boot:0x8 (SPI_FAST_FLASH_BOOT)
Saved PC:0x42001fec
0x42001fec: esp_panic_handler at C:/Users/Flo/esp/esp-idf/components/esp_system/panic.c:382 (discriminator 1)

SPIWP:0xee
mode:DIO, clock div:1
load:0x3fce3808,len:0x177c
load:0x403c9700,len:0xcb4
load:0x403cc700,len:0x357c
entry 0x403c9998
I (24) boot: ESP-IDF HEAD-HASH-NOTFOUND 2nd stage bootloader
I (25) boot: compile time 12:14:46
I (25) boot: chip revision: 0
I (27) boot.esp32s3: Boot SPI Speed : 80MHz
I (32) boot.esp32s3: SPI Mode : DIO
I (37) boot.esp32s3: SPI Flash Size : 16MB
I (42) boot: Enabling RNG early entropy source...
I (47) boot: Partition Table:
I (51) boot: ## Label Usage Type ST Offset Length
I (58) boot: 0 nvs WiFi data 01 02 00009000 00006000
I (65) boot: 1 phy_init RF data 01 01 0000f000 00001000
I (73) boot: 2 factory factory app 00 00 00010000 00400000
I (80) boot: 3 db_pneus WiFi data 01 02 00410000 00010000
I (88) boot: End of partition table
I (92) esp_image: segment 0: paddr=00010020 vaddr=3c020020 size=07a54h ( 31316) map
I (106) esp_image: segment 1: paddr=00017a7c vaddr=3fc8ff70 size=02698h ( 9880) load
I (111) esp_image: segment 2: paddr=0001a11c vaddr=40374000 size=05efch ( 24316) load
I (123) esp_image: segment 3: paddr=00020020 vaddr=42000020 size=15810h ( 88080) map
I (141) esp_image: segment 4: paddr=00035838 vaddr=40379efc size=06070h ( 24688) load
I (147) esp_image: segment 5: paddr=0003b8b0 vaddr=50000000 size=00010h ( 16) load
I (154) boot: Loaded app from partition at offset 0x10000
I (154) boot: Disabling RNG early entropy source...
I (159) cpu_start: Pro cpu up.
I (162) cpu_start: Starting app cpu, entry point is 0x403750e4
0x403750e4: call_start_cpu1 at C:/Users/Flo/esp/esp-idf/components/esp_system/port/cpu_start.c:160

I (0) cpu_start: App cpu up.

Posted: **Mon Oct 14, 2024 3:15 am**

Try adding the RC filter first; it's likely that solves the issue.

Posted: **Mon Oct 14, 2024 6:55 am**

Ok thanks,

Is the rc filter and enable pin internally switch off/on when there is a reset via vs code ?
Or is it just when we supply the board ?

I also wonder why my ESP-IDF Size command do not change the RAM size and i'm still in overflow whereas I change the device from 2MB to 8MB of ram ( N16R2 to N16R8)

Console with my new device:

Total sizes:
Used static IRAM: 82382 bytes ( 279858 remain, 22.7% used)
.text size: 81355 bytes
.vectors size: 1027 bytes
Used stat D/IRAM: 211001 bytes ( -38073 remain, 122.0% used) Overflow detected! You can run idf.py size-files for more information.
.data size: 19169 bytes
.bss size: 191832 bytes
Used Flash size : 1626899 bytes
.text : 1077135 bytes
.rodata : 549508 bytes
Total image size: 1728450 bytes (.bin may be padded larger)

thanks a lot

Posted: **Mon Oct 14, 2024 9:07 am**

Olfox59 wrote: ↑
Mon Oct 14, 2024 6:55 am
Is the rc filter and enable pin internally switch off/on when there is a reset via vs code ?
Or is it just when we supply the board ?

It's input-only; the RC filter is needed to give a proper power-on reset

I also wonder why my ESP-IDF Size command do not change the RAM size and i'm still in overflow whereas I change the device from 2MB to 8MB of ram ( N16R2 to N16R8)

Because normally, psram is only added to the heap; statically-allocated stuff still goes into internal memory.

Posted: **Mon Oct 14, 2024 2:20 pm**

So all the ble , wifi, lvgl will never go into the 8MB ram ? The 8MB or 2MB ram are external memory ?

ESP32 Forum

waiting for download after replacing wrrom module

waiting for download after replacing wrrom module

Re: waiting for download after replacing wrrom module

Re: waiting for download after replacing wrrom module

Re: waiting for download after replacing wrrom module

Re: waiting for download after replacing wrrom module

Re: waiting for download after replacing wrrom module

Re: waiting for download after replacing wrrom module

Re: waiting for download after replacing wrrom module

Re: waiting for download after replacing wrrom module