I HATE intermittent problems…
This random restart reporting a ADL_POWER_ON event has reminded me of something I struck 18 months ago.
I had a modem that was uploading data to a server using the WIP FTP API. Occasionally I would get both REBOOT_FROM_EXCEPTION and POWER_ON restart events - I eventually tracked down the REBOOT_FROM_EXCEPTION to a buffer overflow problem, and the POWER_ON event appeared to occur when I was within the WIP FTP API.
I never did resolve the FTP issue - it appeared that the module was somehow being power cycled from within the FTP library under certain conditions. Like yourself, I was not getting any debug traces out when this happened, and in the end I talked the client into using HTTP to do the uploads instead of FTP - and the problem went away. I was also logging data (at roughly 5 sec intervals) internally to the A&D flash and there was a gap of about 30-40 minutes between the last logged record and the POWER_ON event. This lead me to believe that there is a long timeout somewhere in the FTP or TCP stack that was hanging up on me - but I have no proof.
I was running my code on a Fastrack FXT009 with FW 7.45 and 7.46 (and associated WIP libs etc).
If you’re convinced that there is no real power problem (and from what you’ve said I now believe that there isn’t), the next place I would start looking is inside your network code (if you’re using TCP) and see if you can do some internal logging yourself - even just dumping internal state variables out the USB or serial port to a PC would be useful. The TCP library has some very long default timeouts that can be tweaked using the wip_netInit() options - maybe shorten these timeouts and see how the problem behaves.