Hi Alexandre,

I use the command "find /opt/tinyos-2.x/ -type f -exec grep -nH 
'tos-set-symbol' {} \;" to find all regular files in the TinyOS 
installation directory that contain the string "tos-set-symbol".

The relevant files are ${TOSROOT}/support/make/msp/msp.rules, 
${TOSROOT}/support/make/avr/avr.rules and 
${TOSROOT}/support/make/pxa27x/pxa27x.rules. In typical makefile slang 
they set an environment variable SET_ID to represent the tool to set the 
symbol. Later in the file (just search for SET_ID) they call it to 
modify the TOS_NODE_ID symbol.

If you don't find this, have a look at the CVS versions, for instance 
directly on the web: 
http://tinyos.cvs.sourceforge.net/tinyos/tinyos-2.x/support/make/msp/msp.rules?view=markup
 
(lines 38 and 83). If I understand the code in line 83 correctly, the 
reason why you don't see the call to tos-set-symbol on your system is 
that you have already generated a copy of the binary with your desired 
node id. Try a different node id or clean up your project with "make 
clean", and you should see the call to tos-set-symbol.

Can you give us some details about your custom platform? Does it use an 
MSP430 or some other processor?

Cheers,
Urs

Alexandre Buist wrote:
> Thanks Urs,
> 
> I look around but I can't find anything in the platform files or the
> platform.target that would link to tos-set-symbols with TOS_NODE_ID. The
> only relevant files I found about tos-set-symbols is the uC msp.rules. Which
> should be just fine without modification. 
> 
> One thing I noticed, In the mote 2 mote tutorial:
> $ make telosb install,1
> ...
>     compiled BlinkToRadioAppC to build/telosb/main.exe
>             9040 bytes in ROM
>              246 bytes in RAM
> msp430-objcopy --output-target=ihex build/telosb/main.exe
> build/telosb/main.ihex
>     writing TOS image
> tos-set-symbols --objcopy msp430-objcopy --objdump msp430-objdump --target
> ihex build/telosb/main.ihex 
> build/telosb/main.ihex.out-1 TOS_NODE_ID=1 ActiveMessageAddressC$addr=1
> ...
> 
> 
> While in my environement
> $ make telosb install,1
> ...
>     compiled BlinkToRadioAppC to build/telosb/main.exe
>            10674 bytes in ROM
>              283 bytes in RAM
> msp430-objcopy --output-target=ihex build/telosb/main.exe
> build/telosb/main.ihex
>     writing TOS image
> cp build/telosb/main.ihex build/telosb/main.ihex.out
>     installing telosb binary using the parallel port jtag adapter
> ...
> 
> The thing to notice is that the tos-set-symbols ... does not show up. Could
> there be something wong with my environment.
> 
> Any thoughts,
> 
> Thanks
_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Reply via email to