This document presents the tools used in the context of Contiki development.

Tunslip

Description

Tunslip is a tool from Contiki allowing to create a SLIP tunnel between a “physical” serial port and a “virtual” network interface (tun).

SLIP is a Serial Line Protocol which encapsulates the IP protocol. You can use the tunslip tool in Contiki to create and bind virtual IP interfaces (tun) to the serial port.

This virtual interface will be used like a real network interface: traffic forwarding, Wireshark analysis, etc. While the “tun” interface driver is available out-of-the-box under Linux, it requires the installation of a kernel extension for Mac OS X (see the TunTap project) and is not yet supported officially. Windows also lacks a tun/tap driver by default and we don't support it yet.

See also http://vtun.sourceforge.net/tun/index.html

Compilation

The compilation of tunslip is totally trivial and GCC will be competent:

gcc tunslip.c -o tunslip

Execution

Use the following command, according to your system parameters, to launch tunslip: tunslip -s SerialPort -B BaudRate IPAddress NetMask

Warning: you must be root to run it.

For example, with a WiSMote visible as ttyUSB0:

tunslip -s /dev/ttyUSB0 -B 57600 192.168.1.1 255.255.255.0

Tips

One machine, several Wismote

To use several WiSMote on the same gateway (for example two WiSMote on the two front USB port of a PC), you must specify two different tun interfaces to tunslip.

For example, in a first terminal:

tunslip -s /dev/ttyUSB0 -t tun0 -B 57600 192.168.1.1 255.255.255.0

In a second terminal:

tunslip -s /dev/ttyUSB1 -t tun1 -B 57600 192.168.1.1 255.255.255.0

Wireshark

Wireshark is a network protocol analyzer for Unix and Windows. Many features are available. For more informations, consult their website.


Wireshark screenshot

Msp430-GCC

Description

MSP430GCC is a GCC toolchain for the Texas Instruments MSP430 family of ultra low power MCUs.

This includes the compiler gcc, the assembler and linker (binutils), the debugger (GDB), and some other tools needed to make a complete development environment for the MSP430. It supports all the current variants of the MSP430 processor, and comes with a full set of header files for the processors, and a basic ’libc’ library (see MSP430 GCC Manual).

Install

Download msp430gcc on their website, or simply:

git clone git://mspgcc4.git.sourceforge.net/gitroot/mspgcc4/mspgcc4

  • Run with perl the script named « buildgcc.pl ».
  • Steps during the build process:
    • Select the latest GCC compiler (today [march 30, 2011], it’s the first option “gcc-4.4.5”).
    • Select the latest GDB (today [march 30, 2011], it’s the first option “GDB-7.2”).
    • Insight is a GDB GUI not useful in our case. For developers not familiar with the GDB command-line, Eclipse can be used.
    • Select the latest TI Libc (today [march 30, 2011], it’s the first option “ti_20110213”). The version names follow the pattern TI_yyyymmdd.
    • Next steps permit to :
      • Strip executables
      • Specify the future toolchain path
      • Create a zip of the produced files
  • Don’t forget to include it in your PATH (and in your shell startup script) and maybe, your MAN-PATH.

Documentation

You can view the documentation on this website.

MSPDebug

Description

MSPDebug is a command-line tool designed for debugging and programming the MSP430 family of MCUs.

It supports the eZ430-F2013, eZ430-RF2500, FET430UIF and Olimex MSP-JTAG-TINY programming tools, as well as a simulation mode. When started with appropriate options, MSPDebug will attempt to connect to the debugging tool specified and identify the device under test.

Once connected, the user is presented with a command prompt which can be used to reflash the device memory, inspect memory and registers, set registers, and control the CPU (single step, run and run to breakpoint).

It can be used as a proxy for gdb or as an independent debugger with support for programming, disassembly and reverse engineering. It is possible to configure and use MSPDebug with Eclipse.

Links

Execution

For an Olimex MSP-JTAG-TINY, the following command can be used to flash and run a device:

mspdebug olimex -j “prog file.wismote” “run”

Warning: currently MSPDebug support only MSP-JTAG-TINY v1. For a MSP-JTAG-TINY v2, use the official software for Windows.

Eclipse

Eclipse is a multi-language software development environment comprising an integrated development environment (IDE) and an extensible plug-in system.

It is written mostly in Java and can be used to develop applications in Java and, by means of various plug-ins, other programming languages including Ada, C, C++, COBOL, Perl, PHP, Python, Ruby (including Ruby on Rails framework), Scala, Clojure, and Scheme.

Eclipse is free and open source software.

For more information, consult their website.


MSPDebug: flash process

 
development/tools.txt · Last modified: 2012/05/07 09:28 (external edit)
 
Except where otherwise noted, content on this wiki is licensed under the following license:CC Attribution-Noncommercial-Share Alike 3.0 Unported
Recent changes RSS feed Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki