• State Resolved
  • Locked Locked
  • Replies 12 replies
  • Answers 2 answers
  • Subscribers 55 subscribers
  • Views 1305 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.

CCS/TM4C1294KCPDT: Debugging Issue

Aaron MacNeill
Prodigy 70 points
Part Number: TM4C1294KCPDT
Other Parts Discussed in Thread: EK-TM4C1294XL

Tool/software: Code Composer Studio

Hey There,

I am having some trouble flashing/debugging a board I have been designing.  I am using a 10 pin JTAG connector with the MikroProg MikroE debugger for Tiva processors.  Just to set the scene:

-I have followed the application notes 'Using TM4C12x Devices Over JTAG Interface'.

-I have defined the predefined symbols ccs="ccs", UART_BUFFERED, TARGET_IS_TM4C129_RA2, PART_TM4C1294KCPDT

-Connection is set to 'Stellaris In-Circuit Debug Interface'

-JTAG frequency is set to 1MHz, the clock for the processor is 25MHz.

-The test program I am attempting to flash works on the EK-TM4C1294XL Rev D board

-The signals coming from the debugger appear to be ok upon shallow examination

-I am using Windows 10 Pro and both my USB ports I believe are USB 3.0 (I am using a surface book 2)

-I am using CCS 8.3.1.00004

-I have gone through posts that have similar issues, tried what was suggested, but have had no success.

When I attempt to flash the processor I get the error 'CORTEX_M4_0: Error connecting to target: timed out while waiting for target powerup/polling a hardware resource'.  Any insights on what could be causing this issue would be greatly appreciated.

Aaron

  • 0
    TI__Guru**** 171309 points

    Aaron,

    We in the tools team do not support this debug probe. Did you contact MikroProg for assistance? 

    I don't see on their product page any reference to Code Composer Studio. Are you sure this probe is compatible? 

    Regards,

    Rafael

  • 0
    TI__Guru*** 135355 points

    Hello Aaron,

    MikroProg is not a tool we support in any manner, it is a third party tool and does not use any TI developed resources. We don't know how the tool works any better than you do unfortunately.

    Specifically from the User's Guide: mikroProg™ for Tiva™ programmer requires special programming software called mikroProg Suite™ for ARM®. This software is used for programming all Tiva™ and Stellaris® ARM® Cortex-M3™ and Cortex-M4™ microcontroller families.

    You will need to contact the MikroE directly for support with this tool.

    Alternatively, you could consider using the XDS200 which includes adapters for the ARM 10-pin connector. That probe would be supported in CCS and is something that we would be happy to help offer support for if you run into any problems with using it.

  • 0 in reply to desouza
    Prodigy 70 points

    Thanks for your reply Rafael.

    I havent contacted them about about their debugger yet.  I know for a fact that it works, just not for my application so far.  We are using this debugger for other board designs and it works reasonably well.

    I just ordered an XDS200, so I will try debugging with that before checking back.

    Aaron

  • 0 in reply to Ralph Jacobi
    Prodigy 70 points

    Thanks for the reply Ralph.  I just ordered an XDS200, should be here in a few days, I will check back in after having tried that out.  For other applications, we were able to program these processors through CCS using this debugger.   Anyways, I will wait until I get the proper debugger and check back in.

    Aside from using the TI debugger, any other insights for things to try out?

    Aaron

  • 0 in reply to Aaron MacNeill
    TI__Guru*** 135355 points

    Hello Aaron,

    Unfortunately not, no one on our TM4C support team has one of these and I didn't see anything in the way of older E2E posts that were relevant either (other posts had the same message, ask MikroE...).

  • 0 in reply to Ralph Jacobi
    Prodigy 70 points

    Thanks Ralph.  I will let you know how the XDS200 pans out.

    Aaron

  • 0 in reply to Aaron MacNeill
    TI__Guru**** 171309 points

    Aaron,

    One detail that may help you with the combination of XDS200 and the TM4C devices is the ability to perform SWO Trace. 

    Setup tips can be found at:

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

    And a small webinar showing the capabilities is:

    https://www.youtube.com/watch?v=HG_i_uln6Es 

    Regards,

    Rafael

  • 0 in reply to desouza
    Prodigy 70 points

    Hi Rafael,

    I received and have attempted debugging with the XDS200 over the 10 pin JTAG interface.  I have received the following error:

    Error connecting to the target:
    (Error -2062 @ 0x0)
    Unable to halt device. 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 8.1.0.00012)

    I have changed the JTAG frequency to 50kHz, 100KHz, 1MHz and have gotten the same error.  When I test the connection I get confirmation that both the JTAG IR and DR integrity scan test has succeeded.  

    I have looked through the using TM4C12x Devices over JTAG document's troubleshooting section.  I can verify 3.3V VDD and VDDA, 1.2V on VDDC.  The capacitance on that pin falls within the spec at 2.03uF.  JTAG header is getting 3.3V.  Reset pin is pulled high by a pullup resistor.  External crystal is oscillating at 25MHz.

    Any insight on this error would be greatly appreciated.

    Aaron

  • 0 in reply to Aaron MacNeill
    TI__Guru*** 135355 points

    Hello Aaron,

    Do you have the pull-up/pull-down resistors installed on the other JTAG lines as well? The Reset pin for 10 pin JTAG does not need a pull-up. See Section 4.3 of the JTAG Document.

    Also is this is a custom board? If so, is the RBIAS resistor populated per errata (see similar thread with that exact error): 

  • 0 in reply to Ralph Jacobi
    Prodigy 70 points

    Hi Ralph,

    The pull up resistor is part of reset button I have.  Attached is a snapshot of my Eagle Schematic to show you what I mean.  This is a custom board and the RBIAS resistor is not populated.  I will attempt to populate it and let you know how that pans out.

    Thanks again,

    Aaron

  • 0 in reply to Aaron MacNeill
    TI__Guru*** 135355 points

    Hello Aaron,

    Okay JTAG schematic looks good - the lack of RBIAS is almost certainly the root cause here, seen this many times before and that always fixed it. Let us know the result when you get it populated.

  • 0 in reply to Ralph Jacobi
    Prodigy 70 points

    Hi Ralph,

    That was indeed the issue.  Many thanks for your assistance with this.

    Aaron