cancel
Showing results for 
Search instead for 
Did you mean: 

stm32 not detected

SS.29
Associate II

STMicroelectronics ST-LINK GDB server. Version 7.0.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.

14 REPLIES 14
FBL
ST Employee

Hello @Community member​ 

Could you please provide more details about the issue you are facing (used product, toolchain, example, board ...)?

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.


I'm out of offce with limited access to my emails.
Happy New Year!
SS.29
Associate II

.

SS.29
Associate II

i am using nucleo board stm32f401re today i interfaced obstacle avoidance sensor with this nucleo board after few seconds the board not responding it showing as not detected i tried to to update the firmware the folder contains fail text file with SWD error some youtube channels mentioned it can be resolved by using stm32 utility by flashing ROM but it was not connecting at all its popping error as

Can not connect to target!

         If you're trying to connect to an STM32W1xx device, please select Normal or HotPlug mode from Target->Settings menu.

17:23:17 : Internal command error

You wired what up, how?

Perhaps you have damaged the chips or power supply.​

Can you check voltages on the board?

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..

How to recover the corrupted stlink

If you've physically damaged it, that'll depend on your diagnostic and repair skills.

At this point you've still failed to clearly explain what you did in wiring up this external board/sensor.

It's very easy to do irreparable damage if you don't know what you are doing.

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..

I used this sensor https://www.electronicscomp.com/infrared-obstacle-avoidance-sensor-module. For sensor supply 5v i taken it from nucleo itself, i connected d4 and d5 for enable and vout of sensor. That's it i did for connection written this code

HAL_GPIO_WritePin(GPIOB, GPIO_PIN_5, 1); //enable
		HAL_Delay(2.10);
		if (HAL_GPIO_ReadPin(GPIOB, GPIO_PIN_4)) { // sensor vout
			HAL_GPIO_WritePin(GPIOA, GPIO_PIN_5, SET);  // LED out
		} else {
			HAL_Delay(3.95);
			if (HAL_GPIO_ReadPin(GPIOB, GPIO_PIN_4)) { // sensor vout
				HAL_GPIO_WritePin(GPIOA, GPIO_PIN_5, SET); // LED out
			} else {
				HAL_GPIO_WritePin(GPIOA, GPIO_PIN_5, RESET); // LED out
			}
		}
		HAL_GPIO_WritePin(GPIOB, GPIO_PIN_5, 0); // enable
		/* USER CODE BEGIN 3 */
	}

reference of this code http://irsensor.wizecode.com/

3.3V might have been a more appropriate choice.

Use STM32 Cube Programmer directly, not through the IDE

Check if you can "Connect Under Reset"

If you still can't access, try pulling the BOOT0 pin on the NUCLEO High (3.3V)

Check also the voltages on the 5V and VDD (expect 3.0 to 3.3V) rails.

Check the code, make sure you're not changing the configuration of PA13,PA14 or other pins related to the debugger, or if you are disabling debug connectivity.

>>How to recover the corrupted stlink

It's saying the Target device, ie STM32F401 isn't findable on the board, not that the ST-LINK is corrupted.

If you've wired the power incorrectly, or shorted things out on the table, or whatever, there aren't magic software fixes.

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..

Hi,

I made a simple board with the STM32F411CE base on the Weact Blackpill STM32F411CEU6 V3.0. My board countains a DC-DC converter (24V to 5V), a LDO regulator for 3.3.V the MCU, a RS-485 transceiver and a connector for some IOs. I'm using STM32CubeIDE 1.14.0, an ST-LINK V2 with firmware V2J43S7. This setup work fine with an original BlackPill with the SWD interface. I'm trying to transfert a simple blink PC13.

When I start programming the mcu, ST-Link starts normaly than stop at the begining. In the console :

STMicroelectronics ST-LINK GDB server. Version 7.5.0

Copyright (c) 2023, 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

I don't have the rest of the message like :

     Target no device found

     Error in initializing ST-LINK device.

     Reason: No device found on target.

I get a popup window with the message :

     Failed to execute MI command:
     target remote localhost:61234

The 3.3V is clean, SWDIO and SWCLK lines are not short with any other line.

Can someone tell me what can I do next to start my board ?

 

Regards,

Brut.