Skip to main content
cherrytasty
Visitor II
August 26, 2024
Solved

NO STM 32 Target Found, Target No Device Found (Nucleo-F446RE)

cherrytasty_0-1724635922479.png

cherrytasty_1-1724635956025.png

what should i do..?

 

This topic has been closed for replies.
TDK
TDKBest answer
August 26, 2024

> Target voltage: 0.31 V

This is a power issue. No change of a chip working without a proper power supply. Ensure the power jumper is set correctly. Perhaps a part on the board got damage in the course of debugging. It sees the ST-Link chip, so the board is probably okay. Consider looking at the schematic to track down the power issue.

"If you feel a post has answered your question, please click ""Accept as Solution""."
View in thread

4 replies

mƎALLEm
mƎALLEm
ST Technical Moderator
August 26, 2024

Hello,

First check if you are using a data cable not a charging cable

To give better visibility on the answered topics, please click "Best answer" on the reply which solved your issue or answered your question.
    Tesla DeLorean
    Tesla DeLorean
    Guru
    August 26, 2024

    Do you have code that's reconfiguring the PA13 / PA14 debug pins, or putting them in a low power or sleep state?

    Do you observe this problem if you pull/set BOOT0 pin HIGH? Here your code on the device won't be running and potentially breaking things.

    Tips, Buy me a coffee, or three.. PayPal Venmo (See Profile) Up vote any posts that you find helpful, it shows what's working..
      Andrew Neil
      Andrew Neil
      Super User
      August 26, 2024

      https://community.st.com/t5/stm32-mcus/how-to-solve-debugger-connection-issues/ta-p/49693

       

      A complex system that works is invariably found to have evolved from a simple system that worked.A complex system designed from scratch never works and cannot be patched up to make it work.
      TDK
      TDKBest answer
      August 26, 2024

      > Target voltage: 0.31 V

      This is a power issue. No change of a chip working without a proper power supply. Ensure the power jumper is set correctly. Perhaps a part on the board got damage in the course of debugging. It sees the ST-Link chip, so the board is probably okay. Consider looking at the schematic to track down the power issue.

      "If you feel a post has answered your question, please click ""Accept as Solution""."
        Terms & ConditionsAccessibility statement