[Tinyos-help]

[Spidernet Lists]

Hi Mirko,
I am trying the TOSSIM to simulate the applications "TestSerial" but i 
am getting the following error, can u tel me why?? because the only 
difference i have made to the platform is adding Led3 and its not able 
to find it.

[root at tinyos-devel TestSerial]# make chipconz sim
mkdir -p build/chipconz
  placing object files in build/chipconz
  writing XML schema to app.xml
  compiling TestSerialAppC to object file sim.o
ncc -c -shared -fPIC -o build/chipconz/sim.o -g -O0 -tossim 
-fnesc-nido-tosnodes=1000 -fnesc-simulate 
-fnesc-nido-motenumber=sim_node\(\)   -finline-limit=100000 -Wall 
-Wshadow -Wnesc-all -target=chipconz -fnesc-cfile=build/chipconz/app.c 
-board=  -Wno-nesc-data-race TestSerialAppC.nc   -fnesc-dump=components 
-fnesc-dump=variables -fnesc-dump=constants -fnesc-dump=typedefs 
-fnesc-dump=interfacedefs -fnesc-dump=tags -fnesc-dumpfile=app.xml
In component `LedsC':
/opt/tinyos-2.x/tos/system/LedsC.nc:46: cannot find `Led3'
make: *** [sim-exe] Error 1


I have made changes to PlatformLedsC,  /tos/system/LedC.nc, 
/tos/system/LedP.nc, /tos/system/NoLedP.nc, /tos/interfaces/Leds.nc

Do i need to make changes anywhere else as well to define a different 
platform... When i see the nesdoc, I can see that Led3 is added and can 
be seen graphically, then why is it giving an error while simulating...
My problem of implementing TestSerial still exists... It is sending the 
packets but not getting anything back.....Its showing

serial@/dev/ttyS0:19200: resynchronising
Sending packet 0
Sending packet 1
Sending packet 2
...

....


I am presently doing what you suggested in your last mail as well but in 
the meantime if you could guide me in any of the above matters, it would 
be great...



Cheers!!!!!!!
VJ


mirko bordignon wrote:
>> I am using tinyos-2.x only.. because i also read about its advantages
>> and other things.
> good thing
>
>> My platform also uses an external crystal of 32.768
>> KHz but they have given a pin outlet to put that crystal...
> I don't understand what you mean by "pin outlet", anyway if you are
> not sure if it is working you can use other timers meanwhile for
> millisecond timing, timer2 for example (micas do not use it, so it's
> available)
>
>> I have been able to program the test applications on to my platform
>> using avrdude..... I was earlier also able to load the programs written
>> in "C" language with the help of libraries given by Chipcon.
> ok, but try to write just in plain C with standard avr-libc tools,
> compile and upload, if you succeed without using any third part
> library you've got a kind if guarantee that the tinoys toolchain is ok
>
>> because a simple application like "Blink" should work as i have
>> changed the ports in the "PlatformLedsC.nc" file as Led's hook up on my
>> platform elsewhere to Mica motes....
> wait, Blink is not that subtle application since it uses millisecond
> timer abstraction, hence requiring (part of) the timer subsystem to be
> in place, not just the leds ... and if you're not sure about your
> port, this is something to check first
>
>> Can you suggest how can i solve this or approach to solve it..
> my suggestion is: take the Blink application and unwire the timer 
> stuff from it:
> remove the "uses timer interface" which appears three time in BlinkC,
> and remove everything timer related from the BlinkAppC wiring. Then
> you can just try too turn on/off your leds in the booted event, if it
> does work at least you know that tinyos succeeds to boot correctly
> -and you're on your way to success- , if it doesn't try to turn them
> on and off manually by setting DDRx and PORTx (where x is the port
> your leds are attached to) properly, since it can be a bug of the leds
> subsystem
>
>> Cheers!!!!
>> VJ
>
> bye
> mirko
>