cancel
Showing results for 
Search instead for 
Did you mean: 

use the LCD screen of the STM32N6570DK

creeper
Associate II

I am currently trying to use the LCD screen of the STM32N6570DK development board. But when I integrate the relevant information from the official firmware package into my project and try to use CUBEIDE for DEBUG, an error message will appear like this:

creeper_0-1746363477412.png

But this problem doesn't always arise, and for such a main function:

creeper_1-1746363573287.png

When I ran the "UTIL_LCD_SetFuncDriver() "function, the LCD backlight screen seemed to have some reaction, but it couldn't perform the setbackcolorr or clear functions properly. My screen remained dark.

Is it because my configuration is incompatible with the relevant BSP firmware library, as the corresponding CUBEMX configuration is not provided in the firmware package? These are all my files, I have tried my best to make everything in order but in vain:

 

3 REPLIES 3
KDJEM.1
ST Employee

Hello @creeper,

I recommend you to look at BSP example in STM32CubeN6 may help you.

This example provides a description of how to use the different BSP drivers.

The BSP example uses this code to clear the LCD:

  /* Clear the LCD */
  UTIL_LCD_SetFont(&UTIL_LCD_DEFAULT_FONT);
  UTIL_LCD_SetBackColor(UTIL_LCD_COLOR_WHITE);
  UTIL_LCD_Clear(UTIL_LCD_COLOR_WHITE);

 

I hope this example can help you to check the issue.

Thank you.

Kaouthar

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

creeper
Associate II

Thank you very much, and I seem to solve this  problem. It seems like a problem in CUBEIDE project manage. If  I  use 

#include "../../Components/STM32N6570-DK/stm32n6570_discovery_errno.h"

instead of 

#include "stm32n6570_discovery_errno.h"

it may solve the problem.

But once I go back to the original code, the LCD can work properly. It's a such strange problem.

KDJEM.1
ST Employee

Hello @creeper;

 

Glad to know that the issue is solved.

Could you please check the path?

KDJEM1_0-1747644266357.png

KDJEM1_1-1747644475603.png

To give better visibility on the answered topics, please click on "Accept as Solution" on the reply which solved your issue.

Thank you.

Kaouthar

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.