Product

Kodak Magnus 800

Background

The Magnus 800 platesetter and the Magnus 800 autoloader each contain one master system board (MSB). Each MSB is loaded with four hex files and consists of approximately 82,000 lines of source code which produce 480KB of binary code.
This procedure describes how to manually upgrade the MSB embedded software via the host monitor.

Procedure

Upgrading the MSB software via the host monitor

Important: Loading the MSB embedded software with the host monitor application can only be performed after either loading the boot code with the MSB cable, or if the MSB board has been shipped with the boot code pre-installed. From August 2005, all boards leaving the factory have the boot code pre-installed.

1. Exit Magnus Controller.
2. Locate the HostMonitor folder (C:\Magnus\COMP_UDC\AllPrj\Common\Bin\ExternalTools\HostMonitor)
3. Double-click the host monitor icon.
4. Double-click HostMonitor.exe.
5. In the dialog box that appears, click Run Script.
6. Locate and then load either one of the following files (The choice is dependant upon the MSB you wish to upgrade):
   • PlatesetterGoToBoot.txt
   • AutoloaderGoToBoot.txt
7. Wait until the Run Script button is enabled.
   Important: During the loading process, avoid running other applications on the computer.
8. In the dialog box, click Run Script.
9. Locate and then load either one of the following files (The choice is dependant upon the MSB you wish to upgrade):
   • PlatesetterMsbFullDownload_New_C.txt
   • AutoloaderMsbFullDownload_New_C.txt
10. Wait until the Run Script button is enabled.
11. After the files have been successfully loaded, the following lines appear in the Host Monitor window:
    Cmoonent index = 0 ,ID = 6
    Cmoonent index = 1 ,ID = 5
    Cmoonent index = 2 ,ID = 1
    Cmoonent index = 3 ,ID = 4
    Cmoonent index = 4 ,ID = 2
12. Restart the platesetter.
13. Startup Magnus Controller.

Note: If you are experiencing problems loading the MSB firmware, then perform the following actions:

1. In the host monitor, enter the command dsc 255. This will erase the board’s memory.
2. Restart this procedure from step 8.

Technical contact(s)

Content owner: Yaron Shifman
See the Escalation page for escalation contacts.

Date submitted

25 Aug 2005