We have been having an issue with the HPI boot process. It seems to come and go and be highly dependent on the particular build. I have found a similar problem from another post listed below:
http://e2e.ti.com/support/dsp/tms320c6000_high_performance_dsps/f/115/p/153708/567375.aspx#567375
In this post one of the comments has this claim:
But then again, running in a bad code space can cause similar symptoms. All of the C6713's peripherals (HPI, JTAG, EDMA, etc) have memory mapped registers, many of them "Reserved", and rogue code that overwrites the registers repeatedly can lock up the peripheral requiring a hard reset.
When we have talked to TI about this issue previously, a POR reset was thought to be able to get any "crashed" code out of this state. The above statement seems to suggest otherwise. I assume the hard reset is a power reset.
Can you confirm if the above statement is true for the C6482 and that some cases will require a power reset to clear some issues?
Regards,
Dan