Feature Enhancements for 882CA/882C/881C Release 2.16.3 - vxWorks: 20.1885803

Notice: For this release, the CA platform cannot perform HDCP compliance test for source or repeater

• Added image caching capability.
• EDID 1.4 EDIDs can now be parsed and shown in EdidData and Edid2 images as well as EDID Editor.
• HDCP transactions are parsed and shown in ACA.

The following anomalies have been corrected in the Release 2.16.3.

• Improved SAM+ so that a more reasonable closest format is shown.
• Improved SAM+ so that it's easier to see which values are measured and which values are expected by SAM+.
• Lipsync toggle menu now shows up when you select LipSync or LipSyncB image and press Options.
• Added more robust syntax checking for TIME command that sets the clock. Syntax is TIME hh mm ss in order to set the clock as hh hours, mm minutes, ss seconds.
• Fixed the problem where the EDID Editor doesn't allow some fields to change.
• Fixed the problem where repeated command queries such as FMTQ? sometimes causes the generator to lock up.
• Fixed the problem where loading EDID from 882 Analyzer Port 1 in EDID Editor loaded from VGA instead of HDMI Tx 1. Loading from Port 1 now loads EDID from HDMI Tx 1, Port 2 loads from HDMI Tx 2, and Port 3 loads from VGA.
• Fixed the problem where selecting Pluge image in VGA will hang the generator.
• Fixed MnslCLR image issues.
• Fixed the problem where grays sometimes show a greenish tint in YCbCr.
• Fixed Ri' mismatch problem that occurs sometimes in HdcpProd and HDCP Compliance Test.
• Fixed the ImageShift glitch which occurs every 512 pixels horizontally.
• Fixed the problem where ACA shows incorrect information when it's used with CEC Controller at the same.
• SAM+ HDMI Input Port Number selection now works correctly.
• Fixed a parsing bug in ACA where Bstatus was reported as Rsvd offset.

• Notice: For this release, the CA platform cannot perform HDCP compliance test for source or repeater
  
  
• Test steps TT01 and TT02 of Test Section 1A-01 are not tested because the application does not have visibility into the control bits of the TMDS data islands. Therefore a Pass result on the test report only applies to the tests within that section that are executed.
  
  
• Test steps TT01 and TT02 of Test Section 1B-01 are not tested because the application does not have visibility into the control bits of the TMDS data islands. Therefore a Pass result on the test report only applies to the tests within that section that are executed.
  
  
• Test Section 1A-08 is not tested because this test requires a DVD with a list of KSVs that have been revoked. We will support this in the future when the DVD with SRM is available.
  
  
• Test Section 1A-09 cannot be tested because the application cannot collect the TMDS video.
  
  
• Test Section 2C-04 cannot be tested because the application cannot control the positioning of the encryption enable signal in DVI.
  

• try running the tests in batch mode by using the front panel interface
  
  
• if there is a problem, try running the tests one by one via the command line (see the repeater AB test procedure below as an example and refer to the user guide)
  
  
• the test reports will be saved in /card0/library/reports if there is a PCMCIA card inserted in the 882CA (/tffs0/library/reports/ if no PCMCIA is inserted)
  
  

• you can monitor the transactions on Tx port 1 using the ACA
  
  

• you can monitor the transactions if you have another 882C/882CA/882E/882EA and a TPA-ACA-3R
  
  
• connect the output of the source device to TPA-ACA-3R's DUT 1, the input 1 of 882CA (test equipment) to TPA-ACA-3R's DUT 2, and output 1 of a different 882C/882CA/882E/882EA (ACA monitoring device) to TPA-ACA-3R's OUT 1
  
  
• use the ACA on the 882C/882CA/882E/882EA that is not the test equipment to monitor the transactions on Tx port 1
  
  

• use a separate source device and connect it to the upstream port of the repeater
  
  
• use the 882CA's Rx 1 port as the sink device and connect it to the downstream port of the repeater
  
  
• you can monitor either downstream or upstream transactions (not both at the same time) if you have another 882C/882CA/882E/882EA and a TPA-ACA-3R
  
  
• in order to monitor the downstream transactions, connect the downstream of the repeater device to TPA-ACA-3R's DUT 1, the input 1 of 882CA (test equipment) to TPA-ACA-3R's DUT 2, and output 1 of a different 882C/882CA/882E/882EA (ACA monitoring device) to TPA-ACA-3R's OUT 1
  
  
• in order to monitor the upstream transactions, connect the output of the source device to TPA-ACA-3R's DUT 1, the upstream of the repeater device to TPA-ACA-3R's DUT 2, and output 1 of a different 882C/882CA/882E/882EA (ACA monitoring device) to TPA-ACA-3R's OUT 1
  
  
• use the ACA on the 882C/882CA/882E/882EA that is not the test equipment to monitor the transactions on Tx port 1
  
  

• connect the 882CA's Tx 1 port to the upstream port of the repeater



• connect the 882CA's Rx 1 port to the downstream port of the repeater



• make sure HdcpProd image is not selected on the 882CA before running the tests



• you can monitor the downstream transactions on Rx port 1 using the ACA



• you can monitor the upstream transactions on Tx port 1 using the ACA

CPTX:DUTT 0 // set up for source test
CPTX:CPTR 16 // configure 2C-1 test
CPTX:CPTU // start the test
// save the test report to the PC and rename it

// repeat above steps for test numbers 17 and 18

CPTX:CPTR 19 // configure 2C-4 test
CPTX:CPTU // start the test
// save the test report to the PC and rename it

CPTX:DUTT 1 // set up for source test
CPTX:CPTR 1 // configure 1A-01 test
CPTX:CPTU // start the test
// save the test report to the PC and rename it

// repeat above steps for test numbers 2 to 14

CPTX:CPTR 15 // configure 1B_06 test
CPTX:CPTU // start the test
// save the test report to the PC and rename it

CPTX:DUTT 3 // set up for repeater AB test
CPTX:CPTR 20 // configure 3A-01 test
CPTX:CPTU // start the test
// save the test report to the PC and rename it

// repeat above steps for test numbers 21 to 28

CPTX:CPTR 29 // configure 3B-05 test
CPTX:CPTU // start the test
// save the test report to the PC and rename it

CPTX:DUTT 2 // set up for repeater C test
CPTX:CPTR 30 // configure 3C1-01 test
CPTX:CPTU // start the test
// save the test report to the PC and rename it

// repeat above steps for test numbers 31 to 44

CPTX:CPTR 45 // configure 3C2-09 test
CPTX:CPTU // start the test
// save the test report to the PC and rename it

The Release 2.16.3 is comprised of the following software components.

Now you can use Quantum Data's new AutoUpdate utility to upgrade your generator firmware and gateware. The AutoUpdate utility automates the process of upgrading firmware. It guides the user through the upgrade process, checking the Quantum Data website for the latest version and installing all files in the correct location on the generator.

Read the AutoUpdate Instructions.
Download AutoUpdate Version 1.1.1 for 880 series (includes instructions)

You can upgrade your generator using the procedures in the Users Guide. Please note that you will have to verify that your current generator is operating with Release 2.1.x, 2.2.x, 2.3, 2.4, 2.5.x, 2.6.0, 2.8.1, 2.8.2, 2.9.0, 2.10.2, 2.10.4, 2.11.0, 2.12.0, 2.13.1, 2.13.3, or 2.15.0. To verify that your current generator is operating with one of these releases, enter the following command:

verf?

Release 2.1.0 should return the following information:

20.1882508, 01.04.11

Release 2.2.0 should return the following information:

20.1882800, 01.04.11

Release 2.2.1 should return the following information:

20.1882901, 01.04.11

Release 2.2.2 should return the following information:

20.1882903, 01.04.11

Release 2.2.3 should return the following information:

20.1882910, 01.04.11

Release 2.3 should return the following information:

20.1883000, 01.04.11

Release 2.4 should return the following information:

20.1883200, 01.04.11

Release 2.5.4 should return the following information:

20.1883404, 01.04.11

Release 2.5.5 should return the following information:

20.1883405, 01.04.11

Release 2.6.0 should return the following information:

20.1883600, 01.04.11

Release 2.8.1 should return the following information:

20.1884200, 01.04.11

Release 2.8.2 should return the following information:

20.1884202, 01.04.11

Release 2.9.0 should return the following information:

20.1884400, 01.04.11

Release 2.10.2 should return the following information:

20.1884602, 01.04.11

Release 2.10.4 should return the following information:

20.1884604, 01.04.11

Release 2.11.0 should return the following information:

20.1884800, 01.04.11

Release 2.12.0 should return the following information:

20.1885000, 01.04.11

Release 2.13.1 should return the following information:

20.1885201, 01.04.11

Release 2.13.3 should return the following information:

20.1885203, 01.04.11

Release 2.15.0 should return the following information:

20.1885600, 01.04.11

After verifying that the generator is operating with either Release 2.1.x, 2.2.x, 2.3, 2.4, 2.5.x, 2.6.0, 2.8.1, 2.8.2, 2.9.0, 2.10.2, 2.10.4, 2.11.0, 2.12.0, 2.13.1, 2.13.3, or 2.15.0, upgrade your generator using the procedures below:

1. Download the 2.16.3 Zip file to your PC and unzip the file. There will be a System and a Library directory.
2. Upgrade the generator using "Upgrading without using PC Card" procedure at this link.
   
3. After power cycling the generator, verify that the generator is running the current 2.16.3 version of the vxWorks file by entering the following command:
   
   verf?
   20.1885803, 01.04.11



4. Verify that the vxWorks file is: 20.1885803.
5. Verify that the BootRom version is: 01.04.11.
6. Verify that the generator is running the current 2.16.3 version of the gateware files by entering the following command:
   
   verg?
   256C,41,5312006:253F,84,4242008:253A,16,5022008



7. The first listing is the CPLD gateware. It might be 253C, 255C, 257C, or 258C.
8. The next two listings are the Tx and Rx gateware respectively. The gatewares are separated by colons. Verify that the Tx gateware file (the second item listed) is: 253F,84,4242008.
9. Verify that the Rx gateware file (the third item listed) is: 253A,16,5022008.

You can obtain Release Notes for past releases as follows:

88xC(A) Release 2.15.0
88xC(A) Release 2.13.3
88xC(A) Release 2.13.1
88xC(A) Release 2.12.0
88xC(A) Release 2.11.0
88xC(A) Release 2.10.4
88xC(A) Release 2.10.2
88xC(A) Release 2.9.0
88xC(A) Release 2.8.2
88xC(A) Release 2.8.1
88xC(A) Release 2.6.0
88xC(A) Release 2.5.5
88xC(A) Release 2.5.4
88xC(A) Release 2.4
88xC(A) Release 2.3
88xC(A) Release 2.2.3