• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 81 subscribers
  • Views 426 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

F28337xD Problem enabling Auxillary clock

CCS/TMS320F28379D: F28337xD Example Code Stuck in F2837xD_SysCtrl command

Izabela Leao
Prodigy 40 points
Part Number: TMS320F28379D
Other Parts Discussed in Thread: CONTROLSUITE

Tool/software: Code Composer Studio

Hello everyone,

I'm having some problems while running the example timed_led_blink_cpu01 from controlsuite.

I've made some modifications to the original project, like adding to my code an .cmd file (2837x_RAM_lnk_cpu1.cmd) and modified the length of RAMGS4 from 0x001000 to 0x12000, and renamed it to LOG.

After that I've commented the other RAMGS lines until the RAMGS15.

I'm also adding in the LEDBLINK.c code, inside the cpu_timer0_isr void the function logger(), and including the logger files .h and .asm to the project.

When I build the project It doesn't show any error, but it does not work since apparently the code is stuck on the F2837xD_SysCtrl.c code in the 556 line: while(ClkCfgRegs.SYSPLLSTS.bit.LOCKS != 1)

Does anyone knows how to fix and/or why this problem is occuring ?

Thanks in advance,


Izabela.

  • 0
    TI__Genius 9850 points

    hi Izabela,

    Can you tell me which logger files are you using ?

    Is the unmodified code working without getting stuck ?

    On which board are you testing the example ?

    The "while(ClkCfgRegs.SYSPLLSTS.bit.LOCKS != 1)" is used to make sure that the clock is set only after the PLL locks successfully.

    What clock source INTosc or XTAL are you using ?

    Regards.