• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 82 subscribers
  • Views 352 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.

Original question:

TMS320F280045: Code does not start without debug active

TMS320F280037C: No output from the controller

Anwesha Mukhopadhyay
Prodigy 10 points

Part Number: TMS320F280037C

Hi,

I am trying to program the TMS320F280037C device on a custom-made board. I am not using Launchpad or any control card available by TI. In first-time programming, loading the code through JTAG gets completed without any error. However, it is not giving any output. Even in the watchdog window, I do not see any change in the GPIO register bits, which the code is supposed to do. I have also tried the Blinky LED example program, but with no luck. 

What may be the reason? Is it some hardware issue? Is there anything to be done for booting?

  • 0
    TI__Guru** 117201 points

    Are you loading the code via CCS and then running it or using some other method to load the code ? After you load the code, it should force the PC to code entry point and then you should be able to run. If not running then when you halt CPU (assuming you are using CCS), does it halt inside your application code or some where else ?

    Vivek Singh

  • 0 in reply to Vivek Singh
    Prodigy 10 points

    Hi..

    To answer your questions:

    Are you loading the code via CCS and then running it or using some other method to load the code ? 

    I am loading the code via CCS.

     After you load the code, it should force the PC to code entry point and then you should be able to run

    I checked in disassembly, PC stays at 

    008455:   764085F9    LCR          InitSysCtrl

    If not running then when you halt CPU (assuming you are using CCS), does it halt inside your application code or somewhere else ?

    It does not stop at the application code, rather it stops at some function for the oscillator, I believe that is part of the InitSysCtrl

    For ref. here is my simple code.Though it does not work with example code also.

    * main.c
    */
    #include "F28x_Project.h"


    int i=0;
    void main(void)
    {


    InitSysCtrl();
    InitGpio();


    {

    EALLOW;

    // GpioCtrlRegs.GPAMUX1.bit.GPIOXX = 0; //Configure 0-15
    GpioCtrlRegs.GPAMUX2.bit.GPIO31 = 0; ////
    GpioCtrlRegs.GPAGMUX2.bit.GPIO31 = 0; //// Configure GPIO16-31 as GPIO for aux conv enabling

    GpioCtrlRegs.GPADIR.bit.GPIO31 = 1; // configure as O/p
    GpioCtrlRegs.GPACSEL4.bit.GPIO31= 0; //CPU1 selected
    GpioCtrlRegs.GPAPUD.bit.GPIO31= 1; //pull up disable

    EDIS;
    }

    while(1)
    {

    DELAY_US(500000);

    GpioDataRegs.GPASET.bit.GPIO31=1;

    i=i+1;
    if(i>10)
    i=0;

    }
    }

    Thanks,

  • +1 in reply to Anwesha Mukhopadhyay
    TI__Guru** 117201 points

    Look like some clocking issue. Please check that clock setting used inside InitSysCtrl are matching with what you have on custom board. E.g. if code is using XTAL then you have XTAL on your custom board.

  • 0 in reply to Vivek Singh
    TI__Guru** 117201 points

    HI Anwesha,

    Were you able to get this working?

    Vivek Singh

  • 0 in reply to Vivek Singh
    Prodigy 10 points

    Thanks..It resolved the issue. By default, XTAL remains selected. However, I was using INTOSC. So, I changed the configuration in InitSysCtrl accordingly.