T042 PLL not locking - set to "kill" in status registers

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

T042 PLL not locking - set to "kill" in status registers

997 Views
danfitzgerald
Contributor I

Hi All - Has anyone seen Platform, DDR, Core complex clocks all showing the "kill" bit set in their respective status registers?  We have a valid single ended SYSCLK, which is used to clock in the RCW, and ASLEEP is driven low, but after the RCW init phase, the internal multipliers are not working and the 100MHz SYSCLK is being used as the platform clock.  Any clues where to begin looking?

Thanks

Labels (1)
Tags (2)
0 Kudos
Reply
4 Replies

756 Views
Bulat
NXP Employee
NXP Employee

Can you clarify what means "ASLEEP is driven low"? Is it driven externally? Note, ASLEEP is an output signal on the T1042 side, so should not be be driven.

Also about RCW, did you check in any way that RCW is actually read? What is the source of the RCW?

0 Kudos
Reply

756 Views
danfitzgerald
Contributor I

Hi – Thanks for the response, good news is we found some IFC bus pull ups that had been optimised out of our CPLD, adding those back in solved the PLL issue.

Many Thanks.

0 Kudos
Reply

756 Views
doronshaanan
Contributor I

Hi

I face the same problem with my board.

I appreciate if you can let me know which signals solve the problem

Thanks

Doron

0 Kudos
Reply

756 Views
lifengwang
Contributor I

which signals of IFC?can you tell me how to solve,I have encounter similar problems!

0 Kudos
Reply