Skip to main content
K
kalvacherla.chandrashekhar
Visitor II
October 9, 2020
Solved

Connecting using ST-Link for STM32H745 Discovery Kit is not working.

  • October 9, 2020
  • 2 replies
  • 2674 views

Hi ,

Additional to this I will need some Technical Support on the Board Bring-up . Please forward me the Technical Support Person Email ID .

I have a Project using STM32H745XI Micro Controller , I have followed previous known steps to Generate Source code using STM32CubeMX for STM32H745XI.

I have sucessfully built the files using the STM32CubeIDE for STM32H745XI Discovery Kit , I am not able to Debug the souce code connecting with using ST-Link on the Discovery Kit . Is there any special settings that needs to be taken care other than the following .

  

 I have installed the ST-Link Driver from the following link

Open On-Chip Debugger 0.10.0+dev-g30d1303 (2020-06-18-09:13)

Licensed under GNU GPL v2

For bug reports, read

http://openocd.org/doc/doxygen/bugs.html

stm32h7x_cti_prepare_restart_one

Info : Listening on port 6666 for tcl connections

Info : Listening on port 4444 for telnet connections

Info : connected to stlink-server

Info : stlink-server API v1, version 1.3.0

Info : STLINK V3J3M2 (API v3) VID:PID 0483:374E

Info : Target voltage: 3.274320

Error: init mode failed (unable to connect to the target)

0693W000004JGX0QAO.png 

0693W000004JGicQAG.png0693W000004JGiNQAW.png0693W000004JHBAQA4.png 

The interface firmware FAILED to reset/halt the target MCU

0693W000004JHPWQA4.png 

    This topic has been closed for replies.
    Best answer by kalvacherla.chandrashekhar

    Hi ,

    Yes the STM32H7 was Bricked , I am able to now recover the board 10K resistance De-Soldered from R143 and Soldered on to R144 .( There should have been an Jumper provided or ,,, the ST-LINK should have had GPIO method to recovered the board )

    0693W000004Jt3OQAS.pngAfter Going through the user manual it is mentioned in an Caution: :sad_but_relieved_face:

    2 replies

    A
    Amel NASRI
    Technical Moderator
    October 13, 2020

    Hi @kalvacherla.chandrashekhar​ ,

    From STM32CubeProgrammer interface, try to perform a Firmware upgrade. Is that possible?

    Does it resolve your issue?

    -Amel

    T
    Tesla DeLorean
    Graduate II
    October 13, 2020

    @Amel NASRI​ 

    See also https://community.st.com/s/question/0D53W00000KopMmSAJ/deadlock-on-stm32h745idisco-board-and-it-throws-error-no-stm32-target-found-in-stm32cubeprogrammer

    Seems more likely that the H7 is bricked with user software, and the ST-LINK here isn't switching to DFU/Update mode. Don't think this board provides jumpers to disconnect SWDIO/SWCLK from the target.

    K
    kalvacherla.chandrashekharAuthorAnswer
    Visitor II
    October 15, 2020

    Hi ,

    Yes the STM32H7 was Bricked , I am able to now recover the board 10K resistance De-Soldered from R143 and Soldered on to R144 .( There should have been an Jumper provided or ,,, the ST-LINK should have had GPIO method to recovered the board )

    0693W000004Jt3OQAS.pngAfter Going through the user manual it is mentioned in an Caution: :sad_but_relieved_face:

    T
    Tesla DeLorean
    Graduate II
    October 13, 2020

    >>Please forward me the Technical Support Person Email ID

    Direct engineering support for STM32 products is typically rendered through the local sales office responsible for your account, and the FAE's stationed there.

    Terms & ConditionsAccessibility statement