Skip to main content
jo512
Associate II
April 9, 2026
Question

STM32H747I-DISCO unable to flash in Ubuntu 22.04.5 LTS

  • April 9, 2026
  • 5 replies
  • 367 views

Hi Support

I have experience in STM32 with Zephyr but I am trying out AMP for the first time.

So I am trying out OpenAMP example from STM32CubeIDE. I can compile the example but cannot flash the same.

I have the following error

jo512_0-1775713970923.png

The ST-Link device is present as shown below

 

jo512_2-1775714007951.png

I have tried other boards like NUCLEO-G431RE with some simple UART example and work well.

I have problems only with AMP board, I am not able to flash M4 and M7 core.

 

My dev environment

Ubuntu 22.04 and STM32CubeIDE ver1.1.8.1

 

Could anyone please help me understand the same?

 

 

5 replies

mƎALLEm
Technical Moderator
April 9, 2026

Hello,


@jo512 wrote:

Ubuntu 22.04 and STM32CubeIDE ver1.1.8.1


You mean 1.18.1?

Did you test another simple project apart from OpenAMP? Try the GPIO example.

 

"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."
jo512
jo512Author
Associate II
April 9, 2026

None of the example works for this particular board. I cannot flash into M4 or M7

mƎALLEm
Technical Moderator
April 9, 2026

What part of the project you cannot flash? CM4 or CM7?

"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."
mƎALLEm
Technical Moderator
April 9, 2026

You didn't answer my question. Which part of project is not uploaded? CM4? CM7 or both?

You have two projects inside the example.

"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."
jo512
jo512Author
Associate II
April 9, 2026

I cannot upload both

mƎALLEm
Technical Moderator
April 9, 2026

Ok did you try to connect to the board with the CubeProgrammer?

Try this please ..

"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."
Andrew Neil
Super User
April 9, 2026

@jo512 wrote:

The ST-Link device is present as shown below

jo512_2-1775714007951.png


So the problem is the connection between the ST-Link and the Target.

Has this board ever worked?

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.
jo512
jo512Author
Associate II
April 9, 2026

This Board has also not worked with CubeProgrammer in Linux. I will try on Windows and will update again

mƎALLEm
Technical Moderator
April 9, 2026

@jo512 wrote:

This Board has also not worked with CubeProgrammer in Linux. I will try on Windows and will update again


Yes do it please ..

"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."
jo512
jo512Author
Associate II
April 9, 2026

Hi Andrew,

This is a new board right out of the box. And has never worked in my hands

Regards

Jo

 

mƎALLEm
Technical Moderator
April 9, 2026

You need to ensure the connection step with CubeProgrammer.

You need to ensure the connection to each of the Cores CM4 and CM7:

To connect to CM7, you need to set the access port to 0:

mALLEm_0-1775731172068.png

To connect to CM4, you need to set the access port to 3:

mALLEm_1-1775731234276.png

Ensure also all the jumpers are set correctly especially JP6: it should be set to ST-LINK option.

If you succeed to connect with CubeProgrammer, try to update the ST-LINK firmware with CubeProgrammer:

mALLEm_2-1775731355663.png

Then,

mALLEm_3-1775731424832.png

"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."