Re: [Tinyos-help] MTS310 - raw sensor data
Octave Technology has a document that outlines the packet format, which could help in your situation. http://www.octavetech.com/newsroom/pubs.html Tehn Yit Chin Embedded System Engineer, Grey Innovation Pty. Ltd. [EMAIL PROTECTED] wrote: Hi, I am getting messages looking like the following from MTS310 boards: 7e 42 7d 5e 00 11 7d 5d 16 00 00 07 00 cd 00 00 00 00 00 00 00 92 00 80 cd ca 00 ff ff 06 cd 53 ec How could I decipher the payload of these packets? Is there any documentation on how to interpret raw data from MTS310? Regards, Andrea ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] multihop problems
I finally got the packets to multihop. Like Ben Kelly said, it took some
work to get it the multihop in the lab.
What I finally did was load all the nodes withe surge application, and
disconnect the antenna from node1 so that its range is severely limited.
Looking at the output from xlisten, I can only see the packets from
node0. Packets from node2 and node1 started to come in after a few
minutes. Now that the packets are being forwarded, I install TOSBase on
node0 to have a closer look at the packets. The output of it shows that
the packets originated from node1 has a source address of node2, which
indicates that it is multihopping from to node0 via node 2.
Thanks for all who helped!
Tehn Yit Chin
Embedded System Engineer, Grey Innovation Pty. Ltd.
Tehn Yit Chin wrote:
Hey all,
Thanks to all that reply, but I haven't manage to get the multihop to
work yet so I put in some debug code.
I put in some code into ReceiveMsg.receive() to toggle the yellow LED.
So the yellow LED will blink when it receives any message. I also put in
code to toggle the green LED when a message has been forwarded and the
red LED when it fails to select a route via RouteSelect.selectRoute().
In an attempt to force the packets from node1 to multihop, I removed the
antenna from its SMA connector and put right next to node2. Hopefully,
the packet will go from node1 to node2 which will forward it base node.
using xlisten, I am only getting the following...
$ ../xlisten -r -b=mica2
xlisten Ver:$Id: xlisten.c,v 1.17 2004/11/18 04:45:10 mturon Exp $
Using params: [baud=0x1001] [raw]
/dev/ttyS0 input stream opened
7e42117d5d0c020002002403ff00a9039f42 [22]
7e42117d5d0c020002002503ff00a803f873 [22]
7e42117d5d0c020002002603ff00a703636f [22]
7e42fa7d5d1002000200270300020100fe00d844 [26]
7e42117d5d0c020002002803ff00a603c687 [22]
7e42117d5d0c020002002903ff00a60315c0 [22]
7e42117d5d0c020002002a03ff00a6036008 [22]
7e42117d5d0c020002002b03ff00a7030739 [22]
7e42117d5d0c020002002c03ff00a7031ffe [22]
7e42117d5d0c020002002d03ff00a703ccb9 [22]
7e42117d5d0c020002002e03ff00a703b971 [22]
7e42117d5d0c020002002f03ff00a7036a36 [22]
7e42117d5d0c020002003003ff00a7031cd2 [22]
7e42117d5d0c020002003103ff00a6037be3 [22]
7e42fa7d5d1002000200320300020100fe00297d5d [27]
7e42117d5d0c020002003303ff00a80387ce [22]
7e42117d5d0c020002003403ff00a9032b7f [22]
7e42117d5d0c020002003503ff00aa0324a3 [22]
7e42117d5d0c020002003603ff00aa03516b [22]
7e42117d5d0c020002003703ff00aa03822c [22]
7e42117d5d0c020002003803ff00aa0340f5 [22]
node2 is sending out SURGE_MSG and MHOP_MSG as well, but I am not
receiving any messages from node1. On the actual motes, the yellow LEDS
are toggling on both unit so they are receiving packets from each other,
but the other leds are not toggling at all so they are not trying to
forward any packets.
When will node2 know to forward the packet?
Tehn Yit Chin
Embedded System Engineer, Grey Innovation Pty. Ltd.
Ben Kelley wrote:
Generally, it should. But sometimes it will take some work, in a lab
setting, to force it to multihop. Sometimes turning the RF power down
will
help, or bending the signal around doorways.
-Original Message-
From: [EMAIL PROTECTED] [mailto:tinyos-help-
[EMAIL PROTECTED] On Behalf Of Tehn Yit Chin
Sent: Monday, July 10, 2006 02:42
To: Aditya Bhave
Cc: tinyos-help@Millennium.Berkeley.EDU
Subject: Re: [Tinyos-help] multihop problems
Thanks for the information.
Does the multihop works out-of-the-box with the surge application?
Tehn Yit Chin
Embedded System Engineer, Grey Innovation Pty. Ltd.
Aditya Bhave wrote:
A packet will multi-hop if node2 is not within radio range of base. Its
packet will reach node1 only who then has to send it to the base
station.
Im not really able to understand your question. To find out neighbors,
have
each mote broadcast a special packet
typedef struct Neighbor
{
int src; /* source mote ID */
int hopCount; /* initilaize to 0 */
}
If a mote A receives a packet of the above type from node B with
hopCount
set to 0, it can conclude that B is its neighbor. Also by controlled
flooding, these packets need to be multihopped across the network with
the
hopCount being incremeneted each time. In this way, motes can get an
idea
about the topology of the network.
To start the nodes in sequence, let each node wait for a START message
from
the base station i.e they are all in receive mode not doing anything
till
the START message arrives. The base station will transmit the START
message.
On 7/10/06, Tehn Yit Chin [EMAIL PROTECTED] wrote:
Hi,
I have the following setup
node2 -- node1 -- base
|^
++
node2 and node1 has the surge application installed.
base has the TOSBase installed.
No matter what I
Re: [Tinyos-help] multihop problems
Thanks for the information.
Does the multihop works out-of-the-box with the surge application?
Tehn Yit Chin
Embedded System Engineer, Grey Innovation Pty. Ltd.
Aditya Bhave wrote:
A packet will multi-hop if node2 is not within radio range of base. Its
packet will reach node1 only who then has to send it to the base station.
Im not really able to understand your question. To find out neighbors, have
each mote broadcast a special packet
typedef struct Neighbor
{
int src; /* source mote ID */
int hopCount; /* initilaize to 0 */
}
If a mote A receives a packet of the above type from node B with hopCount
set to 0, it can conclude that B is its neighbor. Also by controlled
flooding, these packets need to be multihopped across the network with the
hopCount being incremeneted each time. In this way, motes can get an idea
about the topology of the network.
To start the nodes in sequence, let each node wait for a START message from
the base station i.e they are all in receive mode not doing anything till
the START message arrives. The base station will transmit the START
message.
On 7/10/06, Tehn Yit Chin [EMAIL PROTECTED] wrote:
Hi,
I have the following setup
node2 -- node1 -- base
|^
++
node2 and node1 has the surge application installed.
base has the TOSBase installed.
No matter what I try, I can't seem to get a packet to multihop from
node2 to node1 to base. All the packets appears to single hop to the
base.
A couple of questions.
1) Does the base node needs to transmit for node1 to work out one of its
neighbours is node 0? One of things I tried is to install surge into
base node but this does not appears to be cause the packet to multihop.
2) Will the packet multihop with only two nodes in the network?
3) Is there a power up sequence? ie base node first, and then node 1 and
the node 2?
4) What are the conditions that will cause a packet to multihop?
Any suggestion is appreciated.
--
Tehn Yit Chin
Embedded System Engineer, Grey Innovation Pty. Ltd.
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] multihop problems
Hey all,
Thanks to all that reply, but I haven't manage to get the multihop to
work yet so I put in some debug code.
I put in some code into ReceiveMsg.receive() to toggle the yellow LED.
So the yellow LED will blink when it receives any message. I also put in
code to toggle the green LED when a message has been forwarded and the
red LED when it fails to select a route via RouteSelect.selectRoute().
In an attempt to force the packets from node1 to multihop, I removed the
antenna from its SMA connector and put right next to node2. Hopefully,
the packet will go from node1 to node2 which will forward it base node.
using xlisten, I am only getting the following...
$ ../xlisten -r -b=mica2
xlisten Ver:$Id: xlisten.c,v 1.17 2004/11/18 04:45:10 mturon Exp $
Using params: [baud=0x1001] [raw]
/dev/ttyS0 input stream opened
7e42117d5d0c020002002403ff00a9039f42 [22]
7e42117d5d0c020002002503ff00a803f873 [22]
7e42117d5d0c020002002603ff00a703636f [22]
7e42fa7d5d1002000200270300020100fe00d844 [26]
7e42117d5d0c020002002803ff00a603c687 [22]
7e42117d5d0c020002002903ff00a60315c0 [22]
7e42117d5d0c020002002a03ff00a6036008 [22]
7e42117d5d0c020002002b03ff00a7030739 [22]
7e42117d5d0c020002002c03ff00a7031ffe [22]
7e42117d5d0c020002002d03ff00a703ccb9 [22]
7e42117d5d0c020002002e03ff00a703b971 [22]
7e42117d5d0c020002002f03ff00a7036a36 [22]
7e42117d5d0c020002003003ff00a7031cd2 [22]
7e42117d5d0c020002003103ff00a6037be3 [22]
7e42fa7d5d1002000200320300020100fe00297d5d [27]
7e42117d5d0c020002003303ff00a80387ce [22]
7e42117d5d0c020002003403ff00a9032b7f [22]
7e42117d5d0c020002003503ff00aa0324a3 [22]
7e42117d5d0c020002003603ff00aa03516b [22]
7e42117d5d0c020002003703ff00aa03822c [22]
7e42117d5d0c020002003803ff00aa0340f5 [22]
node2 is sending out SURGE_MSG and MHOP_MSG as well, but I am not
receiving any messages from node1. On the actual motes, the yellow LEDS
are toggling on both unit so they are receiving packets from each other,
but the other leds are not toggling at all so they are not trying to
forward any packets.
When will node2 know to forward the packet?
Tehn Yit Chin
Embedded System Engineer, Grey Innovation Pty. Ltd.
Ben Kelley wrote:
Generally, it should. But sometimes it will take some work, in a lab
setting, to force it to multihop. Sometimes turning the RF power down will
help, or bending the signal around doorways.
-Original Message-
From: [EMAIL PROTECTED] [mailto:tinyos-help-
[EMAIL PROTECTED] On Behalf Of Tehn Yit Chin
Sent: Monday, July 10, 2006 02:42
To: Aditya Bhave
Cc: tinyos-help@Millennium.Berkeley.EDU
Subject: Re: [Tinyos-help] multihop problems
Thanks for the information.
Does the multihop works out-of-the-box with the surge application?
Tehn Yit Chin
Embedded System Engineer, Grey Innovation Pty. Ltd.
Aditya Bhave wrote:
A packet will multi-hop if node2 is not within radio range of base. Its
packet will reach node1 only who then has to send it to the base
station.
Im not really able to understand your question. To find out neighbors,
have
each mote broadcast a special packet
typedef struct Neighbor
{
int src; /* source mote ID */
int hopCount; /* initilaize to 0 */
}
If a mote A receives a packet of the above type from node B with
hopCount
set to 0, it can conclude that B is its neighbor. Also by controlled
flooding, these packets need to be multihopped across the network with
the
hopCount being incremeneted each time. In this way, motes can get an
idea
about the topology of the network.
To start the nodes in sequence, let each node wait for a START message
from
the base station i.e they are all in receive mode not doing anything
till
the START message arrives. The base station will transmit the START
message.
On 7/10/06, Tehn Yit Chin [EMAIL PROTECTED] wrote:
Hi,
I have the following setup
node2 -- node1 -- base
|^
++
node2 and node1 has the surge application installed.
base has the TOSBase installed.
No matter what I try, I can't seem to get a packet to multihop from
node2 to node1 to base. All the packets appears to single hop to the
base.
A couple of questions.
1) Does the base node needs to transmit for node1 to work out one of
its
neighbours is node 0? One of things I tried is to install surge into
base node but this does not appears to be cause the packet to multihop.
2) Will the packet multihop with only two nodes in the network?
3) Is there a power up sequence? ie base node first, and then node 1
and
the node 2?
4) What are the conditions that will cause a packet to multihop?
Any suggestion is appreciated.
--
Tehn Yit Chin
Embedded System Engineer, Grey Innovation Pty. Ltd.
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
Re: [Tinyos-help] Use of C functions in nesc code
Yes, you should be able to as nesc is just a preprocessor for C. I just
tried it out. I did the following as an experiment.
At the top MultiHopEngineM.nc, I added
#include stdlib.h
in initialize(), I added did the following
static void initialize() {
int n;
unsigned int x; Added
for (n=0; n FWD_QUEUE_SIZE; n++) {
FwdBufList[n] = FwdBuffers[n];
}
x=atoi(123); Added
iFwdBufHead = iFwdBufTail = 0;
}
I did a build for one of the tutorial that uses MultiHop, and no errors
were reported for stdlib.h or atoi().
cheers,
Tehn Yit Chin
Embedded System Engineer, Grey Innovation Pty. Ltd.
saadia khan wrote:
Can anyone tell me whether the C functions can be used in nesc code, e.g.,
using basic math functions like sqrt() or pow() or other maths functions?
Thankyou
S Khan
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] multihop problems
Hi, I have the following setup node2 -- node1 -- base |^ ++ node2 and node1 has the surge application installed. base has the TOSBase installed. No matter what I try, I can't seem to get a packet to multihop from node2 to node1 to base. All the packets appears to single hop to the base. A couple of questions. 1) Does the base node needs to transmit for node1 to work out one of its neighbours is node 0? One of things I tried is to install surge into base node but this does not appears to be cause the packet to multihop. 2) Will the packet multihop with only two nodes in the network? 3) Is there a power up sequence? ie base node first, and then node 1 and the node 2? 4) What are the conditions that will cause a packet to multihop? Any suggestion is appreciated. -- Tehn Yit Chin Embedded System Engineer, Grey Innovation Pty. Ltd. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] multihop routing in surge
Tehn Yit Chin wrote: Hi, I am experimenting with multihop routing in the surge tutorial. While I was browsing through the source, in particular, tos/lib/Router/MultiHopRouter.nc, I noticed that it uses MultiHopRouteM or MultiHopEngineM depending on whether OLD_ROUTING is defined. What is the difference between the MultiHopRouteM and MultiHopEngineM? It appears that MultiHopRouteM has better facilities for routining a packet. The reason that I am looking through the multihop source is that I am not able to get the packet to multihop in the Surge tutorial. cheers, I did some more digging, and found that it is calling RouteSelect.selectRoute() in MultiHopLEPSM.nc, however it appears to be returning a FAIL all the time. Does this means that the motes are not able to find a suitable route, and just drop the packet? I also programmed the base mote with the surge application and this is the application that appears to be forwarding packets. I don't understand why the base station is forwarding any packets as the packets already reached its destination, right? Tehn Yit Chin Embedded System Engineer, Grey Innovation Pty. Ltd. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] __attribute__ ((C, spontaneous))
Philip Levis wrote: On Jul 5, 2006, at 11:24 AM, Adam wrote: I notice GenericComm has this following function: TOS_MsgPtr handleReceived(TOS_MsgPtr packet) __attribute__ ((C, spontaneous)) I am curious that what's the difference if we use __attribute__ ((C, spontaneous)) or not to define an global function? I have written several global function without using the _attribute, it seems working fine so far. Dead code elimination. Spontaneous tells nesC that the function might be called from elsewhere and therefore shouldn't be removed. Phil Out of curiosity, would nesC also not perform any optimisation on this bit of code as well, or is that left up to avr-gcc? cheers, Tehn Yit Chin Embedded System Engineer, Grey Innovation Pty. Ltd. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] error Direct Parallel Access not defined
Sorry, I thought you were on linux. On cygwin, just replace /dev/ttyS0 with the name of your comport, which might be com1. On my cygwin setup, all i do is the following the results... $ make mica2 reinstall.0 MIB510=com1 installing mica2 binary set-mote-id build/mica2/main.srec build/mica2/main.srec.0.out `echo reinstall.0 |perl -pe 's/^reinstall.//; $_=hex if /^0x/i;'` uisp -dprog=mib510 -dserial=com1 -dpart=ATmega128 --wr_fuse_e=ff --erase --upload if=build/mica2/main.srec.0.out Firmware Version: 2.1 Atmel AVR ATmega128 is found. Uploading: flash Fuse Extended Byte set to 0xff cheers, Tehn Yit Chin Embedded System Engineer, Grey Innovation Pty. Ltd. zhiqiang zhang wrote: hi guys: I attached the command and message below : *$ make micaz reinstall.0 MIB510=/dev/ttyS0* * set-mote-id build/micaz/main.srec build/micaz/main.srec.out-0 0 Could not find symbol TOS_LOCAL_ADDRESS in build/micaz/main.exe, ignoring symbol. installing micaz binary with dapa uisp -dprog=dapa --wr_fuse_h=0xd9 -dpart=ATmega128 --wr_fuse_e=ff --erase /dev/parport0: No such file or directory Failed to open ppdev. make: *** [program] Error 2* ** i am using serial port,but it seems like using parallel port .i don't know how to solve this problem. By thy way ,you said there should be a symbol link between /dev/ttyS0 and /dev/parport0 ,how to do this? because i even can't find /dev ( i am using cygwin). regards zhiqiang ** * * On 03/07/06, Tehn Yit Chin [EMAIL PROTECTED] wrote: There probably isn't a /dev/parport0 available? Why are you using the parallel port? Is there symbolic link between /dev/ttyS0 and /dev/parport0? What happens when you try make mica2 reninstall.1 mib510=/dev/ttyS0 Tehn Yit Chin Embedded System Engineer, Grey Innovation Pty. Ltd. zhiqiang zhang wrote: hi,guys: I met the same question with campbell gao. Now i try the command make mica2 reinstall,1 mib510,/dev/ttyS0,then i met another error. */dev/parport0:no such file or directory , Failed to open ppdev.* Do you know how to solve it ? zhiqiang * * On 03/07/06, Tehn Yit Chin [EMAIL PROTECTED] wrote: campbell gao wrote: hi all when i type make mica2 reinstall,1 mib510,COM1 or make mica2 reinstall,1 mib510,/dev/ttyS0 I get the error Direct Parallel Access not defined. why ,anyone know it ?? I believe that the syntax is make mica2 reinstall.0 MIB510=COM1 or make mica2 reinstall.0 MIB510=/dev/ttyS0 Don't use any commas. Tehn Yit Chin Embedded System Engineer, Grey Innovation Pty. Ltd. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] #ifdef support in nesc.
Hi,
Does anyone know if #ifdef is supported in nesc?
I was experimenting with SurgeM.nc in apps/surge, and the following bit
of code is not compiling for me.
event result_t Timer.fired() {
dbg(DBG_USR1, SurgeM: Timer fired\n);
timer_ticks++;
if (timer_ticks % TIMER_GETADC_COUNT == 0) {
call ADC.getData();
}
// If we're the focused node, chirp
if (focused timer_ticks % TIMER_CHIRP_COUNT == 0) {
#ifdef CHIRP_ENABLE
call Sounder.start();
#endif /* CHIRP_ENABLE*/
}
// If we're the focused node, chirp
if (focused timer_ticks % TIMER_CHIRP_COUNT == 1) {
#ifdef CHIRP_ENABLE
call Sounder.stop();
#endif /* CHIRP_ENABLE*/
}
The results are
$ make mica2
compiling Surge to a mica2 binary
ncc -o build/mica2/main.exe -Os -board=micasb -target=mica2
-I%T/lib/Route -I%T/lib/Queue -I%T/lib/Broadcast -Wall -Wshadow -DDEF_TO
S_AM_GROUP=0x7d -Wnesc-all -finline-limit=10
-fnesc-cfile=build/mica2/app.c Surge.nc -lm
SurgeM.nc: In function `Timer.fired':
SurgeM.nc:163: Sounder.start not connected
SurgeM.nc:169: Sounder.stop not connected
SurgeM.nc: In function `Bcast.receive':
SurgeM.nc:248: Sounder.init not connected
SurgeM.nc:265: Sounder.stop not connected
make: *** [build/mica2/main.exe] Error 1
I also has the following the module definition as well.
#ifdef CHIRP_ENABLE
interface StdControl as Sounder;
#endif /* CHIRP_ENABLE */
I am using nesc 1.1. Any pointer is appreciated.
--
Tehn Yit Chin
Embedded System Engineer, Grey Innovation Pty. Ltd.
--
Tehn Yit Chin
Embedded System Engineer, Grey Innovation Pty. Ltd.
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Loading programs onto Mica2: Prelim question
2) The RfmToLeds compiles and gets loaded. But when made to work in conjunction with another mote that has CntToLedsAndRfm, it does nothing. The LED still keeps on blinking on the mote that has the latter installed. Hi, I just completed this tutorial yesterday. Check that the group ID are the same for the two motes. The individual ID shouldn't matter as CntToLedsAndRfm is broadcasting the packets to all receivers. cheers, -- Tehn Yit Chin Embedded System Engineer, Grey Innovation Pty. Ltd. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] #ifdef support in nesc.
Philip Levis wrote:
On Jun 29, 2006, at 5:33 PM, Tehn Yit Chin wrote:
Hi,
Does anyone know if #ifdef is supported in nesc?
The full C preprocessor is supported. Your bug is that you are not
wiring the Sounder. You need to include it in the configuration.
In Surge.nc, I was wiring Sounder as
implementation {
components Main, SurgeM, TimerC, LedsC, NoLeds, Photo as Sensor,
RandomLFSR,
GenericCommPromiscuous as Comm, Bcast, MultiHopRouter as multihopM,
QueuedSend;
#ifdef CHIRP_ENABLE
Components Sounder;
#endif /* CHIRP_ENABLE */
}
Is this valid? Must all components be specify in one statement?
thanks,
tyc
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Loading programs onto Mica2: Prelim question
Arijit Ghosh wrote: I did set the same group id for both. I used the MakeXbowlocal file. Did yours work straight out of the box? Can you please send me your makelocal/makexbowlocal file? Mine work straight out of the box. All I added was to create a Makelocal which I placed into tinyos-1.x/tools/make. My Makelocal is # Makelocal File DEFAULT_LOCAL_GROUP = 0x33 PFLAGS += -DCC1K_DEF_FREQ=CC1K_915_998_xxMHZ I did not use MakeXbowlocal at all. I also used the apps in tiny-1.x/apps instead of in contrib/xbow/apps. BTW, please reply to the list so that someone else will also benefit from our discussions... Cheers, tyc ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] component documentation
Hi, I was wondering if there are any documentation on what components are standard in the tinyos 1.1.0, other than browsing through the source? many thanks -- Tehn Yit Chin Embedded System Engineer, Grey Innovation Pty. Ltd. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] tinyos RAM calculation: just .bss (not .data)?
You can also use the size utility to find out sizes of various sections
as well, or the avr equivalent avr-size.
Tehn Yit Chin
Software Engineer, Grey Innovation Pty. Ltd.
Leonardo B. Oliveira wrote:
Hi all,
it seems that .data is not considered while tinyos calculate the
amount of RAM mem consumed. Why not?
@echo @objdump -h $(MAIN_EXE)|
perl -ne
'$$b{$$1}=hex $$2 if /^\s*\d+\s*\.(text|data|bss)\s+(\S+)/;
END { printf(%16d bytes in ROM\n%16d bytes in RAM\n,
$$b{text}+$$b{data},$$b{bss}); }'
^^^
Thx in advance,
Leonardo
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] development environment
Hi all, Just starting to get my head around the tinyos with the development environment. My current development environment also caters for developing other Atmel AVR micros so I have already have the AVR gnu toolchain all setup. However, reading the install documentation that came with tinyos-1.1.0, it said to remove this installation as well. Is this because tinyos has its own verion of gcc that it uses? Has anyone found a way of just downloading the tinyos source and nesc without reinstalling the gnu toolchain? many thanks, -- Tehn Yit Chin Software Engineer, Grey Innovation Pty. Ltd. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
