Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ESP32S3] Value of 'CONFIG_ESP32S3_USE_FIXED_STATIC_RAM_SIZE' can only been set to '0x34000' max in 'menuconfig' (IDFGH-8845) #10270

Closed
3 tasks done
sbithinx opened this issue Nov 29, 2022 · 6 comments
Assignees
Labels
Resolution: Done Issue is done internally Status: Done Issue is done internally

Comments

@sbithinx
Copy link

sbithinx commented Nov 29, 2022

Answers checklist.

  • I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
  • I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
  • I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report

Hi,
'CONFIG_ESP32S3_USE_FIXED_STATIC_RAM_SIZE' can maximal been set to 0x34000 via menuconfig. I would expect to be able to set it to maximal available RAM of 512KB.

image

Is this intended? If yes, why? If not, this is properly a bug.

This may also related to the issue #10271. At least it can be analyzed of fixed together.

Greetings
Sebastian

@espressif-bot espressif-bot added the Status: Opened Issue is new label Nov 29, 2022
@github-actions github-actions bot changed the title [ESP32S3] Value of 'CONFIG_ESP32S3_USE_FIXED_STATIC_RAM_SIZE' can only been set to '0x34000' max in 'menuconfig' [ESP32S3] Value of 'CONFIG_ESP32S3_USE_FIXED_STATIC_RAM_SIZE' can only been set to '0x34000' max in 'menuconfig' (IDFGH-8845) Nov 29, 2022
@sbithinx
Copy link
Author

Also, if the maximal value of 0x34000 is configured, the compilation always fails.

@espressif-bot espressif-bot added Status: Selected for Development Issue is selected for development and removed Status: Opened Issue is new labels Nov 30, 2022
@chipweinberger
Copy link
Contributor

@sbithinx, can you explain what this setting is supposed to do?

See my related issue: #10281

@ESP-Marius
Copy link
Collaborator

@chipweinberger I think the idea is that it should give you a fixed and reliable heap size, e.g. if you add one more bss variable it wont change your total heap memory, as it would already have reserved a static amount for this.

@ESP-Marius
Copy link
Collaborator

Unfortunately the option seems to have been broken during refactoring, and no longer does what it is supposed to do as far as I can see. Ill look at it today...

@ESP-Marius
Copy link
Collaborator

@sbithinx With regards to your original question: this value will be less than the chips total memory, as not all of it can be used for this purpose. E.g. parts are used by the software bootloader, and will only be available as heap memory after app startup.

@sbithinx
Copy link
Author

sbithinx commented Dec 1, 2022

@ESP-Marius Thanks for the support. I'm aware of this. I was just to lazy to calculate the exact values. This is better done by you :-) But it actually can't exceed the maximal value of available RAM, even though it is less than that. :-D

@espressif-bot espressif-bot added Status: In Progress Work is in progress and removed Status: Selected for Development Issue is selected for development labels Dec 1, 2022
espressif-bot pushed a commit to espressif/esp-hal-components that referenced this issue Mar 20, 2023
The USE_FIXED_STATIC_RAM_SIZE was not actually causing the heap to start
at a fixed address.

Closes espressif/esp-idf#10270
Closes espressif/esp-idf#10271
espressif-bot pushed a commit to espressif/esp-hal-components that referenced this issue Mar 20, 2023
The USE_FIXED_STATIC_RAM_SIZE was not actually causing the heap to start
at a fixed address.

Closes espressif/esp-idf#10270
Closes espressif/esp-idf#10271
@espressif-bot espressif-bot added Resolution: Done Issue is done internally Status: Done Issue is done internally and removed Status: In Progress Work is in progress labels Mar 23, 2023
espressif-bot pushed a commit that referenced this issue May 14, 2023
The USE_FIXED_STATIC_RAM_SIZE was not actually causing the heap to start
at a fixed address.

Closes #10270
Closes #10271
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution: Done Issue is done internally Status: Done Issue is done internally
Projects
None yet
Development

No branches or pull requests

4 participants