cancel
Showing results for 
Search instead for 
Did you mean: 

remoteprocessor starts firmware at linux boot time on STM32MP257f-ev1

MBassi
Associate III

Hi,

I'm using an stm32mp257f-ev1 for the first time. I configured the board to boot from emmc: I flashed it using starter package image for fastboot with opteemin image. I noticed that at openSTlinux boot-time remoteproc starts M33 core with USBPD_DRP_UCSI_CM33_NonSecure_stripped.elf.
I try to figured out if it's possible to avoid firmware starting at boot-time in some way without deleting it from /lib/firmware.
I tried to search if there is something to change on DT or in kernel configuration, but I don't found anything useful

Here's the board boot log concerning firmware starting:

[ 11.524092] remoteproc remoteproc0: powering up m33
[ 11.529609] remoteproc remoteproc0: Booting fw image USBPD_DRP_UCSI_CM33_NonSecure_stripped.elf, size 144140
[ 11.539164] rproc-virtio rproc-virtio.2.auto: assigned reserved memory node vdev0buffer@812fa000
[ 11.550597] rproc-virtio rproc-virtio.2.auto: registered virtio0 (type 7)
[ 11.551849] remoteproc remoteproc0: remote processor m33 is now up
[ 11.564734] Booting fw image for stm32mp257f-ev1
[ 11.577557] virtio_rpmsg_bus virtio0: rpmsg host is online

 

Could someone give me a hint please

Marco

0 REPLIES 0