创龙AM5708 IPU看门狗复位问题

czs----Tronlong

创龙公司，你好，
     最近在调试项目时，遇到一个问题，显示的实时图像的帧率会突然下降，并出现卡顿现象，通过串口查看，发现如下信息：

[  180.833887] remoteproc remoteproc1: handling crash #16 in 55020000.ipu
[  180.845969] remoteproc remoteproc1: recovering 55020000.ipu
[  180.894043] remoteproc remoteproc1: stopped remote processor 55020000.ipu
[  180.900876] remoteproc remoteproc1: powering up 55020000.ipu
[  180.933541] remoteproc remoteproc1: Booting fw image dra7-ipu2-fw.xem4, size 3743096
[  180.952358] omap-iommu 55082000.mmu: 55082000.mmu: version 2.1
[  181.119999] virtio_rpmsg_bus virtio0: rpmsg host is online
[  181.125695] remoteproc remoteproc1: registered virtio0 (type 7)
[  181.154394] remoteproc remoteproc1: remote processor 55020000.ipu is now up
[  181.172969] prueth pruss2_eth: pruss MC Mask 0:0:0:0:0:0
[  181.178509] prueth pruss2_eth: port 1: using random MAC addr: da:43:26:bc:f8:25
[  191.121768] remoteproc remoteproc1: crash detected in 55020000.ipu: type watchdog
[  191.129345] remoteproc remoteproc1: handling crash #17 in 55020000.ipu
[  191.138009] remoteproc remoteproc1: recovering 55020000.ipu
[  191.189886] remoteproc remoteproc1: stopped remote processor 55020000.ipu
[  191.202531] remoteproc remoteproc1: powering up 55020000.ipu
[  191.229425] remoteproc remoteproc1: Booting fw image dra7-ipu2-fw.xem4, size 3743096
[  191.239722] omap-iommu 55082000.mmu: 55082000.mmu: version 2.1
[  191.409613] virtio_rpmsg_bus virtio0: rpmsg host is online
[  191.415164] remoteproc remoteproc1: registered virtio0 (type 7)
[  191.442474] remoteproc remoteproc1: remote processor 55020000.ipu is now up
[  191.460188] prueth pruss2_eth: pruss MC Mask 0:0:0:0:0:0
[  191.467233] prueth pruss2_eth: port 1: using random MAC addr: 02:71:95:56:92:c5

上述信息一直重复打印，请问这是什么原因造成的？我们应该怎么解决呢？
谢谢！

梁淑怡-Tronlong

问题分析：
   1.TI 官方对IPU2的watchdog的默认配置是timer 4和 timer 9；
   2.但是我司TL570x-EVM开发板PWM风扇中，已将timer 4作为PWM输出，因此我司将IPU2的watchdog定时器默认的timer 4修改为timer 12；



   3.我司对AM5708对应的IPC包做过修改，主要是将IPU2的watchdog定时器默认的timer 4修改为timer 12，如果您使用的是TI编译好的IPU镜像，则可能出现timer4冲突问题。


问题解决建议：
      可以将设备树文件中，先把IPU2的watchdog恢复成默认的timer4和timer9；然后将pwm风扇设备节点注释，同时注释掉PWM风扇对应的timer4定时器，排查是否时应为定时器冲突导致IPU重启。