It is the testbed installation software that sets these addresses. It
is good to try to find both $ and _ versions and substitute them
because testbed users might be using different versions of TinyOS.

- om_p

On Mon, Feb 7, 2011 at 5:05 AM, Michiel Konstapel <m.konsta...@sownet.nl> wrote:
> Some time ago (TinyOS 2.1.1?), the default separator in generated code 
> changed from $ (ActiveMessageC$addr) to __ (ActiveMessageAddressC__addr). If 
> your tools still try to replace the version with $ in it, they won't find it 
> and the default value of 1 will remain in your program. The names of the 
> variables to replace are set in $TOSROOT/support/make/msp/msp.rules.
> Hope this helps,
> Michiel
>
>> -----Original Message-----
>> From: tinyos-help-boun...@millennium.berkeley.edu [mailto:tinyos-help-
>> boun...@millennium.berkeley.edu] On Behalf Of Thomas Schmid
>> Sent: maandag 7 februari 2011 12:28
>> To: Xiaohui Liu
>> Cc: Tinyos-Help
>> Subject: Re: [Tinyos-help] Latest TinyOS distribution issue
>> withTOS_AM_ADDRESS
>>
>> Where and how do you set your node ids? This is usually done in a
>> separate step of the make system, after compilation. Look at the
>> difference when you type:
>>
>> make telosb
>>
>> make telosb install,32
>>
>> You will see a line similar to the following:
>> tos-set-symbols --objcopy msp430-objcopy --objdump msp430-objdump
>> --target ihex build/telosb/main.ihex build/telosb/main.ihex.out-32
>> TOS_NODE_ID=32 ActiveMessageAddressC__addr=32
>>
>> - Thomas
>>
>>
>>
>>
>>
>> On Sun, Feb 6, 2011 at 11:36 AM, Xiaohui Liu <whu...@gmail.com> wrote:
>> > Hi,
>> > compile:
>> > make telosb
>> > Then I upload the executable on NetEye testbed, which programs nodes:
>> > usr/sbin/tos-bsl --telosb -c /dev/ttyUSB$1 -r -e -I -p $2
>> > $1 is the USB port number, $2 executable uploaded.
>> > Before my upgrade, the executable works well on NetEye.
>> > On Sat, Feb 5, 2011 at 3:51 AM, Omprakash Gnawali
>> <gnaw...@cs.stanford.edu>
>> > wrote:
>> >>
>> >> On Fri, Feb 4, 2011 at 1:42 PM, Xiaohui Liu <whu...@gmail.com>
>> wrote:
>> >> >
>> >> > Hi everyone,
>> >> > I upgrade my TinyOS distribution to the lastest version from
>> google code
>> >> > yesterday. Previously I was using TinyOS 2.1 with release-
>> dates.txt saying
>> >> > "These release notes are as of: $Date: 2008/06/18 23:07:04 $". Now
>> I find
>> >> > the following
>> >> > TOS_NODE_ID TOS_AM_ADDRESS ActiveMessageC$AMPacket$address()
>> >> > TinyOS 2.1 30 1 30
>> >> > Latest 30 1 1
>> >> >
>> >> > Since many places of my code use link addresses, my protocol now
>> does
>> >> > not work anymore under the latest version. For
>> >> > example, ActiveMessageC$AMPacket$source() always return 1 for all
>> packets
>> >> > received, even though they are from many different nodes with
>> various
>> >> > TOS_NODE_IDs. Has anyone encountered this problem with the latest
>> version
>> >> > and how should I resolve this? I find it appeared before in this
>> thread.
>> >> > Also, can somebody please tell me where TOS_AM_ADDRESS is set from
>> >> > initial value 1 to TOS_NODE_ID as in TinyOS 2.1. Thanks very much.
>> >>
>> >> How do you compile/program the nodes? It is likely you are not
>> setting
>> >> proper ActiveMessageAddressC.addr.
>> >>
>> >> - om_p
>> >
>> >
>> >
>> > --
>> > -Xiaohui Liu
>> >
>> > _______________________________________________
>> > 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 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

Reply via email to