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.

CCSv6 and TMS320F28335: C28xx:Can't Single Step Target Error when using XINTF

Guru 19965 points
Other Parts Discussed in Thread: TMS320F28335

Hello,

I have not been successful getting the TMS320F28335 XINTF to write to a flash chip.  The Chip select and address lines seem to be working.  However, I noticed the Write Strobe is not going low when I execute  the following 3 lines of code.

*((Uint16*)0x200555UL)= 0x00AAU;
*((Uint16*)0x2002AAUL)= 0x0055U;
*((Uint16*)0x200555UL)= 0x0020U;

.

Those three lines are in the flash drivers initialization function. They occur after the external interface is initialized.

After stepping over those three lines of code, I run to a function that contains the following code. When I try to step over *((Uint16*)0x200555UL) = 0x00A0U; in the code shown below, CCS pops up with a error dialog box and the error shown below in the command window.

What could be causing the CCS error?

Stephen

for(i=0;i<u16NumberOfDataItems;i++,pu16MemLocation++)
{
    *((Uint16*)0x200555UL) = 0x00A0U;  <--- stepping over the following line causes the CCS debugger error
    *pu16MemLocation = pu16Data[i];

    DSP28x_usDelay(1000U);
}

C28xx: Can't Single Step Target Program: (Error -1156 @ 0x800) Device may be operating in low-power mode. Do you want to bring it out of this mode? (Emulation package 6.0.14.5) 

C28xx: Error: (Error -1135 @ 0x3203D7) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 6.0.14.5)
C28xx: Unable to determine target status after 20 attempts
C28xx: Failed to remove the debug state from the target before disconnecting. There may still be breakpoint op-codes embedded in program memory. It is recommended that you reset the emulator before you connect and reload your program before you continue debugging

  • I moved the line causing the issue from the for loop to right after the previous 3 lines of code as shown below and I am still getting the debugger issue when I step over that line.

        *((Uint16*)0x200555UL)= 0x00AAU;
        *((Uint16*)0x2002AAUL)= 0x0055U;
        *((Uint16*)0x200555UL)= 0x0020U;
        *((Uint16*)0x200555UL) = 0x00A0U;

    Stephen

  • Am I posting this question in the correct e2e forum?

  • Stephen,

    stevenh said:
    Am I posting this question in the correct e2e forum?

    I suspect not. Although the error message is related to CCS, it seems to be a direct consequence of the operations running on the device. In this case, the experts at the C2000 device forum would be better enlightened to help you.

    I will move this thread there.

    Cheers,

    Rafael

  • Hello,

    I was able to write to and read from the flash.

    If I increase the read and write XINTF lead time from 5 to 8, the dialog box shown below will pop up when I run my program.

    Can the XINTF somehow cause problems with the XDS100v2 debugger?

    Stephen