Thanks for replying Phil........ If you could send the complete compile output of 'make micaz sim' that would help.
make micaz sim mkdir -p build/micaz placing object files in build/micaz writing XML schema to app.xml compiling tableImplC to object file sim.o ncc -c -shared -fPIC -o build/micaz/sim.o -g -O0 -tossim -fnesc-nido-tosnodes=1000 -fnesc-simulate -fnesc-nido-motenumber=sim_node\(\) -finline-limit=100000 -Wall -Wshadow -DDEF_TOS_AM_GROUP=0x7d -Wnesc-all -target=micaz -fnesc-cfile=build/micaz/app.c -board=micasb -Wno-nesc-data-race tableImplC.nc -fnesc-dump=components -fnesc-dump=variables -fnesc-dump=constants -fnesc-dump=typedefs -fnesc-dump=interfacedefs -fnesc-dump=tags -fnesc-dumpfile=app.xml /opt/tinyos-2.x/tos/lib/tossim/sim_packet.c:109: warning: '__nesc_nido_resolve' defined but not used /opt/tinyos-2.x/tos/lib/tossim/sim_packet.c:119: warning: '__nesc_nido_initialise' defined but not used compiling Python support into pytossim.o and tossim.o g++ -c -shared -fPIC -o build/micaz/pytossim.o -g -O0 /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx -I/usr/include/python2.3 -I/opt/tinyos-2.x/tos/lib/tossim -DHAVE_CONFIG_H g++ -c -shared -fPIC -o build/micaz/tossim.o -g -O0 /opt/tinyos-2.x/tos/lib/tossim/tossim.c -I/usr/include/python2.3 -I/opt/tinyos-2.x/tos/lib/tossim linking into shared object ./_TOSSIMmodule.so g++ -shared -fPIC build/micaz/pytossim.o build/micaz/sim.o build/micaz/tossim.o -lstdc++ -o _TOSSIMmodule.so copying Python script interface TOSSIM.py from lib/tossim to local directory *** Successfully built micaz TOSSIM library. Looking at the Makefile should help you figure out what's going wrong. The makefile for this code: COMPONENT=tableImplC include $(MAKERULES) Looking at the Makefile should help you figure out what's going wrong. or may be I did'nt get it right.....What exactly I should be looking at? Have you tried the 2.0 release? tinyos-2.0.0beta2-3 (RPM version 4.4.2) - Is this not the latest release??? I did update my tinyOS only recently. I will update it again today and try. Thanks a lot for helping :) Shilpa On 3/10/07, Philip Levis <[EMAIL PROTECTED]> wrote:
On Mar 10, 2007, at 10:53 AM, shilpa bhatt wrote: > Hello all, > > I am getting an Import Error when trying rum sumilation in TOSSIM. > > When I do a make micaz sim it successfully builts micaz TOSSIM > library. Though there are two warnings: > /opt/tinyos-2.x/tos/lib/tossim/sim_packet.c:109: warning: > '__nesc_nido_resolve' defined but not used > /opt/tinyos-2.x/tos/lib/tossim/sim_packet.c:119: warning: > '__nesc_nido_initialise' defined but not used > > But when I compile this code I get the following error: > > Traceback (most recent call last): > File "test.py", line 1, in ? > from TOSSIM import * > File "/opt/tinyos-2.x/tinyos-2.x/apps/tableModule/TOSSIM.py", line > 5, in ? > import _TOSSIM > ImportError: /opt/tinyos-2.x/tinyos-2.x/apps/tableModule/ > _TOSSIMmodule.so: undefined symbol: sim_mote_start_time > > Also, when use gdb I get the following message: > (gdb) make micaz > mkdir -p build/micaz > compiling tableImplC to a micaz binary > ncc -o build/micaz/main.exe -Os -finline-limit=100000 -Wall - > Wshadow -DDEF_TOS_AM_GROUP=0x7d -Wnesc-all -target=micaz -fnesc- > cfile=build/micaz/app.c -board=micasb -fnesc-dump=wiring -fnesc- > dump='interfaces(!abstract())' -fnesc-dump='referenced > (interfacedefs, components)' -fnesc-dumpfile=build/micaz/wiring- > check.xml tableImplC.nc -lm > /usr/lib/gcc/avr/3.4.3/../../../../avr/lib/avr5/crtm128.o(.init9 > +0x0): In function `__bad_interrupt': > ../../../crt1/gcrt1.S:104: undefined reference to `main' > make: *** [exe0] Error 1 > (gdb) > > I am using tinyos-2.0.0beta2-3 (RPM version 4.4.2) installed in > Fedora Core release 5 (2.6.18-1.2257.fc5). > > Any idea as to why I am getting these errors. Please help. > If you could send the complete compile output of 'make micaz sim' that would help. Something is wrong with the linking when building TOSSIMmodule.so. For some reason, it isn't linking in the object file that defines sim_mote_start_time. This is a C linking problem. Looking at the Makefile should help you figure out what's going wrong. Have you tried the 2.0 release? Phil
-- Best Regards, Shilpa Bhatt Email: [EMAIL PROTECTED] Ph: (313)-384-9933
_______________________________________________ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
