cancel
Showing results for 
Search instead for 
Did you mean: 

Setting for debugging on STM32h757 Controller using stmcube IDE

Shiv09
Senior

Hello All,

 

I am facing a problem for debugging one of the board which uses stm32h7 controller.

I am not sure why this is happening but on other board I am able to debug it, but for first one its not working.

Though the code and debug config settings are same for both the board and using same system to debug both, but on one board I am able to debug while on other its is not. so could you please tell me what I can try to resolve this issue.

 

Thanks,

SD 

6 REPLIES 6
Andrew Neil
Super User

You need to give more details - please see: 

How to write your question to maximize your chances to find a solution

 

In particular:

  • Full details of these two boards.
  • Has the non-working board ever worked?
  • What CubeIDE version, on what platform, etc?
  • What debug probe?
  • Does CubeProgrammer work OK?
  • What, exactly, happens when you try to debug? Show error messages, etc ...

 

PS:

See also:

How to solve connection errors when connecting and programming the STM32 target board;

How to solve debugger connection issues

 

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.
mƎALLEm
ST Employee

Hello,

All STM32H7xx devices are not the same. Their ST boards too.

What board are you using. NUCLEO? DISCO? Custom?

Some boards are configured in SMPS others are in LDO.

So you need to check what power config is set in the board by hardware and set accordingly the power config by software.

But before that you need to recover the board from the power deadlock state: How can I recover my STM32H7/STM32H7RS board after facing a power configuration deadlock?

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.

Hello @Andrew Neil ,

 

Thanks for the quick reply, The post would be long so hence didn't post lot of details,

here are the details as required.

  • Full details of these two boards.- These are custom board using STM32H757BITb on it
  • Has the non-working board ever worked?- No
  • What CubeIDE version, on what platform, etc?  STM32CubeIDE
    Version: 1.17.0
  • What debug probe? ST Link gdb
  • Does CubeProgrammer work OK?- Yes using the cube programmer I am able to Flash code but have to set frequency to 1800, while other board works on 4000 (able to debug it)
  • What, exactly, happens when you try to debug? Show error messages, etc ... Have attached the images from cubeprogrammer for both frequencies. on 4000 its not getting detected but getting connected at 1800 as in images
  • Shiv09_0-1779271030222.pngShiv09_1-1779271069508.png

     

  •  
  • Shiv09_2-1779271185481.png

     

  • Changed the setting in STM CubeIDE in Debug Config set freq to Auto got above.
  • Changed the frequency to 1000, as here Shiv09_3-1779271534934.png

     

This is what happening after the code is flashed and after few seconds getting "Target is not responding, retrying"

Shiv09_4-1779272749788.png

 

1- Please provide details about the power config of your custom board? LDO? SMPS? what you have configured by software?

2- "I am not sure why this is happening but on other board I am able to debug it, but for first one its not working."

-> Are the boards having the same schematic/hardware?

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.

@Shiv09 wrote:
  • What debug probe? ST Link gdb

What version of ST-Link?

Is it genuine?

How to recognize a genuine ST-LINK/V2 versus a cloned one

Have you tried connecting under hardware reset?

Have you tried using the System Bootloader?

 


@Shiv09 wrote:
  • Full details of these two boards.- These are custom board using STM32H757BITb on it
  • Has the non-working board ever worked?- No

Then please show schematics.

Is the non-working working board functional at all ?

 

As @mƎALLEm suggested, have you verified the power configuration?

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.

Hello @mƎALLEm 

 

Here is the details 

Shiv09_0-1779273998720.pngThough the settings and configuration is notchanged.

Yes both the boards are identical, and same.