Skip to main content
J
Jack3
Graduate II
January 25, 2024
Solved

Nucleo-H755ZI-Q How can I resolve ST-Link "No device found on target" error?

  • January 25, 2024
  • 2 replies
  • 3393 views

I have made a simple program flashing LED's from both cores and sending data between the two cores using a struct that resided on the same memory space for both.

I used latest STM32CubeMX (Version: 6.9.2), STM32CubeIDE (Version: 1.14.1), and latest STLink firmware.

It kept working reliable, until I added a few more peripherals to the project.

After that I suddenly got programming errors, like:

"No STM32 targets found"

I needed to use STM32CubeProgrammer to erase the chip, where I only could connect using mode "Power down".

After this, I could download (Download verified successfully), but the cores do not start anymore.

After a few attempts, I get these errrors again:

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 foundError in initializing ST-LINK device.
Reason: No device found on target.

 

I tried several settings in STM32CubeMX, 5V external power, and using an ST-Link V3 probe.

I already destroyed two NUCLEO-H755ZI-Q boards by just flashing their LEDs, and I'm out of ideas.

How can I recover those?

I don't hope the multi-core MCU gets that easily destroyed.

I have put the project on github.

The simple project needs to flash a few LEDs and goes into "No STM32 targets found" easily, after a few times of programming.

https://github.com/AngryCarrot61/NUCLEO-H755ZI-Q_001

I hope somebody finds my mistake.

 

I have used numerous Nucleo-Boards and custom boards and never got big problems.

Some projects got large and complicated, but it always works flawlessy using STM32's.

This is the first time I get puzzled, using this multi-core MCU, after I first got it running succesful, and then nothing can run anymore on them, even flashing them got very troublesome.

 

    This topic has been closed for replies.
    Best answer by Tesla DeLorean

    You're supposed to be using the SMPS power supply setting not the LDO.

    How to recover, add jumper pins between BT0 and VDD, bridge jumper, remove and apply power connection / USB a couple of times, open / connect in STM32 Cube Programmer, and Mass Erase devices. After erase you can remove the jumper.

     

    /**
 * @brief System Clock Configuration
 * The system Clock is configured as follow :
 * System Clock source = PLL (HSE BYPASS)
 * SYSCLK(Hz) = 400000000 (CPU Clock)
 * HCLK(Hz) = 200000000 (Cortex-M4 CPU, Bus matrix Clocks)
 * AHB Prescaler = 2
 * D1 APB3 Prescaler = 2 (APB3 Clock 100MHz)
 * D2 APB1 Prescaler = 2 (APB1 Clock 100MHz)
 * D2 APB2 Prescaler = 2 (APB2 Clock 100MHz)
 * D3 APB4 Prescaler = 2 (APB4 Clock 100MHz)
 * HSE Frequency(Hz) = 8000000
 * PLL_M = 4
 * PLL_N = 400
 * PLL_P = 2
 * PLL_Q = 4
 * PLL_R = 2
 * VDD(V) = 3.3
 * Flash Latency(WS) = 4
 * None
 * @retval None
 */
static void SystemClock_Config(void)
{
 RCC_ClkInitTypeDef RCC_ClkInitStruct;
 RCC_OscInitTypeDef RCC_OscInitStruct;
 HAL_StatusTypeDef ret = HAL_OK;

 /*!< Supply configuration update enable */
 HAL_PWREx_ConfigSupply(PWR_DIRECT_SMPS_SUPPLY); // <<< DO THIS, NOT LDO

 /* 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_SCALE1);

 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;
 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;

 RCC_OscInitStruct.PLL.PLLM = 4;
 RCC_OscInitStruct.PLL.PLLN = 400;
 RCC_OscInitStruct.PLL.PLLFRACN = 0;
 RCC_OscInitStruct.PLL.PLLP = 2;
 RCC_OscInitStruct.PLL.PLLR = 2;
 RCC_OscInitStruct.PLL.PLLQ = 4;

 RCC_OscInitStruct.PLL.PLLVCOSEL = RCC_PLL1VCOWIDE;
 RCC_OscInitStruct.PLL.PLLRGE = RCC_PLL1VCIRANGE_1;
 ret = HAL_RCC_OscConfig(&RCC_OscInitStruct);
 if(ret != HAL_OK)
 {
 Error_Handler();
 }

/* Select PLL as system clock source and configure bus clocks dividers */
 RCC_ClkInitStruct.ClockType = (RCC_CLOCKTYPE_SYSCLK | RCC_CLOCKTYPE_HCLK | RCC_CLOCKTYPE_D1PCLK1 | RCC_CLOCKTYPE_PCLK1 | \
 RCC_CLOCKTYPE_PCLK2 | RCC_CLOCKTYPE_D3PCLK1);

 RCC_ClkInitStruct.SYSCLKSource = RCC_SYSCLKSOURCE_PLLCLK;
 RCC_ClkInitStruct.SYSCLKDivider = RCC_SYSCLK_DIV1;
 RCC_ClkInitStruct.AHBCLKDivider = RCC_HCLK_DIV2;
 RCC_ClkInitStruct.APB3CLKDivider = RCC_APB3_DIV2;
 RCC_ClkInitStruct.APB1CLKDivider = RCC_APB1_DIV2;
 RCC_ClkInitStruct.APB2CLKDivider = RCC_APB2_DIV2;
 RCC_ClkInitStruct.APB4CLKDivider = RCC_APB4_DIV2;
 ret = HAL_RCC_ClockConfig(&RCC_ClkInitStruct, FLASH_LATENCY_4);
 if(ret != HAL_OK)
 {
 Error_Handler();
 }

 /*activate CSI clock mondatory for I/O Compensation Cell*/
 __HAL_RCC_CSI_ENABLE() ;

 /* Enable SYSCFG clock mondatory for I/O Compensation Cell */
 __HAL_RCC_SYSCFG_CLK_ENABLE() ;

 /* Enables the I/O Compensation Cell */
 HAL_EnableCompensationCell();
}

     

    2 replies

    T
    Tesla DeLoreanAnswer
    Graduate II
    January 25, 2024

    You're supposed to be using the SMPS power supply setting not the LDO.

    How to recover, add jumper pins between BT0 and VDD, bridge jumper, remove and apply power connection / USB a couple of times, open / connect in STM32 Cube Programmer, and Mass Erase devices. After erase you can remove the jumper.

     

    /**
 * @brief System Clock Configuration
 * The system Clock is configured as follow :
 * System Clock source = PLL (HSE BYPASS)
 * SYSCLK(Hz) = 400000000 (CPU Clock)
 * HCLK(Hz) = 200000000 (Cortex-M4 CPU, Bus matrix Clocks)
 * AHB Prescaler = 2
 * D1 APB3 Prescaler = 2 (APB3 Clock 100MHz)
 * D2 APB1 Prescaler = 2 (APB1 Clock 100MHz)
 * D2 APB2 Prescaler = 2 (APB2 Clock 100MHz)
 * D3 APB4 Prescaler = 2 (APB4 Clock 100MHz)
 * HSE Frequency(Hz) = 8000000
 * PLL_M = 4
 * PLL_N = 400
 * PLL_P = 2
 * PLL_Q = 4
 * PLL_R = 2
 * VDD(V) = 3.3
 * Flash Latency(WS) = 4
 * None
 * @retval None
 */
static void SystemClock_Config(void)
{
 RCC_ClkInitTypeDef RCC_ClkInitStruct;
 RCC_OscInitTypeDef RCC_OscInitStruct;
 HAL_StatusTypeDef ret = HAL_OK;

 /*!< Supply configuration update enable */
 HAL_PWREx_ConfigSupply(PWR_DIRECT_SMPS_SUPPLY); // <<< DO THIS, NOT LDO

 /* 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_SCALE1);

 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;
 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;

 RCC_OscInitStruct.PLL.PLLM = 4;
 RCC_OscInitStruct.PLL.PLLN = 400;
 RCC_OscInitStruct.PLL.PLLFRACN = 0;
 RCC_OscInitStruct.PLL.PLLP = 2;
 RCC_OscInitStruct.PLL.PLLR = 2;
 RCC_OscInitStruct.PLL.PLLQ = 4;

 RCC_OscInitStruct.PLL.PLLVCOSEL = RCC_PLL1VCOWIDE;
 RCC_OscInitStruct.PLL.PLLRGE = RCC_PLL1VCIRANGE_1;
 ret = HAL_RCC_OscConfig(&RCC_OscInitStruct);
 if(ret != HAL_OK)
 {
 Error_Handler();
 }

/* Select PLL as system clock source and configure bus clocks dividers */
 RCC_ClkInitStruct.ClockType = (RCC_CLOCKTYPE_SYSCLK | RCC_CLOCKTYPE_HCLK | RCC_CLOCKTYPE_D1PCLK1 | RCC_CLOCKTYPE_PCLK1 | \
 RCC_CLOCKTYPE_PCLK2 | RCC_CLOCKTYPE_D3PCLK1);

 RCC_ClkInitStruct.SYSCLKSource = RCC_SYSCLKSOURCE_PLLCLK;
 RCC_ClkInitStruct.SYSCLKDivider = RCC_SYSCLK_DIV1;
 RCC_ClkInitStruct.AHBCLKDivider = RCC_HCLK_DIV2;
 RCC_ClkInitStruct.APB3CLKDivider = RCC_APB3_DIV2;
 RCC_ClkInitStruct.APB1CLKDivider = RCC_APB1_DIV2;
 RCC_ClkInitStruct.APB2CLKDivider = RCC_APB2_DIV2;
 RCC_ClkInitStruct.APB4CLKDivider = RCC_APB4_DIV2;
 ret = HAL_RCC_ClockConfig(&RCC_ClkInitStruct, FLASH_LATENCY_4);
 if(ret != HAL_OK)
 {
 Error_Handler();
 }

 /*activate CSI clock mondatory for I/O Compensation Cell*/
 __HAL_RCC_CSI_ENABLE() ;

 /* Enable SYSCFG clock mondatory for I/O Compensation Cell */
 __HAL_RCC_SYSCFG_CLK_ENABLE() ;

 /* Enables the I/O Compensation Cell */
 HAL_EnableCompensationCell();
}

     

      T
      Tesla DeLorean
      Graduate II
      January 25, 2024

      The -Q boards use SMPS

      https://github.com/STMicroelectronics/STM32CubeH7/blob/master/Projects/NUCLEO-H745ZI-Q/Examples/BSP/CM7/Src/main.c#L217

      https://github.com/STMicroelectronics/STM32CubeH7/blob/master/Projects/NUCLEO-H745ZI-Q/Templates/BootCM4_CM7/CM7/Src/main.c#L142

      The H755ZI-Q is the crypto/hash version of the H745ZI-Q

       

      You're doing this 

      https://github.com/AngryCarrot61/NUCLEO-H755ZI-Q_001/blob/main/CM7/Core/Src/main.c#L172

       

      BT0 (BOOT0) and VDD jumper. Bridge with spare jumper, and power cycle board completely twice.

      nucleo144_boot0_jumper.jpg

        J
        Jack3Author
        Graduate II
        January 26, 2024

        Thank you very much!

        This solved the problem.

        Note I could erase the chip without the jumper in STM32CubeProg using mode Power down.

        I tested with the jumper and it works very well.

        And the code is executing again.

        I bought you a coffee!

        chrome_solj2TPwGk.png

         

        I found this in the board user manual:

        If a deadlock is faced due to a mismatch between the
        hardware board setting and the firmware setting (LDO/SMPS),
        the user can recover the board by doing the following:
        - Power off the board
        - Connect CN11 ‘BT0’ pin (BOOT0) to VDD using a wire
        - This changes the BOOT0 pin to HIGH instead of LOW and
        thus the device boot address is changed to boot address 1
        making the bootloader starting in System memory, instead of
        starting the firmware in the user Flash (Firmware that is
        setting a wrong LDO/SMPS configuration)
        - Power on the board and connect using STM32CubeProgrammer
        - Erase the user Flash
        - Power off the board and remove the wire between BOOT0 and VDD
        - The recovery is now completed and the board can be used normally.

        AcroRd32_500W9cbqdQ.png

        stm32cubeide_5rF0F8H5HD.png

        Notice that STM32CuneMX 6.9.2 (the lastest) doesn't let you configure it correctly, you have to do it manually.

        2fKtNMVKqK.png

         

        Terms & ConditionsAccessibility statement