STM32H743IIT6 Development Board

I. Peripheral Overview

SDRAM: Uses Winbond's W9825G6KH, with a 16-bit bandwidth, 32MB size, 13 address lines, and 16 data lines. Expanded via FMC, version V1, limited by board size and my own capabilities, didn't use equal-length lines, but it still ran. Version V2 had equal-length address and data lines, and only ran at 100MHz in testing; higher speeds haven't been tested.
FLASH: Uses Winbond's W25Q128JVEIQ (other W25Q series packages with WSON-8 can also be used). Both V1 and V2 versions had equal-length data lines and ran normally, but the maximum speed wasn't tested.
EEPROM: Uses JSM24C02 from J.S. Microelectronics (same as AT24C, the only difference is that J.S. Microelectronics offers coupons). All three address lines of the chip are grounded, i.e., addresses 0xA0 and 0xA1 (I accidentally lost the test code for this peripheral, but I tested it before and it ran).
SDMMC: To ensure the development board can use all onboard peripherals simultaneously without conflict, only the SD card can be mounted on SDMMC2. The card slot is connected to the CD (insertion detection pin). However, due to a lack of careful attention, a pull-up resistor wasn't added to the CD pin. Therefore, to use insertion detection, a pull-up resistor needs to be configured internally. (Furthermore, initialization without a TF card will cause failure, so the lack of response during program burning might be due to the card not being inserted.)
USB: The USB interface uses a Type-C female connector. Both CC pins are pulled down with 5.1k resistors. The C to C cable can also be powered (I encountered a product with a floating Type-C CC pin, which was incredibly strange; my C to C PD adapter and power bank seemed unable to power it, and I only discovered the reason after disassembling it). The board does not include a CH340 connector; the Type-C port is only used as a USB interface.
Debug: The board provides 8 pins (4 power, 4 data) as a debug interface. The four data lines are SWDIO and SWCLK for SWD, and PA9 and PA10 for USART1 (pin descriptions are omitted for aesthetic purposes; please add them to the PCB if needed).
SPI LCD: The board has an 8-pin FPC socket as an SPI LCD interface, suitable for driving a 1.14-inch LCD screen (135*240 resolution, through-hole type) with the ST7789 chip. If you want to use an SPI screen with other pinouts, you will need to modify the wiring yourself. Also, although this screen is quite durable (I've reversed the power supply), please carefully check the pinout before using
the MCU. LCD: Since I have two 8080 parallel port screens with a 565 interface (one of which is a 3.5-inch 320x480 Atomic screen driving an NT35310), the onboard interface is a 565 interface, which can directly plug into the 3.5-inch Atomic screen (other sizes should also work, but I haven't tried it). However, this is only for the display interface; the touch interface is different and cannot be used directly. Also, to facilitate future use of capacitive touch, two pull-up resistors and a switch are reserved for later use of software IIC. This part has two interfaces: one is a female header, and the other is an FPC socket. Under -O3 optimization, using FreeRTOS, with an FMC frequency of 240MHz, the full-screen monochrome refresh rate is 170 frames per second (without DMA).
DCMI Interface: Due to the lack of a suitable camera, this part of the design was not verified
. Power Supply: Given the numerous peripherals on the development board and considering extreme cases, a WD1117 (1.35A/3.3V) was used as a linear regulator to reduce the 5V to 3.3V. If not so many peripherals are used simultaneously, a standard AMS1117 (1A/3.3V) can be used. Also, because the H743 is relatively expensive (around 29), unipolar TVS diodes for 3.3V and 5V were designed, and two tantalum capacitors were used. The H743's BAT pin is also connected to the battery and 3.3V via a bat54c. The battery holder is a CR1220.
Interaction Interface: Provides a tri-color LED and three user buttons. The three colors of the LED are controlled by three separate pins, and all three buttons are pulled down by resistors (press to raise).
GPIO expansion: 136 GPIOs were brought out, plus 16 GND and 8 3V3, which made up two 80p headers (the power supply is symmetrical, so it doesn't matter if they are plugged in upside down).

2. Precautions:

There are no instructions on the Debug interface and FPC interface on the PCB. You should either add them or refer to the schematic diagram to make sure you don't connect them in reverse.
The PCB supports DFU download. After powering on, press the BOOT button to set it to 1, then press and release the RST button to complete the reset and restart. Then click the refresh button on the right side of the USB mode in STM32CubeProgrammer. After the USB device appears, click CONNECT to connect.
The V1 version is a two-layer board with a 10x8.4 resolution and supports free prototyping. The V2 version is a two-layer board with a 12x8 resolution and does not support free prototyping (but it is longer and looks better). The V1 and V2 versions are slightly different. The differences are as follows: (1) The reference voltage VREF+ of the V1 version is not directly connected to VDDA, but a 0-ohm resistor is placed as a jumper. The V2 version connects VREF+ directly to VDDA. (2) The LCD backlight pin of version V1 is PB1, and that of version V2 is PB5 (same as Atom, the display part can directly use Atom's routine). Therefore, if you want to use the routine to light up the LCD of version V1, you need to connect PB1 to the 3V3 pin with DuPont wire, or modify the program to set LCD_BL to PB1. (3) The overall wiring of version V2 is more human-like, and the SDRAM, screen header interface and flash data line are all of equal length. As a verification board, version V1 only has equal length in flash, and the wiring is more abstract.
In the SD card routine, FATFS will be used to write files to the card. If it fails to write, the TF card needs to be formatted to FAT format first. Also, if you want to use the CD (insertion detection) pin, remember to pull it up. Do not initialize if it is not inserted.
The BOM table provided for version V1 is slightly inaccurate. The BOM table of version V2 is more accurate, but it is only for reference. You still need to check each item before purchasing.
H743IIT6 has two versions, one is V and the other is Y. Version v supports up to 480MHz, while version y only supports up to 400MHz. The version can be identified by the last character of the silkscreen. CubeMX's default configuration is up to 400MHz. To use 480MHz, in the System Core's RCC, change the Product revision in System Parameters to rev.V, and then change the Power Regulator Voltage Scale to Scale 0. The silkscreen identification is shown in Figure

3. Example Descriptions:
       Due to limited personal ability, only the following examples are provided. All examples are written using STM32CubeMX and Keil5 based on the HAL library. The parallel LCD driver is ported from Atom, and the SPI LCD driver is ported from a certain boring

DAC_TEST (outputting a cyclically changing voltage on pin PA4).
FreeRTOS: Uses two tasks, one responsible for continuous red and blue screen refresh, and the other responsible for recording and outputting the frame count every second (using a parallel port screen).
FLASH: Use QSPI to perform read and write tests on the FLASH memory, and print the results via serial port (PA9, PA10).
SDRAM: Use FMC to perform read and write tests on the SDRAM memory, and print the results via serial port (PA9, PA10)
. LCD: Use SPI to power on the LCD.
USART: Use QSPI to read and write to the FLASH memory, simultaneously powering on the SPI LCD, and using the internal ADC interface to acquire, calculate, and output the chip's internal junction temperature.
lvgl: Use FMC to drive a parallel port LCD to run a simple LVGL interface (directly using an Atomic 3.5-inch LCD).
SD_T: Use FATFS to operate the TF card via SDIO and write two files.

IV. Appearance