Skip to main content
Eldam
Senior
September 10, 2020
Solved

st-image_core & M4 copro

  • September 10, 2020
  • 2 replies
  • 995 views

Hi ST Teams,

I'm building successfuly an image "st-image-core", for stm32mp1 machine.

I'm able to add python package and remove some package too.

But unfortunately, My team who works on M4 copro can't connect anymore on it.

If i made a sd card with starter kit on it, M4 can connect (ie debug run & so on)

If i made my st-image-core, it can't.

Is there any special "append" to add to my distro in order to get things works?

I'm using SDK 1.2

Thanks in advance.

This topic has been closed for replies.
Best answer by Eldam

Well after checking ST Forums

We managed to get things works

I need to add "eclipse-debug" in local.conf in EXTRA_IMAGE_FEATURES part

this thread helped me:

https://community.st.com/s/question/0D53W000003NX6YSAW/how-to-debug-m4-firmware-based-on-stimagecore-using-the-ev1-board

Works with 1.2 SDK

seeya!

2 replies

mleo
Visitor II
September 16, 2020

Hi @Eldam​ .

I've just tried running M4 code on  "st-image-core" - on both ecosystems 1.2 and 2.0 following steps:

https://wiki.st.com/stm32mpu-ecosystem-v1/wiki/Linux_remoteproc_framework_overview#How_to_use_the_framework

And everything works.

Could you be more specific about the failure you face? Any log? What file are you trying to execute?

Best regards,

Milan

Eldam
EldamAuthorBest answer
Senior
September 22, 2020

Well after checking ST Forums

We managed to get things works

I need to add "eclipse-debug" in local.conf in EXTRA_IMAGE_FEATURES part

this thread helped me:

https://community.st.com/s/question/0D53W000003NX6YSAW/how-to-debug-m4-firmware-based-on-stimagecore-using-the-ev1-board

Works with 1.2 SDK

seeya!