Feature Enhancements for 882CA/882C/881C Release 2.10.2 - vxWorks: 20.1884602


Important Note: This release can be used on an 882CA with or without the HDCP Compliance Test option. This is a unified release for 88xC(A).

Known Issue #1: The ability to corrupt bits in the CEC cores is broken. This affects CECT 9.5-1 of the CEC Compliance Test. This will be fixed in a future release. If CECT 9.5-1 is one of the tests you need to run for your DUT, please use beta 4505 instead. This is based on release 2.9.0 and has some of the bug fixes shown below.

Known Issue #2: HDCP Compliance Test applet on the web interface is broken. HDCP Compliance Test can be run via front panel or command line.

The following features are included in the Release 2.10.2.

• EDID Compliance Test now supports HDMI CTS 1.3b.
• Added DMT1360H format.
• For development purposes, CEC devices should be able to force a logical address to one that is already found on the bus. The command to use is CEC<N>:CECU 1 where N is 1, 2, or 3. Below is an example.

// Force a logical address. This may result in more than one CEC device with the same logical address.
CEC1:CECL CECDev01
CEC1:CECU 1

// Take the next available logical address for the same CEC device type. This is the normal way.
CEC1:CECL CECDev01
CEC1:CECU

The following anomalies have been corrected in the Release 2.10.2.

• General HDCP Compliance Test improvements.
• Fixed the problem where CEC Rx start error (10303) and Tx line error (10310) show up when extreme 0 bit low period is set.
• Changed labeling for ReadRGB function with YCbCr source. ReadRGB function is renamed to ViewPix, and YCbCr 4:4:4 and 4:2:2 information is shown properly.
• Fixed the problem where AFD test image doesn't restore state properly.
• Fixed the problem where AV mute bit is not set when changing formats.
• Fixed the problem where Format image's text gets chopped off on the left and top side depending on the format.
• Fixed the problem where 10-bit YCbCr Ramp12 (grayscale mode) bottom ramp shows some green on the end.
• Fixed the problem where 10-bit Ramp12 does not show correct number of bits on bottom ramp.
• Changed Audio images' text so that SPDIF and I2S audio are no longer shown.
• Fixed the problem where video resets itself if in external audio mode when no external audio is present.
• Fixed the problem where *rst command doesn't return with a prompt in HyperTerminal.
• Removed HDCP menu item from the main menu until the HDCP tester mode is fully functional.
• Fixed the problem where TOGG command doesn't return with a prompt in HyperTerminal.
• Fixed the problem where Monoscope doesn't draw properly in 1360x768.
• Fixed the problem where non-root CEC devices could get the physical address of 0.0.0.0.
• Fixed some problems with HdcpProd and HDCP query.
  

• Test steps TT01 and TT02 of Test Section 1A-01 are not tested because the application does not have visability 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 visability 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.
  
  
• Test Section 1A-09 cannot be tested because the application cannot collect the TMDS video.
  
  
• Test Section 2C-01 test S302 cannot be tested because the application cannot currently process Pj. Therefore a Pass result on the test report only applies to the tests within that section that are executed.
  
  
• Test Section 2C-04 cannot be tested because the application cannot collect TMDS data.
  
  

• do not use CMD Terminal tool in the generator's web interface to run the Compliance Test via command line; use Telnet (Ethernet) or HyperTerminal (serial) instead
  
  
• 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)
  
  
• running the tests using release 2.6.1 (20.1883610 firmware) saves the test reports in /tffs0/library/reports/
  
  
• running the tests using a beta firmware (20.1883611 and later) or release 2.10.2 (20.1884602 firmware) saves the test reports 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/882EA (ACA monitoring device) to TPA-ACA-3R's OUT 1
  
  
• use the ACA on the 882C/882CA/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.10.2 is comprised of the following software components.

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, or 2.9.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

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, or 2.9.0, upgrade your generator using the procedures below:

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



4. Verify that the vxWorks file is: 20.1884602.
5. Verify that the BootRom version is: 01.04.11.
6. Verify that the generator is running the current 2.10.2 version of the gateware files by entering the following command:
   
   verg?
   256C,41,5312006:223F,80,6112007:253A,11,5142007



7. The first listing is the CPLD gateware. It might be 253C, 255C, 257C, or 258C. 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,80,6112007.
8. Verify that the Rx gateware file (the third item listed) is: 253A,11,5142007.

You can obtain Release Notes for past releases as follows:

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