STM32CubeIDE + STLINK-V3MINI + NUCLEO-L496ZG

CKugl.1 · ‎2022-12-09

I'm running a STM32L496ZGT6U on a NUCLEO-L496ZG. Previously, I used the NUCLEO's integrated ST-LINK/V2-1 debugger/programmer. Now, I have sawed off the ST-LINK part of the PCB. I want to program and debug using a STLINK-V3MINI.

I wired up STDC14 for STLINK-V3MINI (STM32 JTAG/SWD and VCP) to the NUCLEO:

(Web page)

I'm powering the NUCLEO board with 9.0 V on Vin.

If I connect a USB cable to the V3MINI and try to debug in STM32CubeIDE, I get:

STMicroelectronics ST-LINK GDB server. Version 7.1.0
Copyright (c) 2022, STMicroelectronics. All rights reserved.
 
Starting server with the following options:
        Persistent Mode            : Disabled
        Logging Level              : 1
        Listen Port Number         : 61234
        Status Refresh Delay       : 15s
        Verbose Mode               : Disabled
        SWD Debug                  : Enabled
        InitWhile                  : Enabled
 
Target no device found
 
Error in initializing ST-LINK device.
Reason: No device found on target.

Error in final launch sequence:
 
Failed to execute MI command:
target remote localhost:61234
 
Error message from debugger back end:
localhost:61234: Connection timed out.
Failed to execute MI command:
target remote localhost:61234
 
Error message from debugger back end:
localhost:61234: Connection timed out.
localhost:61234: Connection timed out.

If I go to Debug Configurations, Debugger, ST-LINK S/N, Scan, it finds 003800194741500820383733.

If I go to Windows Device Manager, Ports (COM & LPT), I see one entry: STMicroelectronics STLink Virtual COM Port (COM7). If I bring up PuTTY, I can connect to that port and interact with the last program that I flashed into the device.

Should I be able to make this work? I have never used the STLINK-V3MINI before.

STLINK-V3MINI LKV3MINI$AT2

MB1467-V3MINI-B02 A213402626

MB1467B9

STM32CubeIDE

Version: 1.11.0

Build: 13638_20221122_1308 (UTC)

I also went to https://www.st.com/en/development-tools/stsw-link009.html and (re)installed the ST-LINK, ST-LINK/V2, ST-LINK/V2-1, STLINK-V3 USB driver for Windows, but it didn't make any difference.

S.Ma · ‎2022-12-09

Probably a wirering mismatch. ST Link v3 mini uses 14 pin Mini connector. After saw off, you used ST Morpho connector? Did you check the schematic to make sure all signals are confirmed routed to STM32L476?

Make sure as this is the main difference...

KnarfB · ‎2022-12-09

For cross checking, you may use the sawn off ST-LINK as well like here (for a different board):

Check boot pin(s), NRST and SWD signalling with a low cost USB-LA.

hth

KnarfB

CKugl.1 · ‎2022-12-10

Dumb, dumb, dumb! I had miscounted the conductors in the ribbon cable, and once I saw it that way, that's the way I saw it for the rest of the day. It is working now.

Thanks for your answers. It helped knowing that I wasn't trying to do something far fetched.