Page 1 of 1

ESP32-S2 what IDF versions should be selected as latest?

Posted: Tue Oct 17, 2023 7:54 pm
by RalphD
The background is that we do not manage to migrate our firmware from version 5.0.1 to 5.1. The firmware does not even reach to the point that a core dump can be created. Does 5.1 not support the S2 ?

Re: ESP32-S2 what IDF versions should be selected as latest?

Posted: Wed Oct 18, 2023 5:44 am
by ESP_Sprite
Yes, it does. Without more info, there's not much more we can say, though. Did you make sure to update your submodules, have you tried a clean build (remove the build folder and retry building)?

Re: ESP32-S2 what IDF versions should be selected as latest?

Posted: Sun Nov 05, 2023 11:26 am
by RalphD
Yes but it came out that my computer had some main issues and needed to be trashed.

Re: ESP32-S2 what IDF versions should be selected as latest?

Posted: Thu Nov 23, 2023 3:02 pm
by RalphD
So OK I am back to life with a new computer and problem is exactly the same. Our long term project does not run with IDF 5.1.2 and reverting it to 5.0.4 fails even it used to work before on 5.0.1

What information should I prepare?

this is the GDB output on the terminal. Never saw this before
  1. GNU gdb (esp-gdb) 12.1_20221002
  2. Copyright (C) 2022 Free Software Foundation, Inc.
  3. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
  4. This is free software: you are free to change and redistribute it.
  5. There is NO WARRANTY, to the extent permitted by law.
  6. Type "show copying" and "show warranty" for details.
  7. This GDB was configured as "--host=x86_64-w64-mingw32 --target=xtensa-esp-elf".
  8. Type "show configuration" for configuration details.
  9. For bug reporting instructions, please see:
  10. Find the GDB manual and other documentation resources online at:
  11.     <http://www.gnu.org/software/gdb/documentation/>.
  12. Info : accepting 'gdb' connection on tcp/3333
  13. Warn : No symbols for FreeRTOS!
  14. Error: No working memory available. Specify -work-area-phys to target.
  15. Warn : not enough working area available(requested 776)
  16. Error: no working area available, can't alloc space for stub data!
  17. Error: Failed to run flasher stub (-308)!
  18. Warn : Failed to get flash mappings (-308)!
  19. Error: No working memory available. Specify -work-area-phys to target.
  20. Warn : not enough working area available(requested 776)
  21. Error: no working area available, can't alloc space for stub data!
  22. Error: Failed to run flasher stub (-308)!
  23. Error: No working memory available. Specify -work-area-phys to target.
  24. Warn : not enough working area available(requested 776)
  25. Error: no working area available, can't alloc space for stub data!
  26. Error: Failed to run flasher stub (-308)!
  27. Error: Failed to probe flash, size 0 KB
  28. Error: auto_probe failed
  29. Error: Connect failed. Consider setting up a gdb-attach event for the target to prepare target for GDB connect, or use 'gdb_memory_map disable'.
  30. Error: attempted 'gdb' connection rejected
  31. shutdown command invoked

Re: ESP32-S2 what IDF versions should be selected as latest?

Posted: Fri Nov 24, 2023 2:32 am
by ESP_Sprite
Odd. How are you starting gdb/openocd?