• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 79 subscribers
  • Views 1120 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

MSP430F5435A: MSP430-GCC-OPENSOURCE 5.1.1.0

Robert Whalley
Prodigy 200 points
Part Number: MSP430F5435A
Other Parts Discussed in Thread: MSP-FET, CODECOMPOSER, UNIFLASH

I am using Linux Mint 18.3 64 bit, and an MSP-FET.

I was using version 5.0.0.25 with the ia32 package installed (to provide 32 bit support).

After upgrading to 5.1.1.0 (64 bit) I noticed the following:

  1. gdb_agent_console was not marked as executable.
  2. After a clean build, and after the MSP-FET had successfully updated its firmware, the following happens when I attempt to load any code via msp430-elf-gdb:

Current directory: /home/arw/workspace/Software/C/IMU9/build/
Command: msp430-elf-gdb -x gdb.cmd /home/arw/workspace/Software/C/IMU9/build/imu9.out
set annotate 1
GNU gdb (SOMNIUM Technologies Limited - msp430-gcc 6.4.0.32) 7.11
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <gnu.org/.../gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "--host=x86_64-redhat-linux --target=msp430-elf".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<www.gnu.org/.../>.
Find the GDB manual and other documentation resources online at:
<www.gnu.org/.../>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /home/arw/workspace/Software/C/IMU9/build/imu9.out...done.
(gdb) load a.out
Loading section .rodata, size 0x1740 lma 0x5c00
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Ignoring packet error, continuing...


The console in which gdb_agent_console is running has this output:

CPU Name             Port
--------             ----
MSP430              :55000

Starting all cores
CPU Name             Status
--------             ------
MSP430               Waiting for client
MSP430               Client connected...Connecting to Target
Found USB FET at ttyACM0
Target connected...Starting server
Unexpected character received waiting for command: -
Unexpected character received waiting for command: -
Unexpected character received waiting for command: -
Unexpected character received waiting for command: -
Unexpected character received waiting for command: -
Unexpected character received waiting for command: -
Received only partial command
Received only partial command
Received only partial command
Received only partial command
Received only partial command
Received only partial command
Received only partial command

I was wondering if anyone else has experienced this sort of behaviour and has any suggestions?

  • 0
    TI__Intellectual 1370 points
    Hi Robert,

    I've contacted our tools team to see if they can replicate the behavior you're seeing. I will provide more details as they become available.

    Thanks,
    Ryan
  • 0
    TI__Prodigy 595 points

    Hi Robert,

    I could verify that the executable flag is not set by the Linux x64 installer. This is going to be fixed in upcoming versions.

    Regarding these packet errors, I cannot reproduce those on Ubuntu 16.04 (64-bit).
    I assume that you are able to download the same .out file with the 5.0.0.25 installer? If so this is quite interesting as the gdb agent version hasn't changed in that release.

    Thanks,
    Bob Heilmaier

  • 0 in reply to Bob Heilmaier
    Prodigy 200 points

    Hi Bob,

    Thanks for your efforts on this.

    I can confirm that I am able to load the same .out file with 5.0.0.25. Not withstanding that the gdb_agent_console might not have changed between that version and 5.1.1.0, clearly the MSP-FET firmware has because a new version is loaded onto it before anything else happens. I am personally suspicious of the libmsp430.so library... that has changed from 32 bits to 64 bits, as far as I can tell. Is there a dependent library incompatibility perhaps?

    I look forwards to your thoughts.

    Rob Whalley

  • 0 in reply to Robert Whalley
    TI__Prodigy 595 points

    Hey Rob,

    I've had a short discussion with a colleague and he proposed you could execute "find / -name "libmsp430.so" 2> /dev/null" and post the output here in the forum.
    This command searches for other libmsp430.so files on the disk.

    One possible explanation is that the old libmsp430.so library is used which won't work with the native 64bit environment.

    Best regards,
    Bob

  • 0 in reply to Bob Heilmaier
    Prodigy 200 points

    Hi Bob,

    That was a good idea and revealed the following:

    ~/ti/gcc/bin/libmsp430.so
    ~ti/ccsv7/ccs_base/DebugServer/drivers/libmsp430.so

    file ~/ti/gcc/bin/libmsp430.so
    ~/ti/gcc/bin/libmsp430.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=184af3c4ba9e919534dc5c6387944b28a188a26f, stripped
    file ~/ti/ccsv7/ccs_base/DebugServer/drivers/libmsp430.so
    ~/ti/ccsv7/ccs_base/DebugServer/drivers/libmsp430.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=ecc1c9dba74c89383c8a57d7595f1beb96a3d12d, stripped

    I've renamed the library under the CodeComposer tree so that, hopefully, the gdb_agent_console won't find it, but the behaviour is exactly the same - unable to load any .out files, and lots of "ignoring packet" errors.

    So, still no joy, I'm afraid.

    Rob

  • 0 in reply to Robert Whalley
    TI__Prodigy 595 points

    Hi Rob,


    I've downloaded Mint 18.3 and ran it in a virtual machine to make sure it's not related to the OS.
    I could not reproduce the error there with neither the 5.1.1.0 release nor with the next upcoming package 5.1.2.0.

    My assumption is that the ia32 package is causing the issue as this is quite the only difference I can think of. At least I was able to us the packages on a clean environment. I'm not quite sure how I can support you from here.
    As I saw in an earlier comment that you have CCS installed, can you use the IDE to do your development and code downloads? In case you look for a smaller application that simply downloads an existing image, you might want to take a look at UniFlash.

    Best regards,
    Bob

  • 0 in reply to Bob Heilmaier
    Prodigy 200 points

    Hi Bob,

    Thank you for your efforts, none the less. The response has been good and whilst I still have a problem, I appreciate the support.

    I'll play around and if I do discover anything I'll maybe post my finding here as well.

    Regards,

    Rob

**Attention** This is a public forum