• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 82 subscribers
  • Views 411 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/TMS320F28377D: Debugger disconnects after running to main

Jayakrishnan Harikumaran51
Prodigy 85 points

Part Number: TMS320F28377D

Tool/software: Code Composer Studio

Hi,

I designed a board using the F28377D dual core device and I am currently trying to get any one of the sample codes from the C2000 ware for the single core to work on the device.

The program compiles (even though it reports that __disable interrupts() function doesnt resolve as well as memcpy is not defined).

I am able to connect to the device and download the code. The code runs to main and it fails in the InitSysCtrl(); function.

I have seen other folks had similar issues but didnt see a clear resolution for the problem. The screenshot is attached below.

I am using the XDS200 JTAG emulator with 14 pin connection. The boot mode is set in Get mode (but is that important in JTAG emulation).

Looking forward your support.

Thanks

Jay

  • 0
    TI__Guru** 117281 points

    Hi,

    What is the clock configuration (INT_OSC/EXT_OSC), you are using? Instead of running the code, please step inside the InitSysCtrl() function and step through the code to check when this error happens. You should also check the status of missing clock bit.

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    Prodigy 85 points

    The clock configuration is XTAL_OSC.

    The error occured when the 

    ClkCfgRegs.SYSCLKDIVSEL.bit.PLLSYSCLKDIV = divsel;

    instruction was executed. After the error, the registers are not readable. So I couldnt check the missing clock bit.

    Divsel used is PLLCLK_BY_2.

    Regards

    Jay

  • 0 in reply to Jayakrishnan Harikumaran51
    Prodigy 85 points

    Hi,

    I modified the clock setup code

    InitSysPll(XTAL_OSC, IMULT_20, FMULT_0, PLLCLK_BY_2);

    to InitSysPll(XTAL_OSC, IMULT_4, FMULT_0, PLLCLK_BY_2);

    The xtal on the custom board is rated at 27MHz. So I think that would explain the issue. The setup is not stable at IMULT_5 either. 

    Ill monitor the actual clock frequency to see what is clock frequency that can be achieved.

    It would be helpful to highlight this in the comment of the initsysctrl function about setting the clock frequency values.

    Thank you

    Jay