Hi Scott
Thanks for your response.
The main issue at the moment it that the problem only repros on a live customer system which makes it almost impossible to do manual/interactive investigations, or use an external debugger. I'm therefore looking for a way to add diagnostics to our firmware to dump information about the core state when we detect the hang has occurred.
I have looked through the errata and have not seen any that seem to be relevant in this situation. I think it is far more likely that the problem is due to a software bug/overwrite than a P4080 hardware bug.
I am therefore currently looking further into the extensive P4080 debug and trace capabilities and will effectively try to implement a limited function debugger that can run on one of the other cores and extract state information at the point of the hang (plus possibly get instruction trace leading up to the hang).
John