STM32G431CBU: section `.bss' will not fit in region `RAM'

[ValterMatos]

Good morning.
Could anyone tell me about this error and how to resolve it.
C:/ST/STM32CubeIDE_1.19.0/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.13.3 .rel1.win32_1.0.0.202411081344/tools/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe: Oscillo_STM32G431CBU.elf section `.bss' will not fit in region `RAM'
C:/ST/STM32CubeIDE_1.19.0/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.13.3 .rel1.win32_1.0.0.202411081344/tools/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe: region `RAM' overflowed by 54928 bytes
I'm using IDE 1.19 to compile the code for a G431CBU
Grateful

Valter Matos

[Ozone]

I vividly remember my university times. Back then, I studied electrical engineering, due to the lack of more specific alternatives. So I was the only one in my study group who had delved into computers and actual coding projects before.

Which became obvious during the final test in the "C programming" course we took, which consisted of "debugging" a short program with about 30 lines. While I was finished in less than 15 minutes, about half struggled until the end.

If it is not the focus area of the study field, a lecturer has to expect a wide variety of performances, and thus moderate his standards.

[Andrew Neil]

I once took a VHDL course.

About half the attendees were electronics (hardware) people, and half were software.

It was fascinating to see the different points which one group would find easy, while the other group struggled!

[ValterMatos]

Much of what has been said I understand.
I am a retired chemist with extensive research experience.
Great experience in electronics and programming since the 8080 and Arduino systems era, with little knowledge of STM.
For this reason, I am seeking help. I do not decide on the project. The G431 MCUs were donated to the team.
Volunteering to help a team that chose this project.
For the electronics team, learning with programming challenges is very good.
Making it happen.
I managed to partially solve the problem.
Manipulating a 480x320 image to fit into a 19K buffer.
It affects resolution. We will try other approaches.
It's a learning experience.

[ValterMatos]

In ILI9488.

This is the key point.

static uint8_t image_buffer[ILI9488_TFTWIDTH*ILI9488_TFTHEIGHT/2 ] = {0};

#define IMG_BUFF_GET(x, y) (((x)%2)==0)?(image_buffer[((y)*240)+((x)/2)]>>4):(image_buffer[((y)*240)+((x)/2)]&0x0F)

#define IMG_BUF_SET(x, y, c) if(((x)%2)==0){image_buffer[((y)*(_width/2))+((x)/2)]&=0x0F;image_buffer[((y)*(_width/2))+((x)/2)]|=((c)<<4);} \
else{image_buffer[((y)*(_width/2))+((x)/2)]&=0xF0;image_buffer[((y)*(_width/2))+((x)/2)]|=(c);}

Manipulate the image into an /8 buffer.

The image uses 4 bits per pixel. I managed to compile, but the image still needs to be adjusted.
With my experience in STM, this is proving difficult.

Challenges are learning experiences that help make things happen.
Thank you all, Valter Matos

---

Edited to apply source code formatting - don't forget How to insert source code !

[ValterMatos]

For a project of this type, two points are of great importance:

The correct manipulation of the signal collected by the electronics.

Correct processing of the signal by the software for final presentation.

For this to happen, the MCU must be loaded with the code.

In this case, we try to use the MCUs we have.

That's where the challenges come in.

[Ozone]

> Challenges are learning experiences that help make things happen.

But challenges that massively overstrains the students, especially under high time and performance pressure, achieve the very opposite.

Such a oscilloscope project would be suited for bachelor or master thesis, or an extra-curricular project for the interested & andvanced students.

My opinion.

My current employer hires students of equivalent level for internships twice a year, including in my team.
Thus I judge by the level of knowledge and capabilities I observe myself.

[Andrew Neil]

---

@Ozone wrote:

challenges that massively overstrains the students, especially under high time and performance pressure, achieve the very opposite..

---

Especially when those challenges have nothing to do with the subject at hand (electronics).

This is burdening electronics beginners with advanced software challenges!

[ValterMatos]

As I said before.

I am a Chemical Engineer with a lot of experience in research.

I have been a student, an employee, a team leader, and I have trained many students.
Today I am retired, a volunteer, and still learning.
If I had given up on the first challenge, I wouldn't have publications and patents registered in my name.
I am learning in STM and trying to guide people with what I know.
Challenges don't overwhelm; they teach you to look for solutions.
The chosen project was attempted in F303, but some structures were not allowed.
They managed to get some G431. I ported it, getting the necessary structures, but I didn't pay attention to the necessary memory.
I am trying to manipulate the image to fit the memory size.
I partially succeeded. It compiles, runs with some deficiencies.
In short, I'm not the one who decides the project. I help and learn.

Don't give up. Change the path to the objective.

Sorry and thank you for your attention.

[ValterMatos]

One more question, if you can help.

BSP_TS_GetState(& osc->touchScreen);

BSP_TS_Init(ILI9488_TFTHEIGHT, ILI9488_TFTWIDTH);
BSP_TS_Init and BSP_TS_GetState are not recognized by IDE versions 1.19 and 1.20.

I have to disable them to compile, so the TOUCH doesn't work.

C:/Users/Valter/STM32CubeIDE/workspace_1.19.0/Oscillo_STM32G431CBU/Debug/../Core/Src/oscilloscope.c:48:(.text.oscilloscopeInit+0x138): undefined reference to `BSP_TS_Init'

C:/Users/Valter/STM32CubeIDE/workspace_1.19.0/Oscillo_STM32G431CBU/Debug/../Core/Src/oscilloscope.c:231:(.text.serveTouchScreen+0x10): undefined reference to `BSP_TS_GetState'

I have never used this command before.

Thanks