From: Alexander Aring <alex.aring@gmail.com>
To: Geoff Chapman <geoff.chapman@mmbresearch.com>
Cc: linux-wpan@vger.kernel.org, werner@almesberger.net
Subject: Re: atusb availability
Date: Thu, 23 Apr 2015 10:30:55 +0200 [thread overview]
Message-ID: <20150423083052.GA1077@omega> (raw)
In-Reply-To: <CAHwW560VTApCL2a4c8uOMC2u-bWzenTf0vwH0pbeLZ3xNLuCOA@mail.gmail.com>
Hi,
I will try to answer a little bit the questions here.
On Tue, Apr 21, 2015 at 11:55:35AM -0400, Geoff Chapman wrote:
> Hello Mr. Almesberger,
>
> My name is Geoff Chapman, and I am working on project to setup a
> simple 6loWPAN network between two laptops running Linux. I am very
> interested in your work on the atusb device detailed at [0], and would
> like to use the device in my project. On each laptop, I would like to
> use one of your atusb devices to implement the 802.15.4 MAC/PHY, while
> using the 6loWPAN stack in the linux kernel. I picture something like
> the following setup for each laptop:
>
>
> Linux Laptop:
>
> | Application Layer |
> |
> socket API
> |
> | 6LoWPAN stack |
> |
> |
> <-----------------USB---------------> atusb
> device implementing 802.15.4 MAC/PHY (ATMega32U2 + at86rf233)
>
So you want a HardMAC driver here. That's not how atusb works currently.
The atusb transceiver is a SoftMAC transceiver with _little_ mac
functionality, this contains checks on dsn/bsn to do some correct
frame deliviery in the firmware to the usb host, if I remember
correctly. I think you know that and you want to put full MAC functionality
into the atusb firmware.
We don't have currently any HardMAC drivers mainline, but the idea is to
handle the HardMAC transceivers like wireless, so with the existing
architecture we have a possibility to access HardMAC transceivers and
write HardMAC drivers. But we don't have a HardMAC driver currently and
I think you need to making some movements from SoftMAC layer (net/mac802154)
to cfg802154/netlink (net/ieee802154) layer, or you have workarounds for
that in your driver layer. I would say for HardMAC drivers go ahead and
try to implement your stuff and orient you at existing wireless HardMAC
drivers and simple don't use any functionality from (net/mac802154)
directory.
Another thing is that I don't believe that ATMega32U2 can full store a compliant
802.15.4 stack (maybe depends on your use case), because the ATMega32U2 has 32
KB flash memory. Maybe I am wrong here, if you think you can do that
then I would give it a try.
Another solution would maybe the RZRAVENUSBSTICK [2] which contains and
AT90USB1287 with at86rf230. In my opinion it's the same like atusb but atusb
contains an easier to use 802.15.4 transceiver, smaller mcu (bigger one is not
necessary here), and of course the case is smaller, etc. The AT90USB1287 has a
128 KB flash memory. Schematics of RZRAVENUSBSTICK can be found at [3].
>
> I have tried purchasing two atusb devices at [1] without any luck, as
> they no longer sell the devices.
> I have two questions:
>
> 1. Do you have any atusb devices available for purchase?
> 2. If you have none for purchase, do you have the schematics available
> that I can use to wire-up my own atusb device? The schematic link on
> your site [2] seems to be broken.
>
The schematics for atusb can be found at the ben-wpan repository [0],
which also includes the firmware, etc., but this requires the great tool
kicad [1] and _maybe_ some additional libs for electronic components.
- Alex
[0] http://projects.qi-hardware.com/index.php/p/ben-wpan/source/tree/master/
[1] http://www.kicad-pcb.org/display/KICAD/KiCad+EDA+Software+Suite
[2] http://www.atmel.com/tools/rzusbstick.aspx
[3] http://www.atmel.com/Images/doc8117.pdf page 22
next prev parent reply other threads:[~2015-04-23 8:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 15:55 atusb availability Geoff Chapman
2015-04-23 8:30 ` Alexander Aring [this message]
2015-05-13 17:24 ` Geoff Chapman
2015-05-13 20:05 ` Alexander Aring
2015-05-22 13:05 ` Stefan Schmidt
2015-05-26 18:29 ` Geoff Chapman
2015-05-27 9:06 ` Stefan Schmidt
2015-05-27 13:00 ` Michael Richardson
2015-05-27 13:18 ` Stefan Schmidt
2015-05-27 13:29 ` Ralph Droms (rdroms)
2015-05-27 13:32 ` Stefan Schmidt
2015-05-27 13:47 ` Alexander Aring
2015-05-27 16:04 ` Ralph Droms (rdroms)
2015-06-02 16:03 ` Alexander Aring
2015-05-27 16:06 ` Ralph Droms (rdroms)
2015-05-27 16:36 ` Stefan Schmidt
2015-05-27 14:00 ` Michael Richardson
2015-05-27 16:07 ` Ralph Droms (rdroms)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150423083052.GA1077@omega \
--to=alex.aring@gmail.com \
--cc=geoff.chapman@mmbresearch.com \
--cc=linux-wpan@vger.kernel.org \
--cc=werner@almesberger.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox