Embedded Coder Support cannot scan the hardware MCU

Dear everyone,

I am having an issue with MATLAB code generation and deployment for the STM32H755ZITx. I used the STM32H7 dual-core example and configured only one core to blink an LED. Code generation and build both complete successfully. I can also use the generated .hex file to flash the board and the .elf file to debug it in IDEs.

The main problem is that I cannot deploy the code directly from MATLAB to the board. I have been investigating this issue for nearly a month, but I have not found any solution online. The only clear symptom I found is that the "Scan" function in Simulink does not detect the STM32H755ZITx. Other MCUs I tested, such as STM32F407, STM32H743, and STM32U series devices, work normally.

My setup is:

• MATLAB R2025a
• Latest Embedded Coder Support Package for STMicroelectronics STM32 Processors
• ST-LINK/V3MINI

Has anyone faced the same issue or found a solution?

Thank you in advance.

Update:

I bought and used the Nucleo H755 kit, and OMG, it was successfully detected and connected!

Previously, I used a custom H755 kit. It uses the same MCU code and the same package, and it works normally with IDEs, but it cannot connect to MATLAB like the Nucleo kit can. Something must be wrong, right?

Has anyone faced the same issue or found a solution?

Thank you in advance.

Answer 1

[Reaj Uddin]

The fact that the same model works on the Nucleo-H755 but not on your custom H755 board strongly suggests that MATLAB/Simulink is relying on more than just the MCU type during “Scan” and deployment.

For custom STM32 boards, MATLAB typically depends on the STM32CubeMX .ioc configuration and the supported STM32 processor-based board workflow. MathWorks documents that STM32 processor support uses STM32CubeMX configuration, and custom boards may need an existing or generated .ioc project rather than behaving exactly like Nucleo/Discovery boards.

Things I would check:

1. ST-LINK wiring on the custom board

• SWDIO
• SWCLK
• NRST
• GND
• VTref / target voltage senseMATLAB’s scan may fail even if CubeIDE can flash manually, especially if reset or voltage reference behavior differs from the Nucleo board.

1. Boot and reset configuration

• BOOT0 state
• NRST connection to ST-LINK
• Power-up timing
• Option bytes
• Whether the core selected by MATLAB is actually the one being debugged/flashed

1. Use “STM32H7xx based board” / custom processor-board workflowDo not configure it as if it were the Nucleo board unless your custom board is electrically equivalent. Use a proper .ioc file for your custom H755 hardware.
2. Compare the Nucleo .ioc and your custom .iocSince Nucleo works, compare:

• debugger interface
• clock tree
• SYS/debug settings
• dual-core boot settings
• M7/M4 project structure
• generated linker/startup files

1. Do not assume “same MCU package” means MATLAB sees the same boardCubeIDE and STM32CubeProgrammer can often connect to almost any valid SWD target. MATLAB deployment is more restrictive because it wraps build, load, run, external mode, and board-detection logic.

Since the Nucleo-H755 is detected successfully, the issue is almost certainly in the custom board’s hardware/debug configuration or in the custom-board Simulink/STM32CubeMX setup, not in MATLAB code generation. I would first compare the SWD/NRST/VTref connections and the CubeMX .ioc settings against the Nucleo-H755 reference design.

Also worth mentioning: MathWorks says the older STM32 support package remains for earlier releases, while newer workflows are moving toward the STM32 Microcontroller Blockset starting R2026a, so if this is a deployment-tool limitation, MathWorks Support may be the right place to confirm it.

[Raven Pham]

Thank you for your detailed solution.

However, in my case, the situation is simply that I opened the sample model example provided by MATLAB, then went to the configuration section to check the device list, so I don’t think the configuration in CubeMX has any effect.

I have checked my debug port and did not notice anything unusual. I can use both ST-Link and J-Link to connect and debug.

I have attached the image below. As you can see, when I plug in the Nucleo H755 kit, it is detected, but my custom board is not.