This package is the Monitor Upgrade Solution (MUS) by Toshiba Global Commerce Solutions, Inc. This will perform silent and remote updating of the Touch and Video Firmware of Toshiba Monitor types 4820_21x/51x ,4820_2Lx/5Lx and 6149-5xx.
The monitor should be connected to the system unit by the usb cable provided with the monitors.
1. Python 2.6.8 on SLE 11 SP3
2. Zypper Commandline Tool version 1.6 and above
NOTE: SLEPOS 11 SP3 Customers should include the Zypper rpm in their image as this is a dependency
Please uninstall any previously installed MUS versions - in particular care should be taken with MUS 1.0 installs to remove the independent elofousb-kmp kernel driver package using rpm uninstall
Example:
# rpm -ev elofousb-kmp-pae-1.0_3.0.13_0.27-4
# rpm -ev elofousb-kmp-default-1.0_3.0.13_0.27-4
Actual name may differ depending your system and any KMP updates but the base name will be the same
elofousb-kmp-<flavor>-<version><kernel-version><release>
The toshiba-mus_op-suse-2.1-{Release-Version}.noarch.rpm contains the operational package and support files that forms the monitor upgrade solution.
# rpm -ivh toshiba-mus_op-suse-2.1-{Release-Version}.noarch.rpm
This will install the Monitor Upgrade Solution (MUS) service and the firmware update utilities in the system as well as other support scripts
Each Upgrade Task is contained in its own RPM package.
These RPMs will install UP Task files under a folder called opt/toshiba/mus/UpdateTasks/. Each task (video, touch, touch configuration) will be installed into its appropriate part of the sub-tree.
Currently known UP Tasks :
toshiba-mus2.1_up_2xx5xx_touch-config_elo-1.0-n.noarch.rpm
toshiba-mus2.1_up_4820-2LX5LX_touch-fw_xxxx-1.0-n.noarch.rpm
toshiba-mus2.1_up_4820-2LX5LX_video-fw_xxxx-1.0-n.noarch.rpm
toshiba-mus2.1_up_4820-21X51X_touch-fw_xxxx-1.0-n.noarch.rpm
toshiba-mus2.1_up_4820-21X51X_video-fw_xxxx-1.0-n.noarch.rpm
toshiba-mus2.1_up_6149_touch-GUID-1.0-n.noarch.rpm
toshiba-mus2.1_up_6149_video-xxxx_xxxx-1.0-n.noarch.rpm
NOTE:
1. xxxx is the version of the firmware.
2. n is the incremental version of the UP which normally contains bug fixes and always start from 1.
3. GUID is the Globally Unique Identifier with 22 characters to identify the content of the UP. Since MUS 2.1, the firmware version of the UP will no longer be included in the UP name as it may contain multiple firmware versions in a UP. User has to check on the release note for the firmware versions it contains.
1. Install by hand
#rpm -ivh toshiba-mus2.1_up_21X51X_touch-fw_010d-1.0-1.noarch.rpm
2. Install at boot time (via the RpmUpdates directory).
The /opt/toshiba/mus/RpmUpdates directory
is the 'magic directory' where the UP RPMs may also be placed when there is a new UP available.
RPMS `dropped` into this directory will get RPM-Installed by the Monitor Upgrade Service on the next system reboot before any update tasks are run.
You could use FTP or other file transfer to put UP RPMS into the directory.
After this kind of install the RPM package will be removed from this directory.
There is an ELO Touch Configuration file:
/opt/toshiba/mus/UpdateTasks/TouchConfig/EloTouch/toshiba-mus2.1_up_2xx5xx_touch-config_elo/eloConfigOpt.ini.
This this is the file that is needed to configure the touch settings of the 4820 monitors with ELO Touch.
This is used by the ELO touch configuration task to update any attached 4820-x1x and 4820-xLx monitors. If the file exists ELO touch settings will be updated on every reboot.
Run the script “mus_uninstall_script” found at the directory /opt/toshiba/mus
The MUS log is placed to /var/log/toshiba/mus/latest/ folder. For normal operations, a minimum log is recorded in the log. However when there is a firmware update operation a thorough logging of the whole process is recorded during boot up of the system.Take note also that a maximum of ten recent logs shall be save in the log's history folder. To view previous logs please take a look at the history folder.
1. MUS 2.1 Linux does not support power loss/ unplug power cable and unplugging of power USB cable from the attached 4820- 21X/51X monitor while a touch firmware update is ongoing. Doing so will cause undesirable damage to the firmware and perhaps to the monitor itself.
2. A possible segmentation fault occurs when a configuration of both 6149 and 4820 Monitor types are attached in a system while performing a video firmware update for the 6149 Monitors. This is a known issue being thrown by the library libusb-1.0 version 1.0.8 when doing asynchronous bulk transfer. This library is being use by the video firmware update utility. To recover firmware update, the customer must remove the 4820 Monitors first before rebooting the system to trigger firmware update.
July 27, 2015 - Updated UP tasks and Known Issues
February 27, 2015 - Version 2.1
February 27, 2014 - Fixes for Autorecovery defects, Change Product ID to 6149
February 05, 2014 - Initial Release