[Mspgcc-users] New MSP430 stand-alone GCC version release available!

[Mitnacht, Thomas]

Hello GCC-enthusiasts,
We just posted a new stand-alone & open source release (v3.02.02.00) on the external web!

This release is the stand-alone equivalent to the MSP430 GCC support in CCSv6 App Center and includes all binaries, the source code and MSP430 device specific support files.
What's new in this release?

• Large memory support in GCC (linker files update)

• Fixed loading of program into GDB with function in high memory.

• Latest MSP430 device support (MSP430FR69xx, MSP430FR68xx, MSP430FR59xx, MSP430FR58xx, RF430FRL15xH)

• Several bug fixes (see release notes<http://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/MSPGCC/3_02_02_00/index_FDS.html>)

How to get it?

• Update your CCS v6.x installation (Help -> Search for updates) to the latest version and visit the CCS App Center under (Help -> Getting Started)
Basic migration advice and links to GCC documentation is provided in the CCSv6 for MSP430 user’s guide<http://www.ti.com/lit/pdf/slau157>

• Use the Stand-alone & Open Source downloads from the GCC tools folder<http://www.ti.com/tool/msp430-gcc-opensource>

Thanks,
Thomas Mitnacht
________________________________
MSP430 Development Tools Manager • Ultra-Low Power MCUs
Texas Instruments • Freising • [phone]



Texas Instruments Deutschland GmbH, Haggertystr. 1, D-85356 Freising. Amtsgericht MÌnchen HRB 40960. GeschÀftsfÌhrer: Dr. Wolfram Tietscher. Vorsitzender des Aufsichtsrates: Andreas Schwaiger

[Peter Bigot]

Thanks Thomas.

https://github.com/pabigot/msp430-elf has been updated with these
releases. I'm not sure why the version jumped from 2.01.01.00 to
3.02.02.00 since the GCC version apparently didn't change but we'll run
with it.

In the gcc_rh branch the only change I made was to remove the execute bits
from the header files and move the contents back to the include directory
from the msp430-gcc-support-files directory they're now in. Note that the
TI versions now use Unix line endings, so to identify content differences
from old versions you need to add -b or -w to the diff command.

In the sources branch the only change was to move the tools directory up
one level, and to remove some .gitignore files that were preventing the
archive from containing certain derived files.

There are changes in the TI sources that appear to need to be backported to
upstream (e.g. the support for longer C++ template names); somebody might
need to file an upstream bug report to get that to happen. There are also
a variety of issues reported on gcc bugzilla and E2E in both the headers
and toolchain that are still outstanding including (by inspection) the
hardware multiplier issues.

FYI: The best information I've collected on how to report bugs in the
toolchain is in the README displayed at:
https://github.com/pabigot/msp430-elf

Thomas, I for one very much appreciate both the new releases and the fact
you're announcing them here.

Peter

Post by Mitnacht, Thomas
Hello GCC-enthusiasts,
We just posted a new stand-alone & open source release (v3.02.02.00) on the external web!
This release is the stand-alone equivalent to the MSP430 GCC support in
CCSv6 App Center and includes all binaries, the source code and MSP430
device specific support files.
What's new in this release?
• Large memory support in GCC (linker files update)
• Fixed loading of program into GDB with function in high memory.
• Latest MSP430 device support (MSP430FR69xx, MSP430FR68xx,
MSP430FR59xx, MSP430FR58xx, RF430FRL15xH)
• Several bug fixes (see release notes<
http://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/MSPGCC/3_02_02_00/index_FDS.html

)

How to get it?
• Update your CCS v6.x installation (Help -> Search for updates)
to the latest version and visit the CCS App Center under (Help -> Getting
Started)
Basic migration advice and links to GCC documentation is provided in the
CCSv6 for MSP430 user’s guide<http://www.ti.com/lit/pdf/slau157>
• Use the Stand-alone & Open Source downloads from the GCC tools
folder<http://www.ti.com/tool/msp430-gcc-opensource>
Thanks,
Thomas Mitnacht
________________________________
MSP430 Development Tools Manager • Ultra-Low Power MCUs
Texas Instruments • Freising • [phone]
Texas Instruments Deutschland GmbH, Haggertystr. 1, D-85356 Freising.
Amtsgericht MÌnchen HRB 40960. GeschÀftsfÌhrer: Dr. Wolfram Tietscher.
Vorsitzender des Aufsichtsrates: Andreas Schwaiger
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
Mspgcc-users mailing list
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

[Paul Sokolovsky]

Hello Peter,

On Thu, 27 Nov 2014 06:23:40 -0600

Post by Peter Bigot
Thanks Thomas.
https://github.com/pabigot/msp430-elf has been updated with these
releases.

Thanks, I kinda missed that you maintain such repo, and star count on
github shows that many more people might miss it, so thanks for regular
announcements of it here.

Post by Peter Bigot
I'm not sure why the version jumped from 2.01.01.00 to
3.02.02.00 since the GCC version apparently didn't change but we'll
run with it.
In the gcc_rh branch the only change I made was to remove the execute
bits from the header files and move the contents back to the include
directory from the msp430-gcc-support-files directory they're now
in. Note that the TI versions now use Unix line endings, so to
identify content differences from old versions you need to add -b or
-w to the diff command.

Ah, too bad they were not dos2unix'ed before the import!


And here's something I wanted to ask for a while - did you or somebody
else considered adding msp430 toolchain to http://crosstool-ng.org/ ?

[Peter Bigot]

Post by Paul Sokolovsky
Hello Peter,
On Thu, 27 Nov 2014 06:23:40 -0600

Post by Peter Bigot
In the gcc_rh branch the only change I made was to remove the execute
bits from the header files and move the contents back to the include
directory from the msp430-gcc-support-files directory they're now
in. Note that the TI versions now use Unix line endings, so to
identify content differences from old versions you need to add -b or
-w to the diff command.

Ah, too bad they were not dos2unix'ed before the import!

My intent is that these be archival; I'll muck with metadata like execute
bits and the containing directory name in an attempt to maintain
consistency across releases, but I won't change the content of individual
files.

Post by Paul Sokolovsky
And here's something I wanted to ask for a while - did you or somebody
else considered adding msp430 toolchain to http://crosstool-ng.org/ ?

Nope. I'm not interested in more things to maintain; my solution for
msp430elf toolchain building is described here:
http://pabigot.github.io/bsp430/msp430elf.html

That page includes a link to the most recent version of my build script
posted here some months ago. If somebody wants to use that as a basis for
other work, feel free. I don't think it's got enough creativity to warrant
a copyright and in any case it'd fall under the BSD-3-Clause licensing of
BSP430.

Peter

[Ghannouchi, Youssef]

Hello GCC-enthusiasts,

We are pleased to announce a new stand-alone & open source release (v3.02.03.00) on the external web!
This release is the stand-alone equivalent to the MSP430 GCC support in CCSv6 App Center and includes all binaries, the source code and MSP430 device specific support files.


· What's new in this release?

o Key Changes to GCC:

§ Fixed initialization of .data section

§ Fixed detection of hardware multiply (for MSP430FR5739).

o Key Changes to Header & Support Files:

§ Update linker scripts to fix initialization of .data section in large memory devices.

§ Change asm to __asm__ in iomacros.h (for C99 compatibility).

o Please refer to the release notes<http://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/MSPGCC/3_02_03_00/index_FDS.html> for more details.


· How to get it?

o Use the Stand-alone & Open Source downloads from the GCC tools folder<http://www.ti.com/tool/msp430-gcc-opensource>

o Update through CCS v6.x installation will be available in the coming days. Please note that updating GCC compiler will also automatically update the GCC MSP430 device specific support files.

§ Update your CCS v6.x installation (Help -> Search for updates) to the latest version and visit the CCS App Center under (Help -> Getting Started)
Basic migration advice and links to GCC documentation is provided in the CCSv6 for MSP430 user's guide<http://www.ti.com/lit/pdf/slau157>


Best regards,
Youssef Ghannouchi

________________________________
Youssef Ghannouchi
Product Manager - Texas Instruments Inc.

[Lev Serebryakov]

On 23/02/2015 17:15, Ghannouchi, Youssef wrote:

Are here any instructions to build this from sources? I have problems
from very beginning with this so named "release" (I didn't seen
releases worse, to be honest):

(1) Sources could not be downloaded automatically. You need browser.
What should distributive build cluster do?

(2) Sources tarball doesn't contains any version indication in its name

(3) There are no instructions at all!

./configure --prefix=/usr/local --target=mdp430 && gmake all

fails in early stages with different problems, looks like it is very
Linux-specific (stock binutils/gcc could be build virtually anywhere!)

I want to update FreeBSD port/package for ancient msp430gcc, but it
looks impossible :-(

Post by Mitnacht, Thomas
Hello GCC-enthusiasts,
We are pleased to announce a new stand-alone & open source release
(v3.02.03.00) on the external web! This release is the stand-alone
equivalent to the MSP430 GCC support in CCSv6 App Center and
includes all binaries, the source code and MSP430 device specific
support files.
· What's new in this release?
§ Fixed initialization of .data section
§ Fixed detection of hardware multiply (for MSP430FR5739).
§ Update linker scripts to fix initialization of .data section in large memory devices.
§ Change asm to __asm__ in iomacros.h (for C99 compatibility).
o Please refer to the release
notes<http://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/MSP

GCC/3_02_03_00/index_FDS.html>

Post by Mitnacht, Thomas
for more details.
· How to get it?
o Use the Stand-alone & Open Source downloads from the GCC tools
folder<http://www.ti.com/tool/msp430-gcc-opensource>
o Update through CCS v6.x installation will be available in the
coming days. Please note that updating GCC compiler will also
automatically update the GCC MSP430 device specific support files.
§ Update your CCS v6.x installation (Help -> Search for updates)
to the latest version and visit the CCS App Center under (Help ->
Getting Started) Basic migration advice and links to GCC
documentation is provided in the CCSv6 for MSP430 user's
guide<http://www.ti.com/lit/pdf/slau157>
Best regards, Youssef Ghannouchi
________________________________ Youssef Ghannouchi Product Manager
- Texas Instruments Inc.
----------------------------------------------------------------------

- --------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server

Post by Mitnacht, Thomas
from Actuate! Instantly Supercharge Your Business Reports and
Dashboards with Interactivity, Sharing, Native Excel Exports, App
Integration & more Get technology previously reserved for
billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.

clktrk

Post by Mitnacht, Thomas
_______________________________________________ Mspgcc-users
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

- --
Black Lion AKA Lev Serebryakov

[Peter Bigot]

I'm unaware of instructions for building from the TI/RedHat forked source,
but the upstream GNU packages are mature.
http://pabigot.github.io/bsp430/msp430elf.html has details on building the
toolchain from them.

Peter

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Are here any instructions to build this from sources? I have problems
from very beginning with this so named "release" (I didn't seen
(1) Sources could not be downloaded automatically. You need browser.
What should distributive build cluster do?
(2) Sources tarball doesn't contains any version indication in its name
(3) There are no instructions at all!
./configure --prefix=/usr/local --target=mdp430 && gmake all
fails in early stages with different problems, looks like it is very
Linux-specific (stock binutils/gcc could be build virtually anywhere!)
I want to update FreeBSD port/package for ancient msp430gcc, but it
looks impossible :-(

Post by Mitnacht, Thomas
Hello GCC-enthusiasts,
We are pleased to announce a new stand-alone & open source release
(v3.02.03.00) on the external web! This release is the stand-alone
equivalent to the MSP430 GCC support in CCSv6 App Center and
includes all binaries, the source code and MSP430 device specific
support files.
· What's new in this release?
§ Fixed initialization of .data section
§ Fixed detection of hardware multiply (for MSP430FR5739).
§ Update linker scripts to fix initialization of .data section in
large memory devices.
§ Change asm to __asm__ in iomacros.h (for C99 compatibility).
o Please refer to the release
notes<http://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/MSP

GCC/3_02_03_00/index_FDS.html>

Post by Mitnacht, Thomas
for more details.
· How to get it?
o Use the Stand-alone & Open Source downloads from the GCC tools
folder<http://www.ti.com/tool/msp430-gcc-opensource>
o Update through CCS v6.x installation will be available in the
coming days. Please note that updating GCC compiler will also
automatically update the GCC MSP430 device specific support files.
§ Update your CCS v6.x installation (Help -> Search for updates)
to the latest version and visit the CCS App Center under (Help ->
Getting Started) Basic migration advice and links to GCC
documentation is provided in the CCSv6 for MSP430 user's
guide<http://www.ti.com/lit/pdf/slau157>
Best regards, Youssef Ghannouchi
________________________________ Youssef Ghannouchi Product Manager
- Texas Instruments Inc.
----------------------------------------------------------------------

- --------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server

Post by Mitnacht, Thomas
from Actuate! Instantly Supercharge Your Business Reports and
Dashboards with Interactivity, Sharing, Native Excel Exports, App
Integration & more Get technology previously reserved for
billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.

clktrk

Post by Mitnacht, Thomas
_______________________________________________ Mspgcc-users
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

- --
Black Lion AKA Lev Serebryakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQJ8BAEBCgBmBQJVKaZFXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGOTZEMUNBMEI1RjQzMThCNjc0QjMzMEFF
QUIwM0M1OEJGREM0NzhGAAoJEOqwPFi/3EePx9gP/jtMTR4YpltOLGrxgJHXYLNs
T18+R8XOLjOMIFAIn8HeHH2IBgTfCNz/Y/6WmUbzyHSdmiDwqiVQnaF3fqjgYluM
+9mt5qIHcdWFRm8CnDmfL0K+fTJTlGN4ei4zrRftldxAYy8KGmINJciuxesJCy2R
6WLHCir5xmGW1079RH0nQ8Mh/Z8BxxVsCDE6rWe3/0EBPGhCHilf6VEnWHN1Em/b
+zMzRcl7nzVWx6ppLQBE0ffbR4u/eVmnFEBVOmoAk1lSWGurFg3YnVWXel+dJ5Pt
Z3XTVWRsMFx3yxIyk3nAsccrtwD2Pmog8Qqex6nNr8pMLNL+IBhJsqUsegbGRT6l
h07RMUZONs7nO7Juow8MWPwaJX71azZE7BSQ/DpdMKpuQetumlQ6h0nEehcT+YoX
IxcUdO2ywTwGkqMMmB3cP041KmBY+/E5jAsnlkdQFCva5JRCX6cpm3RDglDu0a9H
ZSCBPgX92pzDkesHpi43jl0kB4KH7vEXuNpvncpkooWzAxI1/6nEg0vOAYkDcxyL
mcI2Ju8bL6sCHTSZ42cJkRo/RyLIsPUB0iCCk2DiOtxoTs+K4o1h4RhdX5R0vTFC
n0Y2Kt0yAExeJ76xcNBnOrya5ByqU2jJh40jpKJHLLFBKe7C4V93BbLAu0mpZ/ee
SDlfYq0NDziDA1hsuL9a
=UuS8
-----END PGP SIGNATURE-----
------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live
exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-
event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
Mspgcc-users mailing list
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

[Lev Serebryakov]

On 12.04.2015 04:41, Peter Bigot wrote:

Thank you, Peter (and for all your effort in the past, too!)

Post by Peter Bigot
I'm unaware of instructions for building from the TI/RedHat forked
source, but the upstream GNU packages are mature.
http://pabigot.github.io/bsp430/msp430elf.html has details on
building the toolchain from them.

- --
// Black Lion AKA Lev Serebryakov

[DJ Delorie]

Post by Lev Serebryakov
(1) Sources could not be downloaded automatically. You need browser.
What should distributive build cluster do?

There's nothing magic about downloading the sources, just use any
command-line URL tool (wget, curl, etc):

wget http://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/MSPGCC/latest/exports/msp430-gcc-source.tar.bz2

Post by Lev Serebryakov
(3) There are no instructions at all!
./configure --prefix=/usr/local --target=mdp430 && gmake all

I use ./configure --prefix=... --target=msp430-elf --enable-languages=c,c++ && make && make install

If you're building the upstream sources, it's a bit trickier because
they're separate packages, but as long as you use --target=msp430-elf
any of the "how to build a cross compiler" instructions should suffice.

Post by Lev Serebryakov
fails in early stages with different problems, looks like it is very
Linux-specific (stock binutils/gcc could be build virtually anywhere!)

It shouldn't be Linux specific. We build it for Linux (native) and
MinGW (cross). If you include the specific error messages perhaps we
could suggest solutions...

Note that - in general - cross builds tend to have stricter
requirements about available tools than native builds. For example, a
cross gcc build is allowed to require that the native compiler is g++,
whereas a native gcc build has to allow pretty much any C++ compiler.

(Also note that *I* don't like unneeded restrictions, and other
compilers should work fine as long as they're mostly compatible :)

[Lev Serebryakov]

On 16.04.2015 19:17, DJ Delorie wrote:

Sorry for huge delay in conversation :)

Post by DJ Delorie
wget
http://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/MSPGCC/la

test/exports/msp430-gcc-source.tar.bz2
File at this URL is not stable. It will be chaneged with next
release. It is bad for any packaging system.

Previous releases are at URLs like
http://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/MSPGCC/3_02
_03_00/exports/msp430-gcc-source.tar.bz2,
but current version doesn't have such UNIQUE URL.

(http://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/MSPGCC/3_0
2_04_00/exports/msp430-gcc-source.tar.bz2
is not found).

Is it possible to add version into FILE NAME and has STABLE URLs for
each file, which will work from release date till "forever" for future
releases, please?

Post by DJ Delorie

Post by Lev Serebryakov
(3) There are no instructions at all!
./configure --prefix=/usr/local --target=mdp430 && gmake all

I use ./configure --prefix=... --target=msp430-elf
--enable-languages=c,c++ && make && make install
If you're building the upstream sources, it's a bit trickier
because they're separate packages, but as long as you use
--target=msp430-elf any of the "how to build a cross compiler"
instructions should suffice.

I'm trying to build release 3_02_04_00 (latest one).

I have such packages installed:

autoconf-2.69
automake-1.15
bash-4.3.33
bison-2.7.1
cloog-0.18.3
expat-2.1.0
gettext-0.19.4
gettext-runtime-0.19.4
gettext-tools-0.19.4
gmake-4.1
gmp-5.1.3
isl-0.14.1
m4-1.4.17
mpc-1.0.3
mpfr-3.1.2
python27-2.7.9

My "configure" (top-level) command line is:

./configure --target=msp430-elf \
--with-gmp=/usr/local \
--with-mpfr=/usr/local \
--with-mpc=/usr/local \
--with-isl=/usr/local \
--disable-isl-version-check \
--with-cloog=/usr/local \
--enable-languages=c,c++ \
--disable-nls \
--prefix=/usr/local/gcc-msp430-ti-toolchain-3.03.04.0

It works (output attached as configure.out).

After that "gmake all" gives error:

updating cache .././config.cache
configure: creating ./config.status
config.status: creating Makefile
config.status: creating dltest/Makefile
config.status: creating tclConfig.sh
gmake[2]: Leaving directory
'/usr/home/lev/FreeBSD/ports/devel/gcc-msp430-ti-toolchain/work/sources/
tools'
Makefile:860: recipe for target 'all' failed
gmake[1]: *** [all] Error 2
gmake[1]: Leaving directory
'/usr/home/lev/FreeBSD/ports/devel/gcc-msp430-ti-toolchain/work/sources/
tools'

Full output is attached as "gmake.out".

I could easily build gcc-arm-embedded on this system with these
packages installed, for example.

- --
// Black Lion AKA Lev Serebryakov