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.

TI Uniflash V4.0 vs CCS Uniflash V3.4

Other Parts Discussed in Thread: UNIFLASH

Hi folks,

I have a small problem.

My hardware setup is RM48L730 µcontroller, and XDS100v2 JTAG probe, a JTAG TI-14 to MIPI-60 to access PCB.


Prior to TIUniflash V4.0, i used successfully the load binary file command (using toolbar Program > Load Binary.

Then i use"d to enter location of binary file, and XDS100v2, and start adress.

Where do I find the same command using TI Uniflash V4.0 ?

Second question: is there a cmd line for scripting use of TI Uniflash V4.0, as it was done in CCS Uniflash V3.4 ? Where to find examples ?

Best Regards.

Colin.

  • Hi Colin,

    I'm going to move this to the CCS forum. Haven't seen Uniflash V4.0 and don't know why they'd have changed something that breaks it for you.
  • Where is located the CCS forum, please.

    And sure it's a regression in features for me, as far as I understand for now.

    Best Regards.

    Colin

  • Colin

    The first thing to do is to setup your target configuration.  Similar to UniFlash v3 you can do that by selecting your device and debug probe or selecting an existing .ccxml file.

    For me I just selected the device and probe and then clicked start.  Next specify the program file.  If you want o load as a binary there is a checkbox beside the

    When you check that box it gives you the option to enter the load address

    At this point I would suggest going to the menu selecting Session and Save Session so that in the future you can just load the session and click the Load image button

    As for the second question there is still a command line interface.  There is more information on how to use it in the Users Guide here: http://processors.wiki.ti.com/index.php/UniFlash_v4_Quick_Guide

    It is different than the one in UniFlash v3.  The main reason is that we are attempting to consolidate additional flashing utilities across our product offering.  It is a pretty simple interface though.  

    dslite --mode flash --config=ccxml-file [options] [flash-file1 ...]

    Regards,

    John