• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 2382 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CCS/UNIFLASH: Uniflash 3.4.1 Segmentation Fault on installation Ubuntu 16.04.4 LTS

Gregory Miles
Prodigy 30 points
Part Number: UNIFLASH
Other Parts Discussed in Thread: CCSTUDIO, CC3200

Tool/software: Code Composer Studio

I followed the installation instructions here to install the required dependancies including libgcyrpt11:

http://processors.wiki.ti.com/index.php/Linux_Host_Support_CCSv6#Ubuntu_16.04_64bit

When trying to install uniflash_setup_3.4.1.00012.bin I get the following errors after extraction (both as a super user and as regular user):

Script stderr:

Directory already exists: /tmp/uniflash_cc0488b7-886f-449d-7781-5aa06fb71216
Unpacking files
Unpacking /tmp/uniflash_cc0488b7-886f-449d-7781-5aa06fb71216/ds_jars.zip
Directory already exists: /tmp/uniflash_cc0488b7-886f-449d-7781-5aa06fb71216
Unpacking files
Executing /opt/ti/uniflash_3.4/eclipse/uniflash -application org.eclipse.equinox.p2.director -repository "file://home/****/Uniflash_3.4.1.00012_linux/repo" -installiu com.ti.ccstudio.p2tool.install.feature.group -destination "/opt/ti/uniflash_3.4/eclipse" -nosplash
Script exit code: 139

Script output:

Script stderr:
Segmentation fault (core dumped)

Error running /opt/ti/uniflash_3.4/eclipse/uniflash -application org.eclipse.equinox.p2.director -repository "file://home/****/Uniflash_3.4.1.00012_linux/repo" -installiu com.ti.ccstudio.p2tool.install.feature.group -destination "/opt/ti/uniflash_3.4/eclipse" -nosplash: Segmentation fault (core dumped)
Executing chmod -R 666 "/tmp/bitrock_installer_2831.log"
Script exit code: 0

I am developing with the CC3200 launchpad so I have to use uniflash 3.4.1.

Thanks

  • 0
    TI__Guru**** 171094 points
    Hi,

    You are not the first to report that; I am repairing and updating my 16.04 VM install and will attempt to install 3.4.1 version here.

    I will report back with my findings.

    Regards,
    Rafael
  • 0 in reply to desouza
    TI__Guru**** 171094 points
    Hi,

    I was able to reproduce this issue on my heavily updated Ubuntu 16.04.

    Just to double check compatibility, I installed a brand new Ubuntu 16.04 VM and was able to install everything without a glitch - in this case I did not update any other components of the system but only added the 32-bit libraries (including the fleeting libgcrypt).

    In this case, the issue is located in one of the updated libraries released after this version was out.

    Unfortunately at this time there is no fix for it - Uniflash 3.4.1 is not supported anymore and I will try to get some priority to fix this, but this is highly uncertain.

    Regards,
    Rafael
  • 0 in reply to desouza
    Prodigy 30 points
    If Uniflash 3.4.1 is no longer supported does that also mean that the CC3200 is also no longer supported?
  • 0 in reply to Gregory Miles
    TI__Guru**** 171094 points
    Hi,

    I understand your point - the device is still fully supported by us . One detail to consider is that this particular device was never supported in Linux Operating Systems - its SDK only had a Windows version.

    What I meant by "not supported" is simply that there will be no more improvements made to this version of Uniflash. However, the tool still works fine on the supported operating systems and the issue is only with the installer (I have this version installed in fully updated Ubuntu 16.04 systems).

    A few ideas to help you workaround this situation. You could install this version in a VM or on a spare host and unzip it to your current system - this way you can bypass the installer itself. Another idea is to use it directly from a regular VM or host that is not updated but keep it isolated from the network (as security features will not be installed).

    I will try to keep testing it here and see if the installer problem can be worked around.

    Hope this helps,
    Rafael
  • 0 in reply to desouza
    Prodigy 30 points
    This might be a topic for a separate thread but I do have a parallels VM running with Windows 7 and my Uniflash 3.4.1 stopped working in that also, even with re-installs it does not work.

    By "stopped working" I mean that when I try to open a path dialog window (such as clicking the "Service Pack Programming" button, no new window to select the service pack opens, the button animation happens and nothing happens). Despite multiple re-install attempts this problem persists.

    I can move this topic to a new thread if that is more appropriate and post any relevant logs although I am not sure which logs would be relevant.
  • 0 in reply to Gregory Miles
    TI__Guru**** 171094 points

    Hi,

    One correction: the Uniflash version I have installed on my Ubuntu 16.04 does not work anymore - I suspect this is a consequence of a post-install update as well. (here is a past discussion about the kernel version dance).

    UART ports tend to work well when used with a Virtual Machine - although there is always a chance that delays may cause issues in a time-sensitive operation like flash.

    The error description is certainly tied to the GUI which, tied to the fact your Windows version stopped working even across installs, hint to me that it is possible the installation directory may have corrupt files from a previous install. I suggest you to completely wipe the Uniflash directory (typically under c:\ti\uniflash) by using Shift+Delete and reinstall the tool - you will probably need to restart your VM to use uniflash. 

    If Uniflash is the only TI tool installed in this VM, I would also scan your home user area (C:\users\user\) and delete any directories such as .TI, ti, Texas Instruments, AppData\Local\Texas Instruments and AppData\Local\.TI

    Does this issue happen with other dialogs? If so, perhaps (by a very long shot) you may want to reinstall/repair the MSVC redistributables as mentioned in this thread. 

    Hope this helps,

    Rafael