Cannot debug at all. Very discouraged: please help. (IDFGH-9253) #10638
Labels
Comments
github-actions
bot
changed the title
|
Here is the doctor command output: |
|
Have you check the log output, there seems to be an error in your application regarding |
|
Thank you Brian, there is a file you can include which defines that. Or, you can kconfig it out by making the debugger not thread aware, or similar. What would help would be a complete tasks.json and launch.json along with the correct driver to use for the two interfaces(JTAG serial) available from the USB port. You have a working configuration you can share? |
Thanks, can you tell me what the difference is between using the espidf debug settings and the C/C++ settings? In terms of what is available and how to interface with the program? Also, how can I get the svd info to get used? Shouldn't it show up in the ESP peripheral view? |
|
@brianignacio5 I think I may have other problems. When following the instructions for running GDB from the command line, this happened: First thing I noticed was that the target was incorrect, and I also mis-interpreted the Anyhow, I ran the I tried changing the target but this is the first time I've used gdb so... Next I tried this: I found a different gdbinit file near there and tried using it: The target is still wrong and also it claims I can't use python with this copy of GDB (but there's tons of python ESP has written for just that...), so I thought maybe that The target is correct now, using the full path, and I can see that it's not even the same gdb now! Now it's I feel like it's probably something obvious that experienced individuals such as yourself and @chipweinberger so please tell me if I'm wasting my time and hopefully what to do/where to go next. Thanks |
|
I got something working for a brief moment but there was weird output form the openocd output. It said
|
|
@chipweinberger @brianignacio5 can either of you provide any further assistance? Specifically, these things:
Thanks for the help you have already given. |
|
When things are not working I suggest going to basics. First make sure you can debug a very basic esp-idf example (such as the blink example). This can help you separate the hardware and extension configuration issues from software issues. Second, I think using the esp32s3 builtin usb config from OpenOCD should work. You can try just starting the openOCD server and see if it works. Third, you can use any debugger you prefer, the About the drivers: Check the jtag configuration for esp32 s3. About the |
espressif-bot
added
Status: Selected for Development
|
@ChrisJones79 did you manage to get rid of the uxTopUsedPriority error by including that file? I'm new to ESP32 & FreeRTOS, how exactly should I include this file in my project? |
|
@ThomasDQS
It was a while ago, I think the thing that worked for me was changing
something in menu config and possibly #defining that ux value.
Sorry I can't be of more help. I eventually just switched over to Linux and
was able to debug just fine.
…On Thu, Apr 27, 2023, 11:03 ThomasDQS ***@***.***> wrote:
@ChrisJones79 <https://github.com/ChrisJones79> did you manage to get rid
of the uxTopUsedPriority error by including that file? I'm new to ESP32 &
FreeRTOS, how exactly should I include this file in my project?
Thanks in advance!
—
Reply to this email directly, view it on GitHub
<#10638 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACY6C5MTFHPBGHE23CE3QJ3XDKDFJANCNFSM6AAAAAAUJZ2FWA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Answers checklist.
General issue report
I am using IDFv5.0 in vscode on Win10x64. The device I'm using is the esp32-s3 n32r8.
Just to try and get debugging, I opened the cdc_acm_vcp example and built it. I checked the boxes in config so that both the bootloader and application had th -Og debug flag.
After flashing, I went to the vscode sidebar and clicked launch arrow
All that is in launch.json:
I currently have both USB ports connected to the desktop, as seen here:
I put a copy of the esp32s3 svd file in my project directory, where the main folder is.
I've reset in to the bootloader and saw different messages, they are below.
I really don't know what to do. I've always used printf messages and never really had very large programs. So just using them worked enough. But I have convinced my employer to use ESP32 for upcoming projects and my first project is pretty big, many source files and printf isn't enough to make steady progress.
I really need help getting debugging working. Thank you in advance for any help!
I will copy everything that was printed during the build and debug start attempts here:
The text was updated successfully, but these errors were encountered: