All of lore.kernel.org
 help / color / mirror / Atom feed
From: anton@picapica.im
To: linux-wpan@vger.kernel.org
Subject: [PATCH] website: Add troubleshooting section in how-tos
Date: Mon, 19 Feb 2018 00:03:16 +0100	[thread overview]
Message-ID: <20180218230316.GA8719@picapica.im> (raw)


Some hints about issues related to SPI bus.

Signed-off-by: Anton Sviridenko <anton@picapica.im>
---
 website/index.txt | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/website/index.txt b/website/index.txt
index 9fd149e..6d9fe88 100644
--- a/website/index.txt
+++ b/website/index.txt
@@ -135,6 +135,21 @@ ip netns exec wpan0 ping6 ff02::1%lowpan0
 Now watch wireshark and all the nice ICMP packets there.
 
 
+Troubleshooting
+~~~~~~~~~~~~~~~
+If you have issues with transceiver connected to SPI bus, check first
+if wiring is correct and SPI controller is properly configured. Try to
+decrease SPI clock frequency. Messages like these ones in dmesg output
+could indicate problems with SPI connection:
+
+---------------------------------------------------------------------
+at86rf230 spi32765.0: unexcept state change from 0x01 to 0x08. Actual state:
+0x01
+WARNING: CPU: 0 PID: 61 at drivers/net/ieee802154/at86rf230.c:696 0xc0442644
+received tx trac status 4
+---------------------------------------------------------------------
+
+
 Sniffing
 ~~~~~~~~
 
-- 
2.3.6



             reply	other threads:[~2018-02-18 23:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-18 23:03 anton [this message]
2018-02-21 14:08 ` [PATCH] website: Add troubleshooting section in how-tos Stefan Schmidt
2018-02-21 15:46   ` Alexander Aring
2018-02-21 16:14     ` Stefan Schmidt
2018-02-21 16:35     ` Anton Sviridenko
2018-02-25 22:02   ` Alexander Aring
2018-02-26 11:53     ` Stefan Schmidt

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=20180218230316.GA8719@picapica.im \
    --to=anton@picapica.im \
    --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 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.