Opened 5 years ago
Last modified 5 years ago
#13356 assigned defect
Asus RT-N10 Plus WPS led does not turn on
Reported by: | Cody P Schafer <openwrt@…> | Owned by: | blogic |
---|---|---|---|
Priority: | normal | Milestone: | Chaos Calmer 15.05 |
Component: | packages | Version: | Trunk |
Keywords: | Cc: |
Description
The WPS led blinks when in tftp mode (hold reset or WPS button while powering on), but it never lights at all once linux is booted.
Examining it once booted (via /sys/class/leds/asus:green:wps) shows the brightness set at 255, but the led is not lit. Setting brightness to 0 (and once at 0 back to 255) has no effect on the physical appearance of the LED
Instructions regarding flashing the rt-n10+ with openwrt indicate that the LED did at one point work.
Attachments (1)
Change History (8)
comment:1 Changed 5 years ago by Cody P Schafer <openwrt@…>
comment:2 Changed 5 years ago by Cody P Schafer <openwrt@…>
Using the gpio api (at some risk to my hardware), I tested gpio 13 and 15 to check for an off-by-one. Neither caused any changes in any LED.
comment:3 Changed 5 years ago by Cody P Schafer <openwrt@…>
comparing the regoster-map of gpio0 in rt3050.dtsi (included by NT-N10-PLUS.dts) appears to match the definitions from the vendor source release, though the vendor source does not use or define the polarity register (GPIO_REG_POL) in RT-N10+.2028/linux-2.6.21.x/drivers/char/ralink_gpio.c
comment:4 Changed 5 years ago by Ayyari
I have some problem.
see the #ticket/13359
Changed 5 years ago by Cody P Schafer <openwrt@…>
comment:5 Changed 5 years ago by Cody P Schafer <openwrt@…>
I've attached a fix. Essentially, the uart mux was not getting set into GPIO mode due to an earlier patch removing the "gpio" entry from uart_mux. While I was there, I also fixed the .gpio_first and .gpio_last for a few other pin groups (.gpio_first and .gpio_last are unused, and it seems like using them means reimplimenting pinctrl).
comment:6 Changed 5 years ago by nbd
- Owner changed from developers to blogic
- Status changed from new to assigned
comment:7 Changed 5 years ago by Cody P Schafer <openwrt@…>
This should be solved by the solution to #13359 (which this is a dup of)
Using the gpio interface directly as follows also has no effect: