LAUNCHXL-F28069M: Uniflash: one_time_setup.bat standalone command line

Justanick

Part Number: LAUNCHXL-F28069M
Other Parts Discussed in Thread: UNIFLASH,

Hi,

in the file one_time_setup.bat seems the important part of the code to be missing.

@echo off
SETLOCAL
SETLOCAL ENABLEDELAYEDEXPANSION

Uniflash version 7.0
Windows
Device: LAUNCHXL-F28069M (LaunchPad)

over 3 years ago

0 Vamsi Gudivada over 3 years ago

TI__Guru* 87155 points

Hi,

I asked our UniFlash team to help you on this.

Please expect a reply in a day or two.

Thanks and regards,

Vamsi

0 Ki over 3 years ago

TI__Guru**** 467511 points

Justanick said:
in the file one_time_setup.bat seems the important part of the code to be missing.

Hello,

I just generated a package using UniFlash 7.0. Those lines are still in the one_time_setup.bat file that was generated. Can you share your generate bat file (the entire file)?

Thanks

0 Justanick over 3 years ago in reply to Ki

Prodigy 50 points

The generated one_time_setup.bat is available under the following link: https://workupload.com/file/M6Ja8C9JqeH

The file does include the three lines in the posting above.
1) Disable the echo function.
2) Create a local container for parameters.
3) Set the local parameter ENABLEDELAYEDEXPANSION.

But where are the lines which are doing the following job mention in uniflash:
Run one_time_setup.bat to install the necessary files on your machine to use your device [Show Less]

0 Ki over 3 years ago in reply to Justanick

TI__Guru**** 467511 points

Justanick said:
But where are the lines which are doing the following job mention in uniflash:

The commands that appear in that bat file will vary depending on the device and debug probe used. For example, there will be extra setup needed for XDS110. If there are no additional commands needed, then you will not see anything beyond those three default commands that are always there.

0 Justanick over 3 years ago in reply to Ki

Prodigy 50 points

Also the XDS100v2 seems to need some extra care.

A fresh windows 10 installation with the latest updates and fresh Uniflash 7.0 command line firmware package.

0 Ki over 3 years ago in reply to Justanick

TI__Guru**** 467511 points

Does flashin via UniFlash GUI work fine?

0 Justanick over 3 years ago in reply to Ki

Prodigy 50 points

No uniflash installation on the fresh testing machine. Like it will be later in the real case.

On the local development machine flashing with the uniflash gui is possible.

0 Ki over 3 years ago in reply to Justanick

TI__Guru**** 467511 points

Ah, sorry I understand now. You are simply using the exported package with a clean Windows 10 installation.

I suspect I know what is happening. I may need to follow up with engineering tomorrow morning. I will update you as soon as I can.

Thanks

0 Justanick over 3 years ago in reply to Ki

Prodigy 50 points

Exactly, that is the case.

+1 Ki over 3 years ago in reply to Justanick

TI__Guru**** 467511 points

I took a closer look and not only is the one_time_setup.bat incomplete... but it looks like the exported package is missing the drivers for the XDS100 completely.

Can you try the below workaround:

1) download and extract the contents of the below zip into: <UNIFLASH EXPORTED PACKAGE>\ccs_base\emulation

windows.zip

If extracted correctly, you should have a path to the ftdi drivers such as:

2) replace one_time_seup.bat with the one below:

one_time_setup.zip

Thanks

0 Justanick over 3 years ago in reply to Ki

Prodigy 50 points

Hi,

that is solving the problem with the not known device and the flash process is working as expected.

Is there a time frame for a new version of Uniflash which does include this fix?

0 Ki over 3 years ago in reply to Justanick

TI__Guru**** 467511 points

I filed a bug for this. Tracking link: https://sir.ext.ti.com/jira/browse/EXT_EP-10728

I don't have a timeframe yet but will push to get it into the next release if possible.

Thanks

C2000™︎ microcontrollers

C2000 microcontrollers forum

LAUNCHXL-F28069M: Uniflash: one_time_setup.bat standalone command line