• State TI Thinks Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 32 subscribers
  • Views 957 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.

Cannot debug TM4C123BE6PM using XDS200

ISHAN SHAH1
Intellectual 370 points

Other Parts Discussed in Thread: TM4C123BE6PM

Hi all,

I have tiva processor TM4C123BE6PM sitting on my custom borad and I was trying to debug it using XDS 200.
but I cannot debug. I get mesage that it is incorrect target ID. (my target configuration is correct)

I am using a 25 Mhz crystal across pin 40 and 41 of the MCU. The MCU is not running any code,
My board is just powered up(I have 3.3V on all required pin of MCU), will I see clock (crystal oscillation) on either pin 40 or 41 ???

I am not seeing any clock on pin 40 or 41. is this a problem ?? or can MCU use internal clock if there is no clock???
Sorry I dont have much know how on how crystal works. 

Any comments or suggestions will be helpful.

Thanks,
Ishan

  • 0
    TI__Prodigy 600 points

    The main oscillator needs to be enabled by software before you will see waveforms on pins 40 and 41 (OSC0 and OSC1).  In the Tivaware examples for TM4C123X this is accomplished with a call to SysCtlClockSet(...); near the beginning of main.

    How are you connecting with the XDS200?  Through CCSv5.3.0 or later?  The XDS200 wiki page has installation instructions and can help you troubleshoot.

    -Joel

  • 0 in reply to Joel East
    Intellectual 370 points
    Hi i am using ccs 5.5.0 . All my drivers are updated. For xds200, i am using 10 pin adaptor that comes along with xds 200. All the 10 pins are connected according to the connections listed in data sheet of xds 200. XDS 200 has a CTI20 header, to which I connect CTI20-ARM10 adapter. Those 10 pin connection goes as below Pin# Connected to 1 3.3 V 2 TMS (JTAG port on device) 3 GND 4 TCK 5 GND 6 TDO 7 GND 8 TDI 9 GND 10 RESET For target configuration i have chisen correct device and ti2xx usb emulator. Can you suggest what could be wrong. Thanks, Ishan
  • 0 in reply to ISHAN SHAH1
    Intellectual 370 points

    To add more information.

    In target configuration 

    In connection I have : Texas Instrument XDS2xx USB emulator .

    (Emulation package 5.1.340.0)

    In board or device I have Tiva Tm4c123be6pm, which is MCU on my custom board.

    When I do test connection I get below message in another window. 

    " The JTAG DR Integrity scan-test has succeeded. "

    But when I try to debug I get below error message. 

    Error connecting to the target:
    (Error -1170 @ 0x0)
    Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).
    (Emulation package 5.1.340.0)

    and then in another window 

    Unable to connect to the target.

    Can somebody please suggest what can be wrong in what I have done, why I am not able to debug. Any comments or suggestion will be helpful. 

    thanks,

    Ishan


  • 0 in reply to ISHAN SHAH1
    TI__Prodigy 600 points

    Were you able to connect to this same device previously?  And have you confirmed the XDS200 works with another board?  Do you have a Tiva Launchpad or other evaluation module that does connect ok? 

    I'm trying to locate a XDS200 to confirm what settings work for me.

  • 0 in reply to Joel East
    Intellectual 370 points

    No this is first time I am trying to bring up the board and I have only 1 board. 

    I have Tiva launch pad as well. So now I am trying to see if I can debug target using debug out feature of launch pad.

    For this I am following this instructions. 

    http://processors.wiki.ti.com/index.php/Stellaris_LM4F120_LaunchPad_Debug_How_To

  • 0 in reply to ISHAN SHAH1
    TI__Prodigy 600 points

    Ishan,

    Were you able to debug using the Launchpad ICDI?

    I'm still waiting to receive an XDS200 unit so I can confirm what settings work with the TM4C123.  I will update you as soon as I am able.

    -Joel

  • 0 in reply to ISHAN SHAH1
    TI__Guru**** 244440 points

    Hello Ishan,

    The test connection means giving a message for scan test being successful means that the device you have is alive and not faulty.

    When you try to connect the debugger the Error message would have two meanings

    1. The device is locked and cannot be functionally accessed: Considering that you have never connected earlier and this is the very first time flash can be ruled out. What cannot be ruled out is what the voltage is on the VDDS and VDDA pins considering it is a custom board. Can you check if it is centred around 3.3V?

    2. The Target configuration is incorrect which causes the XDS200 to fail.

    Can you share the ccxml file?

    Amit

  • 0 in reply to ISHAN SHAH1
    TI__Prodigy 600 points

    Ishan,

    I received a XDS200 and was able to successfully to program the DK-TM4C123G development board.  I used the ARM10 pin adapter and CCS 5.4.0.00091.

    1) I imported the blinky example from "TivaWare_C_Series_2...\examples\boards\dk-tm4c123g\blinky\ccs" into CCS.

    2) I followed all steps in section 3.1 of the quickstart guide which creates a new target configuration file.

    3) In the Target Configurations tab I deleted the default configuration file "target_config.xxcml" that loaded with the TivaWare example project.

    Make sure your new target configuration file is the only *.ccxml file associated with your project. 

    Please let me know if this helps.

    -Joel