Hello Hauke, and thanks for the info.
> You can't find it because we are not using it... The main reason for this is
> manifold: TI's firmware is bloated, in-efficient and I am not sure about the
> licensing (though this might not be an issue). Personally I also doubt, that
> it makes porting so m
Hi,
just wanted to link my self in.
I am currently working on a port for the openmote, but I am only making
slow progress so far,
as I have only limited time unfortunately.
You can find my fork here: https://github.com/AnonMall/RIOT/tree/network
Right now the driver for the RF is sending out
Hi Aaron,
good to hear you want to put some work into the OpenMote! Let me try to
answer your questions best to my knowledge:
On 13.12.2015 04:06, 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
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 impl
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
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 boa
