FLASHTOOL: Uniflash Tool V7.1 on ubuntu18.04

Rio Chan

Genius 14995 points

Part Number: FLASHTOOL
Other Parts Discussed in Thread: UNIFLASH, MSP-FET

Hi Champs:

While installed the uniflash tool 7.1, and launching it,

Ubuntu will give me these errors.

How to solve it?

BR Rio

(Setup:9915): IBUS-WARNING **: 23:00:04.576: The owner of /home/rio/.config/ibus/bus is not root!
root@ubuntu:/opt# [10146:10169:0228/230254.338721:ERROR:bus.cc(397)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[10146:10169:0228/230254.338845:ERROR:bus.cc(397)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[10146:10169:0228/230254.471959:ERROR:bus.cc(397)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[10146:10169:0228/230254.474622:ERROR:bus.cc(397)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[10194:10194:0228/230254.777881:FATAL:nw_content_renderer_hooks.cc(53)] Failed to load node library (error: libatomic.so.1: cannot open shared object file: No such file or directory)
#0 0x7fa1803ce463 (/opt/ti/uniflash_7.1.0/node-webkit/lib/libnw.so+0x57b5462)
#1 0x7fa1803e1a8e (/opt/ti/uniflash_7.1.0/node-webkit/lib/libnw.so+0x57c8a8d)
#2 0x7fa185317ec5 (/opt/ti/uniflash_7.1.0/node-webkit/lib/libnw.so+0xa6feec4)
#3 0x7fa18537e1c2 (/opt/ti/uniflash_7.1.0/node-webkit/lib/libnw.so+0xa7651c1)
#4 0x7fa17ff397f6 (/opt/ti/uniflash_7.1.0/node-webkit/lib/libnw.so+0x53207f5)
#5 0x7fa17ff36f26 (/opt/ti/uniflash_7.1.0/node-webkit/lib/libnw.so+0x531df25)
#6 0x7fa17ff37a9b (/opt/ti/uniflash_7.1.0/node-webkit/lib/libnw.so+0x531ea9a)
#7 0x7fa17cc6f866 ChromeMain
#8 0x7fa17a80109b __libc_start_main
Crash keys:
"switch-19" = "--user-data-dir=/home/rio/.config/Uniflash"
"switch-18" = "--enable-crashpad"
"switch-17" = "--shared-files=v8_context_snapshot_data:100"
"switch-16" = "--launch-time-ticks=1124384130"
"switch-15" = "--renderer-client-id=5"
"switch-14" = "--num-raster-threads=1"
"switch-13" = "--lang=en-US"
"switch-12" = "--field-trial-handle=11734278632836316258,15781706659671034314,1"
"switch-11" = "--no-zygote"
"switch-10" = "--no-sandbox"
"switch-9" = "--change-stack-guard-on-fork=enable"
"switch-8" = "--display-capture-permissions-policy-allowed"
"switch-7" = "--extension-process"
"switch-6" = "--nwjs"
"switch-5" = "--nwapp-path=/opt/ti/uniflash_7.1.0"
"switch-4" = "--user-data-dir=/home/rio/.config/Uniflash"
"switch-3" = "--enable-crash-reporter=,"
"switch-2" = "--crashpad-handler-pid=10152"
"switch-1" = "--enable-crashpad"
"num-switches" = "20"
"osarch" = "x86_64"
"pid" = "10194"
"ptype" = "renderer"

[0228/230254.789769:ERROR:file_io_posix.cc(144)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq: No such file or directory (2)
[0228/230254.789858:ERROR:file_io_posix.cc(144)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: No such file or directory (2)
Received signal 6
#0 0x7fa1803ce463 (/opt/ti/uniflash_7.1.0/node-webkit/lib/libnw.so+0x57b5462)
#1 0x7fa180464321 (/opt/ti/uniflash_7.1.0/node-webkit/lib/libnw.so+0x584b320)
#2 0x7fa17abf1dd0 (/lib/x86_64-linux-gnu/libpthread-2.28.so+0x12dcf)
#3 0x7fa1803e1f17 (/opt/ti/uniflash_7.1.0/node-webkit/lib/libnw.so+0x57c8f16)
#4 0x7fa185317ec5 (/opt/ti/uniflash_7.1.0/node-webkit/lib/libnw.so+0xa6feec4)
#5 0x7fa18537e1c2 (/opt/ti/uniflash_7.1.0/node-webkit/lib/libnw.so+0xa7651c1)
#6 0x7fa17ff397f6 (/opt/ti/uniflash_7.1.0/node-webkit/lib/libnw.so+0x53207f5)
#7 0x7fa17ff36f26 (/opt/ti/uniflash_7.1.0/node-webkit/lib/libnw.so+0x531df25)
#8 0x7fa17ff37a9b (/opt/ti/uniflash_7.1.0/node-webkit/lib/libnw.so+0x531ea9a)
#9 0x7fa17cc6f866 ChromeMain
#10 0x7fa17a80109b __libc_start_main
r8: 0000000000000000 r9: 00007ffc17a35ae0 r10: 0000000000000008 r11: 0000000000000246
r12: 00000000000000b6 r13: 00007ffc17a36e00 r14: 00007ffc17a36e10 r15: 00007ffc17a36e18
di: 0000000000000002 si: 00007ffc17a35ae0 bp: 00007ffc17a35d30 bx: 00007ffc17a35d41
dx: 0000000000000000 ax: 0000000000000000 cx: 00007fa17a81e077 sp: 00007ffc17a35ae0
ip: 00007fa17a81e077 efl: 0000000000000246 cgf: 002b000000000033 erf: 0000000000000000
trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace]
[10195:10195:0228/230254.832103:FATAL:nw_content_renderer_hooks.cc(53)] Failed to load node library (error: libatomic.so.1: cannot open shared object file: No such file or directory)
#0 0x7f42fa1d7463 (/opt/ti/uniflash_7.1.0/node-webkit/lib/libnw.so+0x57b5462)
#1 0x7f42fa1eaa8e (/opt/ti/uniflash_7.1.0/node-webkit/lib/libnw.so+0x57c8a8d)
#2 0x7f42ff120ec5 (/opt/ti/uniflash_7.1.0/node-webkit/lib/libnw.so+0xa6feec4)
#3 0x7f42ff1871c2 (/opt/ti/uniflash_7.1.0/node-webkit/lib/libnw.so+0xa7651c1)
#4 0x7f42f9d427f6 (/opt/ti/uniflash_7.1.0/node-webkit/lib/libnw.so+0x53207f5)
#5 0x7f42f9d3ff26 (/opt/ti/uniflash_7.1.0/node-webkit/lib/libnw.so+0x531df25)
#6 0x7f42f9d40a9b (/opt/ti/uniflash_7.1.0/node-webkit/lib/libnw.so+0x531ea9a)
#7 0x7f42f6a78866 ChromeMain
#8 0x7f42f460a09b __libc_start_main
Crash keys:
"switch-19" = "--user-data-dir=/home/rio/.config/Uniflash"
"switch-18" = "--enable-crashpad"
"switch-17" = "--shared-files=v8_context_snapshot_data:100"
"switch-16" = "--launch-time-ticks=1124417890"
"switch-15" = "--renderer-client-id=6"
"switch-14" = "--num-raster-threads=1"
"switch-13" = "--lang=en-US"
"switch-12" = "--field-trial-handle=11734278632836316258,15781706659671034314,1"
"switch-11" = "--no-zygote"
"switch-10" = "--no-sandbox"
"switch-9" = "--change-stack-guard-on-fork=enable"
"switch-8" = "--display-capture-permissions-policy-allowed"
"switch-7" = "--extension-process"
"switch-6" = "--nwjs"
"switch-5" = "--nwapp-path=/opt/ti/uniflash_7.1.0"
"switch-4" = "--user-data-dir=/home/rio/.config/Uniflash"
"switch-3" = "--enable-crash-reporter=,"
"switch-2" = "--crashpad-handler-pid=10152"
"switch-1" = "--enable-crashpad"
"num-switches" = "20"
"osarch" = "x86_64"
"pid" = "10195"
"ptype" = "renderer"

[0228/230254.917153:ERROR:file_io_posix.cc(144)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq: No such file or directory (2)
[0228/230254.919601:ERROR:file_io_posix.cc(144)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: No such file or directory (2)
Received signal 6
#0 0x7f42fa1d7463 (/opt/ti/uniflash_7.1.0/node-webkit/lib/libnw.so+0x57b5462)
#1 0x7f42fa26d321 (/opt/ti/uniflash_7.1.0/node-webkit/lib/libnw.so+0x584b320)
#2 0x7f42f49fadd0 (/lib/x86_64-linux-gnu/libpthread-2.28.so+0x12dcf)
#3 0x7f42fa1eaf17 (/opt/ti/uniflash_7.1.0/node-webkit/lib/libnw.so+0x57c8f16)
#4 0x7f42ff120ec5 (/opt/ti/uniflash_7.1.0/node-webkit/lib/libnw.so+0xa6feec4)
#5 0x7f42ff1871c2 (/opt/ti/uniflash_7.1.0/node-webkit/lib/libnw.so+0xa7651c1)
#6 0x7f42f9d427f6 (/opt/ti/uniflash_7.1.0/node-webkit/lib/libnw.so+0x53207f5)
#7 0x7f42f9d3ff26 (/opt/ti/uniflash_7.1.0/node-webkit/lib/libnw.so+0x531df25)
#8 0x7f42f9d40a9b (/opt/ti/uniflash_7.1.0/node-webkit/lib/libnw.so+0x531ea9a)
#9 0x7f42f6a78866 ChromeMain
#10 0x7f42f460a09b __libc_start_main
r8: 0000000000000000 r9: 00007ffe99941b20 r10: 0000000000000008 r11: 0000000000000246
r12: 00000000000000b6 r13: 00007ffe99942e40 r14: 00007ffe99942e50 r15: 00007ffe99942e58
di: 0000000000000002 si: 00007ffe99941b20 bp: 00007ffe99941d70 bx: 00007ffe99941d81
dx: 0000000000000000 ax: 0000000000000000 cx: 00007f42f4627077 sp: 00007ffe99941b20
ip: 00007f42f4627077 efl: 0000000000000246 cgf: 002b000000000033 erf: 0000000000000000
trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace]
[10146:10172:0228/230259.013383:ERROR:chrome_browser_main_extra_parts_metrics.cc(227)] START: ReportBluetoothAvailability(). If you don't see the END: message, this is crbug.com/1216328.
[10146:10172:0228/230259.013577:ERROR:chrome_browser_main_extra_parts_metrics.cc(230)] END: ReportBluetoothAvailability()
[10183:10189:0228/230356.547030:ERROR:cert_verify_proc_builtin.cc(600)] No net_fetcher for performing AIA chasing.
^C
root@ubuntu:/o

over 3 years ago

0 Ki over 3 years ago

TI__Guru**** 467521 points

Hello,

It looks like some permissions issue.

With what permissions was UniFlash installed with? Can you try running it as sudo?

Thanks

0 Rio Chan over 3 years ago in reply to Ki

TI__Genius 14995 points

Hi Ki:

Yes, I'm doing this for sudo as root always.

BR Rio

0 Errol Kowald over 3 years ago

Intellectual 540 points

I am seeing similar problems with Uniflash 7 on Unbuntu 20.04. I haven't looked at the log, but there is a distinct difference in the file size of uniflash_7.1.0/node-webkit/nw and uniflash_6.1.0/node-webkit/nw. The former is only 224kB , while the latter is 72.5MB. (uniflash_4.5.0/node-webkit/nw is also 72.5MB)

I have all installed in ~/ti

0 Ki over 3 years ago in reply to Errol Kowald

TI__Guru**** 467521 points

Errol - with what permissions did you install UniFlash and what permissions to run?

I can install and run UniFlash 7.1 (with normal (non-sudo) permissions) without issue. I tried with Ubuntu 18 and 20.

0 Errol Kowald over 3 years ago in reply to Ki

Intellectual 540 points

Hello Ki, I installed 7.1.0 with no permissions, same as when I installed 6.1.0

If I run 7.1.0 with ./nw I get the following:-

0 Errol Kowald over 3 years ago in reply to Errol Kowald

Intellectual 540 points

If I run 6.1.0 from a terminal I get

(That's without a MSP-FET connected)

0 Ki over 3 years ago in reply to Errol Kowald

TI__Guru**** 467521 points

Errol,

Errol Kowald said:
If I run 7.1.0 with ./nw I get the following:-

I believe the way UniFlash is launched has changed with UniFlash 7.1.

For UniFlash 7.1, please also pass in the root path to the UniFlash installation folder. Example:

> ./nw ~/ti/uniflash_7.1.0

Let me know if that works

Thanks

0 Errol Kowald over 3 years ago in reply to Ki

Intellectual 540 points

Not so good

errol@Engenia:~$ cd ti/uniflash_7.1.0/node-webkit

errol@Engenia:~/ti/uniflash_7.1.0/node-webkit$ ./nw ~/ti/uniflash_7.1.0

chrome_crashpad_handler: --database is required

Try 'chrome_crashpad_handler --help' for more information.

errol@Engenia:~/ti/uniflash_7.1.0/node-webkit$

0 Ki over 3 years ago in reply to Errol Kowald

TI__Guru**** 467521 points

hmm... that should work.

Can you try launching UniFlash with the desktop shortcut (UniFlash.desktop) in the uniflash folder? May have toc opy to the desktop and change permissions to allow execution.

0 Errol Kowald over 3 years ago in reply to Ki

Intellectual 540 points

copied the "shortcut" to the desktop, checked it was executable, double clicked it and it opened in a text editor!

How do i run it?

0 Ki over 3 years ago in reply to Errol Kowald

TI__Guru**** 467521 points

If you right-click on the desktop icon, there should be an option in the context menu to "Allow Launching".

Since I already selected that for my shortcut, I have an option to "Don't Allow Launching" instead in the same spot:

0 Ricky Lau over 3 years ago in reply to Errol Kowald

TI__Genius 13095 points

Hi Rio and Errol,

We updated the dependency checking in UniFlash 7.2. Can you try installing that version and let me know if it detects that you are missing any dependencies during installation?

https://www.ti.com/tool/download/UNIFLASH/7.2.0

If you are missing any dependencies, can you try installing them and see if you still run into any issues when starting UniFlash after install?

Thanks,

Ricky

Processors

Processors forum

FLASHTOOL: Uniflash Tool V7.1 on ubuntu18.04