Part Number: AM6422
Other Parts Discussed in Thread: AM6421
Hello Team,
We have developed a product based on AM6421/22 based processor. We have two custom designed boards/revisions. One baord has a single core AM6421 and other revision has dual core AM6422. We have deployed a custom Yocto based image on the board. Also, we have optimized the bootup time in order to meet the requirements of the prodcut (boot time into application < 40 sec).
Our primary issue is related to reboot (without power cycle), when we perform this continuously, AM6421 based board gets stuck during reboot after around 2500 reboot cycles.
Initially, the reboot stuck frequency was around 200-300 reboot cycles. Searching online and checking, initially we found that USB (as CDC_NCM device) and eMMC were initialized almost at the same time creating some race conditions and linux kernel was stuck there even before jumping to user space ans starting systemd. As a fix, we have disabled the USB and CDC_MCM support in the linux kernel. After this the reboot was successful for around 2500 cycles and after that it was getting stuck in user space waiting for /dev/ttyS2 in systemd.
To rule out any h/w and s/w related issues, we cheked the same thing on ti image on AM6421-EVM. we observed that similar case we could reproduce on the EVM as well where it gets stuck for /dev/ttyS2 in systemd forever, almost after 3500 reboot cycles.
The same issue we are observing on AM6422 board, but on this board we are able to reproduce the issue often, just after 10-20 reboots and this time we get kernel dump..
------------------------------------
To temporarily resolve this, we tried to enable the watchdog in uboot and in kernel. This worked and we were able to recover the board if it gets stuck it timeouts and reboots automatically.
However, on AM6422 based board, if we enable the watchdog in uboot, the CPU 1 fails to start
'
It only starts if watchdog is disabled in the U-boot.
But we want it to be running from Uboot
Searching online we found something related to power-domain

so removed it and tried.. but still it is not working if we enable watchdog in uboot.
---------------------
Please guide us to identify and fix both the issues