From: "Michael C. Cambria" <mcc@fid4.com>
To: Alexander Aring <alex.aring@gmail.com>
Cc: Varka Bhadram <varkabhadram@gmail.com>, linux-wpan@vger.kernel.org
Subject: Re: at86rf233 on BeagleBone Black
Date: Mon, 20 Apr 2015 14:04:48 -0400 [thread overview]
Message-ID: <55353FC0.5050909@fid4.com> (raw)
In-Reply-To: <20150417221913.GA3338@omega>
On 04/17/2015 06:19 PM, Alexander Aring wrote:
> On Fri, Apr 17, 2015 at 09:28:37AM -0400, Michael C. Cambria wrote:
> ....
>> With those changes the "arguments longer than property" message does go
>> away. I now get this probe error:
>>
>>
>> [ 9.815400] of_get_named_gpiod_flags: parsed 'reset-gpio' property of
>> node '/ocp/spi@481a0000/at86rf231@0[0]' - stat)
>> [ 9.815437] of_get_named_gpiod_flags: parsed 'sleep-gpio' property of
>> node '/ocp/spi@481a0000/at86rf231@0[0]' - stat)
>> [ 10.287193] at86rf230 spi1.0: Non-Atmel dev found (MAN_ID 00 00)
>> [ 10.971416] at86rf230: probe of spi1.0 failed with error -22
>>
> Meanwhile I got private repsonse that somebody have a working openlabs
> module on a beaglebone, so it's _really_ possible! :-)
Thanks for all the help. My BBB now works with the openlabs radio. I
had P9_28 & P9_30 in the the wrong holes (blush).
I still have those two messages at modprobe time, but the radio is probed.
[ 11.346020] of_get_named_gpiod_flags: parsed 'reset-gpio' property of
node '/ocp/spi@481a0000/at86rf233@0[0]' - status (0)
[ 11.346056] of_get_named_gpiod_flags: parsed 'sleep-gpio' property of
node '/ocp/spi@481a0000/at86rf233@0[0]' - status (0)
[ 11.349282] at86rf230 spi1.0: Detected at86rf233 chip version 1
I'll test e..g ping6 to another BBB and Pi ASAP.
Here is what I appended to the existing am335x-boneblack.dts file:
&am33xx_pinmux {
spi1_pins: pinmux_spi1_pins {
pinctrl-single,pins = <
0x190 (PIN_INPUT_PULLDOWN | MUX_MODE3) /*
mcasp0_aclkx.spi1_sclk */
0x194 (PIN_INPUT | MUX_MODE3) /*
mcasp0_fsx.spi1_d0 */
0x198 (PIN_OUTPUT_PULLDOWN | MUX_MODE3) /*
mcasp0_axr0.spi1_d1 */
0x19c (PIN_OUTPUT_PULLUP | MUX_MODE3) /*
mcasp0_ahclkr.spi1_cs0 */
0x1a4 (PIN_INPUT | MUX_MODE7) /* IRQ:
mcasp0_fsr.gpio3_19 */
0x1ac (PIN_OUTPUT_PULLDOWN | MUX_MODE7) /*
SLP_TR: mcasp0_ahclkx.gpio3_21 */
0x044 (PIN_OUTPUT_PULLUP | MUX_MODE7) /* RESET:
gpmc_a1.gpio1_17 */
>;
};
};
&spi1 {
status = "okay";
pinctrl-names = "default";
pinctrl-0 = <&spi1_pins>;
at86rf233@0 {
compatible = "atmel,at86rf233";
spi-max-frequency = <500000>;
reg = <0>;
interrupts = <19 4>;
interrupt-parent = <&gpio3>;
reset-gpio = <&gpio1 17 1>;
sleep-gpio = <&gpio3 21 1>;
xtal-trim = /bits/ 8 <0xF>;
};
};
I'll post the J1 to BBB P9 pin mapping ASAP as well.
next prev parent reply other threads:[~2015-04-20 18:09 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 ` at86rf233 on BeagleBone Black Alexander Aring
2015-04-03 19:36 ` 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 [this message]
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=55353FC0.5050909@fid4.com \
--to=mcc@fid4.com \
--cc=alex.aring@gmail.com \
--cc=linux-wpan@vger.kernel.org \
--cc=varkabhadram@gmail.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.