- Trying to program M4 with ST-link via SWD
St-link connected to pads SWDIO SWCLK and GND on odyssey side near audio jack
Created project in STM32CubeIDE with LED blinking. Enable SWD in CubeMX.
If I manually scp elf file to debian buster side and run it by
sudo cp /usr/STM32MP157_TEST_CM4.elf /lib/firmware/
echo ‘STM32MP157_TEST_CM4.elf’ | sudo tee -a /sys/class/remoteproc/remoteproc0/firmware
echo ‘start’ | sudo tee -a /sys/class/remoteproc/remoteproc0/state
everything works fine
But in STM32CubeIDE Debug not working with settings
I got error
Error in final launch sequence:
Failed to start GDB server
Failed to start GDB server
Error in initializing ST-LINK device.
Reason: (4) No device found on target.
or another error when M4 firmware is running from debian side
Error in final launch sequence:
Failed to execute MI command:
monitor reset
Error message from debugger back end:
Protocol error with Rcmd
Failed to execute MI command:
monitor reset
Error message from debugger back end:
Protocol error with Rcmd
Protocol error with Rcmd
- Trying to test vitrual uart between A7 and M4
Created project in STM32CubeIDE with VIRT_UART_Init and VIRT_UART_RegisterCallback as shown in examples from stm ev board.
Run it from A7 side. It works, led blinking, but I have no /dev/ttyRPMSG0 in ls /dev/tty*
What I missed?