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 12:21:22 +0200 [thread overview]
Message-ID: <20150727102121.GC18090@omega> (raw)
In-Reply-To: <CAPpUg6PBF9mSOkcNRdN-nqKPan+wmD5iQaMBqV0zpVDY+ccE3w@mail.gmail.com>
On Mon, Jul 27, 2015 at 12:08:18PM +0200, Baptiste Clenet wrote:
...
>
> Receiving side:
> [ 176.921637] CID flag is set, increase header with one
> [ 176.931640] NH flag is set, next header carried inline: 02
> [ 176.942502] SAC bit is set. Handle context based source address.
> [ 176.954397]
> [ 176.957352] ieee802154 phy0 wpan0: SAM value 0x3 not supported
>
Yes this is not what it was transmitted before from the other node.
That's why I would ask for some sniffing device, somewhere in the lower
layers mac or phy it will fill your frame with garbage.
I can't tell you now if it's the transmitted node or the receiving node.
You need to debug it there.
To ensure the transmitted node don't send garbage I would like to check
it with some sniffer device. If you see garbage on the sniffer device
then it's something wrong with the transmitting.
- Alex
next prev parent reply other threads:[~2015-07-27 10:21 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 [this message]
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
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=20150727102121.GC18090@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