AnsweredAssumed Answered

External ST-LINK/V2 programmer/debugger with STM32F4DISCOVERY board

Question asked by .michele. on Jan 9, 2014
Latest reply on Jan 10, 2014 by Clive One
Hi,

I have bought:
1)a STM32F4DISCOVERY board (with on-board ST-LINK/V2 programmer/debugger)
http://www.st.com/web/en/catalog/tools/PF252419
2)a separate ST-LINK/V2 programmer/debugger.
http://www.st.com/web/catalog/tools/FM146/CL1984/SC724/SS1677/PF251168
 
I have downloaded and installed on my PC (windows XP) the following tools:
1) STSW-LINK003 (ST-LINK/V2 USB driver for Windows 7, Vista and XP)
http://www.st.com/web/en/catalog/tools/PF258167
2) STSW-LINK004 (STM32 ST-LINK utility)
http://www.st.com/web/en/catalog/tools/PF258168
 
So, I have:
STM32 ST-LINK Utility.exe v3.2.1
STLinkUSBDriver.dll v4.2.4.0
ST-LINK_CLI.exe v1.8.1

I have verified, by the ST-LINK utility, that:
1)ST-LINK/V2 adapter firmware version is "V2.J17.S4 JTAG+SWIM Debugger"
2)On-board ST-LINK/V2 programmer firmware version is "V2.J14.S0 JTAG"
 
When I connect by a USB cable the PC with STM32F4DISCOVERY board (with jumpers JP1 and CN3 ON), and I try to the target by the menu command "target->connect" of the ST-LINK utility, I obtain the following log messages (connection OK):

        ST-LINK Firmware version : V2J14S0
        Connected via SWD.
        Connetion mode : Connect Under Reset.
        Debug in sleep and stop mode enabled.
        Device ID:0x413
        Device flash Size : 1 Mbytes
        Device family :STM32F40x / STM32F41x

However, when I try to connect the target by using the separate ST-LINK/V2 programmer/debugger, I obtain the error message "can not connect to target". The ST-LINK/V2 status led is initially RED (communication between the PC and ST-LINK/V2 is established), then (when I try to connect the target) becomes blinking GREEN/RED (data are being exchanged between the target and the PC), and finally becomes ORANGE (ST-LINK/V2 communication with the target has failed).

To perform this trial, I have:
1) removed the two CN3 jumpers (to switch to the external programmer/debugger)    
2) connected the STM32F4DISCOVERY board with the PC by an USB cable (only for power supply)
3) connected the ST-LINK/V2 with the PC by an USB cable
4) connected JTAG/SWD connector (20 pin) of the ST-LINK/V2 to SWD connector (6 pin) of the STM32F4DISCOVERY board as in the following:
    VDD        pin #1  of JTAG/SWD 20-pin connector on ST-LINK/V2 <-> pin #1 of SWD
      6-pin connector on STM32F4DISCOVERY
    VDD        pin #2  of JTAG/SWD 20-pin connector on ST-LINK/V2 <-> pin #1 of SWD
      6-pin connector on STM32F4DISCOVERY
    GND        pin #4  of JTAG/SWD 20-pin connector on ST-LINK/V2 <-> pin #3 of SWD
      6-pin connector on STM32F4DISCOVERY
    SWDIO    pin #7  of JTAG/SWD 20-pin connector on ST-LINK/V2 <-> pin #4 of
      SWD 6-pin connector on STM32F4DISCOVERY
    SWCLK    pin #9  of JTAG/SWD 20-pin connector on ST-LINK/V2 <-> pin #2 of SWD
       6-pin connector on STM32F4DISCOVERY
    NRST    pin #15 of JTAG/SWD 20-pin connector on ST-LINK/V2 <-> pin #5 of SWD
      6-pin connector on STM32F4DISCOVERY
        
Someone knows why the configuration with the external ST-LINK does not work?

Michele

Outcomes