Using STM32WB55RGV6 to program another board

[Kolab]

Hello! On the board STM32WB55RGV6 there is the connector CN13, where is written STLINK (reserved). Can I use these pins to program another board?

[Mike_ST]

Hello,

No, as you wrote, CN13 is a "reserved" connector, so please avoid touching it.

Use JP5 and remove appropriate jumpers to get the SWDIO/SWDCLK/GND signals and plug them to another target. Should work.

Please check MB1355 schematics here:

https://www.st.com/en/evaluation-tools/p-nucleo-wb55.html#cad-resources

[Kolab]

i'll try it thank you

[Kolab]

@Mike_ST​ Keil uVision cannot find the target (SWDIO: no target connected) . The target is an usb dongle

[Tesla DeLorean]

More details...

You'll need to pick the ST-LINK and the target.

Make sure the jumpers are in place to connect the on-board ST-LINK to the internal target.

Perhaps also try to validate connectivity using STM32 Cube Programmer.

Current version of Keil, most up to date ST-LINK .DLL's etc?

[Tesla DeLorean]

The STM32WB55RGV6 is a chip, not a board.

The NUCLEO/DISCO boards will have an on-board ST-LINK/V2 or V3 debugger implemented in an F103 or F723 IC

[Mike_ST · Accepted solution]

Just tested, it is working fine with STM32CubeProgrammer. I connected an MB1355 to an MB1319 (STM32L452) with 3 wires only.

MB1319 ST-LINK is kept under reset to allow using MB1355 one.

[Kolab]

@Mike_ST​ I see that you put a jumper between VDD and BOOT0. Did you put a jumper somewhere else on the MB1355 ?

[Kolab]

@Community member​ Current version of Keil, most up to date ST-LINK .DLL's etc?

And how can I do this?

[Mike_ST]

This BOOT0 jumper is not important as the ST-LINK probe on the MB1355 is disconnected from the STM32WB55.

I haven't done anything else.