STM32H7 family

st.com STM32H7 family page

GitHub STM32CubeH7 FW

Single core STM32

STM32H743xx

STM32H743ZI devices are based on the high-performance Arm Cortex-M7 32-bit RISC core operating at up to 480 MHz.

st.com STM32H743ZI MCU page

NUCLEO_H743ZI2

st.com NUCLEO page

mbed.com Target page

• Total FLASH is 2 MB (0x200000)

  • 2x8 sectors of 128 KB
  • Flash memory bank 1 @ 0x0800 0000
  • Flash memory bank 2 @ 0x0810 0000

• RAM: 1 MB

  • DTCM : 128 KB (0x20000) @0x2000 0000
  • SRAM : 512 KB (0x80000) @0x2400 0000
  • SRAM1 : 128 KB (0x20000) @0x3000 0000
  • SRAM2 : 128 KB (0x20000) @0x3002 0000
  • SRAM3 : 32 KB (0x8000) @0x3004 0000
  • SRAM4 : 64 KB (0x10000) @0x3800 0000

NUCLEO_H743ZI

Note that NUCLEO_H743ZI is deprecated. Please update your board to NUCLEO_H743ZI2:

• new MCU chip revision
• new ST Link version

How to use NUCLEO_H743ZI with mbed-os-6:

PeripheralPins.c and PinNames.h are available in mbed-os repo, so you just have to create a custom_targets.json file with:

{
    "NUCLEO_H743ZI": {
        "inherits": [
            "MCU_STM32H743xI"
        ],
        "config": {
            "d11_configuration": {
                "help": "Value: PB_5 for the default board configuration, PA_7 in case of solder bridge update (SB33 on/ SB35 off)",
                "value": "PB_5",
                "macro_name": "STM32_D11_SPI_ETHERNET_PIN"
            },
            "hse_value": {
                "value": "8000000",
                "macro_name": "HSE_VALUE"
            }
        },
        "device_has_add": [
            "EMAC"
        ],
        "overrides": {
            "network-default-interface-type": "ETHERNET"
        },
        "supported_form_factors": [
            "ARDUINO"
        ],
        "device_name": "STM32H743ZI"
    }
}

STM32H7A3xx

STM32H7A3/7B3 devices are based on an Arm Cortex-M7 core (with double-precision floating point unit) running up to 280 MHz.

st.com STM32H743ZI MCU page

NUCLEO_H7A3ZI_Q

st.com NUCLEO page

mbed.com Target page

• Total FLASH is 2 MB (0x200000)

  • 2x128 sectors of 8 KB
  • Flash memory bank 1 @ 0x0800 0000
  • Flash memory bank 2 @ 0x0810 0000

• RAM: 1312 KB

  • DTCM : 128 KB (0x20000) @0x2000 0000
  • SRAM : 1024 KB (0x100000) @0x2400 0000
  • SRAM1 : 64 KB (0x10000) @0x3000 0000
  • SRAM2 : 64 KB (0x10000) @0x3001 0000
  • SRAM3 : 32 KB (0x8000) @0x3800 0000

Dual core STM32

STM32H747xx

DISCO_H747I

The STM32H7x7 lines combine the performance of the Cortex-M7 (with double-precision floating point unit) running up to 480 MHz and the Cortex-M4 core (with single-precision floating point unit).

st.com STM32H747ZI MCU page

st.com board page

mbed.com Target page

• Total FLASH is 2 MB (0x200000)

  • Flash memory bank 1 @ 0x0800 0000: 8 sectors of 128 KB => 1MB
  • Flash memory bank 2 @ 0x0810 0000: 8 sectors of 128 KB => 1MB

• RAM: 1 MB

  • DTCM : 128 KB (0x20000) @0x2000 0000 - only CM7 side
  • SRAM : 512 KB (0x80000) @0x2400 0000 - shared
  • SRAM1 : 128 KB (0x20000) @0x3000 0000 - shared
  • SRAM2 : 128 KB (0x20000) @0x3002 0000 - shared
  • SRAM3 : 32 KB (0x8000) @0x3004 0000 - shared
  • SRAM4 : 64 KB (0x10000) @0x3800 0000 - shared

WARNING: Ethernet connector is not enabled by default on this board

More information in the wiki page : Ethernet HW Patch

STM32H745xx

st.com STM32H745 MCU page

How to create a custom board with STM32H745xI MCU:

After creating your local PeripheralPins.c and PinNames.h files in TARGET_BOARD_H745xI directory,

create a custom_targets.json file with:

{
    "BOARD_H745xI_CM4": {
        "inherits": [
            "MCU_STM32H745xI_CM4"
        ],
        "extra_labels_add": [
            "BOARD_H745xI"
        ]
    },
    "BOARD_H745xI_CM7": {
        "inherits": [
            "MCU_STM32H745xI_CM7"
        ],
        "extra_labels_add": [
            "BOARD_H745xI"
        ]
    }
}

Dual mode configuration

Configuration can be checked/changed with STM32CubeProgrammer software in the Option bytes (OB) panel.

https://www.st.com/en/development-tools/stm32cubeprog.html

Default configuration is booting both CM7 and CM4:

• CM7 at 0x0800 0000
• CM4 at 0x0810 0000

Note that Drag and Drop feature for binary application (.bin files) is flashing at 0x0800 0000

IP HW usage warning

All resources (GPIO, UART, SPI, ...) can be used by both cores.

It is up to application to choose which instance is used by which core.

For GPIO, HW semaphore have been implemented which allows applications to use same GPIO port in both sides (CM4 can use PA_1, and CM7 PA_2).

NB : Virtual Com Port is using the same UART pins in CM4 and CM7.

It is not recommended to enable printf from both cores without any protection mechanism.

System clock configuration

Clock configuration is shared between both cores.

During boot procedure:

• M7 core is managing clock tree settings, and then wake up M4
• M4 is waiting for wake up from M7

When exiting Deep Sleep mode, first core (either M4 or M7) that woke up, is setting back this clock configuration.

Make application on M7 side

• Flash memory bank 1 is used
• DTCM and SRAM are used
• SRAM3 is used for Ethernet support

As explained in the Dual mode configuration above part, you can drag and drop applications.

For application compilation, you can use DISCO_H747I or DISCO_H747I_CM7 target name.

For MBED tests execution, you have to use DISCO_H747I target name (mbed detect name).

Make application on M4 side

• Flash memory bank 2 is used
• SRAM1, SRAM1 and SRAM3 is used (with @0x1000 0000 alias)

For application compilation, you have to use DISCO_H747I_CM4 target name.

For flashing, method is depending on the format:

• hexadecimal files: use drag and drop
• binary files: use STM32CubeProgrammer software

hexa drag and drop

Please check the ST Link FW version you have:

$ mbedls
| platform_name | platform_name_unique | mount_point | serial_port | target_id                | daplink_version |
|---------------|----------------------|-------------|-------------|--------------------------|-----------------|
| DISCO_H747I   | DISCO_H747I[0]       | D:          | COM13       | 081402210D03E72132477E08 | V3J7M2          |

Minimum version is V3J7M2 (https://www.st.com/en/development-tools/stsw-link007.html)

Configuration to add in mbed-os json configuration:

        "OUTPUT_EXT": "hex",

binary flashing

STM32CubeProgrammer software is available:

https://www.st.com/en/development-tools/stm32cubeprog.html

Here is command lines for flashing (but you can use graphical tool):

FLASHPATH="C:\Program Files (x86)\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin"
export PATH=$FLASHPATH:$PATH
STM32_Programmer_CLI -c port=SWD mode=UR -w BUILD/DISCO_H747I_CM4/ARM/mbed-os.bin 0x8100000