• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 2948 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CCS/CC1310: Uniflash generated dslite command line utility failed to program secondary IEEE MAC

Andrzej Rudel
Intellectual 310 points
Part Number: CC1310
Other Parts Discussed in Thread: UNIFLASH

Tool/software: Code Composer Studio

I have problem to program secondary IEEE on CC1310 with dslite.bat file

Uniflash is generating Standalone Command Line utility that includes genertated.ufsetting with with secondary mac value.

When dslite batch file is execauted it fails to program or recognize -l option.

Executing default command:
> dslite flash -c user_files/configs/cc1310f128.ccxml -l user_files/settings/gen
erated.ufsettings

Failed: nothing to do

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


Options:
  -c [ --config ] arg        Configuration (ccxml) file.
  -l [ --load-settings ] arg Apply settings file generated by UniFlash GUI.


I was able to program and read back secondary IEEE MAC from UniFlash GUI but we need automated method to setup production line.

Andrew

  • 0
    TI__Guru**** 161615 points
    Andrzej,

    The command line options I see in the uniflash guide are a little different.

    Usage:

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

    -c [ --config ] arg Configuration (ccxml) file.
    -l [ --load-settings ] arg Apply settings file generated by UniFlash GUI.
    -s [ --setting ] arg Override a specific setting by using id=value.
    Can be specified multiple times.
    -b [ --before ] arg Operation(s) to perform before loading. Can be
    specified multiple times, and are performed in the
    order they appear on the command line.
    -f [ --flash ] Load the file(s) specified at the end of the
    command line to flash. This is assumed to be set
    unless verify is set.
    -v [ --verify ] Verify the file(s) specified at the end of the
    command line.
    -a [ --after ] arg Optional operation to perform after loading. Can
    be specified multiple times, and are performed in
    the order they appear on the command line.
    -t [ --timeout ] arg Timeout in seconds, infinite if unspecified.
    -g [ --log ] arg Enable detailed logging to the specified file.
    -e [ --verbose ] Outputs progress messages to the console.
    -r [ --core ] arg (=0) Zero based index of core to operate on.
    -p [ --list-ops ] List the available flash operations.
    -n [ --list-settings ] List the final settings applied.
    -h [ --help ] Print this message.


    You would also need: --before WriteSecIeee

    Regards,
    John
  • 0 in reply to JohnS
    Intellectual 310 points
    John

    I added --before WriteSecIeee at the end of dslite.bat file CMD as in line below


    CMD /C "!DEBUGSERVER_ROOT!bin\DSLite" flash -c user_files/configs/cc1310f128.ccxml -l user_files/settings/generated.ufsettings -e -f -v user_files/images/MyFirmware.out --before WriteSecIeee

    Still read IEEE result is FF:FF:FF:FF:FF:FF:FF


    generated.ufsetting file looks like this

    {"Texas Instruments XDS110 USB Debug Probe/Cortex_M3_0":{"DeviceIeeeSecondary":"FF:FF:FF:FF:FF:FF:12:34","FlashEraseSetting":"Necessary Sectors Only","KeepCcfgSetting":false}}

    Does WriteSecIeee takes argument ? What is the format ?

    Andrew
  • 0 in reply to Andrzej Rudel
    Intellectual 310 points
    I have changed command to --after WriteSecIee and now it works fine .


    Thank you.

    Andrew