Custom platform with:
- OMAP4430 ES2.3 + TWL6030 + TWL6040
- Powered by PoE using LM5073 and LM5576
- Ethernet connection via USB3320 and LAN9512
Issue description:
In some occasions, the OMAP4430 does not complete a reboot cycle after a restart has been triggered by the NRESWARM pin.
Because the application running on the OMAP is not able to kick an external watchdog circuit in time, the external watchdog circuit pulls down the NRESWARM signal. The OMAP4430 keeps this signal low for some time and then releases the signal. In normal operation, the OMAP4430 sends out a message on the UART interface just after the NRESWARM pin has been released. However, in our case, the expected messages on the UART interface are not printed.
I would expect that the OMAP4430 completes the normal startup cycle when the NRESWARM pin was pulled low.
When I connect the output of the watchdog to the NRESPWRON pin, the OMAP4430 does complete the boot cycle successfully.
What can cause the OMAP4430 not to complete its boot cycle? Can this be caused by some register settings?