Computer Vision application demonstrating the deployment of several object detection models execution in series on the STM32N6570-DK or NUCLEO-N657X0-Q board. The chosen use case is single-hand landmark detection. It consists of two models that execute sequentially:
- A palm detection (pd) model is executed in the first stage to detect the hand’s palm.
- A hand landmark (hl) detection model is executed in the second stage to identify the landmarks of the hand detected during the first stage. After the execution of the first model, a resize operation takes place to provide the expected input to the second model. On STM32N6570-DK GPU2D is used to also perform a rotation to orient hand vertically.
This top README gives an overview of the app. Additional documentation is available in the Doc folder.
- Multi-threaded application flow (FreeRTOS)
- NPU-accelerated quantized AI model inference
- GPU2D usage to perform resize and rotation
- Execute multiple models in series
- Dual DCMIPP pipelines
- DCMIPP cropping, decimation, and downscaling
- DCMIPP ISP usage
- LTDC dual-layer implementation
- Development mode
- Boot from external flash
Supported development platforms:
- STM32N6570-DK Discovery Board
- Connect to the onboard ST-LINK debug adapter (CN6) using a USB-C to USB-C cable for sufficient power.
- OTP fuses are configured for xSPI IOs to achieve maximum speed (200MHz) on xSPI interfaces.
- NUCLEO-N657X0-Q Nucleo Board
- Connect to the onboard ST-LINK debug adapter (CN9) using a USB-C to USB-C cable for sufficient power.
- OTP fuses are configured for xSPI IOs to achieve maximum speed (200MHz) on xSPI interfaces.
STM32N6570-DK board with MB1854B IMX335.
Supported camera modules:
- Provided IMX335 camera module
- STEVAL-55G1MBI
- STEVAL-66GYMAI1
For the Nucleo board, one of the following displays is required:
- A USB host for data transmission via USB/UVC (using the USB OTG port CN8)
NUCLEO-N657X0-Q board with USB/UVC display.
- X-NUCLEO-GFX01M2 SPI display
NUCLEO-N657X0-Q board with SPI display.
- IAR Embedded Workbench for Arm (EWARM 9.40.1) + N6 patch (EWARMv9_STM32N6xx_V1.0.0)
- STM32CubeIDE (v1.17.0)
- STM32CubeProgrammer (v2.18.0)
- STEdgeAI (v2.2.0)
The STM32N6 series does not have internal flash memory. To retain firmware after a reboot, program it into the external flash. Alternatively, you can load firmware directly into SRAM (development mode), but note that the program will be lost if the board is powered off in this mode.
Development Mode: used for loading firmware into RAM during a debug session or for programming firmware into external flash.
Boot from Flash: used to boot firmware from external flash.
STM32N6570-DK | NUCLEO-N657X0-Q | |
---|---|---|
Boot from flash | ![]() |
![]() |
Development mode | ![]() |
![]() |
You can see application messages by attaching a console application to the ST-Link console output. Use the following console parameters:
- Baud rate of 115200 bps.
- No parity.
- One stop bit.
To program the board's external flash, follow these steps:
- Set the board to development mode.
- Program
Binary/ai_fsbl.hex
(First Stage Boot Loader). - Program
Binary/palm_detector_data.hex
(parameters of the palm detector model). - Program
Binary/hand_landmark_data.hex
(parameters of the hand landmarks model). - Program
Binary/x-cube-n6-ai-hand-landmarks-dk.hex
(firmware application). - Set the board to boot from flash mode.
- Power cycle the board.
Note: The Binary/x-cube-n6-ai-hand-landmarks-dk.hex
firmware is built for MB1939 STM32N6570-DK REV C02 with any of the listed camera modules.
To program the board's external flash, follow these steps:
- Set the board to development mode.
- Program
Binary/ai_fsbl.hex
(First Stage Boot Loader). - Program
Binary/palm_detector_data.hex
(parameters of the palm detector model). - Program
Binary/hand_landmark_data.hex
(parameters of the hand landmarks model). - Program
Binary/x-cube-n6-ai-hand-landmarks-nucleo-uvc.hex
(firmware application). - Set the board to boot from flash mode.
- Connect a USB cable to the USB OTG port (CN8), next to the RJ45 port. Connect the other end to a USB host (PC, USB hub, etc.) for data transmission via USB/UVC.
- Power cycle the board.
- Start the camera application on the host. On Windows, search for "camera" in the Start menu.
Note: The Binary/x-cube-n6-ai-hand-landmarks-nucleo-uvc.hex
firmware is built for MB1940 NUCLEO-N657X0-Q REV C01 with USB/UVC host display and any of the listed camera modules.
To program the board's external flash, follow these steps:
- Set the board to development mode.
- Program
Binary/ai_fsbl.hex
(First Stage Boot Loader). - Program
Binary/palm_detector_data.hex
(parameters of the palm detector model). - Program
Binary/hand_landmark_data.hex
(parameters of the hand landmarks model). - Program
Binary/x-cube-n6-ai-hand-landmarks-nucleo-spi.hex
(firmware application). - Set the board to boot from flash mode.
- Put the X-NUCLEO-GFX01M2 shield on top of the NUCLEO-N657X0-Q board.
- Power cycle the board.
Note: The Binary/x-cube-n6-ai-hand-landmarks-nucleo-spi.hex
firmware is built for MB1940 NUCLEO-N657X0-Q REV C01 with X-NUCLEO-GFX01M2 SPI display and any of the listed camera modules.
See How to program hex files STM32CubeProgrammer.
Ensure the STM32CubeProgrammer bin
folder is in your PATH.
export DKEL="<STM32CubeProgrammer_N6 Install Folder>/bin/ExternalLoader/MX66UW1G45G_STM32N6570-DK.stldr"
# First Stage Boot Loader
STM32_Programmer_CLI -c port=SWD mode=HOTPLUG -el $DKEL -hardRst -w Binary/ai_fsbl.hex
# Network parameters and biases
STM32_Programmer_CLI -c port=SWD mode=HOTPLUG -el $DKEL -hardRst -w Binary/palm_detector_data.hex
STM32_Programmer_CLI -c port=SWD mode=HOTPLUG -el $DKEL -hardRst -w Binary/hand_landmark_data.hex
# Application Firmware
STM32_Programmer_CLI -c port=SWD mode=HOTPLUG -el $DKEL -hardRst -w Binary/x-cube-n6-ai-hand-landmarks-dk.hex
Ensure the STM32CubeProgrammer bin
folder is in your PATH.
export NUEL="<STM32CubeProgrammer_N6 Install Folder>/bin/ExternalLoader/MX25UM51245G_STM32N6570-NUCLEO.stldr"
# First Stage Boot Loader
STM32_Programmer_CLI -c port=SWD mode=HOTPLUG -el $NUEL -hardRst -w Binary/ai_fsbl.hex
# Network parameters and biases
STM32_Programmer_CLI -c port=SWD mode=HOTPLUG -el $NUEL -hardRst -w Binary/palm_detector_data.hex
STM32_Programmer_CLI -c port=SWD mode=HOTPLUG -el $NUEL -hardRst -w Binary/hand_landmark_data.hex
# Application Firmware
# USB/UVC display
STM32_Programmer_CLI -c port=SWD mode=HOTPLUG -el $NUEL -hardRst -w Binary/x-cube-n6-ai-hand-landmarks-nucleo-uvc.hex
# SPI display
STM32_Programmer_CLI -c port=SWD mode=HOTPLUG -el $NUEL -hardRst -w Binary/x-cube-n6-ai-hand-landmarks-nucleo-spi.hex
Before building and running the application, you must program palm_detector_data.hex
and hand_landmark_data.hex
(model weights and biases). This only needs to be done once unless you change the AI model. See Quickstart using prebuilt binaries for details.
For more information about boot modes, see Boot Overview.
Set your board to development mode.
Double-click STM32CubeIDE/<board_name>/.project
to open the project in STM32CubeIDE. Build and run the project.
Double-click EWARM/<board_name>/x-cube-n6-ai-hand-landmarks-dk.eww
to open the project in IAR. Build and run the project.
Run the following commands (ensure required tools are in your PATH):
- Build the project:
make -j8
- Start a GDB server connected to the STM32 target:
ST-LINK_gdbserver -p 61234 -l 1 -d -s -cp <path-to-stm32cubeprogramer-bin-dir> -m 1 -g
- In a separate terminal, launch a GDB session to load the firmware:
$ arm-none-eabi-gdb build/Project.elf (gdb) target remote :61234 (gdb) monitor reset (gdb) load (gdb) continue
Note: To select the board, specify BOARD=STM32N6570-DK
or BOARD=NUCLEO-N657X0-Q
as a Makefile option.
Note: To select the NUCLEO-N657X0-Q display interface, specify SCR_LIB_SCREEN_ITF=UVCL
or SCR_LIB_SCREEN_ITF=SPI
as a Makefile option.
Set your board to development mode.
Double-click STM32CubeIDE/<board_name>/.project
to open the project in STM32CubeIDE. Build the project.
Double-click EWARM/<board_name>/x-cube-n6-ai-hand-landmarks-dk.eww
to open the project in IAR. Build the project.
Ensure all required tools are in your PATH, then build the project:
make -j8
After building the application, you must add a signature to the binary file:
STM32_SigningTool_CLI -bin build/Project.bin -nk -t ssbl -hv 2.3 -o build/Project_sign.bin
Program the signed binary at address 0x70100000
.
On STM32N6570-DK:
export DKEL="<STM32CubeProgrammer_N6 Install Folder>/bin/ExternalLoader/MX66UW1G45G_STM32N6570-DK.stldr"
# Adjust build path as needed
STM32_Programmer_CLI -c port=SWD mode=HOTPLUG -el $DKEL -hardRst -w build/Project_sign.bin 0x70100000
On NUCLEO-N657X0-Q:
export NUEL="<STM32CubeProgrammer_N6 Install Folder>/bin/ExternalLoader/MX25UM51245G_STM32N6570-NUCLEO.stldr"
# Adjust build path as needed
STM32_Programmer_CLI -c port=SWD mode=HOTPLUG -el $NUEL -hardRst -w build/Project_sign.bin 0x70100000
Note: Only the application binary needs to be programmed if fsbl
and networks data have already been programmed.
Set your board to boot from flash mode and power cycle to boot from external flash.