Hi,
On my BeagleBone Black, the USR0–USR3 LEDs used to blink on boot with kernel 4.19.94-ti-r73, showing the board was alive. After upgrading to 6.17.2-bone10, the LEDs no longer blink.
I use a custom device tree where I configure many pins myself. I noticed that
BONE_P9_27 (PIN_OUTPUT_PULLDOWN | MUX_MODE7)
and
BONE_P9_41 (PIN_INPUT_PULLUP | MUX_MODE7)
specifically stop the USR LEDs from working. Without these two pins, the USR LEDs work normally.
Has anyone seen this issue when moving from 4.19.x to 6.17.x? Any idea what changed that affects the USR LEDs? @RobertCNelson maybe?
Thanks!
those pins should not affect the usr led’s, unless you routed them to the gpio-led and then they caused an issue..
sudo beagle-version
Will show some info on that..
Regards
Here’s the output from beagle-version:
user@beagle:~$ sudo beagle-version
eeprom:[A335BNLTEIA02320SBI03711]
model:[TI_AM335x_BeagleBone_Black]
dogtag:[BeagleBoard.org Debian Trixie Base Image 2025-10-16]
/usr/bin/beagle-version: 12: cannot create /tmp/SPL.tmp: Permission denied
Moreover, I define P9_27 in gpio-leds:
P9_27 { label = “P9_27_PIN”; gpios = <&gpio3 19 GPIO_ACTIVE_HIGH>; default-state = “off”; };
Regards,
K.
oh that’s fun… we lost the most important info after that section..
dmesg | grep pinctrl
voodoo@PB2UBOOT:~$ dmesg | grep pinctrl
[ 0.051636] pinctrl core: initialized pinctrl subsystem
[ 2.902752] pinctrl-single 44e10800.pinmux: 142 pins, size 568
Regards,
user@beagle:~$ dmesg | grep pinctrl
[ 0.067197] pinctrl core: initialized pinctrl subsystem
[ 2.609506] pinctrl-single 44e10800.pinmux: 142 pins, size 568
[ 3.749177] pinctrl-single 44e10800.pinmux: Invalid number of rows: 0
[ 3.749201] pinctrl-single 44e10800.pinmux: no pins entries for pinmux_timer6_pin
[ 3.749343] pinctrl-single 44e10800.pinmux: Invalid number of rows: 0
[ 3.749353] pinctrl-single 44e10800.pinmux: no pins entries for pinmux_timer5_pin
[ 3.749467] pinctrl-single 44e10800.pinmux: Invalid number of rows: 0
[ 3.749477] pinctrl-single 44e10800.pinmux: no pins entries for pinmux_timer7_pin
[ 3.749584] pinctrl-single 44e10800.pinmux: Invalid number of rows: 0
[ 3.749595] pinctrl-single 44e10800.pinmux: no pins entries for pinmux_timer4_pin
[ 3.749810] pinctrl-single 44e10800.pinmux: pin PIN95 already requested by 4819c000.i2c; cannot claim for leds
[ 3.749825] pinctrl-single 44e10800.pinmux: error -EINVAL: pin-95 (leds)
[ 3.749841] pinctrl-single 44e10800.pinmux: error -EINVAL: could not request pin 95 (PIN95) from group pinmux_ecs01_gpio_led_pins on device pinctrl-single
[ 5.412969] pinctrl-single 44e10800.pinmux: pin PIN10 already requested by 48022000.serial; cannot claim for 481a0000.spi
[ 5.436658] pinctrl-single 44e10800.pinmux: error -EINVAL: pin-10 (481a0000.spi)
[ 5.444735] pinctrl-single 44e10800.pinmux: error -EINVAL: could not request pin 10 (PIN10) from group pinmux_bb_spi1_pins on device pinctrl-single
[ 5.533200] pinctrl-single 44e10800.pinmux: Invalid number of rows: 0
[ 5.539926] pinctrl-single 44e10800.pinmux: no pins entries for pinmux_bb_gpio0_12_pins
that’s where you led’s went…