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/TMS320DM365: license for using CCS V9.3 + XDS510 USB

Part Number: TMS320DM365

Tool/software: Code Composer Studio

Hi,

I was using CCS V3.3 + XDS510USB to work with my DM365.

Now I want to transfer to a higher version CCS because if Win 10 system is used.

But when I tried to use CCS V9.3, I always get a error message which says "License can not be acquired", please see below.

How can I get proper license to use CCS V9.3 + XDS510USB to work with my DM365?

Thanks and Best Regards,

Ivy

  • Ivy,

    The screen capture is not coming through.  There is information on how to post images here: https://e2e.ti.com/support/tools/ccs/f/81/t/821597

    A couple things to note:

    • CCSv9.3 does not use software licensing.  i.e. there is no license management in it
    • CCSv9.3 does not supprt XDS510.  The last version to support XDS510 class debug probes is CCSv8.3.1

    Thus you are going to need to use CCSv8.3.1.  I am curious when that license error is displayed as we don't have a license management system in CCSv9.

    Regards,

    John

  • Thanks John!!!

    Will V6.3 support XDS510USB?

    Yesterday I tried V6.3 and get the same error as V9.3, please see below.

    Thanks and Best Regards,

    Ivy

  • Ivy,

    Prior to CCSv7 we had flexera licensing in CCS that was used for license management.  That was physically removed in CCSv7 and later.  

    We did not do a CCSv6.3 release.  We did have a 6.1.3.  It did use flexera licensing. So it would pop up that message if when using XDS510 without a full CCS license.

    CCSv9.3.0 does not have licensing so it would not display that message.  It also would not let you configure an XDS510 debug probe as it doesn't include support for them.

    I would suggest using CCSv8.3.1.  You can download it at the link below.  

    https://software-dl.ti.com/ccs/esd/documents/ccs_downloads.html

    Regards,

    John

  • Thanks John!!

    Sorry for the typo, it was V6.2.

    I will try V8.3.1 and update you later.

    Thanks and Best Regards,

    Ivy

  • Hi John,

    I can use V8.3.1 now.

    But when I launch the configuration file, I always get error below.

    Could you please help me with it?

    Thanks and Best Regards,

    Ivy

    ARM9: Trouble Writing Register CPSR: This operation is not supported by this driver
    ARM9: GEL: Error while executing OnTargetConnect(): Target failed to write register CPSR
    at CPSR=0x400000D3 [evmdm365-orig.gel:96]
    at OnTargetConnect()

  • Ivy,

    I will need to bring in someone else to help as I don't have access to this hardware.

    Basically it is launching the debugger and executing the initialization script (emudm365-orig.gel).  Looking at the script it tries to write to CPSR and set to supervisor mode and disable IRQ/FIQ.  That is failing.

    John

  • Thanks John!

    Best Regards,

    Ivy

  • Hi John,

    Could you please help to find someone to help with this issue?

    Thanks and Best Regards,

    Ivy

  • My colleague has located a board.  Hopefully he is able to reply in the next day or so.

    Regards,

    John

  • Hi Ivy,

    Ivy Liu1 said:
    ARM9: Trouble Writing Register CPSR: This operation is not supported by this driver
    ARM9: GEL: Error while executing OnTargetConnect(): Target failed to write register CPSR
    at CPSR=0x400000D3 [evmdm365-orig.gel:96]
    at OnTargetConnect()

    I am unable to reproduce the issue with my DM365 LeopardBoard. I tried both the standard DM365 configuration and the one for the DM365 EVM. Since your configuration is using the evmdm365.gel file, I assume you are using the EVM configuration. Are you actually using the TMDXEVM365 board?

    Thanks

    ki

  • Ki said:
    Since your configuration is using the evmdm365.gel file

    Actually the name of your file is a little different - evmdm365-orig.gel. Where did you get this file? It looks like it was renamed (likely the original copy that was used to make custom versions of)?

  • Thanks Ki for your reply.

    I am using our own designed PCB board with TMS320DM365 chip.

    The board was working perfectly with CCS V3.3 on my old Win 7 PC.

    But my old PC is broken, so I have to install CCS 8.3.1 on my win 10 now.

    The gel file I used actually is the evmdm365.gel file, I just renamed. 

    And I tried my old gel file from CCS V3.3, it gave the same error.

    Did I do wrong in configuration?

    The steps I did are,

    1. View->Target Configuration

    2. choose EVMDM365, click "Target Configuration" in "Advanced Setup", the configuration is as below.

    Thanks and Best Regards,

    Ivy

  • Ivy Liu1 said:
    The board was working perfectly with CCS V3.3 on my old Win 7 PC.

    For the above configuration, can you confirm that the gel file was being used?

  • Ivy Liu1 said:

    Thanks Ki for your reply.

    I am using our own designed PCB board with TMS320DM365 chip.

    The board was working perfectly with CCS V3.3 on my old Win 7 PC.

    But my old PC is broken, so I have to install CCS 8.3.1 on my win 10 now.

    The gel file I used actually is the evmdm365.gel file, I just renamed. 

    And I tried my old gel file from CCS V3.3, it gave the same error.

    Did I do wrong in configuration?

    The steps I did are,

    1. View->Target Configuration

    2. choose EVMDM365, click "Target Configuration" in "Advanced Setup", the configuration is as below.

    Thanks and Best Regards,

    Ivy

    The above screenshot has "Data Snapshot Viewer" as the connection type. This is not correct.  You should be using one for the XDS510 USB

  • Hi Ki,

    I realize that I should choose TM320DM365 instead of DM365EVM.

    I created another target configuration file and launched it.

    It looks like it is working, please see picture below.

    But I can't see anything in the Disassembly view and I can't interrupt it either.

    Thanks and Best Regards,

    Ivy

  • Hi Ki,

    I figured it out. I didn't really run it, :).

    Now it is working.

    Thanks and Best Regards,

    Ivy

  • Great to hear! 

    Note that when debugging, you need to have the Debug view open and a proper context selected. Otherwise you will not be able to do a lot of target actions. In your last screenshot, I don't see it open.

    Thanks

    ki

  • Thanks Ki and John for your great help!!!

    Best Regards,

    Ivy