Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add LED status help commands in CLI #118

Closed
ghost opened this issue Jul 2, 2018 · 5 comments
Closed

Add LED status help commands in CLI #118

ghost opened this issue Jul 2, 2018 · 5 comments
Assignees

Comments

@ghost
Copy link

ghost commented Jul 2, 2018

There are different raspi versions having different LED configurations (1 or 2 LEDs with a status LED (PWR) common to all rpi boards) such as: (PWR: POWER, ACT: Activity)
RPI 3 B+ - 2 LEDs - PWR , ACT
RPI 3 - 2 LEDs - PWR , ACT
RPI Zero - 1 LEDs - ACT
RPI 2 - 2 LEDs - PWR , ACT
RPI A+ - 2 LEDs - PWR , ACT
RPI B+ - 2 LEDs - PWR , ACT
RPI A - 2 LEDs - PWR , ACT
RPI B (rev 2) - 5 LEDs - ACT, PWR, FDX, LNK and 100
RPI B (rev 1) - 5 LEDs - OK, PWR, FDX, LNK and 10M

The LEDs have the following meanings :

Label LED color Meaning
OK/ACT Green SD card activity
PWR Red Power
FDX Green Full Duplex (LAN) connected
LNK Green Link/Activity (LAN)
10M/100 Yellow 100Mbit (LAN) connected

(For later RPI models such as Pi 3, Pi 2 and B+ Ethernet socket has two additional status LEDs.)

Label LED color Meaning
10M/100 Yellow 100Mbit (LAN) connected
LNK Green Link/Activity (LAN)
@dogi
Copy link
Member

dogi commented Jul 12, 2018

@i5o look at pirate-sh/ip#9

@dogi dogi assigned i5o Jul 12, 2018
@i5o
Copy link
Collaborator

i5o commented Jul 12, 2018

root@raspberrypi:/sys/devices/platform/leds/leds/led0# cat trigger 
none rc-feedback kbd-scrolllock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock timer oneshot [heartbeat] backlight gpio cpu cpu0 cpu1 cpu2 cpu3 default-on input panic mmc1 mmc0 rfkill-any rfkill0 rfkill1 
root@raspberrypi:/sys/devices/platform/leds/leds/led0# 

@i5o
Copy link
Collaborator

i5o commented Jul 12, 2018

none                No trigger
kbd-scrolllock      Keyboard scroll lock
kbd-numlock         Keyboard num lock
kbd-capslock        Keyboard caps lock
kbd-kanalock        Keyboard kana lock
kbd-shiftlock       Keyboard shift
kbd-altgrlock       Keyboard altgr
kbd-ctrllock        Keyboard ctrl
kbd-altlock         Keyboard alt
kbd-shiftllock      Keyboard left shift
kbd-shiftrlock      Keyboard right shift
kbd-ctrlllock       Keyboard left ctrl
kbd-ctrlrlock       Keyboard right ctrl
timer               Flash at 1 second intervals
oneshot             Flash only once
heartbeat           Flash like a heartbeat (1-0-1-00000)
backlight           Always on
gpio                Flash when a certain GPIO is high???
cpu0                Flash on cpu0 usage
cpu1                Flash on cpu1 usage
cpu2                Flash on cpu2 usage
cpu3                Flash on cpu3 usage
default-on          Always on
[input]             Default state
panic               Flash on kernel panic
mmc0                Flash on mmc0 (primary SD Card interface) activity
mmc1                Flash on mmc1 (secondary SD Card interface) activity
rfkill0             Flash on wifi activity
rfkill1             Flash on bluetooth activity

https://raspberrypi.stackexchange.com/questions/69674/are-there-other-act-led-trigger-options-besides-mmc-and-heartbeat/69734

@dogi dogi assigned ghost Jul 18, 2018
@ghost
Copy link
Author

ghost commented Jul 18, 2018

@dogi Should I create a individual issue for each trigger and explain the trigger in detail?

@i5o
Copy link
Collaborator

i5o commented Jul 19, 2018

I think this issue should be merged with
treehouses/builder#74

otherwise it makes no sense to show what each trigger means

@dogi dogi closed this as completed in 512314d Jul 26, 2018
i5o added a commit that referenced this issue Sep 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants