How to program one NUCLEO-H753ZI Board using another's ST-Link?

[Vasanth_L]

Hello ST Community,

I have two NUCLEO-H753ZI boards and I want to use Board 1's on-board ST-Link
to program Board 2's MCU through the CN5 (MIPI-10) connector.

My Setup:
- Board 1 (Programmer): Connected to PC via USB, will provide ST-Link
- Board 2 (Target): Connected via 10-pin ribbon cable to Board 1's CN5
- Both boards are NUCLEO-H753ZI (MB1549 or MB1940)

My Questions:

1. Which jumpers need to be removed on Board 2 to disconnect its on-board
ST-Link from the target MCU?
- I see several connectors with jumpers in the ST-Link section (CN2, JP4, JP5, etc.)
- Which specific jumpers control the SWD connection (SWDIO/SWCLK)?

2. Should jumpers remain installed on Board 1 (the programmer board)?

3. What is the correct CN5 pinout for the MIPI-10 connector on NUCLEO-H753ZI?
- I want to verify my ribbon cable connections are correct

4. For power, should I:
- Power Board 2 through CN5 Pin 3 (VCC) from Board 1?
- Or use separate USB power for Board 2?

5. In STM32CubeIDE, I'm getting "Multiple ST-LINKs detected" error.
How do I configure it to use only Board 1's ST-Link?

What I've Tried:
- Connected both boards via 10-pin ribbon cable on CN5
- Attempted to remove jumpers but unsure which ones are correct
- Getting intermittent connection errors

Any guidance on the correct jumper configuration and connection procedure
would be greatly appreciated!

Thank you!

[Peter BENSCH]

Welcome @Vasanth_L, to the community!

Unfortunately, with the newer NUCLEO-144, the embedded STLINK-V3E can no longer be used to program other targets because the connection between STLINK and the target on that specific NUCLEO-144 cannot be easily disconnected.

You would therefore need to use an ST-LINK that can operate independently: either a separate ST-LINK/V2 or ST-LINK/V3, alternatively one from a NUCLEO-64/-144 with ST-LINK/V2-1, i.e. STM32F103 as the debugger chip, e.g. boards based on MB1137, MB1312 or MB1361 (st.com lists all variants if you are searching for one of these MBxxxx).

Regards
/Peter

[Andrew Neil]

To be honest, I'd recommend getting a standalone ST-link: it avoids a lot of faffing around, some pitfalls, and is not expensive.

For example, see this and this.