Advantech RSB-4760, User Manual

Page: 41 / 49

40
3.1.15. LED Test
1. Check if LED triggers are expected.
[WiFi]
$ cat /sys/class/leds/apq8016 ‐ sbc:green:wlan/trigger
none kbd ‐ scrollock kbd ‐ numlock kbd ‐ capslock kbd ‐ kanalock kbd ‐ shiftlock
kbd ‐ altgrlock kbd ‐ ctrllock kbd ‐ altlock kbd ‐ shiftllock kbd ‐ shiftrlock
kbd ‐ ctrlllock kbd ‐ ctrlrlock mmc0 mmc1 timer oneshot heartbeat backlight gpio
cpu0 cpu1 cpu2 cpu3 default ‐ on hci0 ‐ power hci0 ‐ tx_rx rfkill0 rfkill1 [phy0rx]
phy0tx phy0assoc phy0radio
[Bluetooth]
$ cat /sys/class/leds/apq8016 ‐ sbc:yellow:bt/trigger
none kbd ‐ scrollock kbd ‐ numlock kbd ‐ capslock kbd ‐ kanalock kbd ‐ shiftlock
kbd ‐ altgrlock kbd ‐ ctrllock kbd ‐ altlock kbd ‐ shiftllock kbd ‐ shiftrlock
kbd ‐ ctrlllock kbd ‐ ctrlrlock mmc0 mmc1 timer oneshot heartbeat backlight gpio
cpu0 cpu1 cpu2 cpu3 default ‐ on hci0 ‐ power [hci0 ‐ tx_rx] rfkill0 rfkill1 phy0rx
phy0tx phy0assoc phy0radio
2. Verify LED behavior
For example, we set LED trigger as phy0rx for WiFi. That means LED should be blink when
data is receiving via WiFi.
3.1.16. M.2 Test
We take M.2 UART function as example. Here, we use AzureWave AW ‐ NB136NF (M.2 Uart BT
module).
Because the serial port conflicts with debug console (UART0). So, you have to disable
serail ‐ getty service, before you test.
$ systemctl mask serial-getty@ttyMSM0.service
$ reboot
$ hciattach /dev/ttyMSM0 bcm43xx 115200 flow
$ hciconfig hci1 up
# You can see a BT hci now. Follow the BT test steps.
After test, you can recover by the command below.