Other Parts Discussed in Thread: SK-AM62B, SK-AM62, AM625,
Tool/software:
We have found that with recent versions of the DM firmwares provided in ti-linux-firmware, it is not possible to interact with the R5 core from Linux using the remoteproc+rpmsg drivers on some variants of the AM62x (on our TQ-Systems TQMa62xx SOM). Probing the remoteproc driver fails with the following messages:
[ 6.670963] platform 78000000.r5f: ti-sci processor request failed: -19 [ 6.671050] platform 78000000.r5f: ti_sci_proc_request failed, ret = -19 [ 6.674274] k3_r5_rproc bus@f0000:bus@b00000:r5fss@78000000: k3_r5_core_of_init failed, ret = -19 [ 6.674301] k3_r5_rproc bus@f0000:bus@b00000:r5fss@78000000: k3_r5_cluster_of_init failed, ret = -19
With older DM firmwares, the same works fine:
[ 6.569096] platform 78000000.r5f: R5F core may have been powered on by a different host, programmed state (0) != actual state (1) [ 6.572660] platform 78000000.r5f: configured R5F for IPC-only mode [ 6.573291] platform 78000000.r5f: assigned reserved memory node r5f-dma-memory@9da00000 [ 6.573941] remoteproc remoteproc3: 78000000.r5f is available [ 6.574088] remoteproc remoteproc3: attaching to 78000000.r5f [ 6.589108] platform 78000000.r5f: R5F core initialized in IPC-only mode [ 6.589191] rproc-virtio rproc-virtio.5.auto: assigned reserved memory node r5f-dma-memory@9da00000 [ 6.589483] rproc-virtio rproc-virtio.5.auto: registered virtio1 (type 7) [ 6.589504] remoteproc remoteproc3: remote processor 78000000.r5f is now attached
I have tested with two different variants of the AM62x:
- AM6234 HS-FS - is affected
- AM6254 GP - is not affected
(I don't have an AM6234 GP or AM6254 HS-FS at hand, so I'm not sure if the security features or a difference between AM6234 and AM6254 is the cause)
I've bisected the issue in ti-linux-firmware, the first bad commit is c7a7dd4e ("ti-dm: Update firmware for am62x, am62ax and am62px").
Versions of other used components:
- ti-linux-kernel - latest 6.1 and 6.6 behave the same
- trusted-firmware-a 00f1ec6b87 - I had to go back to this version for the bisect to make boot work at all with the older ti-linux-firmware, but latest ti-linux-firmware + trusted-firmware-a master is affected as well
- ti-u-boot-2023.04 (83660642085) - We have not updated the TQMa62xx to 2024.04 yet, are there any patches in the new version that might be relevant for this issue?