• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 53 subscribers
  • Views 691 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.

Uniflash Redhat compatibility

Bradley Nilsen
Prodigy 30 points
Other Parts Discussed in Thread: MSP430F1611, UNIFLASH, MSP-FET

Hi,

My company generally uses Redhat as our OS of choice, and we are trying to get a new machine setup for flashing our MSP430F1611 board using a MSP430-FET.  Our current OS installed is Redhat Linux 2.6.32-358.el6.i686.   Originally we used the old parallel port flashing device, but this did not work on the new machine. So we got the new FET, and technical support guided us to using CCS or uniflash (uniflash in our case as we only need to flash our device).  

Our problem is that our glibc libraries are not comptabile for the current uniflash, but we are unsure which Redhat version to move to, to get compatibility.   Do ya'll happen to know which Redhat version will be recent enough to work?  We did see that on the wiki for CCS 5, Redhat 6 is listed as one of the testing suites, so that gave us some hope that we may be able to find a compatible version to get the current Uniflash working.

Thanks,

Brad Nilsen

  • 0
    TI__Genius 16490 points

    Brad,

    Based only on scanning the installation folder, here is the info I can provide...

    A full install of the latest v3.3 of uniflash has a dependency on v2.15 of glibc.  According to this, you would need RHEL7.1.  However, if you select only MSP430 at installation time, the glibc dependency drops to v2.9 which would imply RHEL-6.6.  Since you are using kernel 2.6.32, you are probably using RHEL6.6 already.

    When you installed uniflash, did you select all devices or only MSP430?

    Note that my scan of the installation folder may not be 100% foolproof, so some testing would need to be done to confirm these versions.

  • 0 in reply to AndyW
    Prodigy 30 points
    Hi Andy,

    Thanks for the info. So we were running RHEL 6.4 and went ahead and upgraded to 6.6. We also installed uniflash 3.3. We are getting an error when we try to start

    java.lang.UnsatisfiedLinkError: /opt/ti/uniflash_3.3/ccs_base/DebugServer/bin/libti_xpcom.so: /usr/lib/libstdc++.so.6: version `CXXABI_1.3.5' not found (required by /opt/ti/uniflash_3.3/ccs_base/DebugServer/bin/libti_xpcom.so)

    Our libstdc++.so.6 with the RHEL 6.6 build goes up to 1.3.3, but we found the libstdc++.so.6 library in the ccs_base/common/install and linked to that, which seems to remove the error. However, now our machine is locking up (as in completely dead, no ssh, keyboard, mouse) whenever the MSP-FET is plugged in. Should we not have linked to the library in the ccs_base path?

    Thanks,
    Brad
  • 0 in reply to Bradley Nilsen
    TI__Genius 16490 points

    Brad,

    Could you clarify what you mean when you say you linked to the libstdc++ library in the Uniflash install folder?

    Uniflash should be using the the libstdc++ in in the uniflash install folder instead of the system folder. I'm not sure why it is loading the system version.

    I'm not sure if this will cause other problems and would likely only be a temporary workaround, but you might also be able to add an LD_PRELOAD for libstdc++ to force uniflash to load the intended version.

    If you undo the link you referred to, does the hanging problem still persist?

  • 0 in reply to AndyW
    Prodigy 30 points
    So, I have some progress although somewhat backwards. The lib it was linking to was /usr/lib/libstdc++.so.6. If we don't link to the uniflash/ccs_base/common/install libstdc++ it just doesn't start up and gives the same error as above:

    java.lang.UnsatisfiedLinkError: /opt/ti/uniflash_3.3/ccs_base/DebugServer/bin/libti_xpcom.so: /usr/lib/libstdc++.so.6: version `CXXABI_1.3.5' not found (required by /opt/ti/uniflash_3.3/ccs_base/DebugServer/bin/libti_xpcom.so)

    What we did do though, and it may be the wrong thing to do, is we reverted to the uniflash 3.1. We get the same linking error which we fix, but suprprisingly it is not crashing now when we hook up the MSP430-FET. We are getting an update firmware message which we ignore (for the moment) and it appears to recognize the device and says it is flashing our board. We are going to try an example to see for sure just with a blinking light. Is there any problems you might foresee with us using this older version?

    Brad
  • 0 in reply to Bradley Nilsen
    TI__Genius 16490 points
    I don't see any issue with using the older Uniflash if it has support for the part you are using.