2021-12-02 09:51 PM
2021-12-03 01:23 AM
Hello,
Have you tried greater values ?
2021-12-03 02:01 AM
Without the exact error, build log and context it is hard to know.
My guess is that this is occurring at the Linker level and already using too much memory, so making bigger won't help.
How large is the code being built?
2021-12-03 06:45 AM
Use higher optimization settings. Maybe buy a bigger chip.
2021-12-03 11:26 PM
thanks for your reply @TDK , in the past also i got the same error , but it was removed by make some change in Stm cube IDE >> properties and made some settings so that the error was gone, recently i update stmcube ide , so the same problem occurring. I am using stm32f070c6t6 and heap=400 and stack =400,how can i remove this error. i am not finding the previous suggested pages in the forum.
the error details in consolr as below.
c:\st\stm32cubeide_1.3.0\stm32cubeide\plugins\com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.9-2020-q2-update.win32_1.5.0.202011040924\tools\arm-none-eabi\bin\ld.exe: LLUSBCDC.elf section `._user_heap_stack' will not fit in region `RAM'
c:\st\stm32cubeide_1.3.0\stm32cubeide\plugins\com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.9-2020-q2-update.win32_1.5.0.202011040924\tools\arm-none-eabi\bin\ld.exe: region `RAM' overflowed by 1408 bytes
collect2.exe: error: ld returned 1 exit status
make: *** [makefile:69: LLUSBCDC.elf] Error 1
"make -j2 all" terminated with exit code 2. Build might be incomplete.
2021-12-03 11:33 PM
thanks for your response @Mike_ST , i have tried with changing the heap and stack values, memory flow error remains same but the size of the memory varying. previously i have the same problem , but it was remove by stm cube IDE >> properties settings , but I am not getting the same page in forum ,so please help me if you have an idea, Thanks in advance....
2021-12-03 11:38 PM
Already too big.
How much heap does it actually use? ie via malloc()/free() used anywhere in your code, or the library/example code.
What it eating up the memory? You could perhaps expand the RAM in the linker script, allowing completion/closure, and then reviewing/auditing the .MAP file,
2021-12-04 06:08 AM
This is a very conceptually simple problem. You can't fit more information into RAM than the chip has space for. You'll need to cut down on your RAM usage by reducing stack and/or heap size, or reducing use of global variables. There is no magic solution that you can enable that allows you to use more memory than the chip has.
You may also want to verify that the size of the RAM in your linker script correctly matches the size of the RAM given in the datasheet.
High optimization settings tend to help with this problem. Project -> Build Config -> Set Active -> Release.