Yes, cool work. We should also consider integrating that atm328p/uno
support to tinyos-main in due time if Johny is interested.

--Vlado


On Sat, Jan 12, 2013 at 5:08 AM, Eric Decker <cire...@gmail.com> wrote:

>
> Hey Markus,
>
> I'd like to capture your code and Johnny's as well in tp-freeforall.
>
>
> On Fri, Jan 11, 2013 at 1:17 AM, Markus Becker 
> <m...@comnets.uni-bremen.de>wrote:
>
>> [...]
>> >
>> > Thanks for the helpful feedback Antonio.  I'd be interested in learning
>> > about other similar projects out there if you (or anybody else) knows of
>> > ones that exist.
>> Hi.
>>
>> I have done an adapter board for an MRF24J40MA 802.15.4 module. That
>> module
>> sells at <10EUR and is supported by the 802.15.4 stack of Linux version
>> 3.7
>> and up. I have backported the 15.4 driver to the 3.6 RPi kernel as well.
>> The
>> appropriate board config for the SPI and the driver are in
>> https://github.com/markushx/linux
>>
>> At the moment I am still struggling a little with attaching that module
>> to an
>> Arduino Uno, based on Johny Mattsson's TinyOS port to Arduino:
>> https://github.com/markushx/tinyos-arduino-MRF24J40MA
>>
>> Markus
>>
>> > With regard to your comment about Raspberry Pi, I totally agree, it is a
>> > much cheaper alternative (and a cool board!).  However, for some people,
>> > the BeagleBone is an attractive platform BECAUSE of the more expensive
>> > Cortex™-A8 processor and feature set.  For example, Ubuntu for ARM is
>> > built for Cortex™-A8 and beyond with all the optimization features the
>> > ARMv7 architecture offers, and can run on the BeagleBone.  However,
>> > Ubuntu is unwilling to support the Raspberry Pi because the processor is
>> > an older Broadcom ARMv6 (http://elinux.org/RPi_Distributions#Ubuntu).
>> >
>> > Obviously, a design constraint for the Epic Cape was not cost (if I'm
>> > really being honest, the ONLY constraint was "quick, what can I finish
>> > in two days before the contest deadline in-between games of rummikub
>> > with my inlaws!?!?" hehe ;)  Using the Epic module + carrier cape adds
>> > significant cost to the overall design, but made my life easier.  The
>> > goal for this first prototype was basically to get to a simple, clean
>> > piece of hardware using building blocks I have experience with (i.e.
>> > Epic).  There are many cheaper and better ways to design a small 15.4
>> > boarder router, but for some people, this combination of well supported
>> > hardware platforms might be attractive.
>> >
>> > Chris
>> >
>> > _______________________________________________
>> > Tinyos-help mailing list
>> > Tinyos-help@millennium.berkeley.edu
>> >
>> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>> ------------------------------------------------
>> | Dipl.-Ing. Markus Becker
>> | Communication Networks
>> | TZI - Center for Computing Technologies
>> | University Bremen
>> | Germany
>> ------------------------------------------------
>> | web: http://www.comnets.uni-bremen.de/~mab/
>> | mailto: m...@comnets.uni-bremen.de
>> | telephone: +49 421 218 62379
>> | building: NW1 room: N2260
>> ------------------------------------------------
>>
>> _______________________________________________
>> Tinyos-help mailing list
>> Tinyos-help@millennium.berkeley.edu
>> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
>
>
>
> --
> Eric B. Decker
> Senior (over 50 :-) Researcher
>
>
> _______________________________________________
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
_______________________________________________
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Reply via email to