[Tinyos-help] Command line help
Hello I wanted to ask about displaying data on a command line in tinyOS I'm having trouble understand the commands involved in showing readings on the command line. Also is there a way of doing it in the program rather than using the MOTECOM listen tool on the command line which is what you need to do on the oscilliscope program. I also wanted to ask if its possible for data retrived to be written to a txt or doc file. Any help would be greatly appreciated. Chris Gungaloo Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Modifying the AMtype field of serial AMPackets
Thanks, Omprakash - that was what I was looking for. Another few lines
fixed the missing group ID:
task uartSendTask() {
[...init variables...]
am_group_t group;
[...read RadioAMPacket fields...]
group = call RadioAMPacket.group(msg);
[...write UartAMPacket source address...]
call UartAMPacket.setGroup(msg, group);
[...call UartSend...]
Problem solved. Thanks.
Andreas
On 21/01/2008, at 13:44, Omprakash Gnawali wrote:
I committed a change to the BaseStation that makes it copy the source
field from the radio to the serial packet. Is that what you wanted?
- om_p
On Jan 21, 2008 2:33 AM, Andreas Reinhardt
[EMAIL PROTECTED] wrote:
When I run BaseStation on telosB motes, it outputs a blank group
field
and a sender address equal to the byte swapped version of the
destination address value. However, I might try and see whether I can
combine the benefits of both.
Andreas
On 21/01/2008, at 10:05, Kevin Klues wrote:
Is there some limitation in the already existing tinyos-2.x/apps/
BaseStation ?
Kevin
On Jan 20, 2008 11:59 PM, Andreas Reinhardt
[EMAIL PROTECTED] wrote:
I was considering implementing a transparent gateway mote that
would
simply forward all packets received on the radio to the USB port.
Like
a T2 version of TOSbase. As I want to maintain the serial packet
format, instead of operating on raw byte data, I was looking for a
way
to keep all header fields intact. Or is there another simple way to
instantiate 256 instances of AMSend?
Andreas
On 15/01/2008, at 16:08, Kevin Klues wrote:
Can I ask why you are trying to dynamically change the value of
the AM
type at runtime via this interface? The traditional way to
change
the AM type is to include multiple instances of
SerialAMSenderC() in
your configuration, each instantiated with a different AM type.
When
you want to send a message with a particular AM type, you choose
the
proper instance of the AMSend interface provided by one of these
components.
I'm not sure exactly why what you were trying to do originally
wouldn't work in theory, but I suspect it has something to do with
not
using the proper components in your configuration.
Kevin
On Jan 15, 2008 1:53 AM, Andreas Reinhardt
[EMAIL PROTECTED] wrote:
Hi,
Using tmotes on tinyos-2.x, I am looking for a solution to
manually
set the AMtype field of an AMPacket that I send out over the
serial
port. When I set it using the AMPacket.setType(..) method prior
to
calling AMSend.send(), it seems it is always reset by
SerialActiveMessageP.nc. But even if I uncomment line 63 in the
AMSend.send() method of that file, things don't change:
// [... ]header-group = TOS_AM_GROUP;
//header-type = id;// Commented out
header-length = len; [...]
However, if I enter any arbitrary number here (such as: header-
type =
4;), it appears correctly in the data stream over the serial
port.
How
can that be - browsing the source code doesn't show up any other
methods handling the packet in the meantime.
Any other solutions are appreciated.
Thanks,
Andreas
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
--
~Kevin
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
--
~Kevin
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Question related to Tmote Sky schematics: pin 6 of JTAG connector
The Tmote Sky schematics show that pin 6 of U8 (JTAG connector) is not connected. However we get the impression that something is connected to this pin. We used pin 6 of U8 to pass an additional signal to an add-on board (since all signals on the U2 and U28 expansion connector have already been used) but the shape of the signal becomes heavily disturbed. Can onebody comment on this? What is actually connected to this pin 6 of U8? Martin This e-mail and its contents are subject to the DISCLAIMER at http://www.tno.nl/disclaimer/email.html ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Tossim compilation error using CollectionC/LinkEstimationP
hi all,
When i want to compile an application using the component CollectionC (for
exemple: EasyCollection, TestNetwork, MultiHopOscilloscope), it works fine
for an simple make micaz. But when i want to compile it for Tossim (make
micaz sim), i always receive the same error linked to LinkEstimatorP.nc:
/
In file included from /opt/tinyos-2.x/tos/lib/net/ctp/CtpP.nc:127,
from /opt/tinyos-2.x/tos/lib/net/ctp/CollectionC.nc:69,
from TestNetworkAppC.nc:21:
In component `LinkEstimatorP':
/opt/tinyos-2.x/tos/lib/net/4bitle/LinkEstimatorP.nc:70: syntax error before
`('
make: *** [sim-exe] Error 1
/
I made all the update via the CVS and i'm working with the components in
file /4bitle.
At the line 70 in the component LinkEstimatorP is written:
//
INFINITY = 0xff,
//
I tried to understand why i have this problem, and nobody never spoke about
it on the mailing list, but i'm not workimg with Tinyos for a long time and
i could not find any reasons.
I just discover that suppressing the line 70 from LinkEstimatorP makes the
Tossim compilation working well, but the simple compilation make micaz
does not work this time.
I tried it because i need Tossim to try my own application using
CollectionC. So i'm able to work in Tossim when i suppress the line 70 but i
have to add it again if i want to compile it on motes.
Did anyone already meet this problem?
Regards,
Jérémy
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Tossim compilation error using CollectionC/LinkEstimationP
Unterfinger Jérémy wrote: At the line 70 in the component LinkEstimatorP is written: // INFINITY = 0xff, // I tried to understand why i have this problem, and nobody never spoke about it on the mailing list, but i'm not workimg with Tinyos for a long time and i could not find any reasons. I just discover that suppressing the line 70 from LinkEstimatorP makes the Tossim compilation working well, but the simple compilation make micaz does not work this time. In the standard C library, the built-in math.h header file predefines INFINITY to be some really large constant. This creates a conflict when you're compiling LinkEstimatorP.nc for TOSSIM, since line 70 will effectively try to redefine the constant INFINITY in a way that the C compiler can't interpret. There's no naming conflict when you do make micaz, since the motes use a limited C library that doesn't predefine INFINITY. The simplest solution to this problem is to do a search-and-replace in LinkEstimatorP.nc, replacing INFINITY with INFINITY_. This version will compile fine for both TOSSIM and actual mote hardware. Greg Hackmann ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Tossim compilation error using CollectionC/LinkEstimationP
Thanks for the bug report - I have committed a fix to the problem you reported: rename INFINITY to VERY_LARGE_EETX_VALUE. - om_p On Jan 22, 2008 8:37 AM, Greg Hackmann [EMAIL PROTECTED] wrote: Unterfinger Jérémy wrote: At the line 70 in the component LinkEstimatorP is written: // INFINITY = 0xff, // I tried to understand why i have this problem, and nobody never spoke about it on the mailing list, but i'm not workimg with Tinyos for a long time and i could not find any reasons. I just discover that suppressing the line 70 from LinkEstimatorP makes the Tossim compilation working well, but the simple compilation make micaz does not work this time. In the standard C library, the built-in math.h header file predefines INFINITY to be some really large constant. This creates a conflict when you're compiling LinkEstimatorP.nc for TOSSIM, since line 70 will effectively try to redefine the constant INFINITY in a way that the C compiler can't interpret. There's no naming conflict when you do make micaz, since the motes use a limited C library that doesn't predefine INFINITY. The simplest solution to this problem is to do a search-and-replace in LinkEstimatorP.nc, replacing INFINITY with INFINITY_. This version will compile fine for both TOSSIM and actual mote hardware. Greg Hackmann ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Which means, and to what use the word reserved INLINE?
-- Tiago de Lima Wanderley Grad. Ciencia da Computacao Departamento de Sistemas e Computacao Universidade Federal de Campina Grande ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] point-to-point or publish/subscribe algorithm for TinyOS
Hi, I'm a Master Student from Center of Informatics - Federal University of Pernambuco, Brazil. My research area is Wireless Sensor Networks and i'm using TinyOS and Mica Motes. How can I implements a point-to-point or publish/subscribe algorithm in TinyOS? Is there a existent code? Regards, Kalil ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] point-to-point or publish/subscribe algorithm for TinyOS
I know there was work being done for publish-subscribe at TU-Berlin. I dont know where they put they're code, but the person to ask is Jan Hauer. Kevin On Jan 21, 2008 9:10 AM, Kalil Araujo Bispo [EMAIL PROTECTED] wrote: Hi, I'm a Master Student from Center of Informatics - Federal University of Pernambuco, Brazil. My research area is Wireless Sensor Networks and i'm using TinyOS and Mica Motes. How can I implements a point-to-point or publish/subscribe algorithm in TinyOS? Is there a existent code? Regards, Kalil ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help -- ~Kevin ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] tinyOS problem
It is not really a big problem, you just need to configure the path for tinyos. please check the mailing list for further assistance. regards; Peizhao Hu 詹閔超 wrote: Hello,my name is Jan,I come from Taiwan. I got some troble when i install the tinyOS. Could you tell me how can i install the rpm file? and i got lots of warning when i keyin tos-check-env. please teach me how to solve these problem, thank you! -- 電子三甲 詹閔超 努力目標: 台清交成 或者直接當兵後到國外讀碩士XD ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] avr-libc failure
Hi Kevin; My MacBook is Intel Core2Duo. and I followed your comments last time to install TinyOS on my Tiger 10.4 without any problem. but I recently upgraded to Leopard 10.5, then I experienced the same problem that other people suggested. regards; Peizhao Hu Kevin Klues wrote: I've compiled binaries for intel based macs and updated the tutorial appropriately. I dont have a power pc based mac, and for some reason I'm having problems compiling a universal binary, so for now I only have the avr tools for intel based macs up on the site. If anyone has a power pc mac and has time to build the tools, let me know and I'll send the scripts over for building them. Kevin On Jan 19, 2008 5:58 PM, Peizhao Hu [EMAIL PROTECTED] wrote: similar problem in Leopard regards; Peizhao Hu NICTA http://www.nicta.com.au Kevin Klues wrote: I've heard other people complaining about this recently as well. Either darwin ports has come out with a newer version of avr-libc that doesnt compile correctly, or your version of X-Code isnt compatible with it. Either way, the best solution is to just provide a precompiled set of binaries for now. I'll update the tutorial later today with instructions on how to get ahold of them. Kevin On Jan 19, 2008 1:28 AM, Spongebob Squarepants [EMAIL PROTECTED] wrote: Hi, I am having a problem installing TinyOS 2 on my MAC OS X Tiger. The error happens when I try to install the avr tools (sudo port install avr-libc) I am following Klues' steps. The error is following reported. I am not sure which path and how I have to change it. Please, let me know if you have any clue how to solve the problem. cheers, Antonio ... --- Cleaning binutils --- Fetching avr-libc --- Attempting to fetch avr-libc-1.4.4.tar.bz2 from http://savannah.nongnu.org/download/avr-libc/ --- Verifying checksum(s) for avr-libc --- Extracting avr-libc --- Configuring avr-libc Error: Target org.macports.configure returned: configure failure: shell command cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_cross_avr-libc/work/avr-libc-1.4.4 ./configure --prefix=/opt/local --prefix=/opt/local --host=avr --build=`./config.guess` returned error 1 Command output: checking build system type... i686-apple-darwin8.11.1 checking host system type... avr-unknown-none checking if configuring for cross compile... yes checking if target host is avr... yes checking for a BSD-compatible install... /usr/bin/install checking whether build environment is sane... yes checking for gawk... no checking for mawk... no checking for nawk... no checking for awk... awk checking whether make sets $(MAKE)... yes checking for avr-strip... avr-strip checking for avr-gcc... /usr/bin/gcc-4.0 checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... yes checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether /usr/bin/gcc-4.0 accepts -g... yes checking for /usr/bin/gcc-4.0 option to accept ANSI C... none needed checking for style of include used by make... GNU checking dependency style of /usr/bin/gcc- 4.0... gcc3 checking for avr-as... avr-as checking for avr-ranlib... avr-ranlib checking for avr-ar... avr-ar configure: error: Wrong C compiler found; check the PATH! ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] avr-libc failure
Does it work now with the new instructions? kevin On Jan 22, 2008 4:42 PM, Peizhao Hu [EMAIL PROTECTED] wrote: Hi Kevin; My MacBook is Intel Core2Duo. and I followed your comments last time to install TinyOS on my Tiger 10.4 without any problem. but I recently upgraded to Leopard 10.5, then I experienced the same problem that other people suggested. regards; Peizhao Hu Kevin Klues wrote: I've compiled binaries for intel based macs and updated the tutorial appropriately. I dont have a power pc based mac, and for some reason I'm having problems compiling a universal binary, so for now I only have the avr tools for intel based macs up on the site. If anyone has a power pc mac and has time to build the tools, let me know and I'll send the scripts over for building them. Kevin On Jan 19, 2008 5:58 PM, Peizhao Hu [EMAIL PROTECTED] wrote: similar problem in Leopard regards; Peizhao Hu NICTA http://www.nicta.com.au Kevin Klues wrote: I've heard other people complaining about this recently as well. Either darwin ports has come out with a newer version of avr-libc that doesnt compile correctly, or your version of X-Code isnt compatible with it. Either way, the best solution is to just provide a precompiled set of binaries for now. I'll update the tutorial later today with instructions on how to get ahold of them. Kevin On Jan 19, 2008 1:28 AM, Spongebob Squarepants [EMAIL PROTECTED] wrote: Hi, I am having a problem installing TinyOS 2 on my MAC OS X Tiger. The error happens when I try to install the avr tools (sudo port install avr-libc) I am following Klues' steps. The error is following reported. I am not sure which path and how I have to change it. Please, let me know if you have any clue how to solve the problem. cheers, Antonio ... --- Cleaning binutils --- Fetching avr-libc --- Attempting to fetch avr-libc-1.4.4.tar.bz2 from http://savannah.nongnu.org/download/avr-libc/ --- Verifying checksum(s) for avr-libc --- Extracting avr-libc --- Configuring avr-libc Error: Target org.macports.configure returned: configure failure: shell command cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_cross_avr-libc/work/avr-libc-1.4.4 ./configure --prefix=/opt/local --prefix=/opt/local --host=avr --build=`./config.guess` returned error 1 Command output: checking build system type... i686-apple-darwin8.11.1 checking host system type... avr-unknown-none checking if configuring for cross compile... yes checking if target host is avr... yes checking for a BSD-compatible install... /usr/bin/install checking whether build environment is sane... yes checking for gawk... no checking for mawk... no checking for nawk... no checking for awk... awk checking whether make sets $(MAKE)... yes checking for avr-strip... avr-strip checking for avr-gcc... /usr/bin/gcc-4.0 checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... yes checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether /usr/bin/gcc-4.0 accepts -g... yes checking for /usr/bin/gcc-4.0 option to accept ANSI C... none needed checking for style of include used by make... GNU checking dependency style of /usr/bin/gcc- 4.0... gcc3 checking for avr-as... avr-as checking for avr-ranlib... avr-ranlib checking for avr-ar... avr-ar configure: error: Wrong C compiler found; check the PATH! ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help -- ~Kevin ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] CC2420 LQI/RSSI bug fix
Hi, Can anyone say if this bug impacted the RssiSample application? (/tinyos-2.x-contrib/stanford-sing/apps/RssiSample/) Thanks, Tal Dane Murdock here at Rincon discovered an edge case bug with the CC2420 receive branch when applying TUnit unit testing to CC2420ReceiveP. This edge case occurred only with receiving a full payload. Having a complete payload to download, the RSSI and LQI bytes were automatically downloaded into the wrong area of the metadata portion of the message_t. These bytes were then re-arranged in the part of the code that intentionally fills out metadata information, and in doing so, the LQI byte was overwritten by the RSSI byte. The fix has been checked into CVS. -David ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-devel] Re: [Tinyos-help] CC2420 LQI/RSSI bug fix
On Jan 22, 2008, at 8:31 PM, Tal Rusak wrote: Hi, Can anyone say if this bug impacted the RssiSample application? (/tinyos-2.x-contrib/stanford-sing/apps/RssiSample/) It shouldn't. That app just reads the RSSI register and doesn't process packets. Phil ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] avr-libc failure
Sorry Kevin; I didn't know there an updated instruction. so now it is not using MacPort. I will try now and let you know soon. regards; Peizhao Hu Kevin Klues wrote: Does it work now with the new instructions? kevin On Jan 22, 2008 4:42 PM, Peizhao Hu [EMAIL PROTECTED] wrote: Hi Kevin; My MacBook is Intel Core2Duo. and I followed your comments last time to install TinyOS on my Tiger 10.4 without any problem. but I recently upgraded to Leopard 10.5, then I experienced the same problem that other people suggested. regards; Peizhao Hu Kevin Klues wrote: I've compiled binaries for intel based macs and updated the tutorial appropriately. I dont have a power pc based mac, and for some reason I'm having problems compiling a universal binary, so for now I only have the avr tools for intel based macs up on the site. If anyone has a power pc mac and has time to build the tools, let me know and I'll send the scripts over for building them. Kevin On Jan 19, 2008 5:58 PM, Peizhao Hu [EMAIL PROTECTED] wrote: similar problem in Leopard regards; Peizhao Hu NICTA http://www.nicta.com.au Kevin Klues wrote: I've heard other people complaining about this recently as well. Either darwin ports has come out with a newer version of avr-libc that doesnt compile correctly, or your version of X-Code isnt compatible with it. Either way, the best solution is to just provide a precompiled set of binaries for now. I'll update the tutorial later today with instructions on how to get ahold of them. Kevin On Jan 19, 2008 1:28 AM, Spongebob Squarepants [EMAIL PROTECTED] wrote: Hi, I am having a problem installing TinyOS 2 on my MAC OS X Tiger. The error happens when I try to install the avr tools (sudo port install avr-libc) I am following Klues' steps. The error is following reported. I am not sure which path and how I have to change it. Please, let me know if you have any clue how to solve the problem. cheers, Antonio ... --- Cleaning binutils --- Fetching avr-libc --- Attempting to fetch avr-libc-1.4.4.tar.bz2 from http://savannah.nongnu.org/download/avr-libc/ --- Verifying checksum(s) for avr-libc --- Extracting avr-libc --- Configuring avr-libc Error: Target org.macports.configure returned: configure failure: shell command cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_cross_avr-libc/work/avr-libc-1.4.4 ./configure --prefix=/opt/local --prefix=/opt/local --host=avr --build=`./config.guess` returned error 1 Command output: checking build system type... i686-apple-darwin8.11.1 checking host system type... avr-unknown-none checking if configuring for cross compile... yes checking if target host is avr... yes checking for a BSD-compatible install... /usr/bin/install checking whether build environment is sane... yes checking for gawk... no checking for mawk... no checking for nawk... no checking for awk... awk checking whether make sets $(MAKE)... yes checking for avr-strip... avr-strip checking for avr-gcc... /usr/bin/gcc-4.0 checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... yes checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether /usr/bin/gcc-4.0 accepts -g... yes checking for /usr/bin/gcc-4.0 option to accept ANSI C... none needed checking for style of include used by make... GNU checking dependency style of /usr/bin/gcc- 4.0... gcc3 checking for avr-as... avr-as checking for avr-ranlib... avr-ranlib checking for avr-ar... avr-ar configure: error: Wrong C compiler found; check the PATH! ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] avr-libc failure
Hi Kevin, I have had the MSP430 package installed. so stow: CONFLICT: /opt/local/stow/msp430/lib/libiberty.a vs. /opt/local/lib/libiberty.a when I tried to stow the MSP430 binary. regards; Peizhao Hu Kevin Klues wrote: Does it work now with the new instructions? kevin On Jan 22, 2008 4:42 PM, Peizhao Hu [EMAIL PROTECTED] wrote: Hi Kevin; My MacBook is Intel Core2Duo. and I followed your comments last time to install TinyOS on my Tiger 10.4 without any problem. but I recently upgraded to Leopard 10.5, then I experienced the same problem that other people suggested. regards; Peizhao Hu Kevin Klues wrote: I've compiled binaries for intel based macs and updated the tutorial appropriately. I dont have a power pc based mac, and for some reason I'm having problems compiling a universal binary, so for now I only have the avr tools for intel based macs up on the site. If anyone has a power pc mac and has time to build the tools, let me know and I'll send the scripts over for building them. Kevin On Jan 19, 2008 5:58 PM, Peizhao Hu [EMAIL PROTECTED] wrote: similar problem in Leopard regards; Peizhao Hu NICTA http://www.nicta.com.au Kevin Klues wrote: I've heard other people complaining about this recently as well. Either darwin ports has come out with a newer version of avr-libc that doesnt compile correctly, or your version of X-Code isnt compatible with it. Either way, the best solution is to just provide a precompiled set of binaries for now. I'll update the tutorial later today with instructions on how to get ahold of them. Kevin On Jan 19, 2008 1:28 AM, Spongebob Squarepants [EMAIL PROTECTED] wrote: Hi, I am having a problem installing TinyOS 2 on my MAC OS X Tiger. The error happens when I try to install the avr tools (sudo port install avr-libc) I am following Klues' steps. The error is following reported. I am not sure which path and how I have to change it. Please, let me know if you have any clue how to solve the problem. cheers, Antonio ... --- Cleaning binutils --- Fetching avr-libc --- Attempting to fetch avr-libc-1.4.4.tar.bz2 from http://savannah.nongnu.org/download/avr-libc/ --- Verifying checksum(s) for avr-libc --- Extracting avr-libc --- Configuring avr-libc Error: Target org.macports.configure returned: configure failure: shell command cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_cross_avr-libc/work/avr-libc-1.4.4 ./configure --prefix=/opt/local --prefix=/opt/local --host=avr --build=`./config.guess` returned error 1 Command output: checking build system type... i686-apple-darwin8.11.1 checking host system type... avr-unknown-none checking if configuring for cross compile... yes checking if target host is avr... yes checking for a BSD-compatible install... /usr/bin/install checking whether build environment is sane... yes checking for gawk... no checking for mawk... no checking for nawk... no checking for awk... awk checking whether make sets $(MAKE)... yes checking for avr-strip... avr-strip checking for avr-gcc... /usr/bin/gcc-4.0 checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... yes checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether /usr/bin/gcc-4.0 accepts -g... yes checking for /usr/bin/gcc-4.0 option to accept ANSI C... none needed checking for style of include used by make... GNU checking dependency style of /usr/bin/gcc- 4.0... gcc3 checking for avr-as... avr-as checking for avr-ranlib... avr-ranlib checking for avr-ar... avr-ar configure: error: Wrong C compiler found; check the PATH! ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] ncg for boomerang/moteiv
The subject says it all. Is there and updated version that supports tmoteinvent? ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] tinyos over msp430
Hi.. Am trying to port tinyos onto a msp430f2x with the help of a msp-FET430UIF USB-Debug-Interface. When i connect the device to a usb port it identifies it as a TI product.. but when i run motelist it says No devices found. Moreover the /dev/ttyUSB* file is not created. am working on linux. The Blink application compiles fine on giving make telosb. But when i try to install it on to the msp430 chip, it times-out MASS ERASE and flags an ERROR. The two basic problems are: its not recognized as a mote by MOTELIST and a /dev/ttyUSB* file is not created on plugging the mspFET. am also not sure if telosb is the right platform to use for a msp430 chip (its not a module/mote, just the msp430f2xx 80 pin ic and the USB-Debug-interface FET). I badly need some help. Regards, Shareef ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
