Am 12.01.2015 um 19:55 schrieb Frank Holtz:
Hello Jan,
i work currently with nRF51 MCU. I have try'd to port RFDuino to plain
nRF51 chips and found this working and more complete project.
1 .RFDuino:
https://github.com/rfswarm/Board-RFduino/wiki/Board:-RFduino
(cpu/nrf51822/startup.c: LED_RED_TOGGLE undeclared -> comment out ->
should become ifdef/ifndef)
(PIN numbering a little bit strange did not investigate further ->
check UART)
What if LED_RED_TOGGLE is defined empty?
The convention in RIOT with this LED is set to:
1. This define maps to a free and usable LED on the board
2. In case there is no free and usable LED on the board, define it to a
GPIO port (you can attach a LED there)
3. This LED is usable from users code, so for portability of RIOT,
every platform *must* have this "LED" defined
3. BLE Stack:
I am realy pissed about nordic and the "open" rfduino BLE support.
Binary blob myass.
It might take some weeks but i got all the test hardware ready to
implement basic BLE support.
I'm not interested using BLE at the moment, but i found this:
http://code.google.com/p/btstack/ I think it's an good idea to check if
btstack can be ported to nRF51. This is widely more open than using
these Blobs from Nordic. btstack has ant support.
There are at least two open PRs for the nrf51822:
https://github.com/RIOT-OS/RIOT/pull/2014
https://github.com/RIOT-OS/RIOT/pull/2010
So feel free to test and comment to make this architecture a biger
success in RIOT:)!
To address the networking support of RIOT via BLE:
1. the new network stack(-architecture) is a generic IPv6/6low stack
2. the primary focus is currently 6low over 15.4
3. it is designed to work with different mac layers
4. in case you need something else than 6low and IPv6 eg. Zigbee or
full Bluetooth you need the vendor stack (which can't do 6low, afaik)
Hope this helps you:)
Best
Christian
_______________________________________________
devel mailing list
[email protected]
http://lists.riot-os.org/mailman/listinfo/devel
