Part Number: AM5728
Dear Champs,
In PLSDK v6.3, my customer loaded IPU FW using remoteproc and they used LED turn-on/off example for IPU FW, and they added while loop to continue LED on/off.
Up to initial 6th loop, there is no issue in LED turn-on/off, but they found below error message from 7th loop.
~~~~~~~~~~~
[ 26.700840] remoteproc remoteproc0: crash detected in 58820000.ipu: type watchdog
[ 26.708410] remoteproc remoteproc0: crash detected in 58820000.ipu: type watchdog
[ 26.715985] remoteproc remoteproc0: handling crash #2 in 58820000.ipu
[ 26.722464] remoteproc remoteproc0: recovering 58820000.ipu
[ 26.731398] remoteproc remoteproc0: stopped remote processor 58820000.ipu
[ 26.746135] remoteproc remoteproc0: powering up 58820000.ipu
[ 26.759684] remoteproc remoteproc0: Booting fw image dra7-ipu1-fw.xem4, size 4297624
[ 26.768933] omap-iommu 58882000.mmu: 58882000.mmu: version 2.1
[ 26.787870] virtio_rpmsg_bus virtio0: rpmsg host is online
[ 26.799359] remoteproc remoteproc0: registered virtio0 (type 7)
[ 26.806351] remoteproc remoteproc0: remote processor 58820000.ipu is now up
~~~~~~~~~~~~
at this time, they got trace info as below.
root@am57xx-evm:~# cat /sys/kernel/debug/remoteproc/remoteproc0/trace0_last
[0][ 0.000] Watchdog enabled: TimerBase = 0x68824000 SMP-Core = 0 Freq = 19200000
[0][ 0.000] Watchdog enabled: TimerBase = 0x68826000 SMP-Core = 1 Freq = 19200000
[0][ 0.000] Watchdog_restore registered as a resume callback
[0][ 0.000] 18 Resource entries at 0x3000
[0][ 0.000] [t=0x001351dd] xdc.runtime.Main: --> main:
[0][ 0.000] Watchdog fired at (PC) = 00007d32
[0][ 0.000] CPU context: thread
[0][ 0.000] BIOS Main name: (null task) handle: 0x0.
[0][ 0.000] BIOS Main stack base: 0x8006d748.
[0][ 0.000] BIOS Main stack size: 0x1000.
[0][ 0.000] R0 = 0x001f1dd6 R8 = 0x00000000
[0][ 0.000] R1 = 0x00989680 R9 = 0x00000000
[0][ 0.000] R2 = 0x00010000 R10 = 0x00000000
[0][ 0.000] R3 = 0x00000000 R11 = 0x00000000
[0][ 0.000] R4 = 0x00018311 R12 = 0x68057000
[0][ 0.000] R5 = 0x00000000 SP(R13) = 0x8006e6d0
[0][ 0.000] R6 = 0x00000000 LR(R14) = 0x00007c77
[0][ 0.000] R7 = 0x8006e748 PC(R15) = 0x00007d32
[0][ 0.000] PSR = 0x21000000
[0][ 0.000] ICSR = 0x0043d83c
[0][ 0.000] MMFSR = 0x00
[0][ 0.000] BFSR = 0x00
[0][ 0.000] UFSR = 0x0000
[0][ 0.000] HFSR = 0x00000000
[0][ 0.000] DFSR = 0x00000000
[0][ 0.000] MMAR = 0xe000ed34
[0][ 0.000] BFAR = 0xe000ed38
[0][ 0.000] AFSR = 0x00000000
[0][ 0.000] Stack trace
[0][ 0.000] 00 [op 47904668] 8006e6d0
[0][ 0.000] -- [op d02b4208] 0000ffff
[0][ 0.000] 01 [op fa96f002] 000161e1 (ret from call to 0001870c)
[0][ 0.000] Stack dump base 8006d748 size 4096 sp 8006e6d0:
[0][ 0.000] 8006e6c0: 68057000 00007c77 00007d32 21000000 000185ab ffffffff ffffffff ffffffff
[0][ 0.000] 8006e6e0: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
[0][ 0.000] 8006e700: ffffffff ffffffff ffffffff ffffffff ffffffff 00000000 00000000 00000000
[0][ 0.000] 8006e720: 00000000 00000000 00000000 00000000 00000000 00000000 8006e74c 001f1dd6
[0][ 0.000] 8006e740: 00000000 000161e1 00000000 00000000 00000000 00000000 00000000 00000000
[0][ 0.000] Terminating execution...
Could you please let me know what is an issue in this case?
When they tested it without linux and load FW using JTAG, there was no issue in continual LED turn-on/off.
Thanks and Best Regards,
SI.
