From: Alexander Aring <alex.aring@gmail.com>
To: Baptiste Clenet <bapclenet@gmail.com>
Cc: Stefan Schmidt <stefan@osg.samsung.com>, linux-wpan@vger.kernel.org
Subject: Re: What is SAM value? "ieee802154 phy0 wpan0: SAM value 0x3 not supported"
Date: Mon, 27 Jul 2015 19:28:17 +0200 [thread overview]
Message-ID: <20150727172816.GB794@omega> (raw)
In-Reply-To: <CAPpUg6OxkeS4T1vkmdhcL4xYvCp7e-k+SkO2gvxxUOYV6t1qVw@mail.gmail.com>
On Mon, Jul 27, 2015 at 05:55:27PM +0200, Baptiste Clenet wrote:
> 2015-07-27 17:13 GMT+02:00 Baptiste Clenet <bapclenet@gmail.com>:
> >>> Then forget that and make some at86rf230 driver debug messages. See
> >>> "print_hex_dump" [0]. Add this add skb->data in at86rf230_xmit and
> >>> at86rf230_rx_read_frame_complete (but after the skb is filled with data,
> >>> otherwise it makes no sense).
> >>>
> >>> This will allow us to see what's the lowest layer is. If the transmit
> >>> side looks correct, but receive side looks weird then I suppose
> >>> something is wrong again with your spi setup.
> >>>
> >>> The reason is that we get the lowest dump of the transmitted and
> >>> received buffer and nobody touched that buffer then.
> >
> > I dump the packet in at86rf230_xmit and
> > at86rf230_rx_read_frame_complete (just before
> > ieee802154_rx_irqsafe(lp->hw, skb, lqi)). This is wireshark analyse of
> > the two packets. The first one is correct and comes from the sender,
> > the second is from the receiver (I manually created the hex dump file)
> > which is wrong! So something seem to occur when the frame goes to the
> > transceiver.
ah, sorry I misunderstood you. So you have capture the raw data for
transmit and receiving and it differs. Then I have still no idea what's
wrong on your side. :-)
- Alex
next prev parent reply other threads:[~2015-07-27 17:28 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-24 7:56 What is SAM value? "ieee802154 phy0 wpan0: SAM value 0x3 not supported" Baptiste Clenet
2015-07-24 8:31 ` Alexander Aring
2015-07-24 8:47 ` Baptiste Clenet
2015-07-24 9:02 ` Baptiste Clenet
2015-07-24 9:45 ` Baptiste Clenet
2015-07-24 9:53 ` Alexander Aring
2015-07-24 9:48 ` Alexander Aring
2015-07-24 9:56 ` Baptiste Clenet
2015-07-24 10:18 ` Alexander Aring
2015-07-24 12:03 ` Baptiste Clenet
2015-07-24 12:13 ` Alexander Aring
2015-07-24 12:53 ` Baptiste Clenet
2015-07-24 13:07 ` Alexander Aring
2015-07-24 14:45 ` Baptiste Clenet
2015-07-24 14:51 ` Stefan Schmidt
2015-07-24 15:14 ` Baptiste Clenet
2015-07-24 16:24 ` Stefan Schmidt
2015-07-26 21:03 ` Baptiste Clenet
2015-07-27 8:03 ` Baptiste Clenet
2015-07-27 8:06 ` Baptiste Clenet
2015-07-27 8:32 ` Alexander Aring
2015-07-27 8:58 ` Baptiste Clenet
2015-07-27 9:05 ` Baptiste Clenet
2015-07-27 9:30 ` Alexander Aring
2015-07-27 10:08 ` Baptiste Clenet
2015-07-27 10:21 ` Alexander Aring
2015-07-27 10:31 ` Baptiste Clenet
2015-07-27 10:38 ` Alexander Aring
2015-07-27 10:52 ` Baptiste Clenet
2015-07-27 11:30 ` Alexander Aring
2015-07-27 12:29 ` Baptiste Clenet
2015-07-27 12:42 ` Alexander Aring
2015-07-27 12:45 ` Baptiste Clenet
2015-07-27 15:13 ` Baptiste Clenet
2015-07-27 15:55 ` Baptiste Clenet
2015-07-27 16:35 ` Alexander Aring
2015-07-27 17:28 ` Alexander Aring [this message]
2015-07-27 17:43 ` Baptiste Clenet
2015-07-27 19:10 ` Alexander Aring
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=20150727172816.GB794@omega \
--to=alex.aring@gmail.com \
--cc=bapclenet@gmail.com \
--cc=linux-wpan@vger.kernel.org \
--cc=stefan@osg.samsung.com \
/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