RIOT - CC26x0 Port ready-ness

Hello RIOT Devel,

I’m looking at adopting RIOT for a new commercial product build using the CC2650 chipset.

I would like to connect with any developers working on a cc26x0 port. I would like to understand the ready-ness of any branches and willingness to collaborate. I’m happy to contribute to a project to help make it work, if it’s looking viable for a stable product release.

Regards Darren

Ph: 0210350341 Skype: darren.bainbridge Linkedin: darren-bainbridge http://www.myapiary.co.nz/ http://findmyhive.com/

MyApiary Logo Full color white background web small.png

DISCLAIMER: This electronic message and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited

Hi,

I would like to connect with any developers working on a cc26x0 port.

I worked for a start-up which intended to use RIOT and the CC2650STK as a platform for a future product. I left the company and had no time since then to continue to work on it, which is a shame since I've had the assumption that it wouldn't be that much work to a have basic working radio.

I would like to understand the ready-ness of any branches and willingness

The repository is over here

https://github.com/SWIE-IO/RIOT

and the main branch is

https://github.com/SWIE-IO/RIOT/tree/swie_802154_frey

We ran into some timer issues. If you have some time left, it would be amazing if you would look into this. Also the actual interface to RIOT for the driver is missing (meaning RIOT/drivers/cc26x0).

The IEEE 802.15.4 part needs some work and there was a bug I wanted to fix (which should be doable).

I would like to do some refactoring of the radio code (the naming is not really consistent since three different people were working on it) and we could talk about the radio again? This would actually allow me to give you a (better) summary what's working and what's not, and how things are structured - if that's okay for you?

Anyway, I'm wondering what the best way would be to "centralize" the code again. Clearly, I'm not going to contribute to the repository of my former employer and the code is nowadays somehow spread across different repositories.

Best, Michael

Hi Michael, Thanks for replying.

I have started looking at the different repos for C26x0. Who is or owns the SWIE-IO repo. when reading the main RIOT wiki it’s not mentioned as a C26x0 development branch also it looks quite advanced.

Darren

Hi,

I have started looking at the different repos for C26x0. Who is or owns the SWIE-IO repo. when reading the main RIOT wiki it's not

The repositories are owned by Swissmic [1], a swiss startup.

mentioned as a C26x0 development branch also it looks quite advanced.

The original work was started by Leon George, a student at FUB (afair). Florent-Val�ry Coen contributed the radio code - particularly BLE. Florent was also with SWIE, but left at the end of July for his master thesis. Nicholas C. Jackson provided support for the programmer/debugger. I don't know if Nicholas is doing this in his spare time or if he is with a company/university. At least that's my understanding. If I missed to mention somebody I'm really sorry!

Providing support for CC26x0 is part of Leons thesis and hence, he "owns" the pull request. Florent and I decided to work on one repository (the swie repository) in different branches. The idea was to create a new branch which would include the feature branches we were working on and open pull requests from that particular branch.

However, since we both don't work at SWIE anymore we probably need another place to clean up the code and contribute to it. The easiest way is probably that I'm fetching the old branch, clean it up and commit to the PR branch (iff features are working). But I'm open for other suggestions!

Best, Michael

[1] https://www.swie.io/

Hi Michael,

I plan to work on CC2650 (phyWAVE-CC2650 from phytec). Could you tell us what is the most up-to-date repository/branch, and a detailed status of the code ?

So interested people could give a try, contribute ?

Thanks,

Olivier Fauchon