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

CC2642R: Segger Support

Mark Ackerson
Genius 10190 points
Part Number: CC2642R
Other Parts Discussed in Thread: SEGGER,

What's the status of Segger support for CC2642R?  CC2642R is not listed in the Segger release notes:

Regards,
Mark

  • 0
    TI__Genius 13660 points
    Mark,

    Here is a list of supported cores ( www.segger.com/.../ ) and supported devices ( www.segger.com/.../supported-devices.php ) published by Segger. Judging by what is published on the "Supported Devices" web-page, it does appear to seem that the CC2642R is supported.

    Best regards,

    Matt
  • 0 in reply to Matt Calvo
    TI__Genius 10190 points

    Hi Matt,

    The customer is still having problems connecting to the Segger J-Link Ultra+ using CCS V7.2.  Unfortunately I don't have a Segger Ultra+ to debug the issue.  See details below:

    I think I know what is wrong, but I don’t know how to fix it.  Refer to the screen shot below.  There is “J-Link Scriptfile Path.”  My hypothesis is that this J-Link script isn’t getting executed.

    When I first looked at this target configuration, I found that the J-Link Scriptfile Path was blank.  This seemed obviously wrong.  Thus, I browsed to the script file provided by TI, verified that the script file worked using SEGGER’s J-Flash application, then I set the path to point to this script.

    Unfortunately,  I still get the impression, from the LEDs, that this script file is not getting executed.  I am still missing a step.  Do you have any ideas?

    The error messages are highlighted below in the console window.  If there is any logging options that I can enable to get more verbose output, please let me know.

    Thanks,
    Mark

  • 0 in reply to Mark Ackerson
    TI__Genius 13660 points
    Mark,

    I found a couple of threads that refer to this error when I search E2E but have not yet been able to find a clear solution to the issue. I will ping a TIer in the CCS team to see if they have any recommendations. To get a little more information, when does the customer see these errors being printed? Are they at the beginning of programming/debugging or are they during execution? Do the errors print consistently?

    -Matt
  • 0 in reply to Mark Ackerson
    TI__Genius 13660 points
    Mark,

    The CCS team has informed me that there are multiple active posts sent to the J-Link Segger support forum that still need to be addressed in regards to this error. Please have the customer reach out directly to the Segger support forum ( support_jlink@segger.com ) to find a solution because the problem seems to be on the programmer side.


    Best regards,

    Matt
  • 0 in reply to Matt Calvo
    TI__Genius 10190 points
    Thanks Matt, we will reach out to Segger.
  • 0 in reply to Mark Ackerson
    TI__Genius 10190 points
    Hi Matt,

    The customer still thinks a problem with CCS. The SEGGER works well with CC26X2 using J-Flash. They use the same initialization file in both cases. CCS if failing to connect.

    Regards,
    Mark
  • 0 in reply to Mark Ackerson
    TI__Guru**** 168357 points

    Mark,

    The error message [ JLINKARM_IsHalted() call ] failed! is thrown either by the low-level Jlink protocol stack or the CCS-Jlink stub interface.

    We (TI) don't own any of these components, therefore Segger will have to provide their insights in this case.

    In another thread, the same error message is displayed during normal execution. Segger provided a link with instructions to collect log information.

    The customer can collect that information and directly contact Segger - this will be more efficient. 

    Regards,

    Rafael