Hi David,
I tried to compile the TestPrintf example, but I got error:
sah224:~/TinyOS/tinyos-2.x/apps/tests/TestPrintf phu$ make mica2
mkdir -p build/mica2
mig java -target=mica2 -I/Users/phu/TinyOS/tinyos-2.x/tos/lib/printf
-DIDENT_PROGRAM_NAME=\"TestPrintfAppC\" -DIDENT_USER_ID=\"phu\"
-DIDENT_HOSTNAME=\"sah224.bne.nict\" -DIDENT_USER_HASH=0xa1b7bbefL
-DIDENT_UNIX_TIME=0x466a5b3cL -DIDENT_UID_HASH=0xeab956a8L
-java-classname=PrintfMsg
/Users/phu/TinyOS/tinyos-2.x/tos/lib/printf/printf.h printf_msg -o
PrintfMsg.java
javac PrintfMsg.java
javac PrintfClient.java
compiling TestPrintfAppC to a mica2 binary
ncc -o build/mica2/main.exe -Os -finline-limit=100000 -Wall -Wshadow
-Wnesc-all -target=mica2 -fnesc-cfile=build/mica2/app.c -board=micasb
-fnesc-separator=\never1096WritE
-I/Users/phu/TinyOS/tinyos-2.x/tos/lib/printf
-DIDENT_PROGRAM_NAME=\"TestPrintfAppC\" -DIDENT_USER_ID=\"phu\"
-DIDENT_HOSTNAME=\"sah224.bne.nict\" -DIDENT_USER_HASH=0xa1b7bbefL
-DIDENT_UNIX_TIME=0x466a5b3cL -DIDENT_UID_HASH=0xeab956a8L
-fnesc-dump=wiring -fnesc-dump='interfaces(!abstract())'
-fnesc-dump='referenced(interfacedefs, components)'
-fnesc-dumpfile=build/mica2/wiring-check.xml TestPrintfAppC.nc -lm
In file included from
/Users/phu/TinyOS/tinyos-2.x/tos/lib/printf/PrintfC.nc:53,
from TestPrintfAppC.nc:42:
/Users/phu/TinyOS/tinyos-2.x/tos/lib/printf/PrintfP.nc:51: warning:
implicit declaration of function `FDEV_SETUP_STREAM'
/Users/phu/TinyOS/tinyos-2.x/tos/lib/printf/PrintfP.nc:51:
`_FDEV_SETUP_WRITE' undeclared here (not in a function)
/Users/phu/TinyOS/tinyos-2.x/tos/lib/printf/PrintfP.nc:51: invalid
initializer
/Users/phu/TinyOS/tinyos-2.x/tos/lib/printf/PrintfP.nc:51: (near
initialization for `atm128_stdout')
make: *** [exe0] Error 1
also, do I need to have a specific JTAG ICE pod? or any thing I can buy
with JTAG ICE support?
David Gay wrote:
On 6/8/07, Peizhao Hu <[EMAIL PROTECTED]> wrote:
thanks David,
I tried to modify your example AntiTheft application to implement
control of sensor node from the root:
1. node notify its appearance to the base station and wait for further
instructions (either into low power waiting mode or start sampling)
2. base station can inactive a node by disseminate the operation mode
with the target ID.
However, I finished everything and deployed onto the motes, I have no
idea how I can debug the application.
so is there any debugging tool that I can use rather than 3 low bits
leds?
Some options:
- http://www.tinyos.net/tinyos-1.x/doc/nesc/nesc-debugging.html
- tossim
- tinyos-2.x/tos/lib/printf
- send some of your own radio or serial messages for debugging
Personally, I tend to mostly use avarice/gdb and the leds...
David
--
regards;
Peizhao
_______________________________________________
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
