On Sat, Jan 21, 2012 at 6:36 PM, Roman Yeryomin <leroi.li...@gmail.com> wrote: > On 21 January 2012 00:53, Marco Antonio Mauro <marcu...@gmail.com> wrote: >> This patch adds support for the Sitecom WL-341 v3 and other Sercomm >> IP1006RRv2 based boards for sysupgrade support and for the initial >> flash through pushbutton initiated recovery mode with the special >> partition table and fixes for the quirks and things required by the >> modified bootloader. >> >> There are two known bugs: >> >> 1. The LED configuration is broken -- only one led is working, an >> amber led, as I found no way to know which GPIOs were used for those. >> The board has 6 unlabeled leds, of which 1 is blue only and 5 are >> amber/blue. If I understand which GPIOs go to which leds I'll submit a >> patch later. > > I had this problem too and wrote a script to test gpios for leds and > buttons (see attachment). > Hope it'll help you (and maybe someone else). > Note that it will not help if your leds are connected via shift > registers (as on Belkin boards).
Your script helped me (but I had to modify it slightly, the ls had to be ls -d else it wouldn't work) I found out 4 more leds, but I still miss 7 leds. Also, your script errors out on some pins: this is the log. Here the pins that return 0s are leds. root@OpenWrt:/tmp# ./blinker.bin /sys/class/gpio/gpiochip0 Testing pins from 0 to 23 pin 0 sh: write error: Device or resource busy output mode qbreaking input mode 1 1 1 breaking pin 1 sh: write error: Device or resource busy pin 2 sh: write error: Device or resource busy pin 3 sh: write error: Device or resource busy pin 4 sh: write error: Device or resource busy pin 5 sh: write error: Device or resource busy pin 6 sh: write error: Device or resource busy output mode qbreaking input mode 1 1 1 breaking pin 7 sh: write error: Device or resource busy pin 8 sh: write error: Device or resource busy pin 9 sh: write error: Device or resource busy pin 10 sh: write error: Device or resource busy output mode qbreaking input mode 0 0 0 qbreaking pin 11 sh: write error: Device or resource busy output mode qbreaking input mode 0 0 0 qbreaking pin 12 sh: write error: Device or resource busy output mode breaking input mode 0 0 0 breaking pin 13 sh: write error: Device or resource busy pin 14 sh: write error: Device or resource busy output mode breaking input mode 0 0 0 breaking pin 15 sh: write error: Device or resource busy pin 16 sh: write error: Device or resource busy pin 17 sh: write error: Device or resource busy pin 18 sh: write error: Device or resource busy pin 19 sh: write error: Device or resource busy output mode qbreaking input mode 1 1 1 breaking pin 20 sh: write error: Device or resource busy output mode qbreaking input mode 1 q1 1 breaking pin 21 sh: write error: Device or resource busy output mode qbreaking input mode 1 1 1 breaking pin 22 sh: write error: Device or resource busy pin 23 sh: write error: Device or resource busy /sys/class/gpio/gpiochip24 Testing pins from 24 to 39 pin 24 sh: write error: Device or resource busy pin 25 sh: write error: Device or resource busy pin 26 sh: write error: Device or resource busy pin 27 sh: write error: Device or resource busy pin 28 sh: write error: Device or resource busy pin 29 sh: write error: Device or resource busy pin 30 sh: write error: Device or resource busy pin 31 sh: write error: Device or resource busy pin 32 sh: write error: Device or resource busy pin 33 sh: write error: Device or resource busy pin 34 sh: write error: Device or resource busy pin 35 sh: write error: Device or resource busy pin 36 sh: write error: Device or resource busy pin 37 sh: write error: Device or resource busy pin 38 sh: write error: Device or resource busy pin 39 sh: write error: Device or resource busy /sys/class/gpio/gpiochip40 Testing pins from 40 to 51 pin 40 sh: write error: Device or resource busy pin 41 sh: write error: Device or resource busy pin 42 sh: write error: Device or resource busy pin 43 sh: write error: Device or resource busy pin 44 sh: write error: Device or resource busy pin 45 sh: write error: Device or resource busy pin 46 sh: write error: Device or resource busy pin 47 sh: write error: Device or resource busy pin 48 sh: write error: Device or resource busy pin 49 sh: write error: Device or resource busy pin 50 sh: write error: Device or resource busy pin 51 sh: write error: Device or resource busy > >> 2. Wi-Fi is not working on my board probably because of the lack of >> RAM (the board only has 16MiB ram, but there is an empty slot for >> another ram chip,) but I don't know for sure. The driver loads but >> hostapd fails to load so I think it's not related to the specific >> device except for the lack of RAM. > > That's very strange, I don't have such problem with my 4/16 MB > Sparklan WCR-150GN. > I don't quite understand how it could be that it's low RAM problem if > all kernel modules are loaded _before_ everything else? It's hostapd that fails executing, not the .kos that fail loading. -- Marcus905 GPG pubkey: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x1FC0ECC932FE5FAC _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
