From patchwork Sun Jul 9 18:27:29 2017 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Alexander Aring X-Patchwork-Id: 9831855 Return-Path: Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org [172.30.200.125]) by pdx-korg-patchwork.web.codeaurora.org (Postfix) with ESMTP id 1143C60318 for ; Sun, 9 Jul 2017 18:28:34 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id DEA0126E56 for ; Sun, 9 Jul 2017 18:27:44 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id BC21026E76; Sun, 9 Jul 2017 18:27:44 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on pdx-wl-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-6.8 required=2.0 tests=BAYES_00, DKIM_ADSP_CUSTOM_MED, DKIM_SIGNED, FREEMAIL_FROM, RCVD_IN_DNSWL_HI, T_DKIM_INVALID autolearn=ham version=3.3.1 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 20F3D26E56 for ; Sun, 9 Jul 2017 18:27:43 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752523AbdGIS1i (ORCPT ); Sun, 9 Jul 2017 14:27:38 -0400 Received: from mail-wr0-f180.google.com ([209.85.128.180]:34803 "EHLO mail-wr0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752430AbdGIS1h (ORCPT ); Sun, 9 Jul 2017 14:27:37 -0400 Received: by mail-wr0-f180.google.com with SMTP id 77so110496086wrb.1 for ; Sun, 09 Jul 2017 11:27:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=FkBN+ltyy6Y4HSly790AOPwnZxVluLuVlukeBTrmkbc=; b=RgJCrQW4Zvw93RMqnAuO1tZRLUynSWD7rQiUS6/RN68PNixD8jAC16Jk/r2BFhHjQn UmWinemnoEXqGvn5HOBGJVSKhm6924Os6Hs58MzPr07K4LvmRumZJxkJ4UGNub7VJDBQ eh0HJo1i3KJOkBcDkzbYpv+KZLFYsaYW3KI0pf5WLmdsvQ/scrix1I6RuQCKEAMdU5r5 Fa1/umJga1ufPyfu+hxNrI8UxE5SJYDy3jBcrBVfqz+06qJzFpYZSB+Q4RIQaXkFJkQ2 56REbwuK7BpfgGe/UVjLbjreL5O/v+vQ4eEV8AjLkM6ywAW2P2zuTv+u73euI2L3nCq+ z28A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=FkBN+ltyy6Y4HSly790AOPwnZxVluLuVlukeBTrmkbc=; b=YOHgXarI0FVuRQT0qzBdFmifOroYvlRDjSR5wro5ho/YF1W1R4HIqRlpoNTcNmgRgE 8HNKSnCTTjiRPQpvVwZykcG1309P7dEryoC518ay2ARgYXp9B1ZQQSJk4elvzPo0SMPR 4qwnGuF3nDiP06IjZgnRXP2DJiyyallhU6D0087MPlIIteKWcY+2WtBxFucqhjk9GK4f zEEUSVVSDpSbaIxV6H7rBg/GP2tFeJ5dUDPp0umM/UWsP6y99r/9KGFDYjhLSyhB3FAd Yr6KKedidoZs7aREmPA95trqw1WjkT4qxc33c/FHRQC/YnDJzaxfNARSa/GbgZRs3mfp FLEg== X-Gm-Message-State: AIVw113pzdQqHdI3ifGxi3oLOD3hGt1ZcE7hm5EyaawZ9CveP7XuiZHb u/6495xGzLQDEAaV X-Received: by 10.223.171.146 with SMTP id s18mr6167032wrc.38.1499624855516; Sun, 09 Jul 2017 11:27:35 -0700 (PDT) Received: from omega (p20030064A913155C41D6098DC31A0AE4.dip0.t-ipconnect.de. [2003:64:a913:155c:41d6:98d:c31a:ae4]) by smtp.gmail.com with ESMTPSA id l46sm7799881wrl.15.2017.07.09.11.27.34 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 09 Jul 2017 11:27:34 -0700 (PDT) Date: Sun, 9 Jul 2017 20:27:29 +0200 From: Alexander Aring To: Balz Cc: linux-wpan@vger.kernel.org Subject: Re: Resend : Reading corrupt IEEE 802.15.4 packages with the AT-REB233 and the BeagleBone Black with IWPAN Message-ID: <20170709182728.kam75j2kpt36ulju@omega> References: <06812919-6657-de81-25c5-63444c1527b9@hm.edu> <20170707110011.pwz272ppmwwu2wzh@omega> <20170708180631.l7lddi475pmua33o@omega> <20170708181113.htxnpxrzxgsrqyva@omega> <20170708181410.64zhqqyfvgp22b6c@omega> <583268dc-46a4-c78d-dfcf-d0083caa0888@hm.edu> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <583268dc-46a4-c78d-dfcf-d0083caa0888@hm.edu> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-wpan-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wpan@vger.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP Hi, On Sun, Jul 09, 2017 at 06:22:29PM +0200, Balz wrote: > Hi, > I do not use the SPIDEV fragment, so I've deleted it out of the Overlay. > The data sheet of the ATREB233 says that the SPI cut get up to 7.5 MHZ but > decreasing it does have no positive effects. > My SPI Configuration is specified for the BBB. > mh, ok. 7Mhz could be too high, I expierenced bad behaviours on RPI with openlabs board which has no jumpwire etc. setup. > I do think that released the RX_Save_MODE means, that the frame buffer is > not any more protected, so that the hardware can override the FrameBuffer. > I've checked the value of register 0x0c periodically but it does not change > its value while operating. But i have no idea how to make the regmap > volatile. > You need to have it volatile otherwise the read will not trigger a register read on the bus. Maybe there exists a runtime solution to add it via debugfs to volatile registers. I know this way only, you can run the cat on registers afterwards and it should trigger a register read. Acutally you could check it on you logic analyzer (but there should be a lot of register read, search for 0x0c). Here is the diff, very easy (recompile kernel and boot it, sure... or just at86rf230.ko replacement): ---------- I reread the datasheet and I think this will not happen, that we lost RX_SAFE_MODE... because the datasheet [0] shows how to setup enable "receive mode" inclusive address filtering etc. there is the RX_SAFE_MODE setting mentioned. That says to me: we need it for hardware init once OR when going into some RX state of at86rf233... but what an ugly behaviour that it will drop RX_SAFE_MODE when changing state - another question: would we always set the address filtering again then? I don't know... I maybe can ask "again" Atmel support for help me, but this support interface of them are very ugly and I only got reponse the last time, because somebody on the list had some support contract with them (I think). Also [0] for running in promiscuous mode (page 59) doesn't mention anything about RX_SAFE_MODE! So question would be if RX_SAFE_MODE working in promiscuous mode? Or does the hardware doesn't support it... in this configuration. The datasheet doesn't contain the information which I need to know... I need the firmware of this chip >:-( - Alex [0] http://www.atmel.com/images/Atmel-8351-MCU_Wireless-AT86RF233_Datasheet.pdf (PDF PAGE 56) --- To unsubscribe from this list: send the line "unsubscribe linux-wpan" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/drivers/net/ieee802154/at86rf230.c b/drivers/net/ieee802154/at86rf230.c index 548d9d026a85..858b07a4febc 100644 --- a/drivers/net/ieee802154/at86rf230.c +++ b/drivers/net/ieee802154/at86rf230.c @@ -311,6 +311,7 @@ at86rf230_reg_volatile(struct device *dev, unsigned int reg) case RG_VREG_CTRL: case RG_PLL_CF: case RG_PLL_DCU: + case RG_TRX_CTRL_2: return true; default: return false;