M4 ELF build done in CUBEIDE is not uploaded to target on dunfell platform

[meiss.M]

The program can not be uploaded under the dunfell distribution via CUBEIDE 1.3.1 to the target system. Using the thud distribution, target uploads works.

Are there any hidden upload scripts in the CUBEIDE - how to debug the debug upload?

Which yocto packages are necessary to cooperate with the CUBEIDE?

[OlivierK · Accepted solution]

Hi,

​The fix is now published.

https://wiki.st.com/stm32mpu/wiki/STM32MP15_ecosystem_release_note_-_v2.0.0

https://wiki.st.com/stm32mpu/wiki/STM32MP15_OpenSTLinux_release_note_-_v2.0.0

some cipher methods have been disabled by the community for security reasons.

As a consequence some ssh requests from STM32CubeIDE may not be functional due to the dropbear package configuration.

In this case, you can either:

• refer to https://github.com/STMicroelectronics/meta-st-stm32mp/commit/36a9911705bd37df136e9ac51dbf418861d510c9
• or use the latest STM32MP1_Starter_Package_-_images :  https://wiki.st.com/stm32mpu/wiki/STM32MP1_Starter_Package_-_images

Best Regards,

Olivier

[meiss.M]

Hi Oliver,

thanks for adding this to upstream.

Did you check firmware upload from STMcubeIDE if the the target is missing the directory /lib/firmware.

On my system, firmware upload works, however, a symlink is created:

lrwxrwxrwx   1 root    root           92 Feb 7 17:11 /lib/firmware -> /usr/local/projects/MYPROJECT/lib/firmware/MYPROJEKT_CM4.elf

and IDECube fails with the message: Failed to insert hardware breakpoints: You have requested too many hardware breakpoints/watchpoints.

Can you reproduce this.

[OlivierK]

​Hi  meiss.M (Community Member)

Indeed, I have the same symlink to the .elf.  But I don't get the message regarding the H/w breakpoint. Could you please share your console log?

[meiss.M]

I can share in a couple of days, since the power controller on our dk2 broke yesterday.