• State TI Thinks Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 3 answers
  • Subscribers 56 subscribers
  • Views 271 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.

Original question:

MSPM0G3507: Unable to access Debug Properties in CCS Theia 1.4.0.12

CC1312R: Segger JLINK doesn't work as a debug platform in CCS 20.1.0

andy rea
Prodigy 130 points
Part Number: CC1312R
Other Parts Discussed in Thread: SEGGER

Tool/software:

if you pick the segger jlink in the project settings

 

then the debug page shows nothing useful

i can see it is trying to access the JLink Debugger as the LEDs are flashing away but it won't connect - 99% sure there are settings that are not right

if i use JFLash or Ozone ( Segger tools ) after setting the connection up as being cJTAG it all works flawlessly

why is CCS just so rubbish that it lets you have the option to use it but isn't supporting it

picking a different one at random, shows more of a we don't support this message. the uart connection was the same as the Segger one

it's not like Segger haven't been around for a long time now and their tools generally do work 

I'm not going back to using a TI dev board as a debugger as that's just rubbish

  • 0
    TI__Mastermind 25936 points

    Hi Andy,

    I have just tried on CCS 20.2.0 and it works out of the box...

    Are you trying with a Launchpad, or your own target board?

    Regards,

    Arthur

  • 0 in reply to Arthur R☑️
    Prodigy 130 points

    custom board

    i know the hardware is all good as it works with the segger tools externally

  • 0 in reply to andy rea
    TI__Expert 7645 points

    Hi Andy,

    could you please test with CCS 20.2.0.

    If there is an issue we would like to further investigate it but since it works out of the box we need more details to understand what is the issue in your case.

    Thank you,
    Theo

  • 0 in reply to Theo Lange
    Prodigy 130 points

    ok so having started another project for the 1312, and had to use the JLink box, I did get it to work but I don't think that CCS  did its job properly

    I had forgotten about the targetConfigs configuration for the tool - probably because it feels more logical to me to have been in that project settings page that was blank but i guess that's just my opinion!

    what I don't understand is why CCS sets the target to JTAG and not cJTAG which it needs to be to work ( and hence not being right is why it hasn't worked before I guess for other projects )

    clearly there are enough options that whatever the defaults are are 'probably' wrong, but to at least choose the interface mode for the basic setup as I have here ie a single CC1312 connected to the JLink box would have been more helpful

    probably would have been more obvious when you have spent more time with these things but given you basically never need to go through that screen when you start up and play with the launchpad boards, and the fact that there was a chunk of settings visible in the project settings screens when using the TI debuggers it is not that intuitive as it as, well IMHO anyway.

  • 0 in reply to andy rea
    TI__Expert 7645 points

    Hi Andy,

    thank you for trying again and I'm happy to hear that you can connect now successfully.

    I understand your frustration that there was no clear information in the debug tab.

    I will forward your feedback and please reach out again if you experience further issues.

    Kind regards,
    Theo

  • 0 in reply to Theo Lange
    Prodigy 130 points

    also as per https://software-dl.ti.com/ccs/esd/documents/users_guide_ccs_20.2.0/ccs_debug-main.html having just found that page to try and actually debug within ccs, there is no test connection option for JLink ever enabled on that screen

  • 0 in reply to andy rea
    Prodigy 130 points

    where am I supposed to set the JLink serial number when you have multiple devices?

    it is tedious having to confirm the JLink dialogue everytime you try to run a flash or debug operation to pick a Debugger when you have multiple debuggers connected

    these dialogue and config options are not fit for purpose

  • 0 in reply to andy rea
    TI__Genius 16520 points

    Hi Andy,

    I see that you are trying to access the debugger properties from the project, there is a small bug for the JLink connection type. We will address this issue in the next release that is targeted for the end of August.

    The workaround would be to launch the debugger first and right click on the CPU in the Threads view, select the 'Properties...' context menu item to open the same dialog.

    Regards,
    Patrick