assert failed: isr_handle_rx_abort esp_ieee802154_dev.c:484 (s_ieee802154_state == IEEE802154_STATE_RX) (TZ-809) #326
Comments
github-actions
bot
changed the title
|
I've now had this on 1.2.1 too: Source: https://github.com/nomis/candle-dribbler/tree/c574069f97d7421069356264f3374282ed13cad5 (0.7.2-3-gc574069) No core dump because it's still creating it with an invalid CRC. |
Every time a core dump happens in I've added extra CRC calculations to the core dump flash process, so that there are 2 before the flash write and 2 after it. All 4 CRC values are different. If I crash in one of my own tasks then all 4 CRC values are the same.
The problem is that it's writing memory that is currently in use (possibly by the core dump process), so it changes on every read within |
…m data This is a direct core dump of the current memory so it may change because of other interrupt handlers or the memory used by the core dump process itself. Always write the data via the cache buffer so that what's written matches the checksum. Fixes part of espressif/esp-zigbee-sdk#326 (invalid CRC when writing a core dump to flash).
…m data This is a direct core dump of the current memory so it may change because of other interrupt handlers or the memory used by the core dump process itself. Always write the data via the cache buffer so that what's written matches the checksum. Fixes part of espressif/esp-zigbee-sdk#326 (invalid CRC when writing a core dump to flash).
This is a direct core dump of the current memory so it may change because of other interrupt handlers or the memory used by the core dump process itself. Always write the data via the cache buffer so that what's written matches the checksum. Fixes part of espressif/esp-zigbee-sdk#326 (invalid CRC when writing a core dump to flash).
|
Hi @nomis , we see this crash, in our 15.4 driver code, we only enabled the |
nomis
changed the title
|
|
…m data This is a direct core dump of the current memory so it may change because of other interrupt handlers or the memory used by the core dump process itself. Always write the data via the cache buffer so that what's written matches the checksum. Fixes part of espressif/esp-zigbee-sdk#326 (invalid CRC when writing a core dump to flash).
|
@zwx1995esp there's still a serious bug in the code dump writing process; is anyone going to look at and merge espressif/esp-idf#13651 ? |
This is a direct core dump of the current memory so it may change because of other interrupt handlers or the memory used by the core dump process itself. Always write the data via the cache buffer so that what's written matches the checksum. Fixes part of espressif/esp-zigbee-sdk#326 (invalid CRC when writing a core dump to flash).
|
@nomis we will follow up espressif/esp-idf#13651 internally. Have you captured the issue again with the 802.15.4 debug mode enabled? |
|
Not yet, the reduced number of RX buffers for testing #304 may be impacting it. I'll try again with the original configuration. |
…m data This is a direct core dump of the current memory so it may change because of other interrupt handlers or the memory used by the core dump process itself. Always write the data via the cache buffer so that what's written matches the checksum. Fixes part of espressif/esp-zigbee-sdk#326 (invalid CRC when writing a core dump to flash).
…m data This is a direct core dump of the current memory so it may change because of other interrupt handlers or the memory used by the core dump process itself. Always write the data via the cache buffer so that what's written matches the checksum. Fixes part of espressif/esp-zigbee-sdk#326 (invalid CRC when writing a core dump to flash).
|
Considering the issue can't be reproduced, closing it. Feel free to file new issue if it happens again. |
Answers checklist.
IDF version.
v5.3-dev-2320-ge4f167df25 (esp_ieee802154_dev.c:484)
v5.3-dev-2321-ga70f4bef18 (esp_ieee802154_dev.c:487)
esp-zigbee-lib version.
1.2.3
esp-zboss-lib version.
1.2.3
Espressif SoC revision.
ESP32-C6
What is the expected behavior?
Does not crash
Does not write core dumps with an invalid CRC
What is the actual behavior?
assert failed: isr_handle_rx_abort esp_ieee802154_dev.c:484 (s_ieee802154_state == IEEE802154_STATE_RX)
Core dump with an invalid CRC is written (this happens every time for this core dump).
Steps to reproduce.
Unknown. This has happened 4 times in a week after updating only the Zigbee libraries from 1.2.1 to 1.2.3.
More Information.
Source: https://github.com/nomis/candle-dribbler/tree/4b5dff82449a19cc4a387f546c0b0c059957466c (0.7.3-1-g4b5dff8)
Binary: candle-dribbler.elf.gz
Core dump: core-dump-2024-04-19.txt and core-dump-2024-04-19-fixed-crc.txt
The text was updated successfully, but these errors were encountered: