README of the iconnect-tools package ------------------------------------ The iconnect-tools package contains some very specific tools for running Debian on a Iomega Iconnect hardware. Such as a systemd service file for controlling and configuring the info LEDs on front of the Iomega Iconnect, as the Power and the OTB LED or the status LEDs of the four USB ports. 1. Controlling the info LEDs **************************** The Power LED is located on the left side, it's a multi-color LED emitting blue and red light. The OTB LED is on the right side above the OTB button. This LED is only providing blue light. The iconnect-tools package is installing a systemd service and SysV Init file which will set various actions to the info LEDs. The service file can be found as /lib/systemd/system/iconnect-leds.service, it's simply firing up the argument 'start' or 'stop' to the helper script /usr/share/iconnect-tools/set-leds.sh This script than is setting the pin control provided by the device tree. Please have a look into this shell script how the controlling is working. You can modify the setup of the LEDs by changing the config which is written into the sysfs part of the kernel. To see the possible options you can write to the pin control by simply cat out the trigger register. The following settings are used for the info LEDs. Power LED (blue): default on Power LED (red) : indicates CPU activity OTB LED (blue): activity by remote SSH logins Possible actions are: # cat /sys/class/leds/otb:blue/trigger none timer disk-activity disk-read disk-write ide-disk mtd nand-disk cpu cpu0 \ default-on panic usb-gadget usb-host rfkill-any rfkill-none \ f1072004.mdio-bus-mii:0b:link f1072004.mdio-bus-mii:0b:1Gbps \ f1072004.mdio-bus-mii:0b:100Mbps f1072004.mdio-bus-mii:0b:10Mbps \ rfkill0 phy0rx phy0tx phy0assoc phy0radio [netfilter-tcpssh] 2. Controlling the USB port status LEDs *************************************** Further the iconnect-tools package is installing a UDEV rule which will turn the USB port status LEDs on and off depending if a USB device is used or not. The UDEV rule can be found in /lib/udev/rules.d/99-usb-leds.rules and the used shell script by the UDEV rule in /usr/share/iconnect-tools/trigger-usb-leds.sh Like for the OTB and Power LED you can use various trigger if you like. Default is to use the 'none' trigger. Possible triggers are the same as above, you can cat out the possible triggers for the LEDs as usual. # cat /sys/class/leds/usb*\:blue/trigger 3. OTB and Reset button *********************** Currently both buttons are not configured by the iconnect-tools package. 4. Decreasing the sync rate for swap file writings ************************************************** The Iconnect hardware hasn't much RAM memory (256MB) so it's very likely that the swap file will be used. In case this swap file is placed on a USB device wit flash memory it's highly recommended to decrease the write cycles onto that file to not burn out the USB flash memory. To do so you can copy a provided sysctl config file. For using this ready to use snippet run the following commands as root. # cp /usr/share/doc/iconnect/examples/98-swap.conf /etc/sysctl.d/ # sysctl -p 5. Config file for fw_printenv and fw_setenv ############################################ The binaries fw_{printenv,setenv} from the u-boot-tools package needing a valid configuration file /etc/fw_env.config which is provided by the iconnect-tools package. Be careful if you make modifications to the U-Boot environment by using the tool fw_setenv as it might result in a non booting system! -- Carsten Schoenert Sat, 04 Jan 2030 19:17:34 +0100