• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 83 subscribers
  • Views 268 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.

TMS320F28379D: GUI Composer: gc-transport-xds and using custom CCXML

Mark Feller
Expert 1220 points
Part Number: TMS320F28379D
Other Parts Discussed in Thread: UNIFLASH

I want to add the debug probe serial number as a connection property, so that I can make sure that the GUI Composer application connects to a specific xds/probe, if there are multiple probes connected.

I have a custom ccxml that works under Code Composer Studio with the serial number.  The custom ccxml file also uses a custom gel file for CPU2

When trying to use my custom ccxml file with gc-transport-xds, I get an error message:

Error: Failed to connect: Loading program for TMS320F28379D core="C28xx_CPU2" failed: File:C:\Users\<username>\AppData\Local\Temp\ti_cloud_storage\ds-service-firmware.data: a data verification error occurred, file load failed.

If I do not use the custom ccxml path for gc-transport-xds, the application works as expected.

Perhaps I need to put the custom GEL file in the proper location for this to work.  If so, what should that be?  

My end goal is to have the GUI Composer application connect to a specific xds/debug probe.  If there are other suggestions for how to do this, please let me know.

Thanks!

--Mark

  • 0
    TI__Guru**** 462941 points

    Hi Mark,

    Mark Feller said:
    a data verification error occurred, file load failed.

    A data verification error has many potential root causes, most of them described in the link below:

    https://dev.ti.com/tirex/explore/node?node=A__APy2XbLelxyqBB2Yz0WR.w__ccs_devtools__FUz-xrs__LATEST

    As mentioned in the article, one common cause is an incorrect debugger memory map. This memory map is often set up by a GEL startup file. 

    Mark Feller said:
    Perhaps I need to put the custom GEL file in the proper location for this to work.  If so, what should that be?  

    That is likely the case. Or you can just specify an absolute path to it in the ccxml file. 

    If you prefer the former (dropping in your custom GEL file into UniFlash) note that many of the default GEL files in UniFlash are located in: <UNIFLASH INSTALL DIR>\deskdb\content\TICloudAgent\win\ccs_base\emulation\gel

    Thanks

    ki