Hi Ken, Well, I figured this would be the place to reach the devs :)
I think I've answered my own questions in the mean time though; it seems @hexluthor has been doing a lot of work on cc2538 support over the past year or so, including (from what I can tell) a more-or-less complete RF driver implementation (PR #2198). So I'm looking forward to that getting merged. Still some work to do on drivers for the OpenBattery sensors though, so I'll probably look into that. /Aaron 2015-12-14 19:06 GMT+13:00 Ken Bannister <kb...@runbox.com>: > Aaron, > > Great idea to improve the OpenMote integration! Have you tried contacting > the OpenMote developers for guidance? In my experience they have been very > helpful and accommodating. I expect they would appreciate your effort. > > Ken > > > On 12/12/2015 10:06 PM, Aaron Sowry wrote: >> >> Hi, >> >> I'd like to try and improve RIOT OS support for the OpenMote platform >> in general, and the TI cc2538 MCU specifically. The most pressing item >> for me currently is RF support, but I would also like to see support >> for the ROM API and a few other things (including the sensors on the >> OpenBattery board, eventually). >> >> I'm new to RIOT and thought I'd try to clear up a few things before >> getting my hands dirty, so you'll have to excuse me if some of these >> questions seem obvious/stupid/irrelevant: >> >> 1) TI provide open-source firmware for the cc2538, but I can't find >> any trace of it in the RIOT tree. It seems like there are a few >> cherry-picked bits and pieces but not in the same format/layout as the >> original firmware. Is there a reason for not including TI's firmware >> in the tree verbatim (I'm thinking licensing/re-distribution issues, >> architectural or coding-style differences, etc)? It seems like this >> would make fully supporting the MCU a lot easier. >> >> 2) To avoid duplication of effort, is there anyone else already >> working on RF support for this chip? >> >> 3) Where should a hypothetical RF driver for the cc2538 live in the >> tree? Since it's on-chip should it live in the cpu subdir? Or >> programmed as a "module" the same way as for peripherals? >> >> 4) Are there any guidelines or example code for this kind of work? The >> only other on-chip RF driver I could find to use as a reference is for >> the nrf51. Perhaps this will do to get me on the right track, but just >> thought I'd check if there's something I missed. >> >> Thanks! >> /Aaron >> _______________________________________________ >> devel mailing list >> devel@riot-os.org >> https://lists.riot-os.org/mailman/listinfo/devel > > > _______________________________________________ > devel mailing list > devel@riot-os.org > https://lists.riot-os.org/mailman/listinfo/devel _______________________________________________ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
