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 official support for JLink?

Other Parts Discussed in Thread: EK-LM3S9D92, SEGGER

Hello TI Team,

with the current 5.2 beta of Code Composer Studio and the 0.1.0.2 TI JLink beta drivers I could make my TMDX570LS20SUSB Dev Kit debuggable via an IAR J-Link JTAG Debugger. For a beta it works very well.
My question is: Are there plans of TI to officially and fully support J-Link JTAG Debuggers in Code Composer Studio, or will it always remain a "gimmick-y" beta function? Will I later be able to fully develop a product with the combination CCS + J-Link?

Greetings,
Jakob

  • Hello,

    We have moved this post to Code Composer forum as it can be better addressed there.

    Regards,

    Diwakar

  • Whoops, sorry for posting in the wrong forum, the CCS forum makes a lot more sense.
    Still, is there nobody who could provide me with an answer to my question?

    Regards,
    Jakob

  • Hello Jakob,

    It will be officially support by CCS. The current schedule is to support it in CCSv5.3.x in the fall of this year.

    Thanks

    ki

  • Hello Ki-Soo,

    I installed the jlink support for CCS5.3: ti_jlink_support_setup_0.1.0.3. But it did not  worked very well with the Stellaris LM3S9D92 kit.

    Has Texas a new schedule for officiall support for the Jlink with Stellaris?

    Ari.

  • Hi Ari,

    Could you please give some description or steps on how to reproduce the problem you are having? There are some limitations with the conflicting implementation on the flash related operations between CCS and JLink driver. If that is your problem, remember to choose and stick to one set of flash solutions and do not mix in the operations. The general debugging functions such as breakpoints and stepping should be working.

    Regards,

    Victor

  • Victor,

    I'm using the EK-LM3S9D92 board, CCS5.2.1 and a Jlink from Segger. 

    I tested the application Timer from Stellarisware.

    First time I started the debugger, the code is loaded into the Microcontroller and run till the end of main function, but the CCS show the message "No source Available for 0x37ff000" and the button suspend is inactive. 

    If I restart the debugger and run again, the CCS works okay, no error message and the button suspend is active. But there's no interrupts.

    when I tested the project Blink, the first time run issue after start debugger also happened, but I know that the code is loaded into the flash because the led blinks if I power the board without the debugger.

    What do you mean by: "remember to choose and stick to one set of flash solutions and do not mix in the operations."? There is a special configuration of CCS for this?

     Ari.

     

  • Hi Ari,

    This should be a bug, thanks for reporting it. I have filed a CQ SDSCM00046255 to track this, and you will be notified with the update on this issue.

    Due to the architecture and design of CCS and the JLink, there are some incompatibilities that would sometimes require special handling. The flash components of JLink library assume it has absolute control on the device's flash, while CCS believes itself is the sole owner of those low level resources as well. To prevent conflict, one must not mix the flash operations from the 2 set of software. There is no option in CCS, but there is an option in the JLink control panel to disable flash breakpoints; also, do not use the flash tool from Segger while in a debug session in CCS. 

    Victor

  • Hi Ari,

    I have tried the timer example. In my observation, if you insert the following lines into your lm3s9d92.gel file, you should be able to avoid this problem:

    OnFileLoaded()
    {
    GEL_Reset();
    GEL_Restart();
    }

    You can also drop the attached file in " <ccs install>\ccsv5\ccs_base\emulation\gel " if you don't want to do the editing. Replace the contents in the original "lm3s9d92.gel" with the contents of this file.

    2514.lm3s9d92.gel

    The interrupts in the timer example can be observed by setting break point in the handler functions.

    Regards,

    Victor

  • Victor,

    It's okay now.

    Thanks.

    Ari.