Linux IEEE 802.15.4 and 6LoWPAN development
 help / color / mirror / Atom feed
From: Josef Filzmaier <j.filzmaier@gmx.at>
To: linux-wpan@vger.kernel.org
Subject: AT86RF212 based USB-Stick (HUL)
Date: Wed, 02 Aug 2017 18:00:45 +0200	[thread overview]
Message-ID: <1909067.WLLFt4d09f@hella-laptop> (raw)

Hello everyone!

Disclaimer: I am new to kernel driver development

I'm trying to get the BUSWARE HUL stick [1] to work using the atusb driver.
I know this is not officially supported, but this stick is very similar to the 
rzusb stick which is stated work experimentally on the linux-wpan website.

I flashed the stick with the atben firmware using dfu-programmer and it seems to 
be working quite nicely.

I'm on Kernel 4.9 lts with arm architecture (raspberry pi b+)

I have modified the atusb driver to support the at86rf212 chip (inspired by the 
at86rf230 driver). It seems to be working just fine. I can configure the stick 
as i like with the iwpan tool, so the configuration over usb seems to be 
working. Also, i can see the wpan0 interface and can create a lowpan interface 
on top of it (as described on the lowpan website).

However, using the lowpan interface has no effect. No data gets sent over USB. 
I am able to capture the traffic using tshark, but the data never arrives at the 
atusb driver's atusb_xmit() function.

My idea currently is to put printk statements within the kernel to detect 
where the data gets lost. I can capture the data with wireshark so i should be 
able to find my calls somewhere in the kernel code.

Do you have any suggestions as to where i should start my debugging adventure? 
I cannot seem to find where a socket call is initiated and how it is propageted 
down to the driver level.

Any help welcome!

[1] http://www.busware.de/tiki-index.php?page=RF212USB

-- 
Josef Filzmaier

             reply	other threads:[~2017-08-02 16:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-02 16:00 Josef Filzmaier [this message]
2017-08-03  6:59 ` AT86RF212 based USB-Stick (HUL) Stefan Schmidt
2017-08-03 13:44   ` Alexander Aring
  -- strict thread matches above, loose matches on Subject: below --
2017-08-03 14:26 Josef Filzmaier
2017-08-03 15:50 ` Stefan Schmidt
2017-08-03 20:51   ` Josef Filzmaier
2017-08-03 21:09     ` Stefan Schmidt
2017-08-16 15:33       ` Josef Filzmaier
2017-08-17  8:28         ` Josef Filzmaier
2017-08-17 10:13           ` Stefan Schmidt
2017-08-17 10:10         ` Stefan Schmidt
2017-08-17 11:14           ` Josef Filzmaier
2017-08-17 11:42             ` Stefan Schmidt
2017-08-18 10:26               ` Josef Filzmaier
2017-08-18 10:33                 ` Stefan Schmidt
2017-08-24 13:54                 ` Stefan Schmidt
     [not found] <526ff7aa-6342-4a8e-8278-0d76d897044e@email.android.com>
2017-08-29  7:30 ` Stefan Schmidt
2017-09-04 16:22   ` Josef Filzmaier
2017-09-11 11:13     ` Stefan Schmidt
2017-09-11 12:05       ` Josef Filzmaier

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=1909067.WLLFt4d09f@hella-laptop \
    --to=j.filzmaier@gmx.at \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox