From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ua0-f169.google.com ([209.85.217.169]:52719 "EHLO mail-ua0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S968527AbdIZMHn (ORCPT ); Tue, 26 Sep 2017 08:07:43 -0400 Received: by mail-ua0-f169.google.com with SMTP id n38so6264851uai.9 for ; Tue, 26 Sep 2017 05:07:43 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <3b39d66c-9ec5-56b1-c612-2bfdf10d6a93@osg.samsung.com> References: <3b39d66c-9ec5-56b1-c612-2bfdf10d6a93@osg.samsung.com> From: Alexander Aring Date: Tue, 26 Sep 2017 08:07:42 -0400 Message-ID: Subject: Re: new atusb firmware candidate Content-Type: text/plain; charset="UTF-8" Sender: linux-wpan-owner@vger.kernel.org List-ID: To: Stefan Schmidt Cc: linux-wpan - ML Hi, On Tue, Sep 26, 2017 at 5:26 AM, Stefan Schmidt wrote: > Hello. > > On 09/25/2017 03:35 PM, Alexander Aring wrote: >> Hi, >> >> according to qi-hardware irc channel, I got notice about this transceivers [0]. >> Maybe a new atusb candidate? Or maybe they already use a non-upstream >> implementation? :-) > > Looking at their manual they are focuses on delivering a Arduino compatible solution. > >> Prices are okay (better than the very expensive one from atmel). > > Prices are good and they are still available. > > I had a quick look at their schematics in the user manuals: > http://freaklabsstore.com/pub/FREAKUSB-900MHz%20v1.1%20Datasheet.pdf > http://freaklabsstore.com/pub/FREAKUSB-2.4GHZ%20v1.1a%20Datasheet.pdf > > They use the at86rf231 and at86rf212 transceivers (I still hope for a 215 device) > > The problem I see is that USB is connected to a FTDI usb serial bridge chip instead directly to the Atmel MCU. > > I have no idea if the FTDI can be swichted into a passthrough mode. If that is the case re-using the existing atusb firmware and USB > protocol to the kernel driver should not be to hard for someone interested. > > If the passthrough is not possible and the whole communication protocol has to go over the serial line that would be significant more work. > Adapting the protocol over a serial line, adapting firmware and adapting the kernel driver. > I see, yes it sounds for me like bring back the serial protocol [0]. Also bluetooth has a lot of uart connected transceiver... but serial over bus protocol is specified by bluetooth... Next time I need to look deeper into it, just saw MCU and USB connector... it's bad that the USB feature is for UART only... I lookup the MCU datasheet, the USB doesn't has any USB support. :-( Serial protocol driver is of course more work but also another possibility to write a Contiki/RIOT/*zephyr* app to use these operating systems as a firmware to access transceivers. - Alex [0] https://github.com/linux-wpan/ieee802154-serial-protocol-version2/blob/master/ieee802154-serial-protocol-2.md