TMS320F280049C: Debug fails when calling DEVICE_DELAY_US function

You need a couple other lines of code along with Board_init()!

We will update our empty project templates to include these! Change your main() to this:

void main(void)
{

    //
    // Initialize device clock and peripherals
    //
    Device_init();

    //
    // Disable pin locks and enable internal pull-ups.
    //
    Device_initGPIO();

    //
    // Initialize PIE and clear PIE registers. Disables CPU interrupts.
    //
    Interrupt_initModule();

    //
    // Initialize the PIE vector table with pointers to the shell Interrupt
    // Service Routines (ISR).
    //
    Interrupt_initVectorTable();

    //
    // Configure ePWM1, ePWM2, and TZ GPIOs/Modules
    //
    Board_init();

    //
    // Enable Global Interrupt (INTM) and real time interrupt (DBGM)
    //
    EINT;
    ERTM;

    // Enter code here

    //
    // IDLE loop. Just sit and loop forever (optional):
    //
    for(;;)
    {
        // Enter code here
    }
}

Thanks. I changed my  main.c as you recommended.

However, the problem is, unfortunately, not solved, le debug still stops as soon as it a DEVICE_DELAY_US(XX) or SysCtl_delay(XX). 

The error is different though :

Break at address "0x3fbd92" with no debug information available, or outside of program code.

I have tried the timer_ex1_cputimers example, and it runs fine even whent going through the SysCtl_delay(XX) function. 

--> is it possible that there is a critical file missing in my project, or that the project isn't properly configured ?

I have copie into my project all of C2000ware's "driverlib" folder (for the relevant part) + device.c / .h. Project configuration is minimal (almost everything has default values). 

I can send the project if it helps, nothing is confidential. 

Hi Nima,

Please find here (TI internal link) the customer's project. This could help your investigation. Thank you.

Best regards,
François.

Thank you Adrien and Francois for sharing this. I will take a look! One more thing that we can check in parallel. Is the debugger halting on it's own or are you pausing it and seeing it is at the location you mentioned above? 

because it could be that you are in the delay function and the debugger just isnt showing you the source code for the delay function!

Thank you Adrien and Francois for sharing this. I will take a look! One more thing that we can check in parallel. Is the debugger halting on it's own or are you pausing it and seeing it is at the location you mentioned above? 

because it could be that you are in the delay function and the debugger just isnt showing you the source code for the delay function!

It is the debugger pausing on its own, unfortunately.

As you can see in the bottom right corner, the disassembly hits an ESTOP0 instruction. I only launched a debug et pressed play, and this is where I end up without pausing or adding any breakpoint of any sort.

Adrien can you send me your main() function content with the call to the delay? The scenario that throws the error. It wasn't in the CCS Project you sent.

Hi Nima,

This is the code / project that fails.

The failure currently happen during Device_init() >  SysCtl_setClock(DEVICE_SETCLOCK_CFG) > SysCtl_selectOscSource(oscSource) > SysCtl_selectXTA() > SysCtl_pollX1Counter() > SysCtl_delay(2000); (sysctl.c file, line 89)

In my earlier project (with only Board_init() and the infinite loop), it failed during Board_init() > ADC_init() > DEVICE_DELAY_US(500); (file board.c, line 102).

If it helps, I am working on an unmodified F280049C Lauchpad.

Perfect I just got my F280049c launchpad. I will run the test.

I just replicated it. Very strange.. you are running out of flash? 

Yes :) I think that was the issue! Let me add one entry to setup the FLASH WAITSTATE and other related items and see if it resolves it!

Hi Nima,

Thank you very much. Adrien now being OoO, he won't respond right away, but you seem to have nailed this issue down. Great!

Side question: should SysConfig do anything about the creation of the _FLASH symbol so that the wait states and the other related items that you mentioned would be taken care of?

Best regards,
François.

Francois, 

So next release will have a FLASH module in SysConfig.

With the Flash module added, the waitstates will be configured in the GUI.

We will at a later release add device.c and device.h to be generated by SysConfig as well.

Nima

Hi Nima,

Very good, thank you.

Best regards,
François.

Thank you very much Nima. It worked !  It had to be something this simple, but tough to find !

Sorry I haven't been able to test it earlier, as I was on vacation.