[Geoff Danielson]

Neeraj,

I’m following up on this. We have flashed STlinux to the SD card, and it boots fine.

When I go through the steps to do the demo, this is what happens:

root@stm32mp1:/usr/local/Cube-M4-examples/STM32MP157C-DK2/Applications/OpenAMP/OpenAMP_TTY_echo_wakeup# ./fw_cortex_m4.sh start
fw_cortex_m4.sh: fmw_name=OpenAMP_TTY_echo_wakeup.elf
[ 816.684551] remoteproc remoteproc0: powering up m4
[ 816.689156] remoteproc remoteproc0: Booting fw image OpenAMP_TTY_echo_wakeup.elf, size 228192
[ 816.697167] mlahb:m4@10000000#vdev0buffer: assigned reserved memory node vdev0buffer@10042000
[ 816.705969] virtio_rpmsg_bus virtio0: creating channel rpmsg-tty-channel addr 0x0
[ 816.713061] virtio_rpmsg_bus virtio0: rpmsg host is online
[ 816.719062] rpmsg_tty virtio0.rpmsg-tty-channel.-1.0: new channel: 0x400 -> 0x0 : ttyRPMSG0
[ 816.726923] mlahb:m4@10000000#vdev0buffer: registered virtio0 (type 7)
[ 816.733524] remoteproc remoteproc0: remote processor m4 is now up

root@stm32mp1:/usr/local/Cube-M4-examples/STM32MP157C-DK2/Applications/OpenAMP/OpenAMP_TTY_echo_wakeup# echo enabled > /sys/devices/platform/soc/4c001000.mailbox/power/wakeup
root@stm32mp1:/usr/local/Cube-M4-examples/STM32MP157C-DK2/Applications/OpenAMP/OpenAMP_TTY_echo_wakeup# echo “*delay” > /dev/ttyRPMSG0
root@stm32mp1:/usr/local/Cube-M4-examples/STM32MP157C-DK2/Applications/OpenAMP/OpenAMP_TTY_echo_wakeup# systemctl suspend
root@stm32mp1:/usr/local/Cube-M4-examples/STM32MP157C-DK2/Applications/OpenAMP/OpenAMP_TTY_echo_wakeup#
[ 866.198175] PM: suspend entry (deep)
[ 866.211649] Filesystems sync: 0.011 seconds
[ 866.226474] Freezing user space processes … (elapsed 0.002 seconds) done.
[ 866.234603] OOM killer disabled.
[ 866.237711] Freezing remaining freezable tasks … (elapsed 0.001 seconds) done.
[ 866.245290] printk: Suspending console(s) (use no_console_suspend to debug)
[ 866.372938] dwc2 49000000.usb-otg: suspending usb gadget configfs-gadget
[ 866.439066] stm32-dma 48001000.dma: Suspend is prevented by Chan 1
[ 866.439096] PM: dpm_run_callback(): platform_pm_suspend+0x0/0x48 returns -16
[ 866.439107] PM: Device 48001000.dma failed to suspend: error -16
[ 866.439118] PM: Some devices failed to suspend, or early wake event detected
[ 866.458849] dwc2 49000000.usb-otg: resuming usb gadget configfs-gadget
[ 866.661605] OOM killer enabled.
[ 866.664755] Restarting tasks … done.
[ 866.684270] PM: suspend exit

root@stm32mp1:/usr/local/Cube-M4-examples/STM32MP157C-DK2/Applications/OpenAMP/OpenAMP_TTY_echo_wakeup#

I searched around on this issue and came to this page: https://community.st.com/s/question/0D53W00000rYk3ySAC/openampttyechowakeup-examples-dont-work

So, how do I “select the right Linux boot mode” on the -BRK board? I don’t see a dtb for the BRK board specific to the m4 examples, but I also don’t know how I’d start selecting one in uboot either.

Suggestions?

[Author]

Posts