as Chanque stated, the Arduino-mega2560 has no transceiver on it. In general I’d recommend to use one of the 32bit arm-cortex based platforms as they have the best support for RIOT. The “Atmel samr21 xplained pro” for example has an onboard IEEE802.15.4 transceiver, but therefore it’s a bit pricey (~40€). If you scroll through RIOT/boards* you can get an overview of our supported platforms.
Actually, we have a Xbee transceiver hardware attached to Arduino-mega2560. My question is that “Does RIOT has the driver support for some transceiver hardware (for example, Xbee transceiver) for Arduino mega 2560 boards?”. I found it looks like there is no driver support for any transceiver in RIOT. Without the driver support of RIOT, transceiver won’t work.
Actually, we have a Xbee transceiver hardware attached to
Arduino-mega2560. My question is that "Does RIOT has the driver support for
some transceiver hardware (for example, Xbee transceiver) for Arduino mega
RIOT's design has architecture-independent drivers. Xbee is supported.
You should be able to use this combination.
That said, the network stack is in flux right now. While link-layer
communication should work rather nice, higher layers, e.g., 6lowpan, are
in stabilzation phase right now.
in addition to Kaspars mail: The Arduino-mega2560 has no GPIO implementation right now (and also no SPI). That's why there is no transceiver support even if we have this architecure-independet drivers. You could use other boards to drive your Xbee like stm boards or arduino-due. They are cheaper but you need cables. (When using arduino-due be aware of the pinout, I'm not sure if we already managed to configure the pins so one could just plug the Xbee shield on the board).
Regarding the Atmel sam21: Even if the status is "in progress" I recommend that platform. It is well supported in RIOT and used by many of our core developers. I think "in progress" means that not all features are implemented now. But the most are, right now.
Did you realize that the Xbee is based on Uart like Hauke stated? I totally forgot that. Means that you may be able to use it with the mega2560. Still, if it’s not about the money or the 8-bit avr stuff I’d recommend to use the Atmel board.
The board I am talking about is this one:
AFAIK ccn-lite is based on the old network stack which is not maintained anymore. Doesn’t mean that nobody on the mailing list could answer specific questions. I don’t now much about the latest status and future plans of ccn-lite. As far as I see it, the old transceiver driver for Atmel’s transceiver is still in RIOT master. Would be nice if someone with more knowledge can report about the ccn-lite status! Best, Peter
don't know if I got you correctly. Just in addition: The Atmel board has an on board IEEE802.15.4. transceiver. So if you are not dependent on the Xbee module it could be comfortable to use this instead of an external module. Otherwise I think you suggested to first try the Xbee+Arduino-mega2560 solution and then go for the Atmel board...
About the sensor selection for the sam21 borad , I am confused about it.
http://www.mouser.com/ProductDetail/Atmel/ATIO1-XPRO/?qs=%2fha2pyFaduhtOCTaz1iZVyfMwgvMHCxNg1zq5ZaphoVS1gdRKq6VlQ%3d%3d This is the sensor we plan to buy. The sam21 board provides the SPI, UART interfaces which matches this sensor’s interface types. I don’t know if this sensor will work properly since it may need a board-specific driver for this sensor. Or, I have to choose a sensor from this list "http://riot-os.org/api/group__drivers.html " which lists the sensor with drivers implemented for RIOT? If so, I may have another problem: These sensors list in the above mentioned list may not fit the sam21 board which only provides SPI, UART interfaces (This means these sensor may require different interfaces that sam21 board doesn’t support.)
Regarding the Atmel extension board:
I did not cross check whether RIOT does support all the sensors on it. If it would, you theoretically only need to specify the peripheral interface each sensor is connected to. As long as Atmel did not do something weird (don't know, I never had this board in my hands), you would not need to implement a special driver for the extension board itself.
At least the temperature sensor is not supported by RIOT right now. However, like I said before, implementing drivers is not so hard.
Regarding the interfaces, you are mistaken.
First, the extension board needs more peripheral interfaces, not only UART and SPI.
For example, quoting the datasheet:
"IO1 Xplained Pro extension board features an Atmel AT30TSE758 temperature sensor chip with an 8kbit serial EEPROM inside. The sensor includes programmable high and low temperature alarms, user-selectable temperature resolution up to 12 bits, and an I2C/SMBus™ compatible serial interface."
Second, the samr21-xpro does feature more peripheral drivers.
"FEATURES_PROVIDED += periph_i2c"