• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 2240 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.

CCS/LAUNCHXL-F28379D: Programs with the C2000Ware examples for F28379D

Hainan Wang
Intellectual 450 points

Part Number: LAUNCHXL-F28379D
Other Parts Discussed in Thread: C2000WARE

Tool/software: Code Composer Studio

Hi, there

I am running an example project from C2000Ware for my Launchpad LAUNCHXL-F28379D. The project is located at "C:\ti\C2000Ware_1_00_04_00_Software\device_support\f2837xd\examples\cpu1\adc_soc_epwm\cpu01"

Here's the problems I see:

1st. When I try to build the project, I got a lot of warnings, do you know why?

2nd. I went ahead to execute the project with the Launchpad. It stuck at the function " InitSysPll(XTAL_OSC, IMULT_20, FMULT_0, PLLCLK_BY_2);" located in "F2837xD_SysCtrl.c"

I stepped through it and found that it stuck in the following code:

    while(sysclkInvalidFreq == true)
    {

       ..........("setup cputimer1 and cputimer2 to verify the PLL)

      sysclkInvalidFreq = ((sysclkToInClkError > 0.10) || (sysclkToInClkError < -0.10));

     }

sysclkInvalidFreq is always true. It seems the cputimer1 and cputimer2 is never working right.

the cputimer1 and cputimer2 interrupt flag is always high even right after a line of code "CpuTimer2Regs.TCR.bit.TIF = 1;" is stepped through.

Why is that, is this problem something to do with the problem 1?

3rd. I tried to use a different source(int_OCS2) or bypass this PLL clock verify. Still not working, it never going to the ADC interrupt.

  • 0
    TI__Guru**** 163015 points

    Hainan,

    That first screen capture makes me think that the linker command files are not getting picked up correctly.  

    When I build that example the only warning I get is that it was set to use a different compiler than the one I have installed.

    When you build do the last few lines in the console view look like this:

    "./F2837xD_usDelay.obj" "./adc_soc_epwm_cpu01.obj"  -lrts2800_fpu32.lib -l2837xD_RAM_lnk_cpu1.cmd -lF2837xD_Headers_nonBIOS_cpu1.cmd -llibc.a

    <Linking>

    Finished building target: "adc_soc_epwm_cpu01.out"

    **** Build Finished ****

    There should be 2 linker command files being passed to the linker.

    Those files are specified in the linker options for the project here:

    If you go there and put your mouse over the ... behind ${INSTALLROOT_F2837XD}/common/cmd and ${INSTALLROOT_F2837XD}/headers/cmd does a little box pop up showing the full path?  I am wondering if you are having an issue where that macro ${INSTALLROOT_F2837XD} is not defined.

    It is defined when you import the project and is path relative to the location of where the project was imported from.

    If those paths are not resolving you could replace them with the absolute paths which in your case would be:

    C:\ti\C2000Ware_1_00_04_00_Software\device_support\f2837xd\common\cmd

    C:\ti\C2000Ware_1_00_04_00_Software\device_support\f2837xd\headers\cmd

    Regards,

    John