Open ligogeorge opened 1 month ago
Hi @lijoppans! We appreciate you submitting your first issue for our open-source project. 🌟
Even though I'm a bot, I can assure you that the whole community is genuinely grateful for your time and effort. 🤖💙
Environment (please complete the following information):
- Using nRF SDK v2.6.1
Maybe this should be plaftorm: nRF.
nRF SDK 2.6.x implies corresponding Zephyr version 3.6.x.
It looks like this fault is not happening on Zephyr 3.7.0 (nRF SDK 2.7.0), but ESP AT code looks same, probably Zephyr layers handling it.
ESP-AT runs ESP-IDF and it is not related to Platform:ESP32 (which is Zephyr on ESP32). This gets the right eyes with the right label.
Describe the bug
ESP_AT WiFi driver causing secure fault on WiFi disconnects.
To Reproduce Steps to reproduce the behavior:
Expected behavior
WiFi disconnect should not cause any hard fault. Impact
This causes unintentional reboots. Logs and console output
It is found that this is caused due to a null pointer access (0x0C).
ESP AT driver is notifying zephyr network layer that the socket connection is closed with a NULL pointer.
This NULL pointer is being used in the zehyr network layer without any checks.
This causing SecureFault as the address 0x0C is under secure domain now.
Environment (please complete the following information):
Additional context