STM32H755 dual core debug - demo project

[lonejack]

Hi, after a lot of wasted time, I've created a demo for dual core with debug files:

Here is the project:

https://github.com/lonejack/stm32cubeide-demo-dualcore 

To make the setup the guide:

https://www.youtube.com/watch?v=k3mXhPZSasw 

has been followed.

I made some changes...

Import the project with option:

three projects..

Generate the code and build projects.

Then run the debug with "stm32cubeide-demo-dualcore"

 

Wait the download and main enter for both processors:

 

Run the CM4, it should go in this state:

Run the CM7, it should go in running:

 

Return in CM4, press run button, it should go in running:

 

Now both cores are running...

The given guide to me didn't work!

If someone has better solution please write here...

Thank you.

C.

 

 

 

 

 

[FBL]

Hello 

> The given guide to me didn't work!

Could you please explain what is the problem? Are you aiming to multi core debug for example? If not, you can simply comment the boot sequences to run one core in debug.

[lonejack]

Hi Mr. Belaid,

you're right, my target is to debug both cores contemporary.

In the guide for example it isn't described how to do this. Do I have to load the two debug launcher? Or just one single (cm7)?

Furthermore, it should be specified that, for syncro reasons, is necessary to run the CM4 and after the CM7.

In order to obtain this I made a "Launch Group" that run the two launcher.

All these info aren't present in the guide...

Anyway, if you have a better solution, write here.

C.

[FBL]

In CM7 debug configuration, you need to:

1. Select ST Link GDB server
2. Define Access port 0 for CM7
3. Connect under reset
4. Enable shared ST LINK
5. In startup tab, add CM4 image file .elf and list it before CM7 elf file then save.

In CM4 debug configuration:

1. Set debug probe ST link GDB server (port number 61238)
2. Define Access Port to 3 for CM4
3. Set None in reset behavior.
4. Enable Shared ST Link
5. In startup tab, edit the CM4 image and disable download (it will be done by CM7). 

[lonejack]

About the CM4 configuration you have only to download the symbols not the code.

So, at this point, what we should do?

• start the CM4 (CM4 at semaphore check goes in stop);
• start the CM7;
• restart the CM4 (that is waiting at the semaphore);

Now you can debug...

But these info, where are described in the video?

[FBL]

Exactly, this is an example. Do you still have issues to debug CM4 core?

[lonejack]

Reading my answer, I understand now that there's a mix of items here. I faced problems these during my first test on the NUCLEO board and the draft dual core project (form STM32CubeIDE) insert a semaphore for both cores synchronization.

So in my initial post I wrote "The given guide to me didn't work!". That statement is incorrect (it is not my intention to offend anyone). The guide explain how to make the two launchers but, after this, you need to make a launch group and start correctly the cores.