Closed ChrisJones79 closed 1 year ago
Here is the doctor command output:
---------------------------------------------- ESP-IDF Extension for Visual Studio Code report ---------------------------------------------
OS win32 x64 10.0.19045
System environment variable IDF_PYTHON_ENV_PATH
undefined
System environment variable PATH
C:\Program Files\Microsoft\jdk-11.0.12.7-hotspot\bin;C:\Program Files\Eclipse Adoptium\jdk-17.0.5.8-hotspot\bin;C:\Program Files\Microsoft MPI\Bin\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Program Files\TortoiseGit\bin;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\NVIDIA Corporation\NVIDIA NvDLISR;C:\ProgramData\chocolatey\bin;C:\Program Files\nodejs\;C:\Program Files\dotnet\;C:<HOMEPATH>\Programs\Python\Python311\Scripts\;C:<HOMEPATH>\Programs\Python\Python311\;C:\Program Files\ngsolve-v6.2.2204\bin;C:<HOMEPATH>\AppData\Local\Microsoft\WindowsApps;C:\Program Files\Graphviz\bin;C:\Program Files\7-Zip;E:\AVRDUDE;C:<HOMEPATH>\Programs\Microsoft VS Code\bin;C:<HOMEPATH>\AppData\Local\Programs\MiKTeX\miktex\bin\x64\;C:\Program Files (x86)\GnuWin32\bin;C:\Xilinx\14.7_VM;C:\Program Files\Git\bin;C:\Program Files\Elmer 9.0-Release\bin;C:\Program Files\ParaView 5.11.0\bin;C:\MinGW\bin;C:<HOMEPATH>\Programs\imagej\ij153t-src\source\apache-ant-1.10.12\bin;C:<HOMEPATH>\AppData\Roaming\npm;C:\Program Files\CMake\bin;C:<HOMEPATH>\Programs\bin;C:<HOMEPATH>\.espressif\tools\openocd-esp32\v0.11.0-esp32-20220706\openocd-esp32\bin;
System environment variable PYTHON
undefined
Visual Studio Code version 1.74.3
Visual Studio Code language en
Visual Studio Code shell C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe
ESP-IDF Extension version 1.5.1
Workspace folder c:<HOMEPATH>\code\esp-idf\SimpleDebug
---------------------------------------------------- Extension configuration settings ------------------------------------------------------
ESP-ADF Path (idf.espAdfPath) ${env:ADF_PATH}
ESP-IDF Path (idf.espIdfPath) C:<HOMEPATH>\espV5\esp-idf
ESP-MDF Path (idf.espMdfPath) ${env:MDF_PATH}
ESP-Matter Path (idf.espMatterPath) ${env:ESP_MATTER_PATH}
Custom extra paths (idf.customExtraPaths) C:<HOMEPATH>\.espressif\tools\xtensa-esp-elf-gdb\11.2_20220823\xtensa-esp-elf-gdb\bin;C:<HOMEPATH>\.espressif\tools\riscv32-esp-elf-gdb\11.2_20220823\riscv32-esp-elf-gdb\bin;C:<HOMEPATH>\.espressif\tools\xtensa-esp32-elf\esp-2022r1-11.2.0\xtensa-esp32-elf\bin;C:<HOMEPATH>\.espressif\tools\xtensa-esp32s2-elf\esp-2022r1-11.2.0\xtensa-esp32s2-elf\bin;C:<HOMEPATH>\.espressif\tools\xtensa-esp32s3-elf\esp-2022r1-11.2.0\xtensa-esp32s3-elf\bin;C:<HOMEPATH>\.espressif\tools\riscv32-esp-elf\esp-2022r1-11.2.0\riscv32-esp-elf\bin;C:<HOMEPATH>\.espressif\tools\esp32ulp-elf\2.35_20220830\esp32ulp-elf\bin;C:<HOMEPATH>\.espressif\tools\cmake\3.24.0\bin;C:<HOMEPATH>\.espressif\tools\openocd-esp32\v0.11.0-esp32-20220706\openocd-esp32\bin;C:<HOMEPATH>\.espressif\tools\ninja\1.10.2;C:<HOMEPATH>\.espressif\tools\idf-exe\1.0.3;C:<HOMEPATH>\.espressif\tools\ccache\4.6.2\ccache-4.6.2-windows-x86_64;C:<HOMEPATH>\.espressif\tools\dfu-util\0.9\dfu-util-0.9-win64
Custom extra vars (idf.customExtraVars) {"OPENOCD_SCRIPTS":"C:\\Users\\cjone\\.espressif\\tools\\openocd-esp32\\v0.11.0-esp32-20220706/openocd-esp32/share/openocd/scripts","IDF_CCACHE_ENABLE":"1"}
Virtual env Python Path (idf.pythonBinPath) C:<HOMEPATH>\.espressif\python_env\idf5.0_py3.8_env\Scripts\python.exe
Serial port (idf.port) COM35
OpenOCD Configs (idf.openOcdConfigs) board/esp32s3-builtin.cfg
ESP-IDF Tools Path (idf.toolsPath) C:<HOMEPATH>\.espressif
Git Path (idf.gitPath) C:<HOMEPATH>\.espressif\tools\idf-git\2.30.1\cmd\git.exe
-------------------------------------------------------- Configurations access -------------------------------------------------------------
Access to ESP-ADF Path (idf.espAdfPath) false
Access to ESP-IDF Path (idf.espIdfPath) true
Access to ESP-MDF Path (idf.espMdfPath) false
Access to ESP-Matter Path (idf.espMatterPath) false
Access to ESP-IDF Custom extra paths
Access to C:<HOMEPATH>\.espressif\tools\xtensa-esp-elf-gdb\11.2_20220823\xtensa-esp-elf-gdb\bin: true
Access to C:<HOMEPATH>\.espressif\tools\riscv32-esp-elf-gdb\11.2_20220823\riscv32-esp-elf-gdb\bin: true
Access to C:<HOMEPATH>\.espressif\tools\xtensa-esp32-elf\esp-2022r1-11.2.0\xtensa-esp32-elf\bin: true
Access to C:<HOMEPATH>\.espressif\tools\xtensa-esp32s2-elf\esp-2022r1-11.2.0\xtensa-esp32s2-elf\bin: true
Access to C:<HOMEPATH>\.espressif\tools\xtensa-esp32s3-elf\esp-2022r1-11.2.0\xtensa-esp32s3-elf\bin: true
Access to C:<HOMEPATH>\.espressif\tools\riscv32-esp-elf\esp-2022r1-11.2.0\riscv32-esp-elf\bin: true
Access to C:<HOMEPATH>\.espressif\tools\esp32ulp-elf\2.35_20220830\esp32ulp-elf\bin: true
Access to C:<HOMEPATH>\.espressif\tools\cmake\3.24.0\bin: true
Access to C:<HOMEPATH>\.espressif\tools\openocd-esp32\v0.11.0-esp32-20220706\openocd-esp32\bin: true
Access to C:<HOMEPATH>\.espressif\tools\ninja\1.10.2: true
Access to C:<HOMEPATH>\.espressif\tools\idf-exe\1.0.3: true
Access to C:<HOMEPATH>\.espressif\tools\ccache\4.6.2\ccache-4.6.2-windows-x86_64: true
Access to C:<HOMEPATH>\.espressif\tools\dfu-util\0.9\dfu-util-0.9-win64: true
Access to Virtual env Python Path (idf.pythonBinPath) true
Access to CMake in environment PATH undefined
Access to Ninja in environment PATH undefined
Access to ESP-IDF Tools Path (idf.toolsPath) true
-------------------------------------------------------- Configurations has spaces -------------------------------------------------------------
Spaces in system environment Path true
Spaces in ESP-ADF Path (idf.espAdfPath) false
Spaces in ESP-IDF Path (idf.espIdfPath) false
Spaces in ESP-MDF Path (idf.espMdfPath) false
Spaces in ESP-Matter Path (idf.espMatterPath) false
Spaces in ESP-IDF Custom extra paths
Spaces in C:<HOMEPATH>\.espressif\tools\xtensa-esp-elf-gdb\11.2_20220823\xtensa-esp-elf-gdb\bin: false
Spaces in C:<HOMEPATH>\.espressif\tools\riscv32-esp-elf-gdb\11.2_20220823\riscv32-esp-elf-gdb\bin: false
Spaces in C:<HOMEPATH>\.espressif\tools\xtensa-esp32-elf\esp-2022r1-11.2.0\xtensa-esp32-elf\bin: false
Spaces in C:<HOMEPATH>\.espressif\tools\xtensa-esp32s2-elf\esp-2022r1-11.2.0\xtensa-esp32s2-elf\bin: false
Spaces in C:<HOMEPATH>\.espressif\tools\xtensa-esp32s3-elf\esp-2022r1-11.2.0\xtensa-esp32s3-elf\bin: false
Spaces in C:<HOMEPATH>\.espressif\tools\riscv32-esp-elf\esp-2022r1-11.2.0\riscv32-esp-elf\bin: false
Spaces in C:<HOMEPATH>\.espressif\tools\esp32ulp-elf\2.35_20220830\esp32ulp-elf\bin: false
Spaces in C:<HOMEPATH>\.espressif\tools\cmake\3.24.0\bin: false
Spaces in C:<HOMEPATH>\.espressif\tools\openocd-esp32\v0.11.0-esp32-20220706\openocd-esp32\bin: false
Spaces in C:<HOMEPATH>\.espressif\tools\ninja\1.10.2: false
Spaces in C:<HOMEPATH>\.espressif\tools\idf-exe\1.0.3: false
Spaces in C:<HOMEPATH>\.espressif\tools\ccache\4.6.2\ccache-4.6.2-windows-x86_64: false
Spaces in C:<HOMEPATH>\.espressif\tools\dfu-util\0.9\dfu-util-0.9-win64: false
Spaces in Virtual env Python Path (idf.pythonBinPath) false
Spaces in ESP-IDF Tools Path (idf.toolsPath) false
----------------------------------------------------------- Executables Versions -----------------------------------------------------------
Git version 2.30.1.windows.1
ESP-IDF version 5.0
Python version 3.8.7
Python's pip version 22.3.1
-------------------------------------------------- Python packages in idf.pythonBinPath ----------------------------------------------------
async-timeout version: 4.0.2
attrs version: 22.2.0
bitstring version: 3.1.9
bleak version: 0.19.5
bleak-winrt version: 1.2.0
CacheControl version: 0.12.11
certifi version: 2022.12.7
cffi version: 1.15.1
charset-normalizer version: 3.0.1
click version: 8.0.4
colorama version: 0.4.6
construct version: 2.10.68
contextlib2 version: 21.6.0
coverage version: 7.0.5
cryptography version: 36.0.2
debug-backend version: 1.0.0
ecdsa version: 0.18.0
esp-coredump version: 1.4.2
esptool version: 4.4
freertos-gdb version: 1.0.2
future version: 0.18.2
gcovr version: 5.2
idf_build_apps version: 0.3.0
idf-component-manager version: 1.2.1
idna version: 3.4
importlib-resources version: 5.10.2
Jinja2 version: 3.0.3
jsonschema version: 4.17.3
junit-xml version: 1.9
kconfiglib version: 14.1.0
lockfile version: 0.12.2
lxml version: 4.9.2
MarkupSafe version: 2.1.1
msgpack version: 1.0.4
netifaces version: 0.11.0
packaging version: 23.0
paho-mqtt version: 1.6.1
pexpect version: 4.8.0
pip version: 22.3.1
pkgutil_resolve_name version: 1.3.10
prettytable version: 3.6.0
protobuf version: 3.20.1
psutil version: 5.9.4
ptyprocess version: 0.7.0
pycparser version: 2.21
pyecharts version: 2.0.1
pyelftools version: 0.27
pygdbmi version: 0.9.0.2
Pygments version: 2.14.0
pyparsing version: 3.0.9
pyrsistent version: 0.19.3
pyserial version: 3.5
python-gitlab version: 3.12.0
pywin32 version: 305
PyYAML version: 6.0
reedsolo version: 1.5.4
requests version: 2.28.2
requests-file version: 1.5.1
requests-toolbelt version: 0.10.1
schema version: 0.7.5
setuptools version: 65.7.0
simplejson version: 3.18.1
SimpleWebSocketServer version: 0.1.2
six version: 1.16.0
tqdm version: 4.64.1
unittest-xml-reporting version: 3.2.0
urllib3 version: 1.26.14
wcwidth version: 0.2.5
websocket-client version: 1.4.2
wheel version: 0.36.2
windows-curses version: 2.3.1
xmlrunner version: 1.7.7
zipp version: 3.11.0
---------------------------------------------------- Check ESP-IDF python requirements.txt -------------------------------------------------
Check ESP-IDF Python packages Python requirements are satisfied.
---------------------------------------------------- Check extension requirements.txt ------------------------------------------------------
Check Extension Python packages Python requirements are satisfied.
---------------------------------------------------- Check ESP-IDF debug adapter requirements.txt ------------------------------------------
Check Debug AdapterPython packages Python requirements are satisfied.
---------------------------------------------------- Visual Studio Code launch.json --------------------------------------------------------
{
"version": "0.2.0",
"configurations": [
{
"type": "espidf",
"name": "Launch",
"request": "launch"
}
]
}
---------------------------------------------------- Visual Studio Code c_cpp_properties.json ----------------------------------------------
{
"configurations": [
{
"name": "ESP-IDF",
"compilerPath": "C:\\Users\\cjone\\.espressif\\tools\\xtensa-esp32s3-elf\\esp-2022r1-11.2.0\\xtensa-esp32s3-elf\\bin\\xtensa-esp32s3-elf-gcc.exe",
"cStandard": "c11",
"cppStandard": "c++17",
"includePath": [
"${config:idf.espIdfPath}/components/**",
"${config:idf.espIdfPathWin}/components/**",
"${config:idf.espAdfPath}/components/**",
"${config:idf.espAdfPathWin}/components/**",
"${workspaceFolder}/**"
],
"browse": {
"path": [
"${config:idf.espIdfPath}/components",
"${config:idf.espIdfPathWin}/components",
"${config:idf.espAdfPath}/components/**",
"${config:idf.espAdfPathWin}/components/**",
"${workspaceFolder}"
],
"limitSymbolsToIncludedHeaders": false
}
}
],
"version": 4
}
--------------------------------------------------------------------------------------------------------------------------------------------
Have you check the log output, there seems to be an error in your application regarding uxTopUsedPriority
?
❌ Error: FreeRTOS: uxTopUsedPriority is not defined, consu[OpenOCD]
lt the OpenOCD manual for a work-around!
[Debug Adapter]
Exception in thread Thread-1:
Traceback (most recent call last):
File "threading.py", line 932, in _bootstrap_inner
Exception in thread Thread-2:
Traceback (most recent call last):
File "threading.py", line 932, in _bootstrap_inner
File "threading.py", line 870, in run
File "threading.py", line 870, in run
File "subprocess.py", line 1366, in _readerthread
File "subprocess.py", line 1366, in _readerthread
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?
look here:
https://github.com/espressif/vscode-esp-idf-extension/blob/master/docs/DEBUGGING.md
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:
Microsoft Windows [Version 10.0.19045.2130]
(c) Microsoft Corporation. All rights reserved.
C:\Users\cjones\moreStaticVars>xtensa-esp32s3-elf-gdb -x gdbinit build/moreStaticVars.elf
GNU gdb (esp-gdb) 11.2_20220823
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "--host=x86_64-w64-mingw32 --target=xtensa-esp-elf".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from build/moreStaticVars.elf...
gdbinit:1: Error in sourced command file:
:3333: Connection timed out.
(gdb)
First thing I noticed was that the target was incorrect, and I also mis-interpreted the Error in sourced command
file line. I thought at first it meant my code, i.e. what I was trying to debug. Now I think it means the gdbinit file (from the prompt) although I did copy without altering from the instructions I linked to the ESP webpage.
Anyhow, I ran the show configuration
command to see this:
gdbinit:1: Error in sourced command file:
:3333: Connection timed out.
(gdb)
(gdb) show configuration
This GDB was configured as follows:
configure --host=x86_64-w64-mingw32 --target=xtensa-esp-elf
--with-auto-load-dir=$debugdir:$datadir/auto-load
--with-auto-load-safe-path=$debugdir:$datadir/auto-load
--with-expat
--with-gdb-datadir=//share/gdb (relocatable)
--with-jit-reader-dir=//lib/gdb (relocatable)
--without-libunwind-ia64
--without-lzma
--without-babeltrace
--without-intel-pt
--without-mpfr
--without-xxhash
--without-python
--without-python-libdir
--without-debuginfod
--without-guile
--disable-source-highlight
--with-separate-debug-dir=//lib/debug (relocatable)
("Relocatable" means the directory can be moved with the GDB installation
tree, and GDB will still find it.)
(gdb) configure --target=xtensa-esp32s3-elf
Undefined command: "configure". Try "help".
I tried changing the target but this is the first time I've used gdb so... Next I tried this:
(gdb) show auto-load
auto-load gdb-scripts: Auto-loading of canned sequences of commands scripts is on.
auto-load local-gdbinit: Auto-loading of .gdbinit script from current directory is on.
auto-load safe-path: List of directories from which it is safe to auto-load files is $debugdir:$datadir/auto-load.
auto-load scripts-directory: List of directories from which to load auto-loaded scripts is $debugdir:$datadir/auto-load.
(gdb) show data-directory
GDB's data directory is "c:\users\cjones\programs\espressif\tools\xtensa-esp-elf-gdb\11.2_20220823\xtensa-esp-elf-gdb\share\gdb".
I found a different gdbinit file near there and tried using it:
C:\Users\cjones\moreStaticVars>xtensa-esp32s3-elf-gdb -x "C:\Users\cjones\Programs\Espressif\tools\xtensa-esp32s3-elf\esp-2022r1-11.2.0\xtensa-esp32s3-elf\share\gdb\gdbinit" build/moreStaticVars.elf
GNU gdb (esp-gdb) 11.2_20220823
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "--host=x86_64-w64-mingw32 --target=xtensa-esp-elf".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from build/moreStaticVars.elf...
C:\Users\cjones\Programs\Espressif\tools\xtensa-esp32s3-elf\esp-2022r1-11.2.0\xtensa-esp32s3-elf\share\gdb\gdbinit:6: Error in sourced command file:
Scripting in the "Python" language is not supported in this copy of GDB.
(gdb) quit
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 xtensa-esp32s3-elf-gdb
wasn't really what I thought it was, at the very least things are still broken, so I explicitly calling the dbg near where the newly used gdbinit was:
C:\Users\cjones\moreStaticVars>"C:\Users\cjones\Programs\Espressif\tools\xtensa-esp32s3-elf\esp-2022r1-11.2.0\xtensa-esp32s3-elf\bin\xtensa-esp32s3-elf-gdb.exe" -x "C:\Users\cjones\Programs\Espressif\tools\xtensa-esp32s3-elf\esp-2022r1-11.2.0\xtensa-esp32s3-elf\share\gdb\gdbinit" build/moreStaticVars.elf
C:\Users\cjones\Programs\Espressif\tools\xtensa-esp32s3-elf\esp-2022r1-11.2.0\xtensa-esp32s3-elf\bin\xtensa-esp32s3-elf-gdb.exe: warning: Couldn't determine a path for the index cache directory.
GNU gdb (crosstool-NG esp-2022r1) 9.2.90.20200913-git
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "--host=x86_64-host_w64-mingw32 --target=xtensa-esp32s3-elf".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from build/moreStaticVars.elf...
C:\Users\cjones\Programs\Espressif\tools\xtensa-esp32s3-elf\esp-2022r1-11.2.0\xtensa-esp32s3-elf\share\gdb\gdbinit:6: Error in sourced command file:
Scripting in the "Python" language is not supported in this copy of GDB.
(gdb) quit
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 GNU gdb (crosstool-NG esp-2022r1) 9.2.90.20200913-git
where before it was GNU gdb (esp-gdb) 11.2_20220823
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 hola juan
a bunch of times...
@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 espidf
should work. Maybe changing the logLevel
to 4 in launch.json can give us a better detail about the error in the debug session.
About the drivers: Check the jtag configuration for esp32 s3.
About the hola Juan
output, apologies, was a log left out on development. It is fixed in master release. You could try with this vsix installer
@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!
@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 https://github.com/espressif/esp-idf/issues/10638#issuecomment-1525861095, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACY6C5MTFHPBGHE23CE3QJ3XDKDFJANCNFSM6AAAAAAUJZ2FWA . You are receiving this because you were mentioned.Message ID: @.***>
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: