Hi Dean,
there is (freshly) also an open PR for the Xbee S1 module driver [1], so
these will be an option for STM32F4discovery boards very soon...
Cheers,
Hauke
[1] https://github.com/RIOT-OS/RIOT/pull/2695
On 23.03.2015 09:13, Peter Kietzmann wrote:
Hi Dean,
I guess most of the STM32F4discovery-users are not strongly interested
in radio communication. However, in general you can use any external
transceiver that is based on SPI or I2C (and of course has RIOT
support). Currently we *just* have the lowlevel support for the
proprietary nrf24l01+ transceiver [1]. I will do the adaptation to the
ng_netdev interface according to the new network stack when this is in
a stable state.
Also there are plans to add support for the external 802.15.4
transceiver MRF24J40MA. But I can't tell when this will be done.
Best,
Peter
[1] http://www.nordicsemi.com/eng/Products/2.4GHz-RF/nRF24L01P
[2] http://www.microchip.com/wwwproducts/Devices.aspx?product=MRF24J40MA
Am 21.03.2015 um 22:23 schrieb Dean Hall:
I'm curious what radio people are using with the STM32F4discovery?
any near 900 MHz?
BTW, if anyone is interested in voice-over-*, there is the codec2
project coming out of the amateur-radio world that has the best voice
compression rates for an open-source codec [1]. codec2 is ported to
the STM32F4 (requires the FPU). I know mesh isn't quite suited for
reliable multi-hop streaming, but I believe it would be sufficient
for delay-tolerant push-to-talk service.
thanks,
!!Dean
[1] http://www.rowetel.com/blog/?page_id=452
_______________________________________________
users mailing list
[email protected]
http://lists.riot-os.org/mailman/listinfo/users
_______________________________________________
users mailing list
[email protected]
http://lists.riot-os.org/mailman/listinfo/users
