background image

November 28, 2012 | Cisco Systems | PrecisionHD 4X Camera Connectivity Problems 

 

PrecisionHD 4X Camera Connectivity Problems 

 
Recently camera connectivity and camera boot problems with PrecisionHD 4X cameras (CTS-PHD-1080P4XS1=) 
have been reported in the field.   We have narrowed down the reported problems to three scenarios: 
 

1.

 

Failed Camera Boot   Failed Initialization (solution available); please see the following Field Notice for 
more information:  

http://www.cisco.com/en/US/partner/ts/fn/635/fn63534.html

 

2.

 

Failed Camera Boot   Continuous Reboot (Preventable but once failed requires RMA) 

3.

 

Wake from Standby (solution and workaround available) 

 
The only scenario above where a replacement is required is scenario 2, as the camera cannot be returned to a 
working state.  All other scenarios have a solution that will restore full camera function.  Root cause has been 
identified for all issues and are listed below. 
 

IMPORTANT NOTES REGARDING FAILED CAMERA BOOT   FAILED INITIALIZATION: 

 

1.

 

Once a PrecisionHD 4X camera displays symptoms of a failed camera initialization (details listed 
Camera Boot   

 the camera must be recovered using either recovery procedure listed in 

this document.  Corrected camera firmware is found in TC4.2.4 and TC5.1.3 and higher; however, merely 
upgrading to a higher version will not correct a camera already in this state.   

 
2.

 

Starting with TC5.1.5, a recovery method for cameras in this failed initialization state can be run from the 
command line of the codec; this is the recommended recovery method.   A second, longer recovery method is 
also provided in this document. 

 

3.

 

If a PrecisionHD 4X camera is currently not displaying any symptoms of failed initialization and otherwise 
operating normally, Cisco recommends upgrading all codecs with a CTS-PHD-10804XS1 connected to a 
software release containing fixed camera firmware (TC4.2.4 or TC5.1.3 or higher). 

 
4.

 

A failed camera initialization can potentially occur at any time; if symptoms of scenario 1 are displayed on a 
previously working camera, the camera must be manually recovered using one of the recovery procedures 
found in this document. 

 
TC4.2.4 and TC5.1.X software (CCO login required): 
 

http://www.cisco.com/cisco/software/release.html?mdfid=283613658&flowid=22765&softwareid=280886992&re
lease=TC5.1.5&relind=AVAILABLE&rellifecycle=&reltype=latest

 

 
Field Notice: 
 

FN - 63534 - PrecisionHD 1080p 4x Camera Does Not Boot up Due to Checksum Validation Failure - S/W Upgrade 
Recommended

 

 
 

 
 
 

 
 

Summary of Contents for PrecisionHD 4X CTS-PHD-1080P4XS1

Page 1: ...ither recovery procedure listed in this document Corrected camera firmware is found in TC4 2 4 and TC5 1 3 and higher however merely upgrading to a higher version will not correct a camera already in this state 2 Starting with TC5 1 5 a recovery method for cameras in this failed initialization state can be run from the command line of the codec this is the recommended recovery method A second long...

Page 2: ...ition 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 CSCua44699 Camera fails to boot due to checksum validation failure As a result of the above the camera cannot be controlled by the codec NOTE The issue described above faile...

Page 3: ...er version if required The camera firmware version containing the fix is found in 20011 and later The current camera firmware version is found by viewing the softwareID as shown in s camera screenshot below Fixed camera firmware is bundled with TC4 2 4 and TC5 1 3 or later codec software Upgrading cameras currently not exhibiting this failure is MANDATORY to prevent any future failure Once the cam...

Page 4: ... Release Notes for more information http www cisco com en US docs telepresence endpoint software tc5 release_notes tc_software_release_not es_tc5 pdf recovery method will take roughly 10 minutes to complete When complete the codec and the camera should be fully operational Below is an example output of the sh The progress of the script can be monitored if root access is enabled on the codec Once t...

Page 5: ...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 Capab...

Page 6: ...ortant Notes Regarding Failed Camera Boot Failed Initialization on page 1 for cameras that are currently in a working state but are potentially affected per the Field Notice 3 Wake from Standby Certain Precision HD 4X cameras may also display the following after working for a period of time 1 System is configured for standby 2 System goes into standby 3 When system resumes from standby camera cann...

Page 7: ...the command line of the codec this is the recommended recovery method The previous recovery method documented here still works but requires additional steps and configuration when The rest of this document pertains to the previous recovery method this should not be used if you have upgraded to TC5 1 5 Again the systemtools camerarescue command in TC5 1 5 has superseded the method below In order to...

Page 8: ...e are below if you wish to make one Please note you must have a null modem cable DB9 F F in order to establish a successful serial connection to the camera Null modem cables can also be purchased at any large computer outlet Please note the camera needs to be powered by means of an external power supply either use the power supply from the C20 codec or use the external 12V 2A power supply for the ...

Page 9: ...in this procedure Once the cables are connected you must determine the COM port number assigned by the system The COM port number can be determined by opening up Device Manager and expanding Ports COM LPT and checking which COM has been assigned to your USB to Serial connection You will need the COM port number to connect using the terminal emulation program In the below example the system assigne...

Page 10: ...u can open the terminal emulation program by going to Start Run and typing in c serial_shell trfs_mini_shell exe Verify Failed Camera Boot Failed Initialization Once all cables are connected software is installed and the connection to the COM port is established using the terminal emulator apply power to the camera by either a plugging in the C20 power cable b using a 12V 2A power supply with appr...

Page 11: ...m validation fails No valid Uimage presentSANGAM If you encounter the above then please proceed on to the next section below However if you encounter the output listed below at the serial console then the camera is constantly rebooting the base LED will remain solid green but the orange LED on the camera will be flashing on off at a steady rate DM365 chip initialization done Board id 00000001 Vers...

Page 12: ... Linux USB Recovery Procedure This method is NOT the preferred method and should ONLY be used as a last resort NOTE The USB drivers do not work on Windows 7 If you install the USB drivers on a Windows 7 machine it will disable all other USB NIC and modem devices until the USB drivers are uninstalled and the PC rebooted Required cables 1 VISCA camera control cable shipped with the C20 DB9 M to RJ45...

Page 13: ...e C20 codec or use the external 12V 2A power supply for the 4X camera part number PSU CAM V See also http www cisco com en US prod collateral ps7060 ps11307 ps11335 data_sheet_c78 669051 html Required Software Terminal Emulation program To access the camera via the serial port one needs to have a terminal emulation program which can talk to a serial COM port set to 115200 bps 8 bits 1 stopbit and ...

Page 14: ...ed files needed are o Libusb win32 filter bin 0 1 12 1 zip o Usb_shell zip o Sangam zip The zipped file can be downloaded at either of the following links https supportforums cisco com servlet JiveServlet downloadBody 25088 102 4 62752 4XUSBRecoveryFiles zip https supportforums cisco com docs DOC 25088 Cisco can provide a zipped file containing all of the above on an as needed basis Installing the...

Page 15: ...modem serial cable to the camera Connect the cables as follows Camera control RJ45 port Camera control DB9 M port DB9 F F Null modem cable USB to serial DB9 M PC USB port Once the cables are connected open up PuTTY and connect via Serial connection The COM port number can be determined by opening up Device Manager and expanding Ports COM LPT and checking which COM has been assigned to your USB to ...

Page 16: ...om Serial Connection A camera not detected by the codec i e xstatus camera 1 shows Connected false will show something similar to the below error on initial boot from console note the Checksum validation fails lines present Keep in mind there can be variations of the below but the camera will always fail to initialize When the camera fails to initialize the base LED will be solid green and the cam...

Page 17: ...on serial connection but now in the USB shell Recovering the Camera Software From the SANGAM prompt execute the command u0 fu u0 Sangam pkg d which will copy the Sangam pkg on the camera Below is the output of a correct upgrade SANGAM SANGAM u0 fu u0 Sangam pkg d total file size read 4375240 Package file size 4375240 read 0 Id is correct Version check passed Package checksum is correct File size c...

Page 18: ...ecksum 212E9ADF Pkg is a valid package and its contents are uncorrupted Invalid file name for file 0 Invalid file name for file 1 TBL upgrade src_buf 0x834FB0B0 sz 0x0001A800 Min Version 0 max version 3748 Current version 3749 New version 3749 block_start 1 block_end 12 TBL upgrade successful FPGA upgrade src_buf 0x835158B0 sz 0x0001C800 Min Version 0 max version 2542 Current version 2543 New vers...

Page 19: ...sum errors you should see the camera go straight to Booting Linux as in the below example DM365 chip initialization done Board id 00000001 Version id 00000006 version 5 Configuring FPGA Done boot_delay 3 boot_delay 2 boot_delay 1 boot_delay 0 Booting Linux Once successful camera boot is verified connect the camera with its newly programmed software to the C series codec Verify the camera is succes...

Reviews: