From: Stefan Schmidt <stefan@osg.samsung.com>
To: Michael Richardson <mcr@sandelman.ca>,
Geoff Chapman <geoff.chapman@mmbresearch.com>
Cc: Alexander Aring <alex.aring@gmail.com>, linux-wpan@vger.kernel.org
Subject: Re: atusb availability
Date: Wed, 27 May 2015 15:18:15 +0200 [thread overview]
Message-ID: <5565C417.70505@osg.samsung.com> (raw)
In-Reply-To: <11929.1432731633@sandelman.ca>
Hello.
On 27/05/15 15:00, Michael Richardson wrote:
> Geoff Chapman <geoff.chapman@mmbresearch.com> wrote:
> > Hi Stefan,
>
> >> Nice, that you used the same schematics and build your boards!
>
> >> Do you by any chance have the infrastructure to handle a bigger run of
> >>these? We often get asked about such a device >for easy hacking with
> >>ieee802154 from a laptop or desktop without any SPI connections
> >>available.
>
> > This is exactly the reason I am interested in the device. I want to
> > set up a simple 6LoWPAN network, but do not have any SPI connections.
>
> I also want to be able to speak 15.4 from a laptop system for diagnostics
> and ease-of-coding purposes. It did take me awhile to figure out that the
> atusb was not a product I could buy... I too would be interested.
Jupp, development convenience really pays off here. Alex is working on
supporting the Atmel usb dongle as well.
http://www.atmel.com/tools/rzusbstick.aspx
It is very similar to the atusb device and Alex already have it working
with the atusb firmware and the atusb mainline driver. So this could be
a device for you. Needs a avr programmer for the firmware writing though.
>
> >> The run Werner did was around 100 - 120 pieces for atusb IIRC. My best
> >>guess would be that there could be interest for another 50-100
> >>depending on the promotions.
>
> > So-far, we have only built two atusb modules. We are in the process
> > of loading the firmware and testing, so I am not sure if the boards
> > are functional yet. At this time, we are not set up to produce
> > numbers in the 50-100 range. This may change once we successfully
> > test the boards.
>
> Put it on kickstarter?
Yeah, that could work. Problems is that someone has to run this.
Production wise but even more logistics and biz wise. I'm not that one,
sorry.
Given that atusb is open hardware with all schematics, production
testing software, firmare, etc available a lot more people could do this
if they are interested.
regards
Stefan Schmidt
next prev parent reply other threads:[~2015-05-27 13:18 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
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 [this message]
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=5565C417.70505@osg.samsung.com \
--to=stefan@osg.samsung.com \
--cc=alex.aring@gmail.com \
--cc=geoff.chapman@mmbresearch.com \
--cc=linux-wpan@vger.kernel.org \
--cc=mcr@sandelman.ca \
/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.