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.

UNIFLASH: Relative path in UNIFLASH session file

Part Number: UNIFLASH


Tool/software:

Hello,

UNIFLASH supports loading saved session file with --session option. However, all image file paths in that file are absolute which limits session file reuse.

  1. How would I use relative paths for images and what are they relative to?
  2. Program tab only shows image file names not their path which is not really helpful to the user
  3. Session doesn't save GUI options like "Quick Settings" which are useful.

Regards,

Eugene

  • Hello,

    How would I use relative paths for images and what are they relative to?

    The session file is exclusive to the GUI version of Uniflash, so it has some limitations with regard to the path to the executable file. 

    Program tab only shows image file names not their path which is not really helpful to the user

    If you hover over the filename it should display the full path.

    Session doesn't save GUI options like "Quick Settings" which are useful.

    The saved session file stores all the settings changed on the menu Settings & Utilities. This includes what you configure in Quick Settings. 

    All in all, if you would like to automate/script something, I suggest using the Uniflash CLI or the standalone package creator from the GUI.

    Best,
    Nima Behmanesh

  • Hello Nima,

    The session file is exclusive to the GUI version of Uniflash, so it has some limitations with regard to the path to the executable file

    Why can't this path be relative to session file? What kind of limitation prevents tool from using relative paths? That would make GUI session file portable and much more useful.

    Regards,

    Eugene

  • Hello,

    Why can't this path be relative to session file? What kind of limitation prevents tool from using relative paths?

    Unfortunately, that's how it was implemented. Though, I do agree with you that it's an interesting limitation. I'll bring it up with the tools team to see if we can get this feature implemented in future releases of the tool.

    For the meantime, I do suggest using the Uniflash CLI. Our customers have had a lot of success using the CLI for automating flashing of devices. 

    You can find the quickstart guide and command line information here: https://software-dl.ti.com/ccs/esd/uniflash/docs/latest_qsguide.html#command-line-interface

    Best,

    Nima Behmanesh

  • I am not automating flashing of the targets. I need to integrate UNIFLASH into our development environment to give developers option of restoring target when CCS fails to do so. That requires GUI and options that UNIFLASH presents there.

    Regards,

    Eugene

  • Why can't this path be relative to session file? What kind of limitation prevents tool from using relative paths? That would make GUI session file portable and much more useful.

    I have filed a ticket for this. Tracking link: https://sir.ext.ti.com/jira/browse/EXT_EP-12182

    Thanks

    ki