FLASHTOOL: Uniflash Tool V8.3.0 on ubuntu20.04LTS Will not open after install

Hi Errol,

Which device do you use Uniflash on?

MSP-FET (S/N: 180500788) used for MSP430G2452 & MSP430F2013 with SBW interface

Hi Errol,

I am routing your query to the MSP team for comments.

Thankyou Bin Lou

Out of curiosity I will shortly install UniFlash 8 on another PC which runs Ubuntu 22.04

Well that didn't turn out as I had hoped. the procedure for installing on another PC running Ubuntu 22.04 follows. I used the same UniFlash install file as above.

$ sudo ./uniflash_sl.8.3.0.4307.run

warning window popped up

Failed to locate system libraries required for UniFlash operation:

libusb-0.1.so.4

libgconf-2.so.4

Please install them before proceeding.

Refer to the support wiki for additional help on installing required libraries: software-dl.ti.com/.../uniflash.html

$ sudo ln -sf /lib/x86_64-linux-gnu/libudev.so.1 /lib/x86_64-linux-gnu/libudev.so.0

returned to the prompt without any response. No idea if it installed

cancelled setup and restarted

same warning popped up

cancelled setup & googled install libusb-0.1.so.4 & libgconf-2.so.4

$ sudo apt-get update

$ sudo apt-get -y install libusb-0.1-4

success

$ sudo apt-get -y install libgconf-2-4

success

$ sudo ./uniflash_sl.8.3.0.4307.run

no warnings this time

accept license agreement

install to /opt/ti/uniflash_8.3.0

check "Create Desktop Shortcut" & "Launch UniFlash" then Finish

it runs - no MSP430 connected though, so it cannot detect the device

UniFlash is stuck "LOADING DEVICE LIST"

entering "MSP430G2452" resulted in "No device matching your search is supported by UniFlash"

Opened Settings & "Re-sync Database"

UniFlash downloads lots of files (NB: it would be nice to limit these to only MSP430, since they will be used exclusively)

"Verifying" - success "Restart application to finish"

NB: at this point there is no Desktop Shortcut for UniFlash

clicked "[Click to Close UniFlash]"

Didn't restart

No desktop icon

opened OS "Show Applications"

UniFlash is not there

Tried searching in "Activities" for "UniFlash" but it wasn't found

/opt/ti/iniflash_8.3.0 is there with it's subdirectories and files

$ /opt/ti/uniflash_8.3.0/node-webkit/nw /opt/ti/uniflash_8.3.0

runs UniFlash8 with terminal response:-

libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)

[542735:542735:0711/125316.682914:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization

libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)

[542799:542799:0711/125316.779654:ERROR:sandbox_linux.cc(380)] InitializeSandbox() called with multiple threads in process gpu-process.

[542760:542781:0711/125316.841983:ERROR:command_buffer_proxy_impl.cc(125)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.

[542704:542719:0711/125318.774207:ERROR:chrome_browser_main_extra_parts_metrics.cc(227)] START: ReportBluetoothAvailability(). If you don't see the END: message, this is crbug.com/1216328.

[542704:542719:0711/125318.774232:ERROR:chrome_browser_main_extra_parts_metrics.cc(230)] END: ReportBluetoothAvailability()

[542739:542750:0711/125417.402712:ERROR:cert_verify_proc_builtin.cc(600)] No net_fetcher for performing AIA chasing.

[542739:542750:0711/125417.432618:ERROR:cert_verify_proc_builtin.cc(600)] No net_fetcher for performing AIA chasing.

no database

Opened Settings & "Re-sync Database"

it did

closed UniFlash then re-opened

Database wasn't available

So, it failed, again. Clearly there is something missing on my two Ubuntu machines, but I have no idea what it might be.

Errol,

Thank you for the detail report.

For the first machine (20.04LTS), did you get any missing dependencies during installation?

And if not, can you try running ./nw in your /opt/ti/uniflash_8.3.0/node-webkit/ folder and let me know if NW.js starts? If it starts correctly, you should just see a grey screen with NW.JS on it.

For the second machine (22.04LTS), you should not need to run "Re-sync Database" after install. That being said, I'm not sure why it is getting stuck on the "LOADING DEVICE LIST" step. Do you see this if you reinstall the application again?

Can you also try using the DSLite command line? I want to see if you are only having issues with using the GUI, or is the command line also not working for you. I've attachedMSP430G2452.ccxml you can use as the configuration file used for DSLite.

Thank you,

Ricky

https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/791/MSP430G2452.ccxml

For the first machine (20.04LTS),

It installed with no issues reported to the screen. I didn't look in the log. There were no missing dependencies. Which isn't surprising because UniFlash 6 had been working fine until the UniFlash 8 install wrecked it.

... try running ./nw in your /opt/ti/uniflash_8.3.0/node-webkit/ folder 

/opt/ti/uniflash_8.3.0/node-webkit$ ./nw

[187637:187637:0714/104638.710710:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization

[187663:187663:0714/104638.895510:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization

[187679:187679:0714/104639.133212:ERROR:sandbox_linux.cc(380)] InitializeSandbox() called with multiple threads in process gpu-process.

[187665:187678:0714/104639.377904:ERROR:command_buffer_proxy_impl.cc(125)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.

[187610:187625:0714/104641.900558:ERROR:chrome_browser_main_extra_parts_metrics.cc(227)] START: ReportBluetoothAvailability(). If you don't see the END: message, this is crbug.com/1216328.

[187610:187625:0714/104641.900601:ERROR:chrome_browser_main_extra_parts_metrics.cc(230)] END: ReportBluetoothAvailability()

the grey NW.JS window popped up, so as you say, it started correctly

NW.JS

nw.js v0.60.0
Node v17.3.0
Chromium 97.0.4692.71
commit hash: b3a2fa0-c2dc453-676ece1-256e201

"For the second machine (22.04LTS), you should not need to run "Re-sync Database" after install. That being said, I'm not sure why it is getting stuck on the "LOADING DEVICE LIST" step. Do you see this if you reinstall the application again?"

Uninstall, reinstalled, create desktop icon & run checked.

Had no problems detecting the MSP430F20x3 at first run from the install.

Closed Uniflash

Desktop icon was there (but I'm not the owner)

Right click "Allow Launching"

Launched correctly, identified MSP430F20x3, selected the 2013 manually. Attempt to load MSP430G2452 code (all I had) which it wouldn't do, as expected.

So it works. No idea what changed.

No need to try DSLite, fortunately, because I've never used it before

For the first machine - 20.04 - I tried the same hoping for magic.

Uninstalled UniFlash 8 then re-installed & checked create Icon & run

$ sudo ./uniflash_sl.8.3.0.4307.run

$ [328143:328164:0716/104445.999060: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")

[328143:328164:0716/104445.999139: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")

[328143:328164:0716/104446.035445: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")

[328143:328164:0716/104446.035505: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")

[328169:328169:0716/104446.152942:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization

[328228:328228:0716/104446.313113:ERROR:sandbox_linux.cc(380)] InitializeSandbox() called with multiple threads in process gpu-process.

[328191:328209:0716/104446.318997:ERROR:command_buffer_proxy_impl.cc(125)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.

[328143:328167:0716/104453.120379:ERROR:chrome_browser_main_extra_parts_metrics.cc(227)] START: ReportBluetoothAvailability(). If you don't see the END: message, this is crbug.com/1216328.

[328143:328167:0716/104453.120416:ERROR:chrome_browser_main_extra_parts_metrics.cc(230)] END: ReportBluetoothAvailability()

[328173:328186:0716/104546.190659:ERROR:cert_verify_proc_builtin.cc(600)] No net_fetcher for performing AIA chasing.

[328173:328186:0716/104546.236560:ERROR:cert_verify_proc_builtin.cc(600)] No net_fetcher for performing AIA chasing.

ran fine, but could not detect MSP430F20x3 on MSP-FET (unlike machine 2 running 22.04)

Closed UniFlash

strangely, the terminal didn‘t return to the command prompt. (Was UniFlash still running?)

double click UniFlash desktop icon (launching allowed)

no response

check Software Monitor to find 5 instances of nw still running (one of UniFlash)

killed 5 nw processes

still no response from double clicking UniFlash icon

Software Monitor showed 1 instance of nw running using 0% CPU

So still no success with 20.04, which is a problem, because that's the lab machine where the project can be powered up & tested. (22.04 was tested above using a tiny '2013 board powered by the MSP-FET)

Errol,

I'm glad you were able to get it working on the Ubuntu 22.04 machine.

As for the 20.04 machine, from your description, it seems to always start up correctly after the installation (I'm assuming using the "Launch UniFlash" option at the end of installation), but does not work afterwards (when you try to double click the desktop icon, or running the nw command on terminal).

The main difference I can think of in those 2 cases would be that you are running as sudo during installation.

So, can you try these 2 scenarios?

1. Start UniFlash with sudo via terminal. For example:

> sudo /opt/ti/uniflash_8.3.0/node-webkit/nw /opt/ti/uniflash_8.3.0

2. Try running the UniFlash installer without sudo, and see if you can install and run it.

Thanks,

Ricky

Sorry for the delay Ricky. I didn't see the email notifying your reply.

On 20.04, running as root (sudo) worked. It didn't detect the '20x3 on the first attempt and failed to load code when I manually selected '2013, but on closing that session and starting a new one (not closing UniFlash) it worked. The terminal response:-

$ sudo /opt/ti/uniflash_8.3.0/node-webkit/nw /opt/ti/uniflash_8.3.0
[sudo] password for errol:
[565805:565825:0720/082202.393753: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")
[565805:565825:0720/082202.393858: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")
[565805:565825:0720/082202.537527: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")
[565805:565825:0720/082202.537572: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")
[565831:565831:0720/082202.617207:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization
[565860:565860:0720/082202.799783:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization
[565877:565877:0720/082203.019282:ERROR:sandbox_linux.cc(380)] InitializeSandbox() called with multiple threads in process gpu-process.
[565863:565878:0720/082203.311487:ERROR:command_buffer_proxy_impl.cc(125)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
[565805:565820:0720/082211.364259:ERROR:chrome_browser_main_extra_parts_metrics.cc(227)] START: ReportBluetoothAvailability(). If you don't see the END: message, this is crbug.com/1216328.
[565805:565820:0720/082211.364285:ERROR:chrome_browser_main_extra_parts_metrics.cc(230)] END: ReportBluetoothAvailability()
[565835:565840:0720/082302.777452:ERROR:cert_verify_proc_builtin.cc(600)] No net_fetcher for performing AIA chasing.
[565835:565840:0720/082302.821216:ERROR:cert_verify_proc_builtin.cc(600)] No net_fetcher for performing AIA chasing.
Error creating proxy: Unknown or unsupported transport “disabled” for address “disabled:” (g-io-error-quark, 13)
Error creating proxy: Unknown or unsupported transport “disabled” for address “disabled:” (g-io-error-quark, 13)
Error creating proxy: Unknown or unsupported transport “disabled” for address “disabled:” (g-io-error-quark, 13)
Error creating proxy: Unknown or unsupported transport “disabled” for address “disabled:” (g-io-error-quark, 13)
Error creating proxy: Unknown or unsupported transport “disabled” for address “disabled:” (g-io-error-quark, 13)

(nw:565805): dconf-WARNING **: 08:23:44.027: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

(nw:565805): dconf-WARNING **: 08:23:44.075: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”

 (the last line repeated many times with the following line interspersed 4x every now and then

Error creating proxy: Unknown or unsupported transport “disabled” for address “disabled:” (g-io-error-quark, 13)

So it works as root with lots of error reports. I can use it that way

I had originally installed UniFlash 8 as user on 20.04 & uninstalled when it didn't work, but have just tried again, leaving the root installed copy as is.

/tmp$ ./uniflash_sl.8.3.0.4307.run
chrome_crashpad_handler: --database is required
Try 'chrome_crashpad_handler --help' for more information.

I had selected "Launch UniFlash" option at the end of installation, but it didn't launch. An icon was created, but it does nothing.

(The root install still works though.)

I'm at a loss

Errol,

Based on your observations, it seems root access is required to run UniFlash GUI on your 20.04 machine. I'm not sure why this is needed, as on my machine, I am able to install and run UniFlash without it. And I have not heard any feedback from other customers on this requirement either.

Is running as root on this machine a solution for you, or do you need to get it working without root?

Thanks,

Ricky