Feature Enhancements for 882CA/882C/881C Release 2.9.0 - vxWorks: 20.1884400


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: Do not enter SDMG 2; FMTU without connecting external audio to the SPDIF-A/V connector first. The video output will keep refreshing itself because of a hot plug detect issue. This will be fixed in a future release.

Known Issue #2: RampDif shows green bars on the bottom ramp in YCbCr 10-bit mode. This will be fixed in a future release.

Known Issue #3: RampDif in 10-bit mode does not show correct number of bits on the bottom ramp. This will be fixed in a future release.

If you need a beta firmware that fixes the issues above, please e-mail Moon Ki Cho at mcho@quantumdata.com.

Click here for HDCP Compliance Test known issues for Release 2.9.0. The bug fixes will be incorporated into the next maintenance release.

The following features are included in the Release 2.9.0.

• Support for 20 and 24 bit audio.
• Fix for anomalies that were occurring on the Master image (colors reversed) using format 480i2x29 YCbCr 4:2:2 with 8-bit depth
• Added CEC "no response" command. CEC<N>:RSPG <X> command, where <N> is the CEC port number and <X> is 1 or 0, allows the user to enable/disable CEC responses from the 882. When the 882 is configured not to respond to CEC messages, it takes the CEC messages and ACK them normally, but it doesn't talk unless it's told to send a command via command line.
• Added CEC core disable command. CEC<N>:CECN followed by CEC<N>:CECU will disable the CEC device at port number <N>.

The following anomalies have been corrected in the Release 2.9.0.

• Fixed the problem where our Hot Plug Detect misses some 100ms pulses.
• Fixed the problem where DCS sync does not come out on VGA interface properly.
• Fixed the problem where 2C sink HDCP Compliance Tests wrongly reports nonzero bits of Bcaps.
• Fixed the problem where the distance between Ri' reads is too long.
• Fixed the problem where the HDMI 1.3a EDID Compliance Test's Test ID 8-2 shows a WARNING when the monitor name terminating byte does not equal 0x0A. A FAIL should be shown instead.
• HDMI 1.3a EDID Compliance Test's Test ID 8-3 report's wording has changed to reflect CEA-861-D properly.
• When a YCbCr bitmap is loaded, gamma correction is turned off automatically in order to show the bitmap correctly.
• Fixed the problem where 576p50 format is using ITU-709 instead of ITU-609.
• Fixed the problem where the repeater HDCP Compliance Tests check for KSV FIFO to be all zeros.
• Fixed the problem where 3C-II-04 repeater HDCP Compliance Test asserts Bcaps ready as 0xC0 instead of 0xE0.
• Fixed the problem where 2C sink HDCP Compliance Tests do not wait at least 30 frames for playing DVI video to get rid of the HDMI condition.
• Fixed the problem where SAM+ on 882CAs with HDCP Compliance Test option has problems measuring format timings correctly.
• Fixed the problem where the Format Editor doesn't change PELD (pixel depth) values correctly.
• Fixed the problem where the ACA does not properly parse HDCP short reads of Ri register.
• Fixed the problem where the ACA does not allow the user to perform a Save As.
• Fixed the problem where the ACA does not handle CEC parameter properly.
• Fixed the problem where the CEC Controller causes eventual hanging of 882 units without CEC ITE option.
• Fixed the problem where CEC Rx start error (10303) or Tx line error (10310) shows up when extreme 0 bit low period is set. The maximum low period configurable in the CEC Controller is changed to 1.68ms.

• 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.9.0 (20.1884400 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 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 (ACA monitoring device) to TPA-ACA-3R's OUT 1
  
  
• use the ACA on the 882C/882CA/882E 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 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 (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 (ACA monitoring device) to TPA-ACA-3R's OUT 1
  
  
• use the ACA on the 882C/882CA/882E 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.9.0 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, or 2.8.2. 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

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

1. Download the 2.9.0 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.
   Note: You can also upgrade by transferring files using the FTP Browser.
3. After power cycling the generator, verify that the generator is running the current 2.9.0 version of the vxWorks file by entering the following command:
   
   verf?
   20.1884400, 01.04.11



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



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,3152007.
8. Verify that the Rx gateware file (the third item listed) is: 253A,11,4202007.

You can obtain Release Notes for past releases as follows:

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