cancel
Showing results for 
Search instead for 
Did you mean: 

STM32MP157: Booting the M4 out of the A7 context fails when the RSVD mux function is used

KWyss.1
Associate II

Hi Community

In the DT the TIM1, TIM4 and SPI4 are assigned to the M4 and in the pinmux the RSVD is set (DT attached). Booting A7 generates no ERROR during Kernel boot. If the M4 is started from the A7 context the following ERROR Messages occurs for all assigned peripherals:

[ 1648.984460] remoteproc remoteproc0: powering up m4

[ 1648.990531] remoteproc remoteproc0: Booting fw image core4-m4-app.elf, size 1164296

[ 1648.998032] stm32mp157-pinctrl soc:pin-controller@50002000: invalid function.

[ 1649.003955] rproc-srm-dev: probe of m4@0:m4_system_resources:timer@40002000 failed with error -22

[ 1649.013430] stm32mp157-pinctrl soc:pin-controller@50002000: invalid function.

[ 1649.019935] rproc-srm-dev: probe of m4@0:m4_system_resources:timer@44000000 failed with error -22

[ 1649.029232] stm32mp157-pinctrl soc:pin-controller@50002000: invalid function.

[ 1649.035907] rproc-srm-dev: probe of m4@0:m4_system_resources:spi@44005000 failed with error -22

[ 1659.359767] rproc-srm-core m4@0:m4_system_resources: failed to bind one or more system resource device(s)

[ 1659.376471] remoteproc remoteproc0: failed to prepare subdevices for m4: -110

[ 1659.383988] remoteproc remoteproc0: Boot failed: -110

If the AFx function is set instead of RSVD then the M4 is booting with the following warnings:

[  14.586526] rproc-srm-dev m4@0:m4_system_resources:timer@40002000: pin config potentially overwritten!

[  14.595866] rproc-srm-dev m4@0:m4_system_resources:timer@44000000: pin config potentially overwritten!

[  14.605128] rproc-srm-dev m4@0:m4_system_resources:spi@44005000: pin config potentially overwritten!

[  14.614225] rproc-srm-dev m4@0:m4_system_resources:adc@48003000: Linked as a consumer to regulator.1

Processor: STM32MP157

Kernel version: v4.19-stm32mp-r2 (To get the RSVD definition the file stm32-pinfunc.h is patched (see attached))

  • Have everyone a idea why booting the M4 crashes when the RSVD mux function is used? Are there more patches necessary for the used Kernel?
  • And does it work to set the AFx instead of RSVD for peripherals assigned to the M4?

Br

Kris

1 ACCEPTED SOLUTION

Accepted Solutions
KWyss.1
Associate II

Solution...

Updating the Patch solves the Problem (Patch attached). For patch generating I took the Sources from Kernel v4.19-stm32mp-r3 .

Br

Kris

View solution in original post

1 REPLY 1
KWyss.1
Associate II

Solution...

Updating the Patch solves the Problem (Patch attached). For patch generating I took the Sources from Kernel v4.19-stm32mp-r3 .

Br

Kris