This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM5726: am5726

Part Number: AM5726

We are seeing an issue that seems to occur both in the TI AM5726 ROM code, and the associated Uboot image where the I/O isolation routine hangs waiting for the

 

The Technical Reference manual, section 18.4.6.1.7 "Isolation Requirements" describes a proceddure for both isolating and de-isolating the I/O pads when configuring the I/O settings.  

 

We would like to understand under what conditions, the CPU would fail to set the ISOCLK_STATUS

 

The steps outlined in section 18.4.6.1.7 describe the following:
2. Write 1 to the PRM_IO_PMCTRL[0] ISOCLK_OVERRIDE bit
3. Poll the PRM_IO_PMCTRL[1] ISOCLK_STATUS bit until it reads 1

 

The ISOCLK_STATUS bit is never set to 1, causing either the ROM code and/or the Uboot code to spin forever waiting for this bit to be set.  A similar question was asked in:
https://e2e.ti.com/support/processors-group/processors/f/processors-forum/983524/am5726-isolation
But there was no clear resolution to this issue.

 

Could you help us understand under what conditions the CPU would behave in this manner.