From: Alexander Aring <alex.aring@gmail.com>
To: "Michael C. Cambria" <mcc@fid4.com>
Cc: linux-wpan@vger.kernel.org
Subject: Re: at86rf233 on BeagleBone Black
Date: Fri, 3 Apr 2015 21:13:22 +0200 [thread overview]
Message-ID: <20150403191320.GD773@omega> (raw)
In-Reply-To: <551EDFCA.3070905@fid4.com>
On Fri, Apr 03, 2015 at 02:45:30PM -0400, Michael C. Cambria wrote:
>
> Hi Alex,
>
> Do you happen to have the pin mapping & device tree overlay needed for the
> Openlabs at86rf233 [0] to run on BeagleBone Black (BBB)?
>
> I only have a few Pi's but do have a few spare BBB I could use. I'd rather
> not experiment an ruin either the BBB or at86rf233 if this information is
> known.
>
What I can give you are my dts entries for the BeagleBone (white),
pinout should be the same:
&am33xx_pinmux {
spi1_pins: pinmux_spi1_pins {
pinctrl-single,pins = <
0x190 0x33 /* mcasp0_aclkx.spi1_sclk, INPUT_PULLUP | MODE3 (special mode input for clock) */
0x194 0x33 /* mcasp0_fsx.spi1_d0, INPUT_PULLUP | MODE3 */
0x198 0x13 /* mcasp0_axr0.spi1_d1, OUTPUT_PULLUP | MODE3 */
0x19c 0x13 /* mcasp0_ahclkr.spi1_cs0, OUTPUT_PULLUP | MODE3 */
0x1a4 0x2f /* mcasp0_fsr.gpio3_19, INPUT, PULL DISABLED | MODE7 */
>;
};
};
&spi1 {
status = "okay";
pinctrl-names = "default";
pinctrl-0 = <&spi1_pins>;
at86rf231@0 {
compatible = "atmel,at86rf231";
spi-max-frequency = <7500000>;
reg = <0>;
interrupts = <19 4>;
interrupt-parent = <&gpio3>;
reset-gpio = $YOUR_GPIO
xtal-trim = /bits/ 8 <0xF>;
};
};
I also changed the "xtal-trim" value. Now it's fit with the openlabs
transceivers.
So you can see how my transceiver (I use the atben which have no reset pin)
is connected to my BeagleBone. Check [0] to get pins for interrupt and
reset pin.
I did the reset pin optional, please don't do that... normally then we
need to run a reset of phy settings if the at86rf233 have no reset pin
which is much unlikely (Okay, the atben have no reset pins...). I did
not implement such a PHY reset handling yet. So please use some free gpio.
This means you need to replace _maybe_ the interrupts and
interrupt-parent property. What you really need to change is the
$YOUR_GPIO property to something like [0] (fast googling which use the
dt naming stuff).
I mean something like:
reset-gpio = <&gpio3 21 1>;
depends on you adaptation from openlabs at86rf233 to a BBB.
- Alex
[0] http://blog.savoirfairelinux.com/wp-content/uploads/2013/11/beaglebone_pins-table.png
[1] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/gpio/gpio.txt
next parent reply other threads:[~2015-04-03 19:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <551EDFCA.3070905@fid4.com>
2015-04-03 19:13 ` Alexander Aring [this message]
2015-04-03 19:36 ` at86rf233 on BeagleBone Black Alexander Aring
2015-04-14 15:06 ` Alexander Aring
2015-04-16 21:08 ` Michael C. Cambria
2015-04-17 3:26 ` Varka Bhadram
2015-04-17 13:28 ` Michael C. Cambria
2015-04-17 22:19 ` Alexander Aring
2015-04-20 18:04 ` Michael C. Cambria
2015-04-20 18:24 ` Alexander Aring
2015-04-21 7:23 ` "Thomas B. Rücker"
2015-04-22 6:57 ` "Thomas B. Rücker"
2015-04-23 9:37 ` Alexander Aring
2015-04-23 13:47 ` Michael C. Cambria
2015-04-23 14:59 ` 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=20150403191320.GD773@omega \
--to=alex.aring@gmail.com \
--cc=linux-wpan@vger.kernel.org \
--cc=mcc@fid4.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 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.