-
Notifications
You must be signed in to change notification settings - Fork 7.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Executing espcoredump.py results in an Error in path (parsing) (IDFGH-7943) #9458
Comments
Some additional information:
When running it, an error in the gen_esp32part.py file arises, no matter if the core dump gets saved as binary or elf to the flash.
|
When trying to decode it via a copied UART print and run info_corefile, I get this error (added more prints to espcoredump.py ):
Command: |
The above error ('NoneType' object is not subscriptable) occurs also in a minimal example project. Project:
Partition table:
Core dump command: Result:
Btw:
|
Is there any update regarding this issue? I am still getting the same behavior as explained by @ddomnik, using following commands:
|
@borjanbozhinovski Did you try to transfer the coredump data with the lower speeds? e.g: 115200 |
@erhankur Actually, I do not remember if I tried with lower speed, as this is something that I was working on 6 mouths ago. Do you think that lower speed will fix the behavior? |
@borjanbozhinovski I couldn't reproduce this yet. We have several users who reported a similar issue on Windows. Not sure lower speed will fix it but I thought It was worth trying. From what I understand, coredump data is not corrupted but we can't transfer it for some reason. Anyway, if you see an error again, please let us know. |
Environment
Problem Description
Via sdkconfig, I enabled the Core dump
Data destination: Flash
Core dump data format: ELF format and also tested Binary format
Core dump data integrity check: Use CRC32 ...
[x] Check core dump data integrity on boot
Maximum number of task: 64
I provoked an error so:
After that I run inside the ESP-IDF 5.0 PowerShell
espcoredump.py -p COM5 info_corefile C:\Users\XXX\Documents\esp\XXX\build\XXX.elf
a new window opens that immediately closes. I tried to catch it, but the only thing I got was in the screenshot attached.
Error in path (parsing) -> tot_len
I also tried to edit the espcoredump.py and add input() to debug it but had no luck (maybe someone can help here)
Expected Behavior
Show info from core dump
The text was updated successfully, but these errors were encountered: