[Tinyos-help] How Access to External Tools by User-specified Annotation?
Hi Recently, I was reading nesC 1.3 Language Reference Manual.In 11 section (Attributes),the Author said: Allow user-specified annotation which are accessible to external tools. ..., please see the nesC compiler manual for details. Now I want to use this function, but I cannot find which part of the nesC compiler manual(available in http://www.tinyos.net/tinyos-1.x/doc/nesc/ncc.html) specify it. Do I take the right documentation? If not, please give me some suggestion. Or give me some stuff about the how to access exteranl tools by user-specified annotation. I will appreciate your help. thank you very much. ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] How to learn nesc complier?
Hi Recently, I wanted to learn nesc complier, but I did't know how.Could you give me some suggestions. I have read the nesC lagnguage reference manual, do you have some more deeply stuff. Additionally, in the reference manual(section 14), it refer the ncc and nescc man page, what is it, and how to get it? Thanks beforehand. ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] about the size of byte of burning into MCU
Hello Recently,one question awlays confuse me: how many bytes was burned(or programmed) into MCU and where them store? For example: the simple Blink, I check its main.ihex (Blink/build/telosb) file find its 7591bytes,DO that means all 7591bytes must be burned into MCU(MSP430)? but through command : make telosb, its appear this application was divided into two part: 2648bytes in ROM, and 54 bytes in RAM,what's happen? What is the difference between 7591bytes and 2702 bytes(2648+54)? IS there a external flash for storing the difference? I want to learn about compile of nes file,Can you give me some advise about how to learn? Thank your attention, I will appreciate your help. ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] So wierd problem about Deluge T2
Hello： Recently, I was trouble in Deluge T2 about not stoping the reprogramed client node. I had correctly injected a revised Blink image to Basestation and sent the image to client node. Then I sent : tos-deluge serial@/dev/ttyUSB0:115200 -dr 1 for reprograming. The client node also runed Blink. But when I wanted to stop the runed program in client node, I sent command: tos-deluge serial@/dev/ttyUSB0:115200 -ls 1 to Basestation by serial port. The client still was running. I could not stop it. Is it a bug, or How can I solve it？ I will very appreciate your help. ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Problem with Deluge T2
Hello： Recently，I was going to use Deluge T2 in term of websit: http://docs.tinyos.net/index.php/Deluge_T2，but I had some troubles：When I respectively install Base station and GoldenImagin to two nodes, and then send command: $tos-deluge serial@/dev/ttyUSB0:115200 -dr 1 The LED1 of Base station node just was bright for several seconds, and then nothing happened. The node with GoldenImagin has any response. My using platform is telosb(msp430+cc2420). Please give me some helps or suggestions, I will very appreciate your help. Please find below the detailed steps I followed and their corresponding outputs: = ( insert node 0 ) $cd /local/src/tinyos-2.x/apps/tests/deluge/Basastation $ make telosb install,0 bsl,/dev/ttyUSB0 Output: compiling BasestationAppC to a telosb binary ncc -o build/telosb/main.exe -Os -O -mdisable-hwmul -DCC2420_DEF_CHANNEL=16 -fnesc-separator=__ -Wall -Wshadow -Wnesc-all -target=telosb -fnesc-cfile=build/telosb/app.c -board= -DDEFINED_TOS_AM_GROUP=0x22 -Ibuild/telosb -DDELUGE_BASESTATION -DIDENT_APPNAME=\BasestationAppC\ -DIDENT_USERNAME=\xubuntos\ -DIDENT_HOSTNAME=\xubuntos-tinyos\ -DIDENT_USERHASH=0x00f95284L -DIDENT_TIMESTAMP=0x4cd91f83L -DIDENT_UIDHASH=0x99572546L -DDELUGE -I/home/xubuntos/local/src/tinyos-2.x/tos/lib/net -I/home/xubuntos/local/src/tinyos-2.x/tos/lib/net/drip -I/home/xubuntos/local/src/tinyos-2.x/tos/lib/net/Deluge -I/home/xubuntos/local/src/tinyos-2.x/tos/lib/net/Deluge/FlashVolumeManager -I/home/xubuntos/local/src/tinyos-2.x/tos/lib/net/Deluge/BlockStorageManager -I/home/xubuntos/local/src/tinyos-2.x/tos/lib/net/Deluge/extra -I/home/xubuntos/local/src/tinyos-2.x/tos/lib/net/Deluge/extra/msp430 -I/home/xubuntos/local/src/tinyos-2.x/tos/lib/net/Deluge/extra/telos -Wl,--section-start=.text=0x4a00,--defsym=_reset_vector__=0x4000 -I/home/xubuntos/local/src/tinyos-2.x/tos/lib/net/Deluge/extra/telosb BasestationAppC.nc -lm /home/xubuntos/local/src/tinyos-2.x/tos/platforms/epic/chips/ds2411/PlatformOneWireLowLevelP.nc:16:2: warning: #warning Please ignore the non-atomic access warnings for shared variables port2 /home/xubuntos/local/src/tinyos-2.x/tos/chips/cc2420/lpl/DummyLplC.nc:39:2: warning: #warning *** LOW POWER COMMUNICATIONS DISABLED *** /home/xubuntos/local/src/tinyos-2.x/tos/chips/msp430/adc12/Msp430Adc12ImplP.nc:68:4: warning: #warning Accessing TimerA for ADC12 compiled BasestationAppC to build/telosb/main.exe 40870 bytes in ROM 1442 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-0 TOS_NODE_ID=0 ActiveMessageAddressC__addr=0 installing telosb bootloader using bsl tos-bsl --telosb -c /dev/ttyUSB0 -r -e -I -p /home/xubuntos/local/src/tinyos-2.x/tos/lib/tosboot/build/telosb/main.ihex MSP430 Bootstrap Loader Version: 1.39-telos-8 Mass Erase... Transmit default password ... Invoking BSL... Transmit default password ... Current bootstrap loader version: 1.61 (Device ID: f16c) Changing baudrate to 38400 ... Program ... 2118 bytes programmed. Reset device ... installing telosb binary using bsl (without mass erase) tos-bsl --telosb -c /dev/ttyUSB0 -r -I -p build/telosb/main.ihex.out-0 MSP430 Bootstrap Loader Version: 1.39-telos-8 Invoking BSL... Transmit default password ... Current bootstrap loader version: 1.61 (Device ID: f16c) Changing baudrate to 38400 ... Program ... 40902 bytes programmed. Reset device ... rm -f build/telosb/main.exe.out-0 build/telosb/main.ihex.out-0 (inject tos_image.xml of Blink with revised in term of websit) $ cd /home/xubuntos/local/src/tinyos-2.x/ $ tos-deluge serial@/dev/ttyUSB0:115200 -i 1 apps/Blink/build/telosb/tos_image.xml Output: Flushing the serial port.. Checking if node is a Deluge T2 base station ... Pinging node ... Connected to Deluge nodes. No valid image was detected. -- Create image: /home/xubuntos/local/bin/tos-build-deluge-image -i 1 apps/Blink/build/telosb/tos_image.xml Ihex read complete: 34184 bytes starting at 0x4A00 32 bytes starting at 0xFFE0 34216 bytes in 2 sections CRCs: 0x271E 0x7109 0x81BD 0x54CB 0x0DEB 0x3CD6 0xC5F3 0x69CB 0xBCA5 0xC337 0xAA9E 0xE863 0x7DBB 0x30B7 0x7E60 0x6236 0xF78D 0xE49C 0xF377 0x3DAF 0x08AA 0x4836 0x0CE2 0x1794 0xD9A9 0x1BEC 0xC951 0xCA9F 0x55F8 0xD942 0x03B8 0xCAC1 -- 35712 bytes in 76.72 seconds (465.4661 bytes/s) -- Replace image with: Prog Name: BlinkAppC UID: 0xC0025B9B Compiled On: Tue Nov 09 17:50:18 2010 Platform:telosb User ID: xubuntos Host Name: xubuntos-tinyos User Hash: 0x00F95284 Size:35712 Num Pages: 32 -- (ping
