About Overlay

83 views
Skip to first unread message

fatih özen

unread,
Jan 18, 2022, 6:59:22 AM1/18/22
to Machinekit
Hi,

I am newbie and want to ask something about overlays. I write an overlay( MOvrly.dts ) as below :

/dts-v1/;
/plugin/;

/{
    compatible = "ti,beaglebone", "ti,beaglebone-black";
    part_number = "custom_overlay";

    exclusive-use =
        "GPIO.112",
        "gpio3_16",
        "GPIO.115",
        "gpio3_19",
        "P9.25",
        "gpio3_21";

    fragment@0
    {
        target = <&am33xx_pinmux>;
        __overlay__
        {
            custom_overlay: pinmux_bs_pinmode_GPIO_112_0xf
            {
                pinctrl-single,pins =   <
                                        0x198 0x0f,
                                        0x1a4 0x2f,
                                        0x1ac 0x2f>;
            };
        };
    };

    fragment@1
    {
        target = <&ocp>;
        __overlay__
        {
            bs_pinmode_GPIO_112_0xf_pinmux
            {
                compatible = "bone-pinmux-helper";
                status = "okay";
                pinctrl-names = "default";
                pinctrl-0 = <&custom_overlay>;
            };
        };
    };
};

and in uEnv.txt file I wrote these lines:

enable_uboot_overlays=1
disable_uboot_overlay_video=1 
disable_uboot_overlay_audio=1 
disable_uboot_overlay_wireless=1 
disable_uboot_overlay_adc=1
dtb_overlay=/lib/firmware/MOvrly-00A0.dtbo

Finally after reboot I saw that pins were configured as in overlay file. But then I added

        "GPIO.113","gpio3_17", "GPIO.116","gpio3_20" lines to exclusive_use

and 

0x1a8 0x2f, 0x19c 0x2f lines in to fragment@0's related part.

After reboot I can't connect to BBB anymore. What could be the reason ? I use 4.14.192-bone-rt-r38 kernel and BBB Rev-C board.
Reply all
Reply to author
Forward
0 new messages