• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 31 subscribers
  • Views 452 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:

TMS570LC4357: How to lock JTAG with OTP and temporally unlock using AJSM

TMS570LC4357: (SECURE) xml file for AJSM use

Darryl Uchitil
Intellectual 410 points
Part Number: TMS570LC4357
Other Parts Discussed in Thread: CCSTUDIO

I have created a SECURE version of the XML file for TMS570LC4357 using the information from spna232a.  I have checked it against the sample SECURE versions that were provided for other processors.  Yet Code Composer does not show my Secure version in the file list, only the two example versions.  The related website has links to the  XML and GEL  files I need for TMS570LC4357 but I do not have access to download even when logged in.  How can I get the correct files?

  • 0
    TI__Guru 69891 points

    Hi Darryl,

    We started working on your issue and will provide you an update ASAP.

    --
    Thanks & regards,
    Jagadish.

  • 0 in reply to jagadish gundavarapu
    TI__Guru 69891 points

    Hi Darryl,

    Apologies for the delay in my response,

    Actually, i don't have knowledge on this topic, i should need to discuss this with my senior colleague who is on the vacation till JAN1st. So please be patient till then.

    --
    Thanks & regards,
    Jagadish.

  • 0 in reply to jagadish gundavarapu
    TI__Guru**** 196776 points

    Hi Darryl,

    1. Copy/past tms570lc43xx.xml, and change the copy file name to tms570lc43xx_secure.xml

    2. Change the desc (Linre #7) of the new xml to "TMS570LC43xx (Secure)"

    3. Open CCS

    4. Open a new target configuration, the new xml file should be in the list

  • +1
    Intellectual 410 points

    Thank you QJ and Jagadish, that seems to work.  The TI  power point from 2017 (Hercules_AJSM_Lock_Unlock.pdf) instructs manually adding the port18 code to the XML.  Apparently this is no longer necessary and causes issues.  The example files included with spna232a.zip still have these changes.  Perhaps time for an update?

    Darryl

  • +1 in reply to Darryl Uchitil
    Intellectual 410 points

    There seems to be a caching issue, as I have now deleted a previous version but when I restart  Code Composer, the deleted version is in the list.  This was likely part of the issue.  And if I don't add  the Port 18 stuff described in spna232a, then the AJSM registers are not available in the target configuration.

    Any idea where the selected target configuration gets saved when I click "SAVE" so I can delete dead versions?

  • +1 in reply to Darryl Uchitil
    Intellectual 410 points

    I found that if I close code composer and delete the cache file C:\ti\ccs920\ccs\eclipse\configuration\com.ti.ccstudio.system.setup\targetdb.cache then the next time I open Code Composer the file is rebuilt and all my existing version show up in the list and deleted versions are gone from the list. There must be some "normal" way to cause this cache to be updated but simply closing and opening CCS did not do it, nor did selecting and saving another device.