• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 83 subscribers
  • Views 325 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.

TMS320F280049C: Automatic selection of the connected target to flash it

Alexandre Tacheux
Prodigy 20 points

Part Number: TMS320F280049C
Other Parts Discussed in Thread: TMS320F280049, TMS320F280039, UNIFLASH

Hello,

I am in the process of migrating software based on C2000 TMS320F280049 MCUs to C2000 TMS320F280039 MCUs. But during the transition, we will use both depending on available stock.

I'm looking for a way to flash from CCS or UNIFLASH without changing the active target (i.e. mounted on the board) through a ccxml file. Same problematic for debbuging from CCS.

Is there automatic or semi-automatic detection of the connected target?

Does anyone faced off to a similar issue?

I use XDS110 JTAG, CCS 12.2, UNIFLASH 8.3

Thanks a lot

Alexandre

  • 0
    TI__Guru* 86150 points

    Alexandre,

    I understand what you want to do, but I'm not sure CCS can do this natively.  However, our devices do have a unique DEVICE/PART ID in the OTP space.  What I'm thinking you could do is use DSS scripting, which is java based control of CCS to connect, read the PARTID, then load a  particular file based on the return value.  The ccxml file you choose may return an error if the device doesn't match, which could also be used to determine what device is connected, but I'm not 100% sure on that point.

    I know Uniflash has a command line interface as well, and ability to read memory, but I'm not as familiar with that. 

    I'll try and look into the Uniflash aspect a bit more tomorrow and reply back.

    Best,
    Matthew