'RAM' overflow and 'FLASH' overflow STM32F7508-DK

[DMeis.1]

I followed the tutorial online. I started a cubeIDE project and used the ST32F7508 template to set up my project. I followed the online setup help to setup. Then I created a touchGFX from the file but when i go to build I keep getting this error and can not figure out how to get pass this.

arm-none-eabi-g++ -o "TouchTestFive.elf" @"objects.list" -l:libtouchgfx-float-abi-hard.a -mcpu=cortex-m7 -T"C:\Users\dmeissner.VR-SIMSBURY\STM32CubeIDE\TouchGFXtest\TouchTestFive\STM32F750N8HX_FLASH.ld" --specs=nosys.specs -Wl,-Map="TouchTestFive.map" -Wl,--gc-sections -static -L"C:\Users\dmeissner.VR-SIMSBURY\STM32CubeIDE\TouchGFXtest\TouchTestFive\Middlewares\ST\touchgfx\lib\core\cortex_m7\gcc" --specs=nano.specs -mfpu=fpv5-sp-d16 -mfloat-abi=hard -mthumb -Wl,--start-group -lc -lm -lstdc++ -lsupc++ -Wl,--end-group
c:\st\stm32cubeide_1.2.0\stm32cubeide\plugins\com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.7-2018-q2-update.win32_1.0.0.201904181610\tools\arm-none-eabi\bin\ld.exe: TouchTestFive.elf section `.text' will not fit in region `FLASH'
c:\st\stm32cubeide_1.2.0\stm32cubeide\plugins\com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.7-2018-q2-update.win32_1.0.0.201904181610\tools\arm-none-eabi\bin\ld.exe: TouchTestFive.elf section `TouchGFX_Framebuffer' will not fit in region `RAM'
c:\st\stm32cubeide_1.2.0\stm32cubeide\plugins\com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.7-2018-q2-update.win32_1.0.0.201904181610\tools\arm-none-eabi\bin\ld.exe: region `RAM' overflowed by 109752 bytes
c:\st\stm32cubeide_1.2.0\stm32cubeide\plugins\com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.7-2018-q2-update.win32_1.0.0.201904181610\tools\arm-none-eabi\bin\ld.exe: region `FLASH' overflowed by 487812 bytes

[Tesla DeLorean]

The STM32F750N8 has a relatively small reported FLASH, 64KB vs 1MB on die. You could pretend you have an F756

You're expected to bring up the SDRAM for larger RAM space and frame buffers, and use the external QSPI FLASH for graphic images and resources. You'd need to describe these in your linker script, and bring up the interfaces in your startup code.

[DMeis.1]

Now I am only getting the RAM error

c:\st\stm32cubeide_1.2.0\stm32cubeide\plugins\com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.7-2018-q2-update.win32_1.0.0.201904181610\tools\arm-none-eabi\bin\ld.exe: TouchTestFive.elf section `TouchGFX_Framebuffer' will not fit in region `RAM'
c:\st\stm32cubeide_1.2.0\stm32cubeide\plugins\com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.7-2018-q2-update.win32_1.0.0.201904181610\tools\arm-none-eabi\bin\ld.exe: region `RAM' overflowed by 109752 bytes
collect2.exe: error: ld returned 1 exit status
make: *** [makefile:89: TouchTestFive.elf] Error 1
"make -j8 all" terminated with exit code 2. Build might be incomplete.
 
15:55:41 Build Failed. 1 errors, 0 warnings. (took 53s.273ms)

[Tesla DeLorean]

If described properly in your linker script you should have 320 KB of Internal SRAM to work with.

Right now the linker is complaining you need 108KB more than you've described to it.

There is 8MB of SDRAM if you tell the linker, and bring it up on your hardware.

[DMeis.1]

Do you know how I can get the linker to bring it up in my SDRAM? Sorry I'm new to all of this.

[DMeis.1]

Ok I Just had to update the both FLASH and RAM Id files. It builds now. but now when i try to debug I get

Error in final launch sequence:

Failed to execute MI command:

load C:\\Users\\dmeissner.VR-SIMSBURY\\STM32CubeIDE\\TouchGFXtest\\TouchTestFive\\Debug\\TouchTestFive.elf 

Error message from debugger back end:

Load failed

Failed to execute MI command:

load C:\\Users\\dmeissner.VR-SIMSBURY\\STM32CubeIDE\\TouchGFXtest\\TouchTestFive\\Debug\\TouchTestFive.elf 

Error message from debugger back end:

Load failed

Failed to execute MI command:

load C:\\Users\\dmeissner.VR-SIMSBURY\\STM32CubeIDE\\TouchGFXtest\\TouchTestFive\\Debug\\TouchTestFive.elf 

Error message from debugger back end:

Load failed

Load failed

[ANguy.3]

Hi,

did you fix the problem? I have the same board and same problem like you