Uniflash freezes during "Loading Image"

Philipp Seifert said:

Do you have any idea, what I could try to make Uniflash run again on my computer?

Please enable GUI logging and DS logging as mentioned near the end of the below article:

https://software-dl.ti.com/ccs/esd/uniflash/docs/v8_1/uniflash_quick_start_guide.html#defect-reporting-and-logging

Then reproduce the issue with 8.2 and provide both logs.

Thanks

ki

Please find both files attached.

uniflash.log

10:50:39:027 log - NWAgentAPI: dinfraConfigue resolved successfully.
10:50:39:458 error - {}
10:50:39:482 error - {}
10:50:39:509 error - {}
10:50:39:511 error - {}
10:50:39:608 error - {}
10:50:39:616 error - {}
10:50:39:643 error - {}
10:50:39:645 error - {}
10:50:39:697 error - {}
10:50:39:711 error - {}
10:50:39:723 error - {}
10:50:39:735 error - {}
10:50:39:740 error - {}
10:50:41:135 error - {}
10:50:41:159 error - {}
10:50:41:164 error - {}
10:50:41:172 error - {}
10:50:41:182 error - {}
10:50:41:332 error - {}
10:50:41:352 error - {}
10:50:41:354 error - {}
10:50:41:358 error - {}
10:50:41:358 error - {}
10:50:41:562 error - {}
10:50:41:562 error - {}
10:50:41:564 error - {}
10:50:41:565 error - {}
10:50:41:620 error - {}
10:50:42:343 error - {}
10:50:46:016 error - {}
10:50:46:039 error - {}
10:50:46:679 error - {}
10:50:46:756 error - {}
10:50:46:763 error - {}
10:50:46:899 error - {}
10:50:46:936 error - {}
10:50:46:937 error - {}
10:50:47:047 error - {}
10:50:47:052 error - {}
10:50:47:276 error - {}
10:50:47:278 error - {}
10:50:48:122 error - {}
10:50:49:193 debug - Target Configuration. Device: iwr1443, Connection: Serial_Connection, LP: false
10:50:49:661 debug - ufDS, session.configured, partnum of current session = iwr1443
10:50:49:750 debug - addTargetStateListener on Cortex_R4_0
10:50:49:776 debug - AddQuickSetting. id: COMPortText, type: property, core: Cortex_R4_0
10:50:49:776 debug - AddQuickSetting. id: COMPort, type: property, core: Cortex_R4_0
10:50:49:901 error - {}
10:51:26:590 error - {}
10:51:26:594 error - {}
10:51:44:479 debug - returning new configure
10:51:45:415 debug - configured

Thank you. I have sent the logs to the engineering team for analysis. I will pass on any updates as I receive them.

ki

Hi Philipp,

Unfortunately, the logs didn't seem to capture any information related to the issue.

Can you let me know if any of the following cases work for you?

1. Clicking on the "Format SFLASH" button under "Settings & Utilities".

2. Entering an incorrect COM port, and see if any output shows up.

3. Turning on "Verbose" in the console, and trying to load an image, and see if any output is observed.

4. Using the command line instead of the GUI to see if it works.

Let me know if you need additional info on how to run any of these tests.

Thanks,

Ricky

Hello Ricky,

thanks for your reply. To the 4 cases mentioned:

1. "Format SFLASH" generates the exact same Uniflash behavior (freeze of GUI), see picture.

2. Incorrect COM Port generates the exact same output as in my first post.

3. w/ and w/o Verbose, there is no print to the console.

4. I generated the standalone command line from uniflash. Same result.

I looked again into the parent folder of the log file. The logfile accumulated to a size of ~200GB in the meantime.

In the task manager, either DS-Lite or nwjs generate a huge CPU load. I have to kill every single task manually even though I closed Uniflash.

I attached a new log-file, which grew to ~64MB in 10seconds (delay to kill all DS-Lite/nwjs tasks in device manager). 

The file is cut since it is repetitive.
Uniflash_Logfile_reduced.log

Philipp,

Thanks for the information and the updated log. This log file does show the sequence of operations up to the hang, although I still can't figure out why the process is hanging for you.

Can you try generating one more log for me?

1. Start up a Command Prompt

2. Browse to you UniFlash install folder

3. Set the PYTHON_SUBPROCESS_LOG_FILE_PATH environment variable by running the following:

> set PYTHON_SUBPROCESS_LOG_FILE_PATH=<pathToLog>

4. Start UniFlash GUI via the following command:

> node-webkit\nw.exe .

5. Configure and Load Program

Please let me know if you have questions on these steps.

Thanks,

Ricky

Hello Ricky,

thanks for tackle down this issue. 

To your 4th point. Is UniFlash supposed to start by nw.exe? If so, it does not work. Start-up freezes at following overlay. 

Kind regards

Philipp

Yes, you can start UniFlash via nw.exe, but you need to pass it the path to the UniFlash install as the first parameter. The '.' in my example command would handle that if it was run from the install folder; but if not, you can also pass in the full path manually.

Thanks.

Thanks for you patience, I overlooked the "."

The log is attached. I tried several precompiled .bin, same result for all of them.

BR

[CLIENT] arg 0: C:\ti\uniflash_8.2.0\deskdb\content\TICloudAgent\win\ccs_base\DebugServer\bin\FlashPythonSubprocess.exe
[CLIENT] arg 1: 9540
[CLIENT] arg 2: C:\ti\uniflash_8.2.0\deskdb\content\TICloudAgent\win\ccs_base\mmWave/gen1
[CLIENT] do_read_header 1: 
[CLIENT] do_read_header 2: 530
[CLIENT] do_read_body 1: 
[CLIENT] do_read_body 2 received cmd blk: {
   "id" : 0,
   "images" : [
      {
         "load_addr" : 2,
         "order" : 2,
         "path" : "C:/ti/mmwave_sdk_02_01_00_04/firmware/radarss/xwr12xx_xwr14xx_radarss_rprc.bin"
      }
   ],
   "properties" : {
      "COMPort" : "COM9",
      "DownloadFormat" : true,
      "FlashDiagnostics" : false,
      "FlashFiles" : "",
      "FlashRAMBackup" : true,
      "FlashTimeoutValue" : 20,
      "FlashVerboseMode" : false,
      "MemSelectRadio" : "SFLASH",
      "partnum" : "IWR1443"
   },
   "type" : "load_images"
}

[CLIENT] do_read_header 1: 

Ricky,

I use Python on a regular basis, so I did not expect any issues here.

Nonetheless, I cleaned my Windows PATHS related to Python. After reinstalling Uniflash 8.2, I am able to flash my xWR again. 

Thanks for your help.

Philipp