Hi,
On Fri, Apr 03, 2015 at 09:13:20PM +0200, Alexander Aring wrote:
> 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 */
> >;
> };
> };
>
since somebody noticed me about several pinmux issues on this setup. I
will update them now with:
&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 */
>;
};
};
This is what [0] describes at page 11, I hope. Can somebody report if it
was successful to get openlabs with bb/bbw working?
- Alex
[0] http://www.atmel.com/images/atmel-8351-mcu_wireless-at86rf233_datasheet.pdf (1.3.2 Pull-up and Pull-down Configuration)
--
To unsubscribe from this list: send the line "unsubscribe linux-wpan" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
