• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 32 subscribers
  • Views 294 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

LP-AM263P: Using CCS-20 will not launch, stuck in initialization

AM2634: Updated from CCS12 to CCS20 cannot connect via XDS110

Jeffrey Hanzlik
Prodigy 90 points
Part Number: AM2634
Other Parts Discussed in Thread: AM263P4

Tool/software:

We are in the middle of development.  We had been using CCS 12.7.  We ran into problems with the AM2634 being shown as a beta part.  We corrected that by updating to MCU SDK 10.0.0.35 and SysCfg 1.22.  This all intern forced us to upgrade to CCS20.  We have been using the XDS110 on the AM2634-CC with no issues as long as we ignored the M4 core.  I have gone through what I believe is the equivalent steps for CCS20, maybe.  It is not working I get the JTAG -1170 error.

We ever we got that with CCs12.7 we knew to reconfigure the JTAG connection in CCS to disable the M4 core.

CC20 has been a nightmare in getting our project to build correctly.

I am looking for the AM263x specific JTAG steps one needs to follow to properly attach to the XDS110 on the AM2634-CC.  The generic help for CCS does not help.

  • 0
    Mastermind 8025 points
    Jeffrey Hanzlik said:
    This all intern forced us to upgrade to CCS20

    It's not clear why you were forced. I think MCU SDK 10.x still works with CCS12.8

  • 0
    TI__Genius 12296 points

    Hi Jeffrey Hanzlik,

    As Kier recommended, I suggest you use the CCS 12.8x version which the official SDK supports.

    Regards,
    Shaunak

  • 0 in reply to Shaunak Deshpande
    Prodigy 90 points

    It does.  I ran into an issue of the CCS12.8 using both 9.x and 10x of the SDK.  That was causing issues.  From inside CCS12.8 I initiated an update of all supporting packages.  This left the CCS12.8 unable to do anything I was stuck in a update loop.  I was getting pop-up error box /updatename unknown.  

    In the interest of moving forward I went and downloaded the latest version of CCS V20.  I noticed this morning reading your note that I could also download 12.8.1.  I will keep that as an option.  I was expecting that CCS20 would work just fine as it is an upgrade from 12.8.

  • 0 in reply to Jeffrey Hanzlik
    Mastermind 8025 points
    Jeffrey Hanzlik said:
    I was expecting that CCS20 would work just fine as it is an upgrade from 12.8.

    You might think that but it's not my experience when using AM263P4 controlCARD with CCS20. I think CCS20 still has some way to go for it to be equivalent to CCS12.8, especially for multi-core debugging.

    My advice is to stick with CCS12.8 so that your SDK problem is not conflated with a CCS20 problem.

  • +1 in reply to Kier
    Prodigy 90 points

    Thank you for the insight.  I will uninstall the "bad" 12.8 and reinstall.  My limited time with CCS20 is that there is a learning curve to migrate CCS12.