[AT-START-F403A Review] 5. Simulate the SPI screen and find a problem

ddllxxrr

[AT-START-F403A Review] 5. Simulate the SPI screen and find a problem [Copy link]

 

I have a 1.3-inch SPI screen. If there is a routine, I put the OLED.c and font library in the routine as a subdirectory. All of them are tested in an AT routine.

I defined four lines:

PB12---------SCL

PB13----------SDA

PB14----------RES

PB15----------DC

Specifically, change the initialization:

RCC_APB2PeriphClockCmd(RCC_APB2PERIPH_GPIOB, ENABLE);	 //ê1üAúê±ó
	GPIO_InitStructure.GPIO_Pins = GPIO_Pins_12|GPIO_Pins_13|GPIO_Pins_14|GPIO_Pins_15;	 
 	GPIO_InitStructure.GPIO_Mode = GPIO_Mode_OUT_PP; 		 //ííìê3
	GPIO_InitStructure.GPIO_MaxSpeed = GPIO_MaxSpeed_50MHz;//ùè50MHz
 	GPIO_Init(GPIOB, &GPIO_InitStructure);	  //3êˉGPIOD3,6
 	GPIO_SetBits(GPIOB,GPIO_Pins_12|GPIO_Pins_13|GPIO_Pins_14|GPIO_Pins_15);	

In the header file:

#define OLED_SCLK_Clr() GPIO_ResetBits(GPIOB,GPIO_Pins_12)//CLK
#define OLED_SCLK_Set() GPIO_SetBits(GPIOB,GPIO_Pins_12)

#define OLED_SDIN_Clr() GPIO_ResetBits(GPIOB,GPIO_Pins_13)//DIN
#define OLED_SDIN_Set() GPIO_SetBits(GPIOB,GPIO_Pins_13)

#define OLED_RST_Clr() GPIO_ResetBits(GPIOB,GPIO_Pins_14)//RES
#define OLED_RST_Set() GPIO_SetBits(GPIOB,GPIO_Pins_14)

#define OLED_DC_Clr() GPIO_ResetBits(GPIOB,GPIO_Pins_15)//DC
#define OLED_DC_Set() GPIO_SetBits(GPIOB,GPIO_Pins_15)
 		     
#define OLED_BLK_Clr()  GPIO_ResetBits(GPIOA,GPIO_Pins_4)//CS
#define OLED_BLK_Set()  GPIO_SetBits(GPIOA,GPIO_Pins_4)

The background is useless, just connect it directly to 3.3V.

As for the chip select, I just selected it. After all, it's just one SPI.

Here are the results:

When I flashed to a blue screen, it means the driver was successful. I can also see a circle when I draw it, but I never expected that a character would not be displayed. It is just a black block. I think there is something wrong with the character display part of the SPI screen.

I don't want to think about it anymore. I'm so tired of thinking about it. To know what happens next, please read the next chapter!

I found a problem. The manual clearly said that all GPIO ports are in AHB, but why are they all APB2 during initialization? I don't understand.

RCC_APB2PeriphClockCmd(RCC_APB2PERIPH_GPIOB, ENABLE);	 

According to the manual, it should be: RCC_AHBPeriphClockCmd(RCC_AHBPERIPH_GPIOB, ENABLE);

littleshrimp

Is it normal to operate this screen in this way when using other microcontrollers before?

ddllxxrr

littleshrimp posted on 2020-10-6 20:08 Is it normal to operate this screen in this way with other microcontrollers before?

I remember it was normal! The screen has turned blue?

okhxyyo

Yatli AT-START-F403A Review Summary

https://bbs.eeworld.com.cn/thread-1143018-1-1.html

w494143467

If the screen can be refreshed, then there must be no problem with the SPI driver. The only possible problem is the function of displaying characters. When debugging, check what the displayed characters are. It may be that all 0x000000 is written, resulting in a black display.

freebsder

Why do you like gpio simulation?

RCSN

Check with a logic analyzer