Recommended way to port X-CUBE-SBSFU from NUCLEO-H753ZI to STM32H733ZGTX

[Zainulabedeen]

I am working with the official X-CUBE-SBSFU package and I need to port the example that is provided for NUCLEO-H753ZI (STM32H753ZI) to my custom board based on STM32H733ZGTX.

This is the closest official example available for my MCU. There is no .ioc file and the whole project structure (SECoreBin + SBSFU + UserApp) is built specifically for the H753ZI.

I have already read AN5056 (Integration guide for the X-CUBE-SBSFU). It explains the hardware adaptations and especially the memory mapping changes (mapping_sbsfu / mapping_fwimg), but it does not give a clear step-by-step procedure for changing the target MCU itself (startup files, linker scripts, CMSIS device headers, project settings, etc.).

Could someone from ST or the community please advise on the recommended and proper way to perform this port?

Specifically I would like to know:

1. The correct sequence of steps to change the target device from STM32H753ZI to STM32H733ZGTX in the three projects (SECoreBin, SBSFU, UserApp).
2. How to properly update / regenerate the startup files, system files and linker scripts.
3. What must be adapted in the shared Linker_Common files because of the different Flash size (2 MB → 1 MB) and memory organization of the H733.
4. Any known pitfalls or additional changes required for the H72x/H73x line (Secure User Memory, WRP, clock configuration, etc.) when starting from the H753 example.

Thank you in advance for any guidance.

 

[Bubbles]

Hello ​@Zainulabedeen,

I’m sure there’s more than one way to proceed.

If I was going to do this porting, I’d probably use CubeMX to generate a simple application project for the intended MCU (STM32H733ZGTX) and then merge the project with each of the three projects of the SBSFU solution.

That gives you the system and startup files directly. With linker, it will require some tinkering.

Most important change is that you are going from dual-bank MCU to a single bank one. Check the SBSFU project for any dual-bank specific parts which may trouble you. But you already mentioned different memory organization, so you may be aware.

By a quick look at the Linker_Common (I assume you mean to port the single slot variant) it doesn’t seem that HDP or PCROP of both banks are used, so you should be fine with one bank.

BR,

J