On Sep 11, 2007, at 5:35 PM, Ajay Mamtura wrote:
Hi,
*** I am re-posting this question since there was no response the
last time. I do hope someone can guide me this time ***
I am a grad student in Toronto. It would be very nice if someone
could help me out a little bit with the following problem I am facing.
When I compile a custom tinyos app (Blimps) using "make micaz", the
app compiles (with a few async call and non-atomic
read/write warnings).
This app is roughly doing the same function as Surge. The
difference is that it senses some items (light, temp, humidity etc)
using the MTS400 sensorboard and sends it to the PC. On the PC the
modified java app (oscilloscope) plots only the temperature
readings. The "Blimps" app uses standard Multihop routing and I've
downloaded the MTS400 support files from
/contrib/xbow/tos/sensorboards/mts400 CVS folder, and placed into /
tos/sensorboards on the local hard drive.
I've also downloaded /contrib/xbow/tos/interfaces/SoDebug.h and
placed into /tos/interfaces on the local hard drive.
If I try to compile using "make pc" (for TOSSIM), I get a lot of
compilation warning messages, unfortunately ending in the app
not compiling. The bulk of the errors seem to related to bunch of
"unidentified identifiers". Was wondering if someone could help me
compile the app sucessfully ?
It seems these identifiers (e.g. UBRR0H) are defined in
/usr/local/avr/include/avr/iom128.h
/usr/local/avr/include/avr/iom162.h
/usr/local/avr/include/avr/iom169.h
/usr/local/avr/include/avr/iom64.h
... and it seems these files in turn are "included" via <io.h>
I don't understand why "make micaz" compiles, while "make pc"
indicates "unidentified identifiers" for the same app.
In case, I need to provide any other information to help someone
suggest possible answers, please let me know.
At the moment I do not know if I am allowed to post messages with
attachments (source files of the Blimps app).
btw, this is just the first step towards trying to integrate
TinySec into this app. Hope I can find a solution via the group's
help.
Thank you to everyone who tries to help me out.
Please read the TOSSIM paper from SenSys 2003. TOSSIM does not have a
simulation implementation of SoDebug. Those identifiers are control
and data registers for the UART, which don't exist in a process
running on a desktop.
Phil
_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
