cancel
Showing results for 
Search instead for 
Did you mean: 

(SOLVED) STMH7A3ZI-Q. No STM32 target found. ST-link working.

MSham.3
Associate

I received my stm32h7 nucleo board yesterday. It worked fine with StmCubeProgrammer and uploaded multiple programs on it but from today I can not connect my board to Cube programmer.

The error code I am receiving is given below :

 00:00:22 : STM32CubeProgrammer API v2.9.0

 00:00:22 : ST-LINK error (DEV_CONNECT_ERR)

 00:06:14 : ST-LINK SN : 002C00483038511834333935

 00:06:14 : ST-LINK FW : V3J9M3

 00:06:14 : Board    : NUCLEO-H7A3ZI-Q

 00:06:14 : Voltage   : 3.26V

 00:06:14 : No STM32 target found!

 00:06:14 : ST-LINK SN : 002C00483038511834333935

 00:06:14 : ST-LINK FW : V3J9M3

 00:06:14 : Board    : NUCLEO-H7A3ZI-Q

 00:06:14 : Voltage   : 3.26V

 00:06:14 : Error: No STM32 target found!

Things I have tried but was unsuccessful:

*Reinstalling everything, drivers included.

*Using a different windows computer.

*Tried hardware button reset then connecting.

*Tried ST-link Utility

*Tried to erase full chip also erase all sectors

*Different cables

*Powering it externally

*Tp1 measures 3.3v and tp2 is 1.8v

*Tried connecting an FTDI usb-uart board to the D0 and D1 pins.

*Changing the frequency and reset mode.

*Upgrading the st-link FW

I have multiple stm32f4 boards and non of those ever acted this way. I am at a loss now. Refunding is not an option unfortunately. I do not have a ST-Link. But I do have st-link enabled nucleo boards. I do not have any jtag accessories only have ftdi usb-uart boards.

I would be extremely grateful if someone could help me with this. I have searched the net for solves but nothing works for me.

Regards

Wahid

Edit- Solved it by connecting BT0 to VDD and erasing the chip. Should have read the user manual first before panicking !

2 REPLIES 2
MM..1
Chief III

STLInk is dedicated MCU and on your board seems have trouble connect to main MCU.

Many possible corruption exist.

Try use secondary usb connected to main MCU and activate system bootloader mode DFU,

or check main MCU other way.

Make sure you're using appropriate SMPS/LDO settings, and VOS settings for the board.

STM32Cube_FW_H7_V1.8.0\Projects\NUCLEO-H7A3ZI-Q\Examples\CRC\CRC_Example\Src\main.c

static void SystemClock_Config(void)
{
  RCC_ClkInitTypeDef RCC_ClkInitStruct = {0};
  RCC_OscInitTypeDef RCC_OscInitStruct = {0};
 
  /*!< Supply configuration update enable */
  HAL_PWREx_ConfigSupply(PWR_DIRECT_SMPS_SUPPLY); // VERY IMPORTANT
 
  /* The voltage scaling allows optimizing the power consumption when the device is
  clocked below the maximum system frequency, to update the voltage scaling value
  regarding system frequency refer to product datasheet.
  */
  __HAL_PWR_VOLTAGESCALING_CONFIG(PWR_REGULATOR_VOLTAGE_SCALE0);
 
  while(!__HAL_PWR_GET_FLAG(PWR_FLAG_VOSRDY)) {}
 
  /* Enable HSE Oscillator and activate PLL with HSE as source */
  RCC_OscInitStruct.OscillatorType = RCC_OSCILLATORTYPE_HSE;
  RCC_OscInitStruct.HSEState = RCC_HSE_BYPASS; // EXTERNAL CLOCK SOURCE
  RCC_OscInitStruct.HSIState = RCC_HSI_OFF;
  RCC_OscInitStruct.CSIState = RCC_CSI_OFF;
  RCC_OscInitStruct.PLL.PLLState = RCC_PLL_ON;
  RCC_OscInitStruct.PLL.PLLSource = RCC_PLLSOURCE_HSE;
...

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