Hi Shrikant,

Only the SplitControl.start is needed to start the radio stack,
nothing special. Can you verify that SplitControl.start is called?
Does this version of BLIP works on TelosB motes for you?

Best,
Miklos

On Thu, May 19, 2011 at 1:39 PM, Shrikant U Hallur
<[email protected]> wrote:
> Hi Miklos,
>
>     We are working on BLIP-rpl code ... which we downloaded from Tinyos
> svn repo  tinyos-main.googlecode.com/svn/trunk/ tinyos-main-read-only
> .. version we are using is r5510....
>
>      In this version BLIP uses cc2420 specific components at 2 files
> IPDispatchC and Ieee154addressC, and i changed at these two places
> and used Ieee154MessageC and ActiveMessageAddressC respectively..
> but this code is not working for IRIS .. while analysing this i
> found that rf230 radio is not starting at all... In the file
> RF230DriverlayerP.nc the state of command 'cmd' is not changing to
> CMC_SIGNAL_DONE it is remaining CMD_NONE only.... and hence this
> component not signalling RadioState.done() to upper component... i
> am not understanding why radio state is not changing ... do i need
> to call any other additional command other than
> splitControl.start()?  to make radio start?... can i get any
> documents on rf230 radio stack implementation which helps me to
> understand its implementation?.... please help...
>
>
> Thanks&Regards,
> Shrikant U Hallur
>
>
>  Hi Shrikant,
>>
>> I never used BLIP, but I was trying to get the RF230 driver in shape
>> to support BLIP. Can you point to which version of BLIP are you using?
>> Where are you downloading it?
>>
>> As far as I know, Ieee154MessageC worked on IRIS.
>>
>> Best,
>> Miklos
>>
>> On Thu, May 12, 2011 at 11:50 AM, Shrikant U Hallur
>> <[email protected]> wrote:
>>>
>>> Hello All,
>>>
>>>      I am Shrikant from IISc Bangalore. i am trying to port BLIP/RPL
>>> on Iris motes, I went through the code and found that code is
>>> exclusivly written for CC2420 radio unlike the earlier BLIP/Hydro
>>> where we could able to implement BLIP on Iris... So i did the
>>> following changes in the BLIP/RPL code in order to make it work on
>>> Iris.
>>>
>>>       I found that in BLIP code two files 'IPDispatchC.nc' and
>>> 'Ieee154AddressC.nc' are wired to CC2420 specific components, i
>>> changed those wiring and wired IPDispatchP to Ieee154MessageC
>>> instead of CC2420RadioC and wired Ieee154AddressP to
>>> ActiveMessageAddressC instead of CC2420ControlC, (same way as in
>>> earlier BLIP/Hydro code) and made correspondent changes in there
>>> interfaces also..
>>>
>>>     The modified code works well with TelosB motes, i can able to ping
>>> motes successfully, but code is not working for Iris, it was
>>> compilling successfully but Iris mote is not sending any kind of
>>> messages.
>>>
>>>      While analysing the problem i found IPDispatchP is not getting
>>> 'RadioControl.startDone' event,but it is successfully calling
>>> RadioControl.start command to Ieee154MessageC. That means to say
>>> Ieee154MessageC component found under /tos/platforms/iris/ is not
>>> sending the required event.... is the available Ieee154MessageC in
>>> Iris is proper working code?.. or i am missing something in this
>>> porting process?..  and which is making existing Ieee154MessageC not
>>> to work correctly?...
>>>
>>>      Please help me in this... is there anybody working in making
>>> BLIP/RPL code independent of platforms? or is ther any recent
>>> version which already have this?... kindly help...
>>>
>>>
>>> Regards,
>>> Shrikant U Hallur
>>> IISC, Bangalore.
>>>
>>>
>>>
>>>
>>> --
>>> This message has been scanned for viruses and
>>> dangerous content by MailScanner, and is
>>> believed to be clean.
>>>
>>>
>>
>> --
>> This message has been scanned for viruses and
>> dangerous content by MailScanner, and is
>> believed to be clean.
>>
>>
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
>

_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Reply via email to