cancel
Showing results for 
Search instead for 
Did you mean: 

[STM32H745XI-DISCO] Unable to debug CM4

BKOSI.1
Associate II

Hi community,

I'm trying to launch an ANN on this discovery board.

I build and programm both CM without error.

However I'm not able to debug CM4 and have this error :

Starting server with the following options:

    Persistent Mode      : Disabled

    Logging Level       : 1

    Listen Port Number     : 61238

    Status Refresh Delay    : 15s

    Verbose Mode        : Disabled

    SWD Debug         : Enabled

Failed to read ROM table via AP 3

Error in initializing ST-LINK device.

Reason: Unknown. Please check power and cabling to target.

I configure project environment as decribe on AN5361.

I've no more ideas, if someone have it...

BR,

Benjamin

9 REPLIES 9
Imen.D
ST Employee

Hello @Community member​ ,

Please try to connect under reset.

If this doesn’t help, I advise you to check the article: Unable to connect to STM32H7 devices.

Please mark my answer as best by clicking on the "Select as Best" button if it helped. This will help other users find that answer faster.

Imen

When your question is answered, please close this topic by clicking "Accept as Solution".
Thanks
Imen
BKOSI.1
Associate II

Hi Imen,

Thanks you for your tips.

Problems appears when I try to debug CM4, I can access to CM7 debug and STLink leds blinking.

HAL_PWREx_ConfigSupply(PWR_DIRECT_SMPS_SUPPLY) is correctly configured by CubeMX.

I try with others small projects and same behavior.

I think about a mistake on Debug / Run configuration...

I can share my project or configuration if needed.

BR

Benjamin

Hi,

After few tests i'm able to :

  • M4 & M7 Registers access through Cubeprogrammer
  • Access to M4 debug through M7 access (ap0)
  • STlinV3 up to date
  • NRST connected to STLink reset

So maybe I brick M4 access port (ap3) or STlink ?

CubeProgrammer and CubeIDE can't access to M4 through ap3...

I will appreciate a support from STemployee if possible... or someone else who meet this situation.

BR

Benjamin

BKOSI.1
Associate II

Associated log

BKOSI.1
Associate II
 
BKOSI.1
Associate II

Hi,

Anyone may help us ?

I didn't understance how we can brick a processor through debug acces without any changes on CubeMX configuration (supplied by ST)...

BR

Hello, I had the same issue today for the first time. The link to the article is void for me.

Could you help me to fix it?

Thank you

Bertrand

 

Hi, did you select "Halt all cores" in the debug configuration of the M7 ?

  1. Open STM32CubeProgrammer and connect via ST-Link.
  2. Click on "OB" for Option bytes.
  3. Open tab "User configuration" and look for "BCM4" and "BCM7".
  4. In your case you want BCM4 to be checked as well as BCM7.
  5. Click Apply and Disconnect.