The toshiba_4820_2xx_5xx_MUS_Operational_Package-1.0.14.bz2.run contains the operational packages and support files that forms the remote monitor firmware update solution. This also includes the Toshiba POS Monitor Inventory Driver for Linux 1.2 toshiba-dspdrv-suse-1.2.3-1.0.i586.rpm package. This self extracting archive file will need the Python 2.6 packages and the Elo KMP Kernel Drivers support packages to be already installed in the system.
1. Python 2.6 ( http://www.python.org/download/releases/2.6.8/)
2. Elo fousb kmp kernel drivers(http://www.elotouch.com/Support/Downloads/dnld_company.asp)
elofousb-kmp-default-1.0_3.0.13_0.27-4.i586.rpm - For “default” configurations
elofousb-kmp-pae-1.0_3.0.13_0.27-4.i586.rpm - For “pae” configurations
% sudo ./toshiba_4820_2xx_5xx_MUS_Operational_Package-1.0.14.bz2.run
This will install the Update scripts and the video( Sampo 4820MonUtil) and touch( elodownload, eloconfig) firmware update utilities in the system as well as the toshiba-dspdrv-suse-1.2.3-1.0.i586 driver.
The monitor should be connected to the system unit by the usb cable provided with the monitors identified in the section: Monitor Support below.
The monitor update solution log is placed to /var/log/toshiba/MonitorUpgrade/mus/MonitorUpgrade.log. 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.
There is a configuration file /etc/opt/toshiba/MonitorUpgrade/CONFIGS/elo/eloConfigOpt.ini. This is the .ini file that is needed to change the touch configuration of the monitor.
SLED 11 with Service Pack 2 32-Bit
SLES 11 with Service Pack 2 32-Bit
SLEPOS 11 with Service Pack 2 32-Bit
The solution may run on other operating systems but this is not supported by Toshiba Global Commerce Solutions at this time.
4820-4676
4820-4677
4820-4678
4820-4679
1.Customer needs to know that while doing Firmware Update, the system will have to reboot twice. First is after the Firmware update Package(UP) is executed, customer is asked to reboot the system to trigger the update. Second, while in the middle of the boot process, just after the MUS finished updating, it will do another reboot. Take note also that whether the update was successful or not the system will undergo two reboots to put back the system into operating condition again.
2.Only ONE Update task should be perform at time. If there are multiple monitor types to be updated, then the user should run each update package for each monitor type one at a time in order to update all monitors.
3.Toshiba MUS will not support a customer setup with which there are a HID-based UPS or similar devices which might affected by the loading and unloading of USBHID by the ELO scripts. ELO is the vendor that provides the Update Utilities to update the Touch firmware of the Monitor, which in turn Toshiba MUS calls during reboot automatically depending on the update task. However, this scenario will not happened as long as the script being is used is the TGCS modified Elo Scripts which is customized to run on SuSe kernels allowed by TGCS.
4.Toshiba MUS will not proceed to update any succeeding monitors when updating the video firmware of the first attached monitor goes into recovery mode. This is the behavior that the Video Firmware Update tool from Sampo was designed. Sampo is the vendor that provides the Video firmware of Toshiba Monitors.
5.During Video firmware update of Multiple 4820_2xx/5xx Monitors. It is expected that the user should not logged in to X first unless all the monitor video firmwares are already updated. It is a known limitation that MUS can allow the user to logged in into X after the first monitor has been updated already while the other monitors are still doing the update in the background.
6.Auto recovery of monitor updates will be one monitor at time. This means that when there are multiple monitors which have failed Firmware Update, then the user should perform recovery multiple times.
Tue April 30, 2013 - Initial Release