Skip to main content
C
Congtran90
Associate
January 20, 2025
Solved

Error: No STM32 target found! (SMT32N657X0-Q)

  • January 20, 2025
  • 2 replies
  • 7580 views

Dear Community Teams,

 

My name is Cong, and who currently perform projects with smt32. However, there is one error that I need advice from you if possible.

The description of the error as below:

- Environment used: Windows 10

- Board: SMT32N657X0-Q

- Tool: SMT32CubeProgrammer

 

- Description:

This is the first setup for my board SMT32N657X0-Q.

I used the SMT32CubeProgrammer to connect the board.

From my laptop: I saw it can connect to my laptop via ST-LINKS

 

After that, I used the smt32cubeprogrammer tool and configuration for ST-Link as the second photo (Reset mode: Software reset), I received the error:

  04:10:41 : Error: Unable to get core ID

  04:10:41 : Error: No STM32 target found! If your product embeds Debug Authentication, please perform a discovery using Debug Authentication

 

When I changed the reset mode to: Hardware reset, I received an error as Third photos:

04:20:12 : Error: Data read failed

 

In this case, I saw the tools can read the board stm32N657X0-Q, but it cannot access the memory.

- Find root causes:

I read documents "stm32_debug authentication (DA)", stm32cubeprogrammer-user_manual, STM32N647xx STM32N657xx datasheet.

 After that, I suppose the error can be relevant by Debug Authentication for the board on the first time to use.

 

- Solution fix:

I tried to see some video guides and documents below:

https://wiki.st.com/stm32mcu/wiki/Security:Debug_Authentication

https://wiki.stmicroelectronics.cn/stm32mcu/wiki/Security:Debug_Authentication_STM32H5_How_to_Introduction

https://wiki.st.com/stm32mcu/wiki/Security:How_to_install_a_trusted_application_on_STM32N6_MCUs

STM32H5 Secure Manager - 07 Debug authentication

STM32Trust Secure Manager: Part 5, Hands-on Debug Authentication

 

The available guides are related to the STM32H5, H7 series, and STM32N657-DK, but I could not find any documents or guides for debug authentication on the STM32N657X0-Q.

Additionally, as shown in the fourth photo, I searched my local PC for the STM32CUBE initialization. For the "STM32N6570-DK" board, I found a folder named "ROT_Provisioning" that allows key generation. However, this folder is not available for the "NUCLEO-N657X0-Q" board.

- My questions are that:

  1. If you notice any errors in the above content, please provide hints or suggestions on how to fix them. Your advice would be greatly appreciated.
  2. I reviewed the datasheet and noticed that the STM32H5 and STM32H7 series have a different core compared to the STM32N6 series. Can I generate a passcode using the STM32H series and apply it to the STM32N657X0-Q board?
  3. I referred to the document available at this link: https://wiki.st.com/stm32mcu/wiki/Security:How_to_install_a_trusted_application_on_STM32N6_MCUs . It provides detailed guidelines for debug authentication on the STM32N6-DK, but it does not apply to the STM32N657X0-Q. How can I adapt the guide for the STM32N6-DK to generate a passcode for the STM32N657X0-Q board?
  4. While reviewing the Secure Programming section, I noticed it requires provisioning. Where can we input the passcode mentioned in the fifth photo?

Thank you a lot for your great advice and suggestions. I appreciate your help!

Have a good day to all our teams

 

Best regards

Cong Tran

01_connect_laptop_port.JPG02_resetmode_Software_Not_connect.JPG03_Hardware_reset_connected.JPG04_Cannot_See_ROT_Provitioning_SMT32N657X0-Q.JPG05_passcode_start_programming_provisioning.JPG

Best answer by RomainR.

Hello @Congtran90 

I understand you are trying to etablish a SWD connection between NUCLEO-N657X0-Q and STM32CubeProgrammer.
Make sure that you are using the last STM32CubeProgrammer v2.18.0 version.

You need to change BOOT1 = 1 (JP2) jumper configuration to put the STM32N6570 in DevBOOT mode.This mode allow Debug port access by the bootROM.  

You can refer to my post below and refer to the attached document (NUCLEO-N6570X0Q_Dev_BOOT.pdf)

https://community.st.com/t5/stm32-mcus-boards-and-hardware/nucleo-n657x0-q-failed-to-start-gdb-server/m-p/756600#M23206

Let me known if it solve your issue?

Best regards,

Romain,

 

2 replies

Andrew Neil
Andrew Neil
Super User
January 21, 2025

You didn't say what board you're using:

https://community.st.com/t5/community-guidelines/how-to-write-your-question-to-maximize-your-chances-to-find-a/tac-p/725146/highlight/true#M54:~:text=2.%20%5BEnvironment%5D%20Describe%20the%20environment%20used%20as%20toolchain%20and%20hardware%20and%20state%20the%20version%20used.%0A3.%20%5BSchematics%5D%20If%20it%20is%20a%20custom%20board%20%2D%2D%3E%20Share%20the%20schematics%20using%20%E2%80%9CAttach%20file%E2%80%9D%20option%20or%20inserting%20some%20image.

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.
    C
    Congtran90Author
    Associate
    January 21, 2025

    Dear Andrew Neil,

    Thank a lot for your advice, I will take experience and take note it. 

    I will follow your guides and template on the next time. 

    My board used as STM32N657X0-Q.

    Thank a lot for your support!

    Have a good day to You!

    Best regards

    Tran Quoc Cong,

    Andrew Neil
    Andrew Neil
    Super User
    January 21, 2025
    @Congtran90 wrote:

    My board used as STM32N657X0-Q.

    That tells us nothing about the rest of the board!

    When it's a custom board, you need to post the schematics, details of how you're connecting to it, etc.

    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.
      RomainR.
      RomainR.Best answer
      ST Employee
      January 21, 2025

      Hello @Congtran90 

      I understand you are trying to etablish a SWD connection between NUCLEO-N657X0-Q and STM32CubeProgrammer.
      Make sure that you are using the last STM32CubeProgrammer v2.18.0 version.

      You need to change BOOT1 = 1 (JP2) jumper configuration to put the STM32N6570 in DevBOOT mode.This mode allow Debug port access by the bootROM.  

      You can refer to my post below and refer to the attached document (NUCLEO-N6570X0Q_Dev_BOOT.pdf)

      https://community.st.com/t5/stm32-mcus-boards-and-hardware/nucleo-n657x0-q-failed-to-start-gdb-server/m-p/756600#M23206

      Let me known if it solve your issue?

      Best regards,

      Romain,

       

      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.
        C
        Congtran90Author
        Associate
        January 21, 2025

        Dear RomainR,

        I would like to thank a lot for your great advice and your suggestion, 

        Your solution is really helpful for me and my work, and that help me to solve the issues.

        Yes, I am developing mode so I need to change connection in the JumpJ2 as your guide documents and then it works well,

        Thank you a lot for your great solution and quick!

        Have a good day to You!

        Best regards

        Tran Quoc Cong,

          Terms & ConditionsAccessibility statement