November 28, 2012 | Cisco Systems | PrecisionHD 4X Camera Connectivity Problems
5
If the recovery script fails to recover the camera, details of why the script failed are found in the historical log
bundle in the camera-rescue.log file. Also, make sure the camera is connected to the serial port of the codec
before running the shell command to recover the camera. If the fault cannot be isolated, please work with the TAC
to determine the cause of the failure.
Important Notes Regarding Failed Camera Boot Failed Initialization
before
proceeding.
2. Failed Camera Boot Continuous Reboot
Customers are also reporting the following symptoms on new installs (new out of box), new replacements
out of box), or after rebooting the codec on a previously working installation for certain Precision HD 4X cameras:
1.
Orange LED on camera blinks on/off at a steady rate.
2.
Green LED present on base of camera.
3.
No PTZ control from any input device (e.g. touchpanel, remote, etc.)
4.
No video on self-view from camera.
5.
The admin CLI command "xstatus camera 1" shows "Connected: False" and no other camera information
is displayed.
xstatus camera 1
*s Camera 1 Connected: False
*s Camera 1 HardwareID: ""
*s Camera 1 Manufacturer: ""
*s Camera 1 Model: ""
*s Camera 1 SoftwareID: ""
*s Camera 1 SerialNumber: ""
*s Camera 1 IpAddress: ""
*s Camera 1 MacAddress: ""
*s Camera 1 Position Pan: 0
*s Camera 1 Position Tilt: 0
*s Camera 1 Position Zoom: 16
*s Camera 1 Position Focus: 4000
*s Camera 1 Capabilities Options: ""
*s Camera 1 Flip: "Off"
** end
OK
6.
Power cycling the camera or codec does not allow codec control of the camera.
Details regarding the above problem are documented in the following bug:
CSCua51146
Header chksum mismatch for factory image of second stage bootloaderUBL
The camera is constantly rebooting itself due to a header checksum mismatch on the factory image during
bootloader initialization. As a result of the above, the camera cannot be controlled by the codec.
Root Cause:
The root cause has been found by our camera team and is fixed in TC 4.2.4 and TC 5.1.3 and higher, both of which
contain corrected camera firmware. In summary, a bug was found in our error correction; the new NAND flash
found in recent cameras, being a different technology, is more likely to have correctable errors, and made the bug
