PROCESSOR-SDK-AM57X: /dev/rpmsg-dce not instantiated

Can someone from TI detail which package(s) govern the instantiation of /dev/rpmsg-dce? Our tisdk-rootfs-image includes ipumm-fw and libdce1. Are we missing anything? Should I be looking for anything in dmesg?

Matt,

Sorry for the delay...I am escalating internally.

Hello Matt,

Using PSDK6.0, I was not able to replicate your errors. However, after removing the "/lib/firmware/dra7-ipu2-fw.xem4" from the filesystem, I saw the same errors on the AM57EVM. By default, the firmware is already installed in the filesystem provided by TI. Please refer to the following thread for building the IPU firmware through Yocto.

Regards,
Krunal

Hi Krunal,

Thank you for your response. With it I was able to isolate the issue to a reorganization of the reserved memory blocks in the Linux device tree files. I made these changes to better support a 512MiB population option. If I change the location of the ipu2_memory_region, remoteproc will load dra7-ipu2-fw.xem4 successfully but /dev/rpmsg-dce will not instantiate with no errors reported in dmesg.

Can you help me identify what I need to modify in the ipumm-fw package and/or source to support a migrated ipu2 memory region? Can you confirm whether this issue will exhibit in other IPU or DSP firmwares if their reserved memory regions are moved?

Thanks,
Matt McKee

Hi Matt,

With regards to the reserved memory regions, could you please share what changes you have made in the device tree files? 

Regards,
Krunal

Hi Krunal,

I took 512MiB after memory base offset (0x A000 0000) and subtracted 16MiB (0x 100 0000) for the LISA map and aligned the memory regions from there:

1c1
< ipu2_memory_region: ipu2-memory@95800000 {
---
> ipu2_memory_region: ipu2-memory@9b800000 {
3c3
< 	reg = <0x0 0x95800000 0x0 0x3800000>;
---
> 	reg = <0x0 0x9b800000 0x0 0x3800000>;
8c8
< dsp1_memory_region: dsp1-memory@99000000 {
---
> dsp1_memory_region: dsp1-memory@97800000 {
10c10
< 	reg = <0x0 0x99000000 0x0 0x4000000>;
---
> 	reg = <0x0 0x97800000 0x0 0x4000000>;
15c15
< ipu1_memory_region: ipu1-memory@9d000000 {
---
> ipu1_memory_region: ipu1-memory@95800000 {
17c17
< 	reg = <0x0 0x9d000000 0x0 0x2000000>;
---
> 	reg = <0x0 0x95800000 0x0 0x2000000>;
22c22
< dsp2_memory_region: dsp2-memory@9f000000 {
---
> dsp2_memory_region: dsp2-memory@95000000 {
24c24
< 	reg = <0x0 0x9f000000 0x0 0x800000>;
---
> 	reg = <0x0 0x95000000 0x0 0x800000>;
28d27
< 

Thanks,
Matt McKee

I have now modified IPU_MEM_IPC_DATA and PHYS_MEM_IPC_VRING in ipumm-fw file platform/ti/dce/baseimage/custom_rsc_table_vayu_ipu.h to match the DSP2 and IPU2 memory region changes in the DTS files. Remoteproc fails to load this new firmware with a "remoteproc remoteproc1: erroneous trace resource entry" error. It seems that I likely need to make changes elsewhere in ipumm-fw or perhaps in other TI-RTOS components used to build the ipumm-fw. I'm not sure where to dig next so any suggestions on where to look would be greatly appreciated.

Thanks,
Matt McKee

Figured it out. I neglected to update the IPU2 memory map in build/config.bld. Now /dev/rpmsg-dce shows up as expected.

Can you confirm that I will not need to make changes in other firmwares to accommodate changes in DTS memory regions? Right now we have no visible failures related to dsp1, ipu1, and dsp2, but would appreciate the expert opinion(s).

Thanks,
Matt McKee