cancel
Showing results for 
Search instead for 
Did you mean: 

STM32H747 Discovery Kit Not Debug/Programmer

FarukSozuer
Associate III

Hello;

I can't program and debug with the STM32H747 Discovery kit. I tried Stm32cubeProgrammer and STM32CubeIDE for this. Below are the errors I have received in both.

0690X00000AsYXWQA3.png

0690X00000AsYXgQAN.png

Debug configuration screen is below;

0690X00000AsYXqQAN.png

STLink Serial number appears, but I can't understand why it can't program it?

Sincelery

1 ACCEPTED SOLUTION

Accepted Solutions

If you've screwed up the LDO/SMPS and/or VOS settings it will brick the board.

The recovery method in that case is to solder a link on the BOOT0 pin so it is high. Then cycle the board power completely (remove all connections/power sources) several times, until you can connect.

Check you can connect with STM32 Cube Programmer or ST-LINK Utilities, and then Mass Erase your code from flash.

On the H747I-DISCO I had, access to BOOT0 was via a small resistor pad (R192) under the screen. You'll need to check docs for current board to confirm.

Then, once recovered, stop putting code with broken settings on it, or provide secondary methods to stop the clock/system configuration code running.

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

View solution in original post

10 REPLIES 10
Ozone
Lead

Perhaps your target device refuses to cooperate, because it goes into a sleep mode or has re-assigned the JTAG pins at runtime.

Try a mass-erase from the system bootloader mode.

Markus GIRDLAND
ST Employee

I recently created this document to show how to get started with a H7 debug session, including how to set up the debug confgurations for both cores.

Check it out and see if it helps you get up and running.

FarukSozuer
Associate III

Hello @Markus GIRDLAND​ 

The result has not changed, although I have implemented the document step by step. I updated to see if there is a problem with the STLINK version. But the result did not change again.

Version information is below;

0690X00000AsZAOQA3.png

Sincelery

Hello @Markus GIRDLAND (ST Employee)​ 

The result has not changed, although I have implemented the document step by step. I updated to see if there is a problem with the STLINK version. But the result did not change again. 

Version information is below;

0690X00000AsZAOQA3.png

In addition 2 of 4 discovery boards are in this case.

Sincelery

And you can't connect through STM32CubeProgrammer either? Then I would check power/cabling and make sure your computer can detect that the board is connected, I don't believe it's CubeIDE related more likely board/HW related.

It might be in low power mode as well, then it could help to "connect under reset" through either CubeIDE or CubeProgrammer.

If you've screwed up the LDO/SMPS and/or VOS settings it will brick the board.

The recovery method in that case is to solder a link on the BOOT0 pin so it is high. Then cycle the board power completely (remove all connections/power sources) several times, until you can connect.

Check you can connect with STM32 Cube Programmer or ST-LINK Utilities, and then Mass Erase your code from flash.

On the H747I-DISCO I had, access to BOOT0 was via a small resistor pad (R192) under the screen. You'll need to check docs for current board to confirm.

Then, once recovered, stop putting code with broken settings on it, or provide secondary methods to stop the clock/system configuration code running.

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

Thanks for answer @Community member​ 

I just tried throwing a blink LED flashing code. In this case the LDO / SMPS / VOS settings corrupt is a bit creepy.

I will try, the things you told me and shared the results.

Hello @Community member​ 

Problem is solved. I have a few questions to fully understand the source of the problem.

  1. I found that the LDO / SMPS / VOS settings are usually related to the clock settings. For example, do I need to make specific changes to LDO / SMPS / VOS to work at 480Mhz?
  2. Are these changes software or hardware?
  3. If it is software, can I do it from CubeMx?

Sincelery

I found the relevant settings. System Core->RCC->Under Parameter Settings.