How can I use different IDF versions concurrently using Eclipse Plug IN

Post Reply
RalphD
Posts: 103
Joined: Thu Nov 25, 2021 9:02 pm

How can I use different IDF versions concurrently using Eclipse Plug IN

Postby RalphD » Tue Oct 17, 2023 7:36 pm

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
Top
ESP_kondalkolipaka
Posts: 188
Joined: Wed Jul 17, 2019 5:26 pm

Re: How can I use different IDF versions concurrently using Eclipse Plug IN

Postby ESP_kondalkolipaka » Tue Oct 24, 2023 2:45 pm

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
Top
ESP_kondalkolipaka
Posts: 188
Joined: Wed Jul 17, 2019 5:26 pm

Re: How can I use different IDF versions concurrently using Eclipse Plug IN

Postby ESP_kondalkolipaka » Tue Oct 24, 2023 2:45 pm

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
Top
RalphD
Posts: 103
Joined: Thu Nov 25, 2021 9:02 pm

Re: How can I use different IDF versions concurrently using Eclipse Plug IN

Postby RalphD » Thu Nov 16, 2023 12:34 pm

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
Top
RalphD
Posts: 103
Joined: Thu Nov 25, 2021 9:02 pm

Re: How can I use different IDF versions concurrently using Eclipse Plug IN

Postby RalphD » Thu Nov 16, 2023 8:34 pm

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:
Code: [Select all] [Expand/Collapse]
  1.  License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
  2. This is free software: you are free to change and redistribute it.
  3. There is NO WARRANTY, to the extent permitted by law.
  4. For bug reporting instructions, please see:
  5. Find the GDB manual and other documentation resources online at:
  6.     <http://www.gnu.org/software/gdb/documentation/>.
  7. Info : [esp32s2] Target halted, PC=0x40031EDE, debug_reason=00000001
  8. Info : accepting 'gdb' connection on tcp/3333
  9. Warn : No symbols for FreeRTOS!
  10. Info : [esp32s2] Target halted, PC=0x40031EDE, debug_reason=00000001
  11. Error: Failed to get flash maps (-8)!
  12. Warn : Invalid magic number in app image!
  13. Warn : Failed to get flash mappings (-4)!
  14. Info : [esp32s2] Target halted, PC=0x40031EDE, debug_reason=00000001
  15. Info : Using flash bank 'esp32s2.irom' size 0 KB
  16. Info : [esp32s2] Target halted, PC=0x40031EDE, debug_reason=00000001
  17. Error: Failed to get flash maps (-8)!
  18. Warn : Invalid magic number in app image!
  19. Warn : Failed to get flash mappings (-4)!
  20. Info : [esp32s2] Target halted, PC=0x40031EDE, debug_reason=00000001
  21. Info : Using flash bank 'esp32s2.drom' size 0 KB
  22. Warn : Prefer GDB command "target extended-remote :3333" instead of "target remote :3333"
  23. Info : JTAG tap: esp32s2.cpu tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
  24. Info : [esp32s2] requesting target halt and executing a soft reset
  25. Info : [esp32s2] Debug controller was reset.
  26. Info : [esp32s2] Core was reset.
  27. Info : [esp32s2] Target halted, PC=0x4001963B, debug_reason=00000000
  28. Info : [esp32s2] Reset cause (3) - (Software core reset)
  29. Info : [esp32s2] Core was reset.
  30. Info : [esp32s2] Target halted, PC=0x40000400, debug_reason=00000000
  31. Info : [esp32s2] Reset cause (3) - (Software core reset)
  32. Info : JTAG tap: esp32s2.cpu tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
  33. Info : [esp32s2] requesting target halt and executing a soft reset
  34. Info : [esp32s2] Debug controller was reset.
  35. Info : [esp32s2] Core was reset.
  36. Info : [esp32s2] Target halted, PC=0x4000F382, debug_reason=00000000
  37. Info : [esp32s2] Reset cause (3) - (Software core reset)
  38. Info : [esp32s2] Core was reset.
  39. Info : [esp32s2] Target halted, PC=0x40000400, debug_reason=00000000
  40. Info : [esp32s2] Reset cause (3) - (Software core reset)
  41. Info : [esp32s2] Debug controller was reset.
  42. Info : [esp32s2] Core was reset.
  43. Info : [esp32s2] Target halted, PC=0x40000400, debug_reason=00000000
  44. Info : [esp32s2] Reset cause (3) - (Software core reset)
  45. Warn : esp_symbols table size (0) is not valid!
  46. Warn : esp_symbols table size (0) is not valid!
  47. Info : JTAG tap: esp32s2.cpu tap/device found: 0x120034e5 (mfg: 0x27
  48. 2 (Tensilica), part: 0x2003, ver: 0x1)
  49. Info : [esp32s2] requesting target halt and executing a soft reset
  50. Info : [esp32s2] Debug controller was reset.
  51. Info : [esp32s2] Core w
  52. as reset.
  53. Info : [esp32s2] Target halted, PC=0x4000F36D, debug_reason=00000000
  54. Info : [esp32s2] Reset cause (3) - (Software core reset)
  55. Info : [esp32s2] Core was reset.
  56. Info : [esp32s2] Target halted, PC=0x40000400, debug_reason=00000000
  57. Info : [esp32s2] Reset cause (3) - (Software core reset)
  58. Warn : address 0x4008b020 not writable
  59. Error: [esp32s2] Error writing instruction to memory: -4
  60. Error: [esp32s2] Failed to write breakpoint instruction (-4)!
  61. Error: [esp32s2] Failed to add SW breakpoint!
  62. Error: can't add breakpoint: unknown reason
  63. Warn : address 0x4008b060 not writable
  64. Error: [esp32s2] Error writing instruction to memory: -4
  65. Error: [esp32s2] Failed to write breakpoint instruction (-4)!
  66. Error: [esp32s2] Failed to add SW breakpoint!
  67. Error: can't add breakpoint: unknown reason
  68. Warn : address 0x4008b098 not writable
  69. Error: [esp32s2] Error writing instruction to memory: -4
  70. Error: [esp32s2] Failed to write breakpoint instruction (-4)!
  71. Error: [esp32s2] Failed to add SW breakpoint!
  72. Error: can't add breakpoint: unknown reason
  73. Warn : address 0x4008b09b not writable
  74. Error: [esp32s2] Error writing instruction to memory: -4
  75. Error: [esp32s2] Failed to write breakpoint instruction (-4)!
  76. Error: [esp32s2] Failed to add SW breakpoint!
  77. Error: can't add breakpoint: unknown reason
  78. Warn : address 0x4008b11a not writable
  79. Error: [esp32s2] Error writing instruction to memory: -4
  80. Error: [esp32s2] Failed to write breakpoint instruction (-4)!
  81. Error: [esp32s2] Failed to add SW breakpoint!
  82. Error: can't add breakpoint: unknown reason
  83. Cannot access memory at address 0x4008b060
  84. Cannot access memory at address 0x4008b11a
  85.  
  86. Info : [esp32s2] Debug controller was reset.
  87. Info : [esp32s2] Core was reset.
  88. Info : [esp32s2] Target halted, PC=0x40000400, debug_reason=00000000
  89. Info : [esp32s2] Reset cause (3) - (Software core reset)
GeSHi © Codebox Plus Extension
another one from the IDF 5.1
Code: [Select all] [Expand/Collapse]
  1. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
  2. This is free software: you are free to change and redistribute it.
  3. There is NO WARRANTY, to the extent permitted by law.
  4. <https://www.gnu.org/software/gdb/bugs/>.
  5.  
  6.  
  7. For help, type "help".
  8. Type "apropos word" to search for commands related to "word".
  9. Info : accepting 'gdb' connection on tcp/3333
  10. Info : [esp32s2] Target halted, PC=0x4003084A, debug_reason=00000000
  11. Warn : No symbols for FreeRTOS!
  12. Info : [esp32s2] Target halted, PC=0x40031EDE, debug_reason=00000001
  13. Info : Flash mapping 0: 0x10020 -> 0x3f000020, 132 KB
  14. Info : Flash mapping 1: 0x40020 -> 0x40080020, 499 KB
  15. Info : Using flash bank 'esp32s2.irom' size 500 KB
  16. Info : [esp32s2] Target halted, PC=0x40031EDE, debug_reason=00000001
  17. Info : Flash mapping 0: 0x10020 -> 0x3f000020, 132 KB
  18. Info : Flash mapping 1: 0x40020 -> 0x40080020, 499 KB
  19. Info : Using flash bank 'esp32s2.drom' size 136 KB
  20. Warn : Prefer GDB command "target extended-remote :3333" instead of "target remote :3333"
  21. Info : JTAG tap: esp32s2.cpu tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
  22. Info : [esp32s2] requesting target halt and executing a soft reset
  23. Info : [esp32s2] Debug controller was reset.
  24. Info : [esp32s2] Core was reset.
  25. Info : [esp32s2] Target halted, PC=0x40019520, debug_reason=00000000
  26. Info : [esp32s2] Reset cause (3) - (Software core reset)
  27. Info : [esp32s2] Core was reset.
  28. Info : [esp32s2] Target halted, PC=0x40000400, debug_reason=00000000
  29. Info : [esp32s2] Reset cause (3) - (Software core reset)
  30. Info : JTAG tap: esp32s2.cpu tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
  31. Info : [esp32s2] requesting target halt and executing a soft reset
  32. Info : [esp32s2] Debug controller was reset.
  33. Info : [esp32s2] Core was reset.
  34. Info : [esp32s2] Target halted, PC=0x40007299, debug_reason=00000000
  35. Info : [esp32s2] Reset cause (3) - (Software core reset)
  36. Info : [esp32s2] Core was reset.
  37. Info : [esp32s2] Target halted, PC=0x40000400, debug_reason=00000000
  38. Info : [esp32s2] Reset cause (3) - (Software core reset)
  39. Note: automatically using hardware breakpoints for read-only addresses.
  40. No source file named C:\\maxill\\maxim-http\\main\\main.c.
  41. No source file named C:\\maxill\\maxim-http\\main\\main.c.
  42. Info : JTAG tap: esp32s2.cpu tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
  43. Info : [esp32s2] requesting target halt and executing a soft reset
  44. Info : [esp32s2] Debug controller was reset.
  45. Info : [esp32s2] Core was reset.
  46. Info : [esp32s2] Target halted, PC=0x40016102, debug_reason=00000000
  47. Info : [esp32s2] Reset cause (3) - (Software core reset)
  48. Info : [esp32s2] Core was reset.
  49. Info : [esp32s2] Target halted, PC=0x40000400, debug_reason=00000000
  50. Info : [esp32s2] Reset cause (3) - (Software core reset)
  51. Info : [esp32s2] Debug controller was reset.
  52. Info : [esp32s2] Core was reset.
  53. Info : [esp32s2] Target halted, PC=0x4001276A, debug_reason=00000000
  54. Info : [esp32s2] Reset cause (3) - (Software core reset)
  55. Info : [esp32s2] Debug controller was reset.
  56. Info : [esp32s2] Core was reset.
  57. Info : [esp32s2] Target halted, PC=0x4001276A, debug_reason=00000000
  58. Info : [esp32s2] Reset cause (3) - (Software core reset)
  59. Info : [esp32s2] Debug controller was reset.
  60. Info : [esp32s2] Core was reset.
  61. Info : [esp32s2] Target halted, PC=0x4000D89E, debug_reason=00000000
  62. Info : [esp32s2] Reset cause (3) - (Software core reset)
  63. Error: [esp32s2] DSR (FFFFFFFF) indicates target still busy!
  64. Error: [esp32s2] DSR (FFFFFFFF) indicates DIR instruction generated an exception!
  65. Error: [esp32s2] DSR (FFFFFFFF) indicates DIR instruction generated an overrun!
  66. Info : [esp32s2] Debug controller was reset.
  67. Info : [esp32s2] Core was reset.
  68. Info : [esp32s2] Target halted, PC=0x4001276A, debug_reason=00000000
  69. Info : [esp32s2] Reset cause (3) - (Software core reset)
  70. Info : [esp32s2] Debug controller was reset.
  71. Info : [esp32s2] Core was reset.
  72. Info : [esp32s2] Target halted, PC=0x40011275, debug_reason=00000000
  73. Info : [esp32s2] Reset cause (3) - (Software core reset)
  74. Info : [esp32s2] Debug controller was reset.
  75. Info : [esp32s2] Core was reset.
  76. Info : [esp32s2] Target halted, PC=0x4001ABCA, debug_reason=00000000
  77. Info : [esp32s2] Reset cause (3) - (Software core reset)
  78. Info : [esp32s2] Debug controller was reset.
  79. Info : [esp32s2] Core was reset.
  80. Info : [esp32s2] Target halted, PC=0x4001ABC6, debug_reason=00000000
  81. Info : [esp32s2] Reset cause (3) - (Software core reset)
  82. Info : [esp32s2] Debug controller was reset.
  83. Info : [esp32s2] Core was reset.
  84. Info : [esp32s2] Target halted, PC=0x40012B60, debug_reason=00000000
  85. Info : [esp32s2] Reset cause (3) - (Software core reset)
  86. Info : [esp32s2] Debug controller was reset.
  87. Info : [esp32s2] Core was reset.
  88. Info : [esp32s2] Target halted, PC=0x4001276F, debug_reason=00000000
  89. Info : [esp32s2] Reset cause (3) - (Software core reset)
  90. Info : [esp32s2] Debug controller was reset.
  91. Info : [esp32s2] Core was reset.
GeSHi © Codebox Plus Extension
The corresponding debug console looks like this:
Code: [Select all] [Expand/Collapse]
  1. Copyright (C) 2022 Free Software Foundation, Inc.
  2. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
  3. This is free software: you are free to change and redistribute it.
  4. There is NO WARRANTY, to the extent permitted by law.
  5. Type "show copying" and "show warranty" for details.
  6. Type "show configuration" for configuration details.
  7. For bug reporting instructions, please see:
  8. Find the GDB manual and other documentation resources online at:
  9.     <http://www.gnu.org/software/gdb/documentation/>.
  10.  
  11. Type "apropos word" to search for commands related to "word".
  12. Note: automatically using hardware breakpoints for read-only addresses.
  13. Quit
GeSHi © Codebox Plus Extension
I will now clean up my system by deleting the .espressife folder and installing the tools for one version only.
Top
RalphD
Posts: 103
Joined: Thu Nov 25, 2021 9:02 pm

Re: How can I use different IDF versions concurrently using Eclipse Plug IN

Postby RalphD » Thu Nov 16, 2023 11:26 pm

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
Code: [Select all] [Expand/Collapse]
  1. 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
  2. * xtensa-esp-elf-gdb: GDB for Xtensa
  3.   - 12.1_20221002 (recommended, installed)
  4. * riscv32-esp-elf-gdb: GDB for RISC-V
  5.   - 12.1_20221002 (recommended, installed)
  6. * xtensa-esp32-elf: Toolchain for Xtensa (ESP32) based on GCC
  7.   - esp-12.2.0_20230208 (recommended, installed)
  8. * xtensa-esp32s2-elf: Toolchain for Xtensa (ESP32-S2) based on GCC
  9.   - esp-12.2.0_20230208 (recommended, installed)
  10. * xtensa-esp32s3-elf: Toolchain for Xtensa (ESP32-S3) based on GCC
  11.   - esp-12.2.0_20230208 (recommended, installed)
  12. * esp-clang: Toolchain for all Espressif chips based on clang (optional)
  13.   - 15.0.0-23786128ae (recommended, installed)
  14. * riscv32-esp-elf: Toolchain for 32-bit RISC-V based on GCC
  15.   - esp-12.2.0_20230208 (recommended, installed)
  16. * esp32ulp-elf: Toolchain for ESP32 ULP coprocessor
  17.   - 2.35_20220830 (recommended, installed)
  18. * cmake: CMake build system
  19.   - 3.24.0 (recommended, installed)
  20.   - 3.16.3 (supported)
  21. * openocd-esp32: OpenOCD for ESP32
  22.   - v0.12.0-esp32-20230921 (recommended, installed)
  23. * ninja: Ninja build system
  24.   - 1.10.2 (recommended, installed)
  25. * idf-exe: IDF wrapper tool for Windows
  26.   - 1.0.3 (recommended, installed)
  27. * ccache: Ccache (compiler cache)
  28.   - 4.8 (recommended, installed)
  29. * dfu-util: dfu-util (Device Firmware Upgrade Utilities)
  30.   - 0.11 (recommended, installed)
  31. * esp-rom-elfs: ESP ROM ELFs
  32.   - 20230320 (recommended, installed)
  33. OK
GeSHi © Codebox Plus Extension
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
Code: [Select all] [Expand/Collapse]
  1. Copyright (C) 2022 Free Software Foundation, Inc.
  2.  
  3.  
  4. For help, type "help".
  5. Info : accepting 'gdb' connection on tcp/3333
  6. Info : [esp32s2] Target halted, PC=0x40029E4E, debug_reason=00000001
  7. Warn : No symbols for FreeRTOS!
  8. Info : [esp32s2] Target halted, PC=0x40029E4E, debug_reason=00000001
  9. Error: Failed to get flash maps (-8)!
  10. Warn : Invalid magic number in app image!
  11. War
  12. n : Failed to get flash mappings (-4)!
  13. Info : [esp32s2] Target halted, PC=0x40029E4E, debug_reason=00000001
  14. Info : Using flash bank 'esp32s2.irom' size 0 KB
  15. Info : [esp32s2] Target halted, PC=0x40029E4E, debug_reason=00000001
  16. Error: Failed to get flash maps (-8)!
  17. Warn : Invalid magic number in app image!
  18. Warn : Failed to get flash mappings (-4)!
  19. Info : [esp32s2] Target halted, PC=0x40029E4E, debug_reason=00000001
  20. Info : Using flash bank 'esp32s2.drom' size 0 KB
  21. Warn : Prefer GDB command "target extended-remote :3333" instead of "target remote :3333"
  22. Info : JTAG tap: esp32s2.cpu tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
  23. Info : [esp32s2] requesting target halt and executing a soft reset
  24. Info : [esp32s2] Debug controller was reset.
  25. Info : [esp32s2] Core was reset.
  26. Info : [esp32s2] Target halted, PC=0x4001963B, debug_reason=00000000
  27. Info : [esp32s2] Reset cause (3) - (Software core reset)
  28. Info : [esp32s2] Core was reset.
  29. Info : [esp32s2] Target halted, PC=0x40000400, debug_reason=00000000
  30. Info : [esp32s2] Reset cause (3) - (Software core reset)
  31. Info : JTAG tap: esp32s2.cpu tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
  32. Info : [esp32s2] requesting target halt and executing a soft reset
  33. Info : [esp32s2] Debug controller was reset.
  34. Info : [esp32s2] Core was reset.
  35. Info : [esp32s2] Target halted, PC=0x4000E4A0, debug_reason=00000000
  36. Info : [esp32s2] Reset cause (3) - (Software core reset)
  37. Info : [esp32s2] Core was reset.
  38. Info : [esp32s2] Target halted, PC=0x40000400, debug_reason=00000000
  39. Info : [esp32s2] Reset cause (3) - (Software core reset)
  40. Info : JTAG tap: esp32s2.cpu tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
  41. Info : [esp32s2] requesting target halt and executing a soft reset
  42. Info : [esp32s2] Debug controller was reset.
  43. Info : [esp32s2] Core was reset.
  44. Info : [esp32s2] Target halted, PC=0x40007299, debug_reason=00000000
  45. Info : [esp32s2] Reset cause (3) - (Software core reset)
  46. Info : [esp32s2] Core was reset.
  47. Info : [esp32s2] Target halted, PC=0x40000400, debug_reason=00000000
  48. Info : [esp32s2] Reset cause (3) - (Software core reset)
  49. Warn : address 0x40087cfc not writable
  50. Error: [esp32s2] Error writing instruction to memory: -4
  51. Error: [esp32s2] Failed to write breakpoint instruction (-4)!
  52. Error: [esp32s2] Failed to add SW breakpoint!
  53. Error: can't add breakpoint: unknown reason
  54. Warning:
  55. Cannot access memory at address 0x40087cfc
  56. Command aborted.
  57. Info : [esp32s2] Debug controller was reset.
  58. Info : [esp32s2] Core was reset.
  59. Info : [esp32s2] Target halted, PC=0x40000400, debug_reason=00000000
  60. Info : [esp32s2] Reset cause (3) - (Software core reset)
  61. Info : [esp32s2] Debug controller was reset.
  62. Info : [esp32s2] Core was reset.
  63. Info : [esp32s2] Target halted, PC=0x40000400, debug_reason=00000000
  64. Info : [esp32s2] Reset cause (3) - (Software core reset)
  65. Info : [esp32s2] Debug controller was reset.
  66. Info : [esp32s2] Core was reset.
  67. Info : [esp32s2] Target halted, PC=0x40000400, debug_reason=00000000
  68. Info : [esp32s2] Reset cause (3) - (Software core reset)
  69. Info : [esp32s2] Debug controller was reset.
  70. Info : [esp32s2] Core was reset.
  71. Info : [esp32s2] Target halted, PC=0x40000400, debug_reason=00000000
  72. Info : [esp32s2] Reset cause (3) - (Software core reset)
  73. Info : [esp32s2] Debug controller was reset.
  74. Info : [esp32s2] Core was reset.
  75. Info : [esp32s2] Target halted, PC=0x40000400, debug_reason=00000000
  76. Info : [esp32s2] Reset cause (3) - (Software core reset)
  77. Info : [esp32s2] Debug controller was reset.
  78. Info : [esp32s2] Core was reset.
  79. Info : [esp32s2] Target halted, PC=0x40000400, debug_reason=00000000
  80. Info : [esp32s2] Reset cause (3) - (Software core reset)
  81. Info : [esp32s2] Debug controller was reset.
  82. Info : [esp32s2] Core was reset.
  83. Info : [esp32s2] Target halted, PC=0x40000400, debug_reason=00000000
  84. Info : [esp32s2] Reset cause (3) - (Software core reset)
GeSHi © Codebox Plus Extension
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 ?
Top
RalphD
Posts: 103
Joined: Thu Nov 25, 2021 9:02 pm

Re: How can I use different IDF versions concurrently using Eclipse Plug IN

Postby RalphD » Fri Nov 17, 2023 4:02 pm

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.

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.
Top
Post Reply

Return to “IDEs for ESP-IDF”

Who is online

Users browsing this forum: No registered users and 64 guests