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

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

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

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

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 ?

Sprite
Espressif staff
Espressif staff
Posts: 10618
Joined: Thu Nov 26, 2015 4:08 am

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

Postby Sprite » Wed Oct 18, 2023 5:44 am

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)?

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

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

Postby RalphD » Sun Nov 05, 2023 11:26 am

Yes but it came out that my computer had some main issues and needed to be trashed.

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

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

Postby RalphD » Thu Nov 23, 2023 3:02 pm

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

Code: Untitled.txt Select all


GNU gdb (esp-gdb) 12.1_20221002
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:
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
Info : accepting 'gdb' connection on tcp/3333
Warn : No symbols for FreeRTOS!
Error: No working memory available. Specify -work-area-phys to target.
Warn : not enough working area available(requested 776)
Error: no working area available, can't alloc space for stub data!
Error: Failed to run flasher stub (-308)!
Warn : Failed to get flash mappings (-308)!
Error: No working memory available. Specify -work-area-phys to target.
Warn : not enough working area available(requested 776)
Error: no working area available, can't alloc space for stub data!
Error: Failed to run flasher stub (-308)!
Error: No working memory available. Specify -work-area-phys to target.
Warn : not enough working area available(requested 776)
Error: no working area available, can't alloc space for stub data!
Error: Failed to run flasher stub (-308)!
Error: Failed to probe flash, size 0 KB
Error: auto_probe failed
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'.
Error: attempted 'gdb' connection rejected
shutdown command invoked

Sprite
Espressif staff
Espressif staff
Posts: 10618
Joined: Thu Nov 26, 2015 4:08 am

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

Postby Sprite » Fri Nov 24, 2023 2:32 am

Odd. How are you starting gdb/openocd?

Who is online

Users browsing this forum: PetalBot and 2 guests