Hi there,
I have serious problems to upgrade a project running just fine under 5.01 to 5.1. There is NO debug information what is happening, no core dump, nothing. The effort to nail this down is beyond financial reasoning. This requires to rollback to 5.01. However, the Eclipse plug in sticks to user .expressive path when using the tools manager, which impedes to use different IDF versions on the same machine or doing everything manual, however even when selecting to install for all users the IDF directory is created under ..\(user)\idfpath.
Something not quite consistent here, so question, can I use different IDF versions with Eclipse and Windows and how to do that right. It is obvious that each version needs its own Eclipse, but how to avoid that the plugin messes up with the .expressive path.
Thanks
How can I use different IDF versions concurrently using Eclipse Plug IN
-
- Posts: 188
- Joined: Wed Jul 17, 2019 5:26 pm
Re: How can I use different IDF versions concurrently using Eclipse Plug IN
As mentioned here viewtopic.php?f=40&t=36331
Recommeded approach would be to use different workspaces if you are dealing with different projects and different IDF versions.
If you want to swtich to a different IDF vesion for the same project, please follow the steps mentioned here https://medium.com/@kondal.kolipaka/swi ... 5d0ad9f7a0
Let me know if you see any issues here! I'll be happy to help!
Thanks
Recommeded approach would be to use different workspaces if you are dealing with different projects and different IDF versions.
If you want to swtich to a different IDF vesion for the same project, please follow the steps mentioned here https://medium.com/@kondal.kolipaka/swi ... 5d0ad9f7a0
Let me know if you see any issues here! I'll be happy to help!
Thanks
-
- Posts: 188
- Joined: Wed Jul 17, 2019 5:26 pm
Re: How can I use different IDF versions concurrently using Eclipse Plug IN
As mentioned here viewtopic.php?f=40&t=36331
Recommeded approach would be to use different workspaces if you are dealing with different projects and different IDF versions.
If you want to swtich to a different IDF vesion for the same project, please follow the steps mentioned here https://medium.com/@kondal.kolipaka/swi ... 5d0ad9f7a0
Let me know if you see any issues here! I'll be happy to help!
Thanks
Recommeded approach would be to use different workspaces if you are dealing with different projects and different IDF versions.
If you want to swtich to a different IDF vesion for the same project, please follow the steps mentioned here https://medium.com/@kondal.kolipaka/swi ... 5d0ad9f7a0
Let me know if you see any issues here! I'll be happy to help!
Thanks
Re: How can I use different IDF versions concurrently using Eclipse Plug IN
Kondal, well I have set up a new virgin system based on win11 pro. I'm getting a bit desperate now because a well running, long existing, error free compiling project does not work using the Eclipse plugin. Why I reach out is that I have different behavior of different ESP32-S2 modules on the same setup and I need ideas how to nail the issue down.
I changed the Jtag speed even down to 1000kHz I lowered the SRAM writing speed to 20MHz and each S2 module reacts different on the same setup.
I compiled and run the HTTP simple server example and it panics as well if the connect to the AP fails. Remember I try to switch between two IDF versions while I experience these issues. (5.0.4 and 5.1) The project was started using IDF 4.4.
How should I approach this to find the cause? Thanks for any idea
I changed the Jtag speed even down to 1000kHz I lowered the SRAM writing speed to 20MHz and each S2 module reacts different on the same setup.
I compiled and run the HTTP simple server example and it panics as well if the connect to the AP fails. Remember I try to switch between two IDF versions while I experience these issues. (5.0.4 and 5.1) The project was started using IDF 4.4.
How should I approach this to find the cause? Thanks for any idea
Re: How can I use different IDF versions concurrently using Eclipse Plug IN
Dear Kondal, using different IDF versions on the same machine does not work on my side.
All following procedures use Eclipse 2023-09 and latest IDE plugin
I installed IDF 5.1 from network using plugin. HTTP simple sample compiles and debugs. However panics when AP does not connect.
I installed a second eclipse environment in different folder and installed IDF 5.1 from prior generated local location. The HTTP simple example compiles and starts. Then I installed in this Eclipse environment IDF 5.0.1. And now everything is fucked up.
The HTTP sample does not flash and start in any environment. Note that each Eclipse is closed while the other is used.
Note as well that the hardware, debugger and board is used before and working fine. No changes made.
here some startup console views after having two IDF versions installed:
another one from the IDF 5.1
The corresponding debug console looks like this:
I will now clean up my system by deleting the .espressife folder and installing the tools for one version only.
All following procedures use Eclipse 2023-09 and latest IDE plugin
I installed IDF 5.1 from network using plugin. HTTP simple sample compiles and debugs. However panics when AP does not connect.
I installed a second eclipse environment in different folder and installed IDF 5.1 from prior generated local location. The HTTP simple example compiles and starts. Then I installed in this Eclipse environment IDF 5.0.1. And now everything is fucked up.
The HTTP sample does not flash and start in any environment. Note that each Eclipse is closed while the other is used.
Note as well that the hardware, debugger and board is used before and working fine. No changes made.
here some startup console views after having two IDF versions installed:
- 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.
- For bug reporting instructions, please see:
- Find the GDB manual and other documentation resources online at:
- <http://www.gnu.org/software/gdb/documentation/>.
- Info : [esp32s2] Target halted, PC=0x40031EDE, debug_reason=00000001
- Info : accepting 'gdb' connection on tcp/3333
- Warn : No symbols for FreeRTOS!
- Info : [esp32s2] Target halted, PC=0x40031EDE, debug_reason=00000001
- Error: Failed to get flash maps (-8)!
- Warn : Invalid magic number in app image!
- Warn : Failed to get flash mappings (-4)!
- Info : [esp32s2] Target halted, PC=0x40031EDE, debug_reason=00000001
- Info : Using flash bank 'esp32s2.irom' size 0 KB
- Info : [esp32s2] Target halted, PC=0x40031EDE, debug_reason=00000001
- Error: Failed to get flash maps (-8)!
- Warn : Invalid magic number in app image!
- Warn : Failed to get flash mappings (-4)!
- Info : [esp32s2] Target halted, PC=0x40031EDE, debug_reason=00000001
- Info : Using flash bank 'esp32s2.drom' size 0 KB
- Warn : Prefer GDB command "target extended-remote :3333" instead of "target remote :3333"
- Info : JTAG tap: esp32s2.cpu tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
- Info : [esp32s2] requesting target halt and executing a soft reset
- Info : [esp32s2] Debug controller was reset.
- Info : [esp32s2] Core was reset.
- Info : [esp32s2] Target halted, PC=0x4001963B, debug_reason=00000000
- Info : [esp32s2] Reset cause (3) - (Software core reset)
- Info : [esp32s2] Core was reset.
- Info : [esp32s2] Target halted, PC=0x40000400, debug_reason=00000000
- Info : [esp32s2] Reset cause (3) - (Software core reset)
- Info : JTAG tap: esp32s2.cpu tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
- Info : [esp32s2] requesting target halt and executing a soft reset
- Info : [esp32s2] Debug controller was reset.
- Info : [esp32s2] Core was reset.
- Info : [esp32s2] Target halted, PC=0x4000F382, debug_reason=00000000
- Info : [esp32s2] Reset cause (3) - (Software core reset)
- Info : [esp32s2] Core was reset.
- Info : [esp32s2] Target halted, PC=0x40000400, debug_reason=00000000
- Info : [esp32s2] Reset cause (3) - (Software core reset)
- Info : [esp32s2] Debug controller was reset.
- Info : [esp32s2] Core was reset.
- Info : [esp32s2] Target halted, PC=0x40000400, debug_reason=00000000
- Info : [esp32s2] Reset cause (3) - (Software core reset)
- Warn : esp_symbols table size (0) is not valid!
- Warn : esp_symbols table size (0) is not valid!
- Info : JTAG tap: esp32s2.cpu tap/device found: 0x120034e5 (mfg: 0x27
- 2 (Tensilica), part: 0x2003, ver: 0x1)
- Info : [esp32s2] requesting target halt and executing a soft reset
- Info : [esp32s2] Debug controller was reset.
- Info : [esp32s2] Core w
- as reset.
- Info : [esp32s2] Target halted, PC=0x4000F36D, debug_reason=00000000
- Info : [esp32s2] Reset cause (3) - (Software core reset)
- Info : [esp32s2] Core was reset.
- Info : [esp32s2] Target halted, PC=0x40000400, debug_reason=00000000
- Info : [esp32s2] Reset cause (3) - (Software core reset)
- Warn : address 0x4008b020 not writable
- Error: [esp32s2] Error writing instruction to memory: -4
- Error: [esp32s2] Failed to write breakpoint instruction (-4)!
- Error: [esp32s2] Failed to add SW breakpoint!
- Error: can't add breakpoint: unknown reason
- Warn : address 0x4008b060 not writable
- Error: [esp32s2] Error writing instruction to memory: -4
- Error: [esp32s2] Failed to write breakpoint instruction (-4)!
- Error: [esp32s2] Failed to add SW breakpoint!
- Error: can't add breakpoint: unknown reason
- Warn : address 0x4008b098 not writable
- Error: [esp32s2] Error writing instruction to memory: -4
- Error: [esp32s2] Failed to write breakpoint instruction (-4)!
- Error: [esp32s2] Failed to add SW breakpoint!
- Error: can't add breakpoint: unknown reason
- Warn : address 0x4008b09b not writable
- Error: [esp32s2] Error writing instruction to memory: -4
- Error: [esp32s2] Failed to write breakpoint instruction (-4)!
- Error: [esp32s2] Failed to add SW breakpoint!
- Error: can't add breakpoint: unknown reason
- Warn : address 0x4008b11a not writable
- Error: [esp32s2] Error writing instruction to memory: -4
- Error: [esp32s2] Failed to write breakpoint instruction (-4)!
- Error: [esp32s2] Failed to add SW breakpoint!
- Error: can't add breakpoint: unknown reason
- Cannot access memory at address 0x4008b060
- Cannot access memory at address 0x4008b11a
- Info : [esp32s2] Debug controller was reset.
- Info : [esp32s2] Core was reset.
- Info : [esp32s2] Target halted, PC=0x40000400, debug_reason=00000000
- Info : [esp32s2] Reset cause (3) - (Software core reset)
- 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.
- <https://www.gnu.org/software/gdb/bugs/>.
- For help, type "help".
- Type "apropos word" to search for commands related to "word".
- Info : accepting 'gdb' connection on tcp/3333
- Info : [esp32s2] Target halted, PC=0x4003084A, debug_reason=00000000
- Warn : No symbols for FreeRTOS!
- Info : [esp32s2] Target halted, PC=0x40031EDE, debug_reason=00000001
- Info : Flash mapping 0: 0x10020 -> 0x3f000020, 132 KB
- Info : Flash mapping 1: 0x40020 -> 0x40080020, 499 KB
- Info : Using flash bank 'esp32s2.irom' size 500 KB
- Info : [esp32s2] Target halted, PC=0x40031EDE, debug_reason=00000001
- Info : Flash mapping 0: 0x10020 -> 0x3f000020, 132 KB
- Info : Flash mapping 1: 0x40020 -> 0x40080020, 499 KB
- Info : Using flash bank 'esp32s2.drom' size 136 KB
- Warn : Prefer GDB command "target extended-remote :3333" instead of "target remote :3333"
- Info : JTAG tap: esp32s2.cpu tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
- Info : [esp32s2] requesting target halt and executing a soft reset
- Info : [esp32s2] Debug controller was reset.
- Info : [esp32s2] Core was reset.
- Info : [esp32s2] Target halted, PC=0x40019520, debug_reason=00000000
- Info : [esp32s2] Reset cause (3) - (Software core reset)
- Info : [esp32s2] Core was reset.
- Info : [esp32s2] Target halted, PC=0x40000400, debug_reason=00000000
- Info : [esp32s2] Reset cause (3) - (Software core reset)
- Info : JTAG tap: esp32s2.cpu tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
- Info : [esp32s2] requesting target halt and executing a soft reset
- Info : [esp32s2] Debug controller was reset.
- Info : [esp32s2] Core was reset.
- Info : [esp32s2] Target halted, PC=0x40007299, debug_reason=00000000
- Info : [esp32s2] Reset cause (3) - (Software core reset)
- Info : [esp32s2] Core was reset.
- Info : [esp32s2] Target halted, PC=0x40000400, debug_reason=00000000
- Info : [esp32s2] Reset cause (3) - (Software core reset)
- Note: automatically using hardware breakpoints for read-only addresses.
- No source file named C:\\maxill\\maxim-http\\main\\main.c.
- No source file named C:\\maxill\\maxim-http\\main\\main.c.
- Info : JTAG tap: esp32s2.cpu tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
- Info : [esp32s2] requesting target halt and executing a soft reset
- Info : [esp32s2] Debug controller was reset.
- Info : [esp32s2] Core was reset.
- Info : [esp32s2] Target halted, PC=0x40016102, debug_reason=00000000
- Info : [esp32s2] Reset cause (3) - (Software core reset)
- Info : [esp32s2] Core was reset.
- Info : [esp32s2] Target halted, PC=0x40000400, debug_reason=00000000
- Info : [esp32s2] Reset cause (3) - (Software core reset)
- Info : [esp32s2] Debug controller was reset.
- Info : [esp32s2] Core was reset.
- Info : [esp32s2] Target halted, PC=0x4001276A, debug_reason=00000000
- Info : [esp32s2] Reset cause (3) - (Software core reset)
- Info : [esp32s2] Debug controller was reset.
- Info : [esp32s2] Core was reset.
- Info : [esp32s2] Target halted, PC=0x4001276A, debug_reason=00000000
- Info : [esp32s2] Reset cause (3) - (Software core reset)
- Info : [esp32s2] Debug controller was reset.
- Info : [esp32s2] Core was reset.
- Info : [esp32s2] Target halted, PC=0x4000D89E, debug_reason=00000000
- Info : [esp32s2] Reset cause (3) - (Software core reset)
- Error: [esp32s2] DSR (FFFFFFFF) indicates target still busy!
- Error: [esp32s2] DSR (FFFFFFFF) indicates DIR instruction generated an exception!
- Error: [esp32s2] DSR (FFFFFFFF) indicates DIR instruction generated an overrun!
- Info : [esp32s2] Debug controller was reset.
- Info : [esp32s2] Core was reset.
- Info : [esp32s2] Target halted, PC=0x4001276A, debug_reason=00000000
- Info : [esp32s2] Reset cause (3) - (Software core reset)
- Info : [esp32s2] Debug controller was reset.
- Info : [esp32s2] Core was reset.
- Info : [esp32s2] Target halted, PC=0x40011275, debug_reason=00000000
- Info : [esp32s2] Reset cause (3) - (Software core reset)
- Info : [esp32s2] Debug controller was reset.
- Info : [esp32s2] Core was reset.
- Info : [esp32s2] Target halted, PC=0x4001ABCA, debug_reason=00000000
- Info : [esp32s2] Reset cause (3) - (Software core reset)
- Info : [esp32s2] Debug controller was reset.
- Info : [esp32s2] Core was reset.
- Info : [esp32s2] Target halted, PC=0x4001ABC6, debug_reason=00000000
- Info : [esp32s2] Reset cause (3) - (Software core reset)
- Info : [esp32s2] Debug controller was reset.
- Info : [esp32s2] Core was reset.
- Info : [esp32s2] Target halted, PC=0x40012B60, debug_reason=00000000
- Info : [esp32s2] Reset cause (3) - (Software core reset)
- Info : [esp32s2] Debug controller was reset.
- Info : [esp32s2] Core was reset.
- Info : [esp32s2] Target halted, PC=0x4001276F, debug_reason=00000000
- Info : [esp32s2] Reset cause (3) - (Software core reset)
- Info : [esp32s2] Debug controller was reset.
- Info : [esp32s2] Core was reset.
- 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.
- Type "show configuration" for configuration details.
- For bug reporting instructions, please see:
- Find the GDB manual and other documentation resources online at:
- <http://www.gnu.org/software/gdb/documentation/>.
- Type "apropos word" to search for commands related to "word".
- Note: automatically using hardware breakpoints for read-only addresses.
- Quit
Re: How can I use different IDF versions concurrently using Eclipse Plug IN
So here is next step, again no success
1. I deleted the user\...\.espressife folder
2. I used Eclipse plugin to download and install IDF 5.1.2
checked if tools installed OK
3. I deleted the build folder of the previous installed HTTP simple server example
4. I compiled, worked fine no errors no warnings
5. I run debug configuration, flashing via Jtag worked but stopped at eloop.c line 63 eloop_init()
7. I canceled debugging.
8. I ran debug configuration again, however the program did not stop at breakpoint because the debugger could not set the break point
consol output
this time I have only one IDF version installed. I need to get this running. Why does it seem to me as a unusable IDE package?
New computer, Win11 pro, all fresh downloads, nothing is working.
What am I doing wrong ?
1. I deleted the user\...\.espressife folder
2. I used Eclipse plugin to download and install IDF 5.1.2
checked if tools installed OK
- Executing C:\Users\ralph\AppData\Local\Programs\Python\Python312\python.exe C:\IDF-5-1-2\esp-idf-v5.1.2\tools\idf_tools.py list
- * xtensa-esp-elf-gdb: GDB for Xtensa
- - 12.1_20221002 (recommended, installed)
- * riscv32-esp-elf-gdb: GDB for RISC-V
- - 12.1_20221002 (recommended, installed)
- * xtensa-esp32-elf: Toolchain for Xtensa (ESP32) based on GCC
- - esp-12.2.0_20230208 (recommended, installed)
- * xtensa-esp32s2-elf: Toolchain for Xtensa (ESP32-S2) based on GCC
- - esp-12.2.0_20230208 (recommended, installed)
- * xtensa-esp32s3-elf: Toolchain for Xtensa (ESP32-S3) based on GCC
- - esp-12.2.0_20230208 (recommended, installed)
- * esp-clang: Toolchain for all Espressif chips based on clang (optional)
- - 15.0.0-23786128ae (recommended, installed)
- * riscv32-esp-elf: Toolchain for 32-bit RISC-V based on GCC
- - esp-12.2.0_20230208 (recommended, installed)
- * esp32ulp-elf: Toolchain for ESP32 ULP coprocessor
- - 2.35_20220830 (recommended, installed)
- * cmake: CMake build system
- - 3.24.0 (recommended, installed)
- - 3.16.3 (supported)
- * openocd-esp32: OpenOCD for ESP32
- - v0.12.0-esp32-20230921 (recommended, installed)
- * ninja: Ninja build system
- - 1.10.2 (recommended, installed)
- * idf-exe: IDF wrapper tool for Windows
- - 1.0.3 (recommended, installed)
- * ccache: Ccache (compiler cache)
- - 4.8 (recommended, installed)
- * dfu-util: dfu-util (Device Firmware Upgrade Utilities)
- - 0.11 (recommended, installed)
- * esp-rom-elfs: ESP ROM ELFs
- - 20230320 (recommended, installed)
- OK
4. I compiled, worked fine no errors no warnings
5. I run debug configuration, flashing via Jtag worked but stopped at eloop.c line 63 eloop_init()
7. I canceled debugging.
8. I ran debug configuration again, however the program did not stop at breakpoint because the debugger could not set the break point
consol output
- Copyright (C) 2022 Free Software Foundation, Inc.
- For help, type "help".
- Info : accepting 'gdb' connection on tcp/3333
- Info : [esp32s2] Target halted, PC=0x40029E4E, debug_reason=00000001
- Warn : No symbols for FreeRTOS!
- Info : [esp32s2] Target halted, PC=0x40029E4E, debug_reason=00000001
- Error: Failed to get flash maps (-8)!
- Warn : Invalid magic number in app image!
- War
- n : Failed to get flash mappings (-4)!
- Info : [esp32s2] Target halted, PC=0x40029E4E, debug_reason=00000001
- Info : Using flash bank 'esp32s2.irom' size 0 KB
- Info : [esp32s2] Target halted, PC=0x40029E4E, debug_reason=00000001
- Error: Failed to get flash maps (-8)!
- Warn : Invalid magic number in app image!
- Warn : Failed to get flash mappings (-4)!
- Info : [esp32s2] Target halted, PC=0x40029E4E, debug_reason=00000001
- Info : Using flash bank 'esp32s2.drom' size 0 KB
- Warn : Prefer GDB command "target extended-remote :3333" instead of "target remote :3333"
- Info : JTAG tap: esp32s2.cpu tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
- Info : [esp32s2] requesting target halt and executing a soft reset
- Info : [esp32s2] Debug controller was reset.
- Info : [esp32s2] Core was reset.
- Info : [esp32s2] Target halted, PC=0x4001963B, debug_reason=00000000
- Info : [esp32s2] Reset cause (3) - (Software core reset)
- Info : [esp32s2] Core was reset.
- Info : [esp32s2] Target halted, PC=0x40000400, debug_reason=00000000
- Info : [esp32s2] Reset cause (3) - (Software core reset)
- Info : JTAG tap: esp32s2.cpu tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
- Info : [esp32s2] requesting target halt and executing a soft reset
- Info : [esp32s2] Debug controller was reset.
- Info : [esp32s2] Core was reset.
- Info : [esp32s2] Target halted, PC=0x4000E4A0, debug_reason=00000000
- Info : [esp32s2] Reset cause (3) - (Software core reset)
- Info : [esp32s2] Core was reset.
- Info : [esp32s2] Target halted, PC=0x40000400, debug_reason=00000000
- Info : [esp32s2] Reset cause (3) - (Software core reset)
- Info : JTAG tap: esp32s2.cpu tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
- Info : [esp32s2] requesting target halt and executing a soft reset
- Info : [esp32s2] Debug controller was reset.
- Info : [esp32s2] Core was reset.
- Info : [esp32s2] Target halted, PC=0x40007299, debug_reason=00000000
- Info : [esp32s2] Reset cause (3) - (Software core reset)
- Info : [esp32s2] Core was reset.
- Info : [esp32s2] Target halted, PC=0x40000400, debug_reason=00000000
- Info : [esp32s2] Reset cause (3) - (Software core reset)
- Warn : address 0x40087cfc not writable
- Error: [esp32s2] Error writing instruction to memory: -4
- Error: [esp32s2] Failed to write breakpoint instruction (-4)!
- Error: [esp32s2] Failed to add SW breakpoint!
- Error: can't add breakpoint: unknown reason
- Warning:
- Cannot access memory at address 0x40087cfc
- Command aborted.
- Info : [esp32s2] Debug controller was reset.
- Info : [esp32s2] Core was reset.
- Info : [esp32s2] Target halted, PC=0x40000400, debug_reason=00000000
- Info : [esp32s2] Reset cause (3) - (Software core reset)
- Info : [esp32s2] Debug controller was reset.
- Info : [esp32s2] Core was reset.
- Info : [esp32s2] Target halted, PC=0x40000400, debug_reason=00000000
- Info : [esp32s2] Reset cause (3) - (Software core reset)
- Info : [esp32s2] Debug controller was reset.
- Info : [esp32s2] Core was reset.
- Info : [esp32s2] Target halted, PC=0x40000400, debug_reason=00000000
- Info : [esp32s2] Reset cause (3) - (Software core reset)
- Info : [esp32s2] Debug controller was reset.
- Info : [esp32s2] Core was reset.
- Info : [esp32s2] Target halted, PC=0x40000400, debug_reason=00000000
- Info : [esp32s2] Reset cause (3) - (Software core reset)
- Info : [esp32s2] Debug controller was reset.
- Info : [esp32s2] Core was reset.
- Info : [esp32s2] Target halted, PC=0x40000400, debug_reason=00000000
- Info : [esp32s2] Reset cause (3) - (Software core reset)
- Info : [esp32s2] Debug controller was reset.
- Info : [esp32s2] Core was reset.
- Info : [esp32s2] Target halted, PC=0x40000400, debug_reason=00000000
- Info : [esp32s2] Reset cause (3) - (Software core reset)
- Info : [esp32s2] Debug controller was reset.
- Info : [esp32s2] Core was reset.
- Info : [esp32s2] Target halted, PC=0x40000400, debug_reason=00000000
- Info : [esp32s2] Reset cause (3) - (Software core reset)
New computer, Win11 pro, all fresh downloads, nothing is working.
What am I doing wrong ?
Re: How can I use different IDF versions concurrently using Eclipse Plug IN
so, update: in the not working attempt I have been using Eclipse 2023-09 and installed ESP-IDF from Marketplace.
As I do need to update an existing project I do need this installation on my new development machine working.
I tried using Eclipse 2023-03 and installed ESP-IDF plugin from the link given here:
https://github.com/espressif/idf-eclips ... stallation
I figured out that with this installation a bunch of other options are installed by default as well. I deselected anything else and had only IDF and cmake editor selected. Now I can compile AND debug the HTTP server example. Problem remaining that it panics when AP does not connect.
Sorry it worked better but after 2 times restarting a debug launch nothing is working again.
after closing Eclipse and reopening the debug launch failed with this message
As I do need to update an existing project I do need this installation on my new development machine working.
I tried using Eclipse 2023-03 and installed ESP-IDF plugin from the link given here:
https://github.com/espressif/idf-eclips ... stallation
I figured out that with this installation a bunch of other options are installed by default as well. I deselected anything else and had only IDF and cmake editor selected. Now I can compile AND debug the HTTP server example. Problem remaining that it panics when AP does not connect.
Sorry it worked better but after 2 times restarting a debug launch nothing is working again.
Code: Select all
An internal error occurred during: "Starting OpenOCD".
RequestMonitor: Sequence "", result for executing step #1 = Status ERROR: org.eclipse.cdt.dsf code=10005
Request for monitor: 'RequestMonitor
(org.eclipse.embedcdt.debug.gdbjtag.core.dsf.GnuMcuGdbServerBackend$GdbServerStep$1@3248dbf9): Status OK:
unknown code=0 OK' resulted in a rejected execution exception., done() method called more than once
after closing Eclipse and reopening the debug launch failed with this message
Code: Select all
Error in services launch sequence
Starting OpenOCD timed out.
Who is online
Users browsing this forum: No registered users and 8 guests