• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 377 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

C6670 PLL GO Operation problem

g.f.
Guru 15520 points

Hi,

I'm having a problem with C6670 PLL initialization.

Our PLL initialization is based on c6670evm.gel file.

When executing GO operation after configuring PLLDIV register etc..,

GOSTAT get set and somtimes it never be cleared(GOSTAT=0).

Is this means that GO operations in progress forever?

In which situation this problem will happen and how to solve?

best regards,

g.f.

  • 0
    TI__Guru* 81335 points

    Hi,

    As long as the GOSTAT bit is set, it means that Go operation is in progress. The GOSTAT bit resets to 0 automatically after SYSCLKs are aligned as specified in the ALNCTL register. Please share the PLLCMD, PLLSTAT, ALNCTL and DCHANGE register values during GO operation to investigate further. 

    Please refer Keystone PLL user guide SPRUGV2 section 3.2 for more details about Go operation.

    Thanks.

  • 0 in reply to Raja
    Guru 15520 points

    Hi Rajasekaran,

    Thank you for the reply.

    Actually, this issue is happening at my customer.

    I will ask my customer about the value of the register.

    I will share the value as soon as possible.

    best regards,

    g.f.

  • 0 in reply to g.f.
    TI__Guru* 81335 points

    Hi,

    OK. Thank you.

  • 0 in reply to Raja
    Guru 15520 points

    Hi Rajasekaran,

    Sorry for the delay.

    This problem has been occured during SPI NOR Flash Boot. But after customer changed the PLL programming, the problem has been fixed.

    They were initializing PLL twice during boot. The problem occurred during second PLL initialization, so customer stopped initializing PLL twice then the problem has been fixed.

    Their boot sequence was as following:

    1.Power on the Board

    2.RBL start running

    3.RBL load the program from NOR Flash to CorePac L2RAM

    4.Secondary boot loader start running

    5.PLL and DDR3 I/F initialized

    6.Reboot RBL

    7.RBL restarted

    8.RBL load program from NOR Flash to CorePac L2RAM and DDR3

    9.Secondary boot loader start running

    10.PLL initialized

    11.CorePac#1 start executing

    12.CorePac#2 start executing

    13.Secondary boot loader finished

    The customer thought that PLL will be bypass mode after rebooting RBL because they are using SPI boot mode. So, they were initializing PLL twice(Step5 and Step10). But the problem occured at the second PLL initialization so they deleted the Step10 PLL initialization then the problem has been fixed without PLL in bypass mode.

    So, I will close this post.

    Thank you so much for the support.

    best regards,

    g.f.

  • 0 in reply to g.f.
    TI__Guru* 81335 points

    Hi GF,

    Glad to hear that the customer problem is resolved. Thank you very much for the detailed response. This information will be very helpful.