RUCKUS Community Forums are now in READ-ONLY mode while we migrate to a new platform.
You will still be able to read posts and knowledge articles, but will be unable to post new content until Go Live on the new platform Monday August 17.
Lennar Smart Home customers: please contact [email protected] for assistance during the week of August 9-17.
10-24-2024 12:04 PM
I don't expect much of a reply on this (unless someone at Ruckus is feeling really generous) but I recently got my hands on a SmartZone 100 controller that's EOL'd and out of support and to add insult to injury, it also has a failing hard drive. It was destined to the e-waste recycler but I snagged it in the hopes I could do something cool with it and so far it's been a beastly OPNSense firewall.
There's one small catch, the flashing red STATUS LED on the front of the chassis.
After performing some disk forensics on the failing hard drive, I've managed to find out that the LED is controlled by a pair of entries in /proc (specifically RED_LED = /proc/v54bsp/sysLed0 and GREEN_LED = /proc/v54bsp/sysLed1) and by a script, /usr/sbin/led.sh. This is called from rks-systools. Further examination of the drive indicates that this may be part of a custom linux module called v54_bsp.ko. I'm guessing that v54_bsp exposes the two sysLed entries in /proc and uses that to manipulate the hardware to flash the LED to indicate various states of the appliance.
Unfortunately, that's where I'm dead in the water.
From what I see, the v54_bsp module does a lot more than just controlling a status LED but that's all that I'm really interested in. I'm not trying to reverse engineer any trade secrets or any of that nonsense, I just want to figure out how to change the STATUS LED to make it more useful. Is there someone that can tell me what the hardware chip is used to control the LED so that I can examine its datasheets and learn how to control it?
Thank you!
