These leds looks really nice, however, as we know in A5A they are too strong, so at night it causes confusing. It’s nice about Bonescript and example with leds. Is any method to However example only show how to switch off only user leds. Is any possibility to switch off power led too? It will be nice if somebody will share with us how to switch off even Ethernet socket leds.
root@arm:~# echo none > /sys/class/leds/beaglebone\:green\:usr0/trigger
root@arm:~# echo none > /sys/class/leds/beaglebone\:green\:usr1/trigger
root@arm:~# echo none > /sys/class/leds/beaglebone\:green\:usr2/trigger
root@arm:~# echo none > /sys/class/leds/beaglebone\:green\:usr3/trigger
Seems to do the job. Can't turn off the power led though!
-- Bas
The Ethernet LEDS are not controlled by SW. That is a function of the PHY.
Options:
Tape
Shoebox upside down over board.
Shoebox with board inside and lid attached.
Towel.
Remove LEDS with ice pick (Voids warranty)
Stab LEDs in Ethernet with Ice Pick
Gerald
Damn - Batsignal in the shoebox - that’s cool 
And power led is followed by which function?
Power LED is controlled by the PMIC. Turn it off and the power LED will go out,
Gerald
This also solves the problem with the NIC leds 
“Power LED is controlled by the PMIC. Turn it off and the power LED will go out”
Is any reference manual for leds and switch buttons control? Leds maybe only switched off/on or there is any way to control them? i.e. blinking, light strength control and so on - is it possible?
As I see not only Bonescript is capable to control leds. It’s possible with bash script too (take a look at above example with user leds)
I’d like to program buttons too, i.e. double short press of user button in order to switch off all blue leds. double short press again - and leds could be switched on again.
Look at the TPS65217C datasheet and turn off the power supply that controls the LED.
Gerald
root@arm:/sys/class/leds/beaglebone:green:usr0# cat trigger
none nand-disk mmc0 mmc1 timer oneshot [heartbeat] backlight gpio cpu0 default-on transient
root@arm:/sys/class/leds/beaglebone:green:usr0# echo “none” >trigger
root@arm:/sys/class/leds/beaglebone:green:usr0# cat trigger
[none] nand-disk mmc0 mmc1 timer oneshot heartbeat backlight gpio cpu0 default-on transient
root@arm:/sys/class/leds/beaglebone:green:usr0#
@William Hermans:
Nice examples. From where did you get them? Could you tell me where is reference/documentation for that. I’m also curious about switch buttons controls. If somebody feels like Joker in Gotham’s city - it’s better to calm down.
Someone on IRC told me that once. But most ( all ? ) GPIO can be used as SYSFS AFAIK. Quite honestly I have not experimented with everything, but if you google around a bit, you will most likely run into several examples like this. I have, while searching various subjects on the web.
Also, do keep in mind that is Debian I am running on the BBB, so things may be slightly different on Angstrom. I do know there is at least one other way to do this on Angstrom, but I do not recall the exact method ( systemd or some such command ), but again, I’ve been using Debian/Linux since early on.
karol82r@gmail.com wrote:
These leds looks really nice, however, as we know in A5A they are too
strong, so at night it causes confusing.
have you considered placing a towel over it at night? always have a towel with you
I’ve run into excessively bright, especially blue, LEDs with lots of devices - routers, modems, serial to USB dongles, etc. A black Sharpie works wonders. Apply as many coats as needed to get desired intensity. Easily cleaned up with alcohol. For large indicator lights, like on my monitor, I use a piece of black electricians tape and punch a tiny hole in it.
10 years late, but someone here figured it out how to turn the power led off: