cancel
Showing results for 
Search instead for 
Did you mean: 

STM32H755 Dual Debug Startup Problem

bramble
Associate III

Hi community,

I have a problem that other people have also raised and I'd be grateful for help.

I followed AN5361 and I watched this STM video on the same topic. First thing to mention is that the video and doc have different advice about whether the CM7 should Halt All Cores (Video advice) or not (AN5361 advice). Grrr!

Now I've got that off my chest here's the problem in more detail.

CM7 like this:

bramble_0-1740832043277.png

 

bramble_7-1740832218457.png

 

bramble_9-1740832308142.png

CM4:

bramble_4-1740832152320.png

 

bramble_6-1740832203055.png

bramble_10-1740832340453.png

With that configuration when I launch CM7 first, then CM4, both pause as expected with CM4 in reset and CM7 ready to go. When I select both cores then click on the green go arrow, CM7 runs straight into this:

bramble_13-1740832649025.png

Caused by the timeout expiring.

If, alternatively, I configure CM7 like this:

bramble_12-1740832561367.png

Then I can debug both cores, but they aren't doing a coordinated start as they should.

I know that I could ignore the timeout error, but then the systems wouldn't be doing a coordinated start as they should.

Any suggestions please?

 

 

 

 

0 REPLIES 0