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.

TMS320F28023PT Debug Problem

Other Parts Discussed in Thread: TMS320F28335, CCSTUDIO

Hello,

 

can I use C2000 XDS510LC USB JTAG (spectrum digital) emulator to debug TMS320F28023PT?

A few months ago I used this emulator with TMS320F28335 without any problem. In my actual project I have designed a board with TMS320F28023PT and always getting the following error:

Error connecting to the target:
Error 0x80000200/-140
Fatal Error during: OCS,
Error generated by SD scan controller module

Could that be a driver problem?

I suppose that there is something wrong in general cause I have measured that the XRS is going down each 12ms for about 50µs. I am using an external 12MHz 3,3V Oscillator (same as in my last project) on pin GPIO38 (XCLKIN) and connected X1 to GND and leave X2 open. The TRST is pulled down through 2k2 and EMU0/EMU1 pulled high with 4k7 (datasheet 6.6 Emulator connection without signal buffering for the MCU).

 

Does anyone can help?

  • certainly you can

     

    make sure you have the driver chosen correctly. if you are using CCS make sure you have the emulator and device chosen correctly.

    after that it could be a hardware issue with your custom board.

     

  •  

    Markus,

    Try this link: http://processors.wiki.ti.com/index.php/Debugging_JTAG_Connectivity_Problems

    How can I find out more about emulator error messages?

    • You can use dbgjtag to find out more about error messages.
    • For example, if I want to find out about error # -121, I could follow the sample below.
    C:\CCStudio_v3.3\cc\bin>dbgjtag -E single,number=-121

    [The explanation of the error number '-121']---------------------------- This error is generated by TI's USCIF driver.

    The value is '-121' (0xffffff87).
    The title is 'SC_ERR_CMD_HANDLE'.

    The explanation is:
    A bad controller handle has been given to a function,
    either before attempting to open the controller, or after
    having opened the controller and ignored its error status.
    Valid controller handles are generated when attempts
    to open the controller return a clean error status.