• State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 20 subscribers
  • Views 4965 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Getting Error " As not target connected" in STM32 controller

Toolchain missing

Hi,

I have generate led blinking project for MDK ARM Keil uvision5.25 using STM32CUbeX IDE. 
Project is compiled successfully with 0 error. 
Getting Error " As not target connected" when i try to load the firmware as per attached images. 
Connecting STM32L151CB microcontroller to ST-LINK/V2 Programmer with given 5 pin ->1) VCC 2) GND 3) SWDCLK 4) NRST 5) TMS/SWDIO

Its kind request to you to provide me the solution to resolve these error as soon as possible.

Parents
  • 0

    These types of errors will frequently occur if your device is in a low power mode or the debug pins have been repurposed or SWD disabled. Check box item in CubeMX

    A device being non-functional is another. Do you have any history with the process working?

    With the stand-alone ST-LINK/V2 you must power pin 1/2 with VTarget. The voltage will be reported in tools like the ST-LINK Utilities.

    Keil's debugger settings provide for assorted connectivity and reset options. If your code is breaking the interface consider "Connect Under Reset" options. In particularly broken situations you can pull the BOOT0 pin HIGH so it resets into ROM allowing for recovery.

    When debugging avoid using low power/sleep modes, via _WFI() for example, as this will power off the logic the debugger is talking too, and it will drop the connection.

Reply
  • 0

    These types of errors will frequently occur if your device is in a low power mode or the debug pins have been repurposed or SWD disabled. Check box item in CubeMX

    A device being non-functional is another. Do you have any history with the process working?

    With the stand-alone ST-LINK/V2 you must power pin 1/2 with VTarget. The voltage will be reported in tools like the ST-LINK Utilities.

    Keil's debugger settings provide for assorted connectivity and reset options. If your code is breaking the interface consider "Connect Under Reset" options. In particularly broken situations you can pull the BOOT0 pin HIGH so it resets into ROM allowing for recovery.

    When debugging avoid using low power/sleep modes, via _WFI() for example, as this will power off the logic the debugger is talking too, and it will drop the connection.

Children
No data