TinyOSmsp430Toolchainmspgcc upgrade in Ubuntu

At present, TinyOS2.1.1, which is released on the official website of TinyOS, supports the mspgcc or earlier version 3.2.3. It is not supported for the TI430 series high-end single-chip microcomputer and only supports low-end series such as megax1611. To port TinyOS to a higher-end microcontroller, such as msp430f2618, you must upgrade the MSPToolchain. The latest version of mspgcc4 has been updated on Sourceforge. This version fully supports the entire TI430 series, the latest

Currently, TinyOS2.1.1, which is released on the official website of TinyOS, supports the mspgcc or earlier version 3.2.3. It is not supported by TI 430 series high-end single-chip microcomputer and only supports low-end series such as megax1611. To port TinyOS to a higher-end microcontroller, such as msp430f2618, you must upgrade the MSP Toolchain.

The latest version of mspgcc4 has been updated on Sourceforge. This version fully supports the full series of TI 430, the latest version of GCC is 4.4.3, the current version of GDB is 7.0.1, and the latest version of Insight is 6.8-1. For more performance improvements, see http://mspgcc4.sourceforge.net.

First, install necessary software packages, which can be obtained using debian's apt-get command. The related commands are as follows:

In this way, you can install related software packages.

Sudo apt-get install subversion gcc-4.4 texinfo patch libncurses5-dev zlibc zlib1g-dev libx11-dev libusb-dev libreadline6-dev

Next, download mspgcc4 from Sourceforge. Here I use SVN

Svn checkout https://mspgcc4.svn.sourceforge.net/svnroot/mspgcc4 mspgcc4

After the download, you can start the installation. It is very simple. If you add a series of keys in one sentence, you will be OK.

Cd mspgcc4 & sudo./buildgcc. sh

You can use the default values for all the options prompted during installation. Select "Create binary package after build ?" And other compressed packages. This option can be selected as needed. I chose n.

Finally, configure its path

Echo 'export PATH = "$ {PATH}:/opt/msp430-gcc/bin/" '> ~ /. Bashrc

For ease of use, write a shell script to implement one-step installation.

1 .#! /Bin/bash
2.
3. echo "--> Install packages <--"
4. sudo apt-get install git subversion gcc-4.4 texinfo patch libncurses5-dev zlibc zlib1g-dev libx11-dev libusb-dev libreadline6-dev
5.
6. cd $ HOME/
7.
8. echo "--> Download mspgcc <--"
9.
10. git clone git: // mspgcc4.git.sourceforge.net/gitroot/mspgcc4/mspgcc4
11. cd mspgcc4
12.
13. echo "--> Build mspgcc <--"
14.
15 ../buildgcc. sh < 16. 1
17. 1
18. 1
19. 2
20. n
21.
22. n
23. y
24. EOF
25.
26. export PATH = $ PATH:/opt/msp430-gcc-4.4.5/bin;

After completing the above steps to achieve the perfect mspgcc upgrade, our Tinyos has not been updated so far. Next we will gradually implement the transformation of TinyOS.

Although mspgcc can support most of the MSP430 Series single-chip microcomputer, but TinyOS's own mspgcc is not synchronized yet, so we need to link the latest TOOLCHAIN to TinyOS. If you select the default installation path when installing TinyOS, you can follow the steps below. Otherwise, modify the installation path according to your own installation directory.

We can view the path of the msp430-gcc tool in the terminal through the command $ which msp430-gcc, my display is/usr/bin/msp430-gcc, so we can do it, by creating a soft connection to replace this msp430-gcc, the corresponding command can be entered $ ln-s/(your mspgcc4 installation directory, if you are a default installation, it must be/opt/msp430-gcc-4.4.3) /bin/msp430-gcc/usr/bin it is best to delete the old version under usr/bin before executing this command. The creation of other soft connection tools can follow suit, and finally replace the msp430 folder under/usr with the msp430 folder under the/opt/msp430-gcc-4.4.3.

After all the data is created, we can test whether TinyOS can run normally and modify the data in the epic platform. in the platform file, change-mmcu = javasx1611 to-mmcu = javasx2618 (this old version is not supported), and change the following version information "version_major/minor" to the corresponding version number, change version = msp430-4.4.3. Well, let's look for an example in the app (it's best to use the simplest Blink, because the definitions of different CPUs are also different, now TinyOS can recognize new MCU, and no longer prompts mcu xxx not supported, and then a long string of damn low-end processors.