[riot-users] RPL on the nRF51822?
hauke.petersen at fu-berlin.de
Tue Nov 4 11:56:21 CET 2014
the rpl_udp example will unfortunately not work so far. The reason for
this is that the NRF radio is not linked to/does not implement the
transceiver interface as of now. So getting the NRF to work with the
network stack does require the completion of 2 tasks: i) finishing the
low-level radio driver so it works reliable and ii) linking the driver
to RIOTs transceiver interface. The branch you checked out is only aimed
at completing i), so ii) is still a TODO.
Maybe have a look at the tranceiver (sys/include/transceiver.h and
sys/transceiver/transceiver.c) for information on fast (but old way) of
linking the radio to the network stack. An important note though: we are
currently in the process of remodeling the network driver interface.
@Martine, can you give more information about this?
Then happy hacking!
On 04.11.2014 11:35, Trevor Jordan wrote:
> Have cloned that fork and checked out that branch. I am however
> getting similar errors when trying to compile the rpl_udp example. ie:
> "There are unsatisfied feature requirements: transceiver"
> Where/how should I tell make to use the nrf51 radio?
> On 31/10/14 17:36, Hauke Petersen wrote:
>> Hi Trevor,
>> the work on the transceiver/radio driver is started and well on its
>> way, I had however due to shifted priorities over the last weeks no
>> time to finish it. You can find the code in my branch in . You are
>> very welcome to test/fix the code. I will get onto it again probably
>> only after next week...
>> Let me know if you need additional infos - anytime :-)
>>  https://github.com/haukepetersen/RIOT/tree/add_nrf_radio
>> On 31.10.2014 15:00, Trevor Jordan wrote:
>>> I don't really want to use ble, or the softdevice. I'd rather just
>>> use the radio as if it were a separate 2.4GHz data transceiver like
>>> the nRF24L01. What would I need to do to make that work?
>>> On 31/10/14 14:52, Christian Mehlis wrote:
>>>> Am 31.10.2014 um 14:10 schrieb Trevor Jordan:
>>>>> It seems the nRF51822 is supported, but not it's internal
>>>>> Is that correct?
>>>> Yes, RIOT is not using the the manufacturer code/binary
>>>> blob/softdevice in any way, so we need to write the ble driver (and
>>>> all the other features) from scratch.
>>>> @hauke has some initial ble code, I think.
>>>> ps: the timer on this platform is currently buggy, but code is on
>>>> its way :)
>>>> pps: in case you want to add some board, have a look at this PR:
>>>> https://github.com/RIOT-OS/RIOT/pull/1896 (nRF51822)
>>>> Christian Mehlis
>>>> users mailing list
>>>> users at riot-os.org
>>> users mailing list
>>> users at riot-os.org
>> users mailing list
>> users at riot-os.org
> users mailing list
> users at riot-os.org
More information about the users