Hi Ralf,
Thank you very much.
I compiled the following BB-gpio-set-00A0.dts file, and copied the
generated BB-gpio-set-00A0.dtbo file to */lib/firmware/*
//file name: BB-gpio-set-00A0.dts
/dts-v1/;
/plugin/;
/ {
compatible = "ti,beaglebone", "ti,beaglebone-black";
/* identification */
part-number = "BB-LED";
version = "00A0";
/* state the resources this cape uses */
exclusive-use =
/* the pin header uses */
"P9.15", /* GPIO1_16 */
/* the hardware ip uses */
"GPIO1_16";
fragment@0 {
target = <&am33xx_pinmux>;
__overlay__ {
bb_GPIO1_16_pins: pinmux_bb_GPIO1_16_pins {
pinctrl-single,pins = <
0x40 0x07 /* P9.15 OUTPUT */
>;
};
};
};
};
Then, I went to */sys/devices/bone_capemgr.8* and performed. *echo
BB-gpio-set > slots*
*cat slots* produced:
0: 54:PF---
1: 55:PF---
2: 56:PF---
3: 57:PF---
4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
5: ff:P-O-L Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
9: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-gpio-set
I re-checked then *cat pins* but pin 16 stayed the same:
pin 16 (44e10840) 00000027 pinctrl-single
Do you have an idea what is wrong or missing in the above steps I took?
On Sunday, February 16, 2014 10:21:44 AM UTC+2, Ralf Roesch wrote:
>
> Matt,
> i made a made a little mistake in my previous post:
> default state after reset of pin 16 is already 0x27 (input with pulldown).
> (cat pins -> pin 16 (44e10840) 00000027)
> Just use your original dts to check, you should get 0x7 afterwards
> (output).
>
> Ralf
>
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
