Cette page appartient aux archives web de l'EPFL et n'est plus tenue à jour.
This page belongs to EPFL's web archive and is no longer updated.

WASAL

the deployment of nodes without antenna
We deployed nodes with 100 ohmic resistance.
The rooms are shown as below.

BC242,BC249,BC209,BC203
BC260,BC267,BC221,BC229
Posted by Yusuke Moriyama at 13:57
Configuration workstations in WASAL
Here is the standard configuration of WASAL machines
J.
Posted by Jacques Panchard at 13:44
Install gdb for msp430
The gdb is NOT installed by defauzlt with the mspgcc module

After struggling to install it, I found the following page (in german) , which is very useful:
http://www.mikrocontroller.net/articles/MSPGCC
Moving the libHIL.so to /usr/local/lib didn't work. I moved it to /lib instead

I also got the error:
error: msp430: Could not initialize device interface (1)

I created a parallel port:
(as root) mknod /dev/parport0 c 99 0
Posted by Jacques Panchard at 17:16
Comments (2)
PicoTux System Programming : Makefile
The most valuable source of information for programming the PicoTux is probably the provided Makefile in the "build" directory of the "picotux-source" archive included in the vendor's CD.

However, as with most makefiles, it's structure may at first seem obscure and unclear to the user. Furthermore, the output obtained by typing a simple "make" command doesn't provide any clear information on what is actually hapenning.

Therefore, I modified the provided Makefile and humbly suggest that any student/programmer willing to build applications for the PicoTux have a look at it.
Posted by Aristidis Papaioannou at 23:24
PicoTux Initialisation : Timeline
The following time measures are based on the repeated PicoTux initialisations that I carried out. They most probably depend on the specific host and/or target hardware, but they give a valuable estimate of how much time one should wait before starting to believe that "something went wrong"...

t=0 : JP4 is pulled low and the PicoTux is powered up.

+ 15 s. : DHCP request is received. The server replies with a DHCP_REPLY including a valid filename, and the PicoTux immediately starts downloading by tftp.

+ 2 s. : Transmission of the original 811K "system-small.elf" completed.
+ 1.4 s. : Transmission of the original 632K "system-netboot.elf" completed.
+ 3.1 s. : Transmission of the original 1359K "system-xmastree.elf" completed.

At this point, the JP4 jumper is removed, and the flashing starts

+ 200 s. : Flashing completed (regardless of the system image size)

At this point, the PicoTux reboots with the new system installed.

Small :
+ 60 s. : First DHCP request is received. Server replies immediately.
+ 40 s. : Second DHCP request is received. Server replies immediately.

Netboot :
+ 30 s : DHCP request followed by NFS mount call for /tftpboot//

At this point, the PicoTux is ready to use.

N.B : When started without the JP4 pulled low, PicoTux takes about 25 s. to send a DHCP request, instead of 15 s.
Posted by Aristidis Papaioannou at 23:09
How to Install tinyOS on Debian
1) Go to IBM website to get the SDK and Javacom packages

2) Use the Debian packages found at: http://thomer.com/tinyos

3) Download the tinyOS tree from sourceforge (http://sourceforge.net/cvs/group_id=28656)

4) Set the PATH and CLASSPATH variables manually in the tinyos user home directory. Copy the contents of $(TOSDIR)/tools/scripts/tinyos.sh.in in a .profile file of the home directory and add the following line at the end of the .bashrc

if [-f .profile]; then
. .profile
fi

5) Follow the instructions in $(TOSDIR)/contrib/shockfish/README to install the msp430 toolchain

6) copy /tools/java/jni/libgetenv.so to the IBMJava/jre/bin directory
Posted by Jacques Panchard at 16:07
Updated inventory
Here is the updated inventory.
However, if we intend to manage documentation and code, I'm note sure a blog will be the best solution.
CVS is a must, but it not designed for web browsing.
What do you think, Michal?
Jacques
Posted by Jacques Panchard at 10:30
Comments (2)