All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Geoff Chapman <geoff.chapman@mmbresearch.com>
Cc: linux-wpan@vger.kernel.org
Subject: Re: atusb availability
Date: Wed, 13 May 2015 22:05:51 +0200	[thread overview]
Message-ID: <20150513200547.GB820@omega> (raw)
In-Reply-To: <CAHwW563+_YBjKLU7Pm8igBeOmWfUg_VEMhQ9Y-GosTdCPLBGUw@mail.gmail.com>

On Wed, May 13, 2015 at 01:24:13PM -0400, Geoff Chapman wrote:
> Hi Alex,
> I just wanted to thank-you for your reply, it certainly helped with my
> understanding.  Initially, I thought the device was a HardMAC device,
> so thank-you for correcting me on that.  It seems that the device
> simply implements a USB-to-SPI interface.
> 
> I have used the schematics at [0] to build a few boards of my own.  I
> would like to use the two boards to send data between two laptop
> computers running linux.
> The description at [1] indicates that the ATMega firmware implements a
> "home-brew protocol on top of USB".  My plan is to do the following:
> 
> 1. Examine the source ATUSB firmware source code to determine the
> home-brew protocol.

that should work, this is what we try to do with the rzusbstick [0],
which have much identically parts like atusb (but atusb is much better
;-))

Then we just need to port the firmware to the rzusbstick.

> 2. Write some application software in C for the two linux PCs using
> Netlink sockets to communicate with the devices and transfer data
> between the two PCs.
> 

No netlink sockets, it's simple an IPv6 socket. What you missing here is
the atusb driver which is not mainline, but I recently send a patch to
support basic operation for atusb. I hope we getting this driver
mainline the next days, if you speak the exactly protocols then it
should work. But _note_ the protocol contains at86rf231 specific
commands which do a register write, look for function:

atusb_write_reg and atusb_read_reg.

Then maybe you need to insert runtime decisions when you not using the
same transceiver. Of course you can send patches for this to make this
behaviour more generic or runtime change that a different register
setting is used.

What I mean is that the protocol isn't a generic 802.15.4 protocol for
all transceivers, but we could make it to somewhat like that. Or you
make different runtime changes when detecting device type while probing.

- Alex

[0] http://www.atmel.com/tools/rzusbstick.aspx

  reply	other threads:[~2015-05-13 20:05 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
2015-05-13 17:24   ` Geoff Chapman
2015-05-13 20:05     ` Alexander Aring [this message]
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=20150513200547.GB820@omega \
    --to=alex.aring@gmail.com \
    --cc=geoff.chapman@mmbresearch.com \
    --cc=linux-wpan@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.