-
Notifications
You must be signed in to change notification settings - Fork 7.3k
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
Comments
Also, if the maximal value of |
@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. |
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... |
@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. |
@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 |
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
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
Answers checklist.
General issue report
Hi,
'CONFIG_ESP32S3_USE_FIXED_STATIC_RAM_SIZE' can maximal been set to
0x34000
viamenuconfig
. I would expect to be able to set it to maximal available RAM of 512KB.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
The text was updated successfully, but these errors were encountered: