Rich_Sewell how I can assign shutdown_req to another pin
that's not straightforward. That is the pin that is used for the Bela button. This is monitored by the Bela program (unless you pass --disable-cape-button-monitoring
to the program), and by the systemd
task /lib/systemd/system/bela_button.service
, which in turn executes /usr/local/bin/bela-cape-btn --pin 115 --hold /opt/Bela/bela_button_hold.sh --delay 10 --monitor-click 0 --verbose --hold-press-timeout-ms 1000
.
I think you may have to edit those overlays and remove the exclusive-use
field as well as this line:
pinctrl-0 = <&pinctrl_eqepX>;
This is because (I think) on the PocketBeagle all the pins are by default owned by the equivalent of cape_universal
, which is what allows you to use config-pin
in the first place. So if you were trying to claim those pins again, it wouldn't work. If you wanted to permanently set them to default to eqep from a dtb, you should do that the same way we do for the bela_digitals
pins here, i.e.:
fragment@2 {
target = <&am33xx_pinmux>;
__overlay__ {
/* .... */
// DEFINE a new default value for specific pins
P2_01_bela: pinmux_default_bela0 { pinctrl-single,pins = <0x48 0x27>; };
/*...*/
}
/* ... */
fragment@8 {
target = <&ocp>;
__overlay__ {
// APPLY a new default value for specific pins
P2_01_pinmux{ pinctrl-0 = <&P2_01_bela>; };
/*...*/
};
};