2-100 Chapter 2 Troubleshooting

2.6 Controller (CP-Cont) Troubleshooting

2.6.1.2 Boot Messages Displayed on Terminal If any errors are detected during Power On Self Test by BIOS, any of the following error
When the controller (CP-Cont) starts up, booting up is performed in the following main steps: messages appears. (For the actions against errors, refer to2.6.2 Troubleshooting the
1) Power ON Self Test by BIOS Controller (CP-Cont) During Boot"
2) The VxWorks OS starts up Chain
Error Details Error Message
3) Communication port setting -Link
4) Application starts up and starts communications with the IOT, IIT, and UI. ERROR
The following lists the messages displayed on the terminal program screen for each of the CMOS 0271:Check date and time settings
step above. 116-310 Checksum ERROR
Note For your convenience, this section lists the messages as per step. Error 0251:System CMOS checksum bad - Default
However, they appear as a series in the actual situation. configuration used
1) Power ON Self Test by BIOS Memory ERROR
116-311
a. Displays BIOS version, CPU, and memory check, etc Check Error 0B4A: Memory Test Alarm occurred.
With this screen, it is possible to check the BIOS version and CPU etc. However, it is ERROR
116-312 HDD Error
difficult to check them because this screen is immediately replaced with BIOS 0B49:HDD Diagnostic alarm
summary if memory capacity has not been changed or no errors have occurred in ERROR
116-313 Battery Error
Power ON Self Test. 0B44:System battery out of the range
CPU Fan
BIOS 4.0 Release 6.0.0008 ERROR
Copyright 1985-2003 Phoenix Technologies Ltd. 116-314 Rotation
0B46:CPU Fan alarm occurred
All Rights Reserved Count Error
CPU
ERROR
116-315 Temperature
CPU = VIA C3 1000A MHz 0B45:CPU Temperature out of the range
639K System RAM Passed Error
1279M Extended RAM Passed System Fan ERROR
116-316
64K Cache SRAM Passed Error 0B4B:System Fan Alarm occurred
System BIOS shadowed ERROR
Fixed Disk 0: SAMSUNG SP0411N PCI Resource
116-317 Resource Conflict - PCI in slot 01 Bus00, Device07,
Conflict
Function00
The following appears if memory capacity has been changed. 116-318 OS not found Operating System not found
BIOS 4.0 Release 6.0.0008 When an error message appears, the following message may appear at the same time.
Copyright 1985-2003 Phoenix Technologies Ltd. However, they can be ignored.
All Rights Reserved Chain
Error Details Error Message
-Link
CPU = VIA C3 1000A MHz Keyboard WARNING
-
639K System RAM Passed Error 0211:Keyboard error
1003M Extended RAM Passed The installed memory is fully checked WARNING
and this part is incremented. - FDD Error
02B0:Diskette Drive A errorr
In normal situation, memory full The following shows an example when HDD error (e.g. power is not supplied to the
64K Cache SRAM Passed
check is skipped and BIOS summary
System BIOS shadowed HDD, or it is not connected) is detected.
is displayed.
Fixed Disk 0: SAMSUNG SP0411N
BIOS 4.0 Release 6.0.0008
System Configuration Data updated
Copyright 1985-2003 Phoenix Technologies Ltd.
All Rights Reserved
---------------------------------To be continued---------------------------------
 ---------------------------------Continued--------------------------------- 2) VxWorks (OS) Boot

CPU = VIA C3 1000A MHz VxWorks System Boot

639K System RAM Passed
1279M Extended RAM Passed
64K Cache SRAM Passed
System BIOS shadowed Copyright 1984-1998 Wind River Systems, Inc.

System Monitoring Check....Passed

WARNING
0211: Keyboard error
ERROR CPU: VIA C3 Nehemiah
Error message about HDD failure Version: 5.4.2
0B49: HDD Diagnostic alarm
WARNING BSP version: 1.2/0
02B0: Diskette drive A error Creation date: Aug 24 2004, 15:30:44

Press <F1> to resume, <F2> to Setup Press any key to stop auto-boot...
0
auto-booting...
b. BIOS Summary Display
This display allows you to check the installed memory capacity and HDD capacity, etc.
Note As the BIOS summary is displayed over data such as CPU memory boot device : tffs=0,0
unit number :0
check, there are cases where some data might remain.
processor number :0
file name : /tffs0/vxWorks
+-----------------------------------------------------------------------------------------------------------+ inet on ethernet (e) : 129.249.150.150:ffffff00
| PhoenixBIOS Setup Utility | flags (f) : 0x8
| | target name (tn) : ryoma
| CPU Type : VIA Nehemiah System ROM : E9BF – FFFF | startup script (s) : /tffs0/startup.com
| CPU Speed : 1000 MHz BIOS Date : 08/27/04 | other (o) : via
| |
| Extended Memory: 1309696 KB Display Type : Monochrome | Attaching to TFFS... done.
| Shadow Ram : 384 KB Installed memory capacity (1280MB | Loading /tffs0/vxWorks...931440 + 98472 + 29152
| Cache Ram : 64 KB in this example) | Starting at 0x108000...
| |
| Hard Disk 0 : 40060MB HDD capacity (40GB in this example) | Attached TCP/IP interface to via unit 0
| Hard Disk 1 : None | Attaching interface lo0...done
| Hard Disk 2 : None |
| Hard Disk 3 : None | Adding 4037 symbols for standalone.
+-----------------------------------------------------------------------------------------------------------+
---------------------------------To be continued---------------------------------
If the whole message above is not displayed in full or the display froze at this screen,
an error may have occurred in the motherboard, memory, or processor.

2-101 2.6 Controller (CP-Cont) Troubleshooting

Chapter 2 Troubleshooting
2-102 Chapter 2 Troubleshooting
2.6 Controller (CP-Cont) Troubleshooting

---------------------------------Continued--------------------------------- 3) Communication Port Settings

***** USB board PCI resources *****
Bus No = 00000000
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
Device No = 00000010
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] Func No = 00000003
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] interrupt level = 5
]]]]]]]]]]] ]]]] ]]]]]]]]]] ]] ]]]] (R) mem base0 (for USB) = fe822400
] ]]]]]]]]] ]]]]]] ]]]]]]]] ]] ]]]] mem base1 (for -----) = 00000000
]] ]]]]]]] ]]]]]]]] ]]]]]] ] ]] ]]]] mem base2 (for -----) = 00000000
]]] ]]]]] ] ]]] ] ]]]] ]]] ]]]]]]]]] ]]]] ]] ]]]] ]] ]]]]] mem base3 (for -----) = 00000000
io base0 (for USB) = ffffffff
]]]] ]]] ]] ] ]]] ]] ]]]]] ]]]]]] ]] ]]]]]]] ]]]] ]] ]]]]
io base1 (for -----) = ffffffff
]]]]] ] ]]]] ]]]]] ]]]]]]]] ]]]] ]] ]]]] ]]]]]]] ]]]]
io base2 (for -----) = ffffffff
]]]]]] ]]]]] ]]]]]] ] ]]]]] ]]]] ]] ]]]] ]]]]]]]] ]]]] io base3 (for -----) = ffffffff
]]]]]]] ]]]]] ] ]]]]]] ] ]]] ]]]] ]] ]]]] ]]]] ]]]] ]]]] Device Type = 00003104
]]]]]]]] ]]]]] ]]] ]]]]]]] ] ]]]]]]] ]]]] ]]]] ]]]]]]] Device Revision = 00000082
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] value = 0 = 0x0
]]]]]]]]]]]]]]]]]]]]]]]]]]]]] Development System cd("/ata0_p0")
]]]]]]]]]]]]]]]]]]]]]]]]]]]] value = 0 = 0x0
]]]]]]]]]]]]]]]]]]]]]]]]]]] VxWorks version 5.4.2
Done executing startup script /tffs0/startup.com
]]]]]]]]]]]]]]]]]]]]]]]]]] KERNEL: WIND version 2.5
-> 0x414812c (usbdEhciInt):
]]]]]]]]]]]]]]]]]]]]]]]]] Copyright Wind River Systems, Inc.,1984-2002 usbdEhciIntMain:Port changed
0x414812c (usbdEhciInt): usbdEhciIntMain: Port[0]=0x1803,Port[1]=0x1803
CPU: VIA C3 Nehemiah. Processor #0. usbDD:(usbDDInit) usbDDInit successful
Memory Size: 0x4bff000. BSP version 1.2/0. *** Waiting for a USB plug check (10sec) ***
WDB: Ready. 0x4144500 (usbdEhciRootHub): usbdEhciRootHubCheck:PortId=0 connected
0x4144500 (usbdEhciRootHub): usbdEhciRootHubRequset:PortId=0 reset
Executing startup script /tffs0/startup.com ...
0x4144500 (usbdEhciRootHub): usbdEhciRootHubRequset:PortId=0 reset
usrAtaConfig(0,0,"/ata0_p0,/ata0_raw,/ata0_p1,/ata0_p2,/ata0_p3,/ata0_p4,/ata0_p
0x4144500 (usbdEhciRootHub): usbdEhciRootHubRequset:PortId=0 reset
5")
0x4144500 (usbdEhciRootHub): usbdEhciRootHubCheck:PortId=1 connected
value = 0 = 0x0 0x4144500 (usbdEhciRootHub): usbdEhciRootHubRequset:PortId=1 reset
ld < /tffs0/ftpdLib.o 0x4144500 (usbdEhciRootHub): usbdEhciRootHubRequset:PortId=1 reset
value = 75478604 = 0x47fb64c 0x4144500 (usbdEhciRootHub): usbdEhciRootHubRequset:PortId=1 reset
ftpdInit Task I/F Save - Memory Clear OK!! Detects the USB connection
*** Open Device (IIT) *** -----> *1 status.
value = 0 = 0x0 usbDD:(iitDDOpen)usbdOpenDevice successful When not connected status
ld < /tffs0/kamld.o usbDD:(iitDDOpen)iit_video usbdOpenPipe successful for IIT or IOT is detected, an
value = 75313304 = 0x47d3098 = ftpdLib.o_bss + 0xe4 usbDD:(iitDDOpen)iit_com usbdOpenPipe successfulerror appears at "*** Open
kamld *** Open Device (IOT) *** -----> *2 Device (xxx) ***" shown to
usbDD:(iotDDOpen)usbdOpenDevice successful the left. (See *1 and *2)
usbDD:(iotDDOpen)iot_video usbdOpenPipe successful
dosChkLib : CLOCK_REALTIME is being reset to WED DEC 08 15:18:30 2004 usbDD:(iotDDOpen)iot_com usbdOpenPipe successful
Value obtained from file system volume descriptor pointer: 0x47da2ec
The old setting was THU JAN 01 00:00:00 1970 ---------------------------------To be continued---------------------------------
Accepted system dates are greater than THU DEC 27 00:00:00 1990
/ata0_p0/ - Volume is OK
KAMATARI IITC board found
 ---------------------------------Continued--------------------------------- *1 : The following appears when a USB connection error between the CP-Cont and IIT
Control PWB is detected.

######EPSV Control Task: Start EpsvCtrl_Task.###### *** Open Device (IIT) ***
baseAddr = 1000 0x41522d4 (ccont_t): Z:/c-cont/kamatari/usbDd/usbdi.c: ERROR:377
irq =5 0x41522d4 (ccont_t): Z:/c-cont/kamatari/usbDd/usbdi.c: ERROR:377
msr = 1006 0x41522d4 (ccont_t): Z:/c-cont/kamatari/usbDd/usbdi.c: ERROR:377
EPSV OFF. :
Version Matched 0x41522d4 (ccont_t): Z:/c-cont/kamatari/usbDd/usbdi.c: ERROR:377
stamp:[0x0220,0x0260,0x0660,0x8660,0x8661] 0x41522d4 (ccont_t): Z:/c-cont/kamatari/usbDd/usbdi.c: ERROR:377
*** UiLanguageCode = Japanese *** 0x41522d4 (ccont_t): Z:/c-cont/kamatari/usbDd/usbdi.c: ERROR:377
offset = 1372 ***** ShutDown Task(FailCode=16251 ChainCode=16 LinkCode=251) *****
**** PANEL_READY Receive **** start TigerScript
Panel Revision :00.01.00 Copy OK: 4595 bytes copied
Figure Revision :00.00.04 Error message indicating Task I/F Save - Write OK!! [/ata0_p2/kamMsgLog20041210145011.bin]
Text Revision :00.00.20 that USB memory is not
Text Set No. :01 connected Done TigerScript
Font Revision :00.00.02 (Normally can be ignored)
Font Set No. :02 *** Open Device (IOT) ***
Init Figure No. :01 usbDD:(iotDDOpen)usbdOpenDevice successful
Init Text No. :01 usbDD:(iotDDOpen)iot_video usbdOpenPipe successful
Flash Map No. :02 usbDD:(iotDDOpen)iot_com usbdOpenPipe successful
0x41522d4 (ccont_t): Z:/c-cont/kamatari/usbDd/usbdi.c: ERROR:377 ######EPSV Control Task: Start EpsvCtrl_Task.######
baseAddr = 1000
Open Device handle Error irq =5
UsbScsiCtrlInit Error msr = 1006
(OUTPUT:iitIf_SndMsg) Error - Send Massage to IIT
(OUTPUT:iitIf_SndMsg) Error - Send Massage to IIT
4) Application Starts up and Starts Communications with IOT, IIT, and UI (OUTPUT:iitIf_SndMsg) Error - Send Massage to IIT
EPSV OFF.
Version Matched
stamp:[0x0220,0x0260,0x0660,0x8660,0x8661]
*** UiLanguageCode = Japanese ***
offset = 1372
**** PANEL_READY Receive ****
Panel Revision :00.01.00
Figure Revision :00.00.04
Text Revision :00.00.32
Text Set No. :01
Font Revision :00.00.02
Font Set No. :02
Init Figure No. :01
Init Text No. :01

----------------------------------To be continued---------------------------------

2-103 2.6 Controller (CP-Cont) Troubleshooting

Chapter 2 Troubleshooting
2-104 Chapter 2 Troubleshooting
2.6 Controller (CP-Cont) Troubleshooting
---------------------------------Continued--------------------------------- ---------------------------------Continued---------------------------------
Map No. :02
0x41522d4 (ccont_t): Z:/c-cont/kamatari/usbDd/usbdi.c: ERROR:377
**** PANEL_READY Receive ****
Panel Revision :00.01.00
Open Device handle Error
Figure Revision :00.00.04
UsbScsiCtrlInit Error
Text Revision :00.00.32
Text Set No. :01
<<< C/P-Cont System Error >>> An error code appears at the end. Font Revision :00.00.02
--> Chain-Link = 016-251 Font Set No. :02
Init Figure No. :01
*2 : The following appears when a USB connection error between the CP-Cont and IOT Init Text No. :01
Flash Map No. :02
Control PWB is detected. 0x41522d4 (ccont_t): Z:/c-cont/kamatari/usbDd/usbdi.c: ERROR:377
*** Open Device (IOT)***
0x41522d4 (ccont_t): Z:/c-cont/kamatari/usbDd/usbdi.c: ERROR:377
0x41522d4 (ccont_t): Z:/c-cont/kamatari/usbDd/usbdi.c: ERROR:377 Open Device handle Error
0x41522d4 (ccont_t): Z:/c-cont/kamatari/usbDd/usbdi.c: ERROR:377 UsbScsiCtrlInit Error
:
: <<< C/P-Cont System Error >>> An error code appears at the end.
0x41522d4 (ccont_t): Z:/c-cont/kamatari/usbDd/usbdi.c: ERROR:377 --> Chain-Link = 016-351
0x41522d4 (ccont_t): Z:/c-cont/kamatari/usbDd/usbdi.c: ERROR:377
0x41522d4 (ccont_t): Z:/c-cont/kamatari/usbDd/usbdi.c: ERROR:377
***** ShutDown Task (FailCode=16351 ChainCode=16 LinkCode=351) *****
start TigerScript
Copy OK: 4532 bytes copied
Task I/F Save - Write OK!! [/ata0_p2/kamMsgLog20041210144439.bin]

Done TigerScript

######EPSV Control Task: Start EpsvCtrl_Task.######

baseAddr = 1000
irq =5
msr = 1006
(IOTIF:iotIf_SndMsg) Error - Send Massage to IOT
(IOTIF:iotIf_SndMsg) Error - Send Massage to IOT
(IOTIF:iotIf_SndMsg) Error - Send Massage to IOT
EPSV OFF.
Version Matched
stamp:[0x0220,0x0260,0x0660,0x8660,0x8661]
*** UiLanguageCode = Japanese ***
offset = 1372

---------------------------------To be continued---------------------------------
2.6.2 Troubleshooting the Controller (CP-Cont) During Boot
It does not boot at all (nothing is displayed on the boot monitor)
Procedure
Replace the Motherboard and Memory in sequence. (PL 8.3)

An error has occurred during BIOS Power ON Self Test

According to the Chain-Link code for "External Device Error" displayed on the Control Panel
or the error message displayed on the boot monitor, perform the following procedures:
CAUTION Always turn the power and breaker OFF before removing or installing
parts. Even if the power is turned OFF, +24VDC is supplied to the
Motherboard.
Note To replace parts, follow the instructions in "Chapter 4
Disassembly/Assembly and Adjustment".
Note If you have switched the DIP SW, restore it to its original position after
servicing.
Chain
Error Details Error Message Procedure
-Link
ERROR Note 01CMOS default value is loaded when CMOS checksum error has
0271:Check date and time settings occurred.
1. Turn the power OFF then ON.
116-310 CMOS Checksum Error → When the system is restored by turning the power OFF then ON, check the
ERROR date and set it to the correct date if necessary.
0251:System CMOS checksum bad - Default configuration used 2. If the CMOS checksum error persists after turning the power OFF then ON,
replace the Motherboard. (PL8.3)
1. Replace the Memory. (PL8.3)
Note When multiple Memories are installed, replace them one by one.
ERROR
116-311 Memory Check Error → If the system starts up correctly, the replaced Memory must be damaged.
0B4A: Memory Test Alarm occurred.
2. If the problem persists after replacing all Memories, replace the Motherboard.
(PL8.3)
1. Check that +5VDC and +12VDC are supplied to the HDD.
→ If they are not supplied, refer to Wiring Data and BSD to check for the relevant
power supply system.
ERROR
116-312 HDD Error 2. Check the IDE cable between the Mother Board and HDD for damage and the
0B49:HDD Diagnostic alarm
connectors for connection failure.
→ If any failure is found, repair the appropriate part.
3. If no failures are found in the above check, replace the HDD. (PL8.3)

2-105 2.6 Controller (CP-Cont) Troubleshooting

Chapter 2 Troubleshooting
2-106 Chapter 2 Troubleshooting
2.6 Controller (CP-Cont) Troubleshooting
Chain
Error Details Error Message Procedure
-Link
Remove the Battery on the Motherboard and check its voltage.
→ If the voltage is measured to be +2.4VDC or lower, replace the Mother Board.
ERROR (PL8.3)
116-313 Battery Error
0B44:System battery out of the range → If the voltage is measured to be higher than +2.4VDC, wipe any contaminations
on the Battery electrodes with clean cloth etc. and then re-install the Battery.
(PL8.3)
1. Check that the CPU Fan is rotating.
→ If the CPU Fan is dirty, clean it.
CPU Fan Rotation ERROR → If the CPU Fan is not rotating or is rotating slowly, check the CPU Fan
116-314
Count Error 0B46:CPU Fan alarm occurred connectors for connection failure.
2. If the problem persists after the above procedures, replace the Motherboard.
(PL8.3)
1. Check the CPU Fan for dirt and abnormalities and clean it. (PL8.3)
ERROR 2. Check the CPU Heat sink for dirt and abnormalities and clean it.
116-315 CPU Temperature Error
0B45:CPU Temperature out of the range 3. If the problem persists after the above procedures, replace the Motherboard.
(PL8.3)
1. Check that the HDD Cooling Fan is rotating.
→ If the HDD Cooling Fan is dirty, clean it.
→ If the HDD Cooling Fan is not rotating or is rotating slowly, check the connectors
ERROR
116-316 System Fan Error for connection failure. If no failures can be found in the connection, replace the
0B4B:System Fan Alarm occurred
HDD Cooling Fan. (PL8.3)
2. If the problem persists after the above procedures, replace the Motherboard.
(PL8.3)
1. Reinstall the firmware.
ERROR
116-317 PCI Resource Conflict 2. If the problem persists after the above procedures, replace the Motherboard.
Resource Conflict - PCI in slot 01 Bus00, Device07, Function00
(PL8.3)
1. Turn OFF the CP-Cont DIP SW Bit 2 (upper) before booting.
→ If the system starts up correctly, there must be an HDD data error or failure.
116-318 OS not found Operating System not found Perform re-installation of firmware.
2. If the problem persists after the above procedures, replace the Motherboard.
(PL8.3)
 An error has occurred after VxWorks boot
Procedure
Turn OFF the CP-Cont DIP SW Bit 2 (upper) before booting.
Note Make sure to restore the DIP SW to its original position after servicing.
→ If the system starts up correctly, there must be an HDD data error. Check the file system
in the controller (CP-Cont) HDD.
(Refer to"2.6.4 Controller (CP-Cont) HDD File System Check")
If no errors are found during the controller (CP-Cont) HDD file system check, re-install the
firmware.
If an error is detected during the controller (CP-Cont) HDD file system check, replace the
HDD. (PL8.3)
An error has occurred at "***Open Device (IIT)***/***Open Device (IOT)***"
Procedure
Swap the IIT and IOT USB connectors that are connected to USB #1/#2 of the CP-Cont and boot
it.
→ If the error location is changed from the IIT to IOT or from the IOT to IIT, replace the
Mother Board. (PL8.3)
→ If the error occurs in the original faulty device (IIT or IOT) even after USB connectors are
swapped between the IIT and IOT, check the USB cable between the CP-Cont and the
device where the error occurred for damage and their respective connectors for
connection failure. If no failures are found, replace the PWB of the device where the error
occurred (IIT Control PWB or IOT Control PWB). (PL8.3/PL8.1)

2-107 2.6 Controller (CP-Cont) Troubleshooting

Chapter 2 Troubleshooting