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: Unable to select Segger J-Link emulator from the connection options CCS 8.2

Other Parts Discussed in Thread: SEGGER, CC3220SF, AM5728

Tool/software: Code Composer Studio

I'm seeing the same issue as seen in this thread:

https://e2e.ti.com/support/tools/ccs/f/81/p/656041/2525163?tisearch=e2e-sitesearch&keymatch=CCS:%20Unable%20to%20select%20Segger%20J-Link%20emulator%20from%20the%20connection%20options#2525163

I have un-installed and reinstalled the Segger for Windows plug in. The connection option is still not available. Any suggestions on how to proceed besides uninstalled and reinstalling? I have used the Jlink for other devices with the current USB drivers, so I highly doubt that is the issue.

Images below:

  • Lucas,

    The screen capture are not coming through.  Are you attempting to use CC3220SF like in the other thread or a different device?

    For me CC3220SF is showing up as valid for JLink

    Here I can create a new target configuration that has J-Link and CC3220SF:

    If I import an example from the CC32xx SDK I am able to change the debug connection to J-Link:

    Regards,

    John

  • Hi John,

    Thanks for the note on the screencaps. Looked like it was fine before I posted, but I guess it got lost in translation.

    Specifically I am attempting to target the AM5728 (dev board from Phytec), but the J-Link is not appearing for this device. It's not that I am unable to verify the JTAG electrical connection, it just appears to not exist for this device.
  • Lucas Rolfes said:
    Specifically I am attempting to target the AM5728 (dev board from Phytec), but the J-Link is not appearing for this device.

    None of the AM57xx devices are currently listed on the SEGGER Supported devices - J-Link

    Which types of AM5728 core(s) do you want to target with the J-Link?

    The Overview of Supported CPUs and Devices says to contact SEGGER if your device has a supported core, but is not on the list of supported devices.

  • The cores I want to target are the M4 cores for IPU1 (non codec processing IPU core). The whole rationale here is I need to be able develop towards these M4's, and I haven't found a means of remotely deploying the code onto the sitara, building, and then reprogramming the IPU from that environment so far. If there is a means of performing it that way, I can re-use my existing work-flows I have setup for the application code.

    Since it is a generic M4, I wonder if there is a different process to get this configured correctly or built properly. Either way, I will send in the request to Segger to get it added.

    The A15s I am using generic G++ over SSH to debug and control, so that isn't something I entirely need.
  • Lucas,

    AM572x is not supported by J-Link.  The list of devices supported is available here:

    CCS is not going to let you select to use J-Link with an AM57xx device as J-Link does not have support for all of the cores that are in the device.  It has 2 Cortex A15s, 2 Cortex M4s and 2 C66x DSPs.  CCS is not going to present the J-Link as a valid option for this device.  Even if you tried to modify the files in CCS that define the device to remove the incompatible cores there are still going to be problems as there are scripts needed to handle the Jtag sequencing that would need to come from Segger.

    Regards,

    John

  • John,


    Thanks for looking into it. I have a request out to segger. I'll keep this post updated if they have any updates.

    As a stop gap, do you know if build output from CCS is able to be loaded into the IPU directly? Or is there a different means of building for use in that environment? Since my target for the compiler is the AM5728 Cortex M, I would think it should be okay.

  • By default CCS will be producing an ELF file but it can be converted to a .bin. There are utilities provided with CCS to do that. The thread below describes the post build step to do this. Alternatively you can just able the hex utility in the project build options which will generate the .hex file which is the first step in converting it to a .bin.

    e2e.ti.com/.../826785