Wrong IRAM usage shown on compile

morfeus
Posts: 1
Joined: Tue Sep 24, 2024 7:24 pm

Wrong IRAM usage shown on compile

Postby morfeus » Mon Sep 30, 2024 7:54 am

Hi,

I am developing a product on ESP32-S3-WROOM-1-N16R8 that have and I2C temperature sensor, I2C MUX and I2C ADC, communicates with an display using UART. Beside that, I have need to use BLE, SoftAP and STA Wifi. As in the development process I always had debug UART connected, I didn't noticed a problem that begin to happen once the device was running without UART debug connected and that is random resets specially when I try to connect to SoftAP. So, if I connect UART, everything works OK, and if I disconnect UART and connect to SoftAP the module reboots. As the problem doesn't hapen when UART is connected, I can't catch what is the problem. So, I upgraded esp-idf from 5.2.1 to 5.3.1. That didn't resolve my problem so I begin to investigate deeper what's happening. What I noticed is IRAM being used 99.99%. Then I tried to disable various unrequired stuff in menuconfig hoping that I'll have some "normal" IRAM usage but what every I did, IRAM usage was 99.99%. So I tried to compile SoftAP example and to my surprise, example also uses 99.99% of IRAM. Is that a bug in esp-idf 5.3.1 and Visual Studio Code or? What might be the cause of resets when using SoftAP without UART connected? Thanks.

vritzka
Posts: 33
Joined: Wed Sep 07, 2022 5:33 am

Re: Wrong IRAM usage shown on compile

Postby vritzka » Sat Jun 07, 2025 10:20 am

same here, shows 99.99% whatever I do.

Sprite
Espressif staff
Espressif staff
Posts: 10636
Joined: Thu Nov 26, 2015 4:08 am

Re: Wrong IRAM usage shown on compile

Postby Sprite » Sat Jun 07, 2025 11:43 am

I haven't checked the code, but potentially because the S3 has most of the RAM available as either IRAM or DRAM and ESP-IDF divides the memory border according to the code it's compiling on this chip; in that case, aside from extreme scenarios, iram usage would always be nearly 100%.

Who is online

Users browsing this forum: Google [Bot], Qwantbot and 2 guests