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.

uniflashCLI problem

Other Parts Discussed in Thread: UNIFLASH

Hi :)

i have a problem using the command line interface of the uniflash tool.

I try to program a *.srec file on a Hercules RM46 but the always fails with

***** Texas Instruments Universal Flash Programmer *****

> Configuring UniFlash with the following configuration: C:\ti\uniflash_3.4\ecli
pse\plugins\..\..\test.usf

> Device: null
> Interface: null
Exception in thread "main" java.lang.NullPointerException
        at com.ti.uniflash.commandline.CommandLine.createDeviceSpecificCommandLi
neHandler(Unknown Source)
        at com.ti.uniflash.commandline.CommandLine.setUpApplication(Unknown Sour
ce)
        at com.ti.uniflash.commandline.CommandLine.main(Unknown Source)


Interestingly if I use the gui version and rename test.usf to test.ccxml everythink works fine...

Could this be an format problem because the CLI version expects *.usf files??

Or maybe I simply missunderstood something ;)

Best regards,

Malte

  • Malte,

    The problem here is that we actually provide 2 different command line tools in UniFlash (uniflash.bat and uniflashCLI.bat).

    The one you should be using is uniflash.bat, which supports all of the MCU devices. uniflashCLI.bat was added into the product at a later date to support the wireless connectivity devices (CC32xx). I realize this is a little confusing, so I want to apologize for this.

    Also, if using uniflash.bat, you do not need to rename your configuration file (ccxml) to usf. The usf format is only used in the CC32xx case.

    Please try using uniflash.bat and let me know if you file any issues with it.

    Thanks,
    Ricky
  • Hi Ricky,

    yes you're right... it seem that i have to use the "uniflash.bat" in the examples folder...

    yeaaah it works!! thanks :)

    Malte