You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
I have searched the issue tracker for a similar issue and not found a similar issue.
IDF version.
Release v5.4
Espressif SoC revision.
ESP32-C3 (QFN32) (version v0.4)
Operating System used.
Linux
How did you build your project?
VS Code IDE
If you are using Windows, please specify command line type.
None
Development Kit.
Custom board with ESP32-C3-WROOM-02 module
Power Supply used.
USB
What is the expected behavior?
Previously provisioned WiFi connection attempt results in ""os_memblock_get failed.." in Monitor log. I do not see this with 5.3.1 or earlier idf versions. Also, free heap is 7K less for the same application compiled with 5.4 compared to 5.3.1 idf version. Not sure the two are related but the warning is a concern on its own.
The app also uses Nimble BLE in the central mode (normal boot mode) and in peripheral mode during WiFi provisioning.
What is the actual behavior?
os_memblock_get failed (size 4) warning seen once to repeated 4 times during boot up wifi connection.
Steps to reproduce.
Compile applicaiton with 5.4, program and boot device.
Debug Logs.
I (7204) _blecent_update_status: Central status set: 8
I (7204) _blecent_update_status: Central status get: 9
----
os_memblock_get failed (size 4)
I (8254) wifi:state: auth -> assoc (0x0)
I (8264) wifi:Association refused temporarily time 1000, comeback time 1100 (TUs)
I (9384) wifi:state: assoc -> auth (0xb0)
os_memblock_get failed (size 4)
os_memblock_get failed (size 4)
os_memblock_get failed (size 4)
I (10244) SYS_Init: Heap 14.2% free - 34472 of 243580 bytes
More Information.
No response
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
"os_memblock_get failed.." in monitor log while trying to connect to WiFi AP.
"os_memblock_get failed.." in monitor log while trying to connect to WiFi AP. (IDFGH-14595)
Feb 7, 2025
Answers checklist.
IDF version.
Release v5.4
Espressif SoC revision.
ESP32-C3 (QFN32) (version v0.4)
Operating System used.
Linux
How did you build your project?
VS Code IDE
If you are using Windows, please specify command line type.
None
Development Kit.
Custom board with ESP32-C3-WROOM-02 module
Power Supply used.
USB
What is the expected behavior?
Previously provisioned WiFi connection attempt results in ""os_memblock_get failed.." in Monitor log. I do not see this with 5.3.1 or earlier idf versions. Also, free heap is 7K less for the same application compiled with 5.4 compared to 5.3.1 idf version. Not sure the two are related but the warning is a concern on its own.
The app also uses Nimble BLE in the central mode (normal boot mode) and in peripheral mode during WiFi provisioning.
What is the actual behavior?
os_memblock_get failed (size 4) warning seen once to repeated 4 times during boot up wifi connection.
Steps to reproduce.
Compile applicaiton with 5.4, program and boot device.
Debug Logs.
More Information.
No response
The text was updated successfully, but these errors were encountered: