Feature Enhancements for 882EA Release 2.12.0 - vxWorks: 20.1885000

The following features are included in the Release 2.12.0.

• A new lipsync test image with flashing white box has been added. The image is called LipSyncB. Please refer to Chapter 2 in the user guide for more information.
• EDID-based offset is also incorporated into the firmware and can be utilized in conjunction with the LipSyncB image.
• A new analyzer functionality has been added to measure audio-to-video delay of a source. This is LipSync under Analyzer menu.
• EDID Editor now supports creating/modifying lipsync information in the vendor specific data block.

The following anomalies have been corrected in the Release 2.12.0.

• Emulate Mode sets color space and sync type based on the interface and format selected. Enabling this mode will make the generator behave in the same way as release 2.4, whereas disabling this mode will make the generator behave in the same way as release 2.5.4 and later. Detailed information can be found in Chapter 2 of the user guide.
• Starting timeout for 1A-04 and 3A-02 tests in HDCP Compliance Test are now back to 9 seconds instead of 2.
• Setting Source Max KSV to a high number doesn't hang the generator anymore.
• CEC end of message testing can now be correctly performed as described in Chapter 11 of the user guide.
• EDID Editor can now correctly calculate the checksum when you load an XML file that you have saved previously.
• EDID Editor can now generate EDID data report and EDID Compliance Test report even if you don't have previously generated files in the internal flash memory.
• You can now ImageShift custom images without having to load and use them at least once.
• MAC address information in the GenStats image/report now shows the correct address in use.
• Default bootline user and password are now set to "anonymous" and "user" respectively.
  

• 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. 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-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. We plan to support this in the future.
  
  
• Test Section 2C-04 cannot be tested because the application cannot control the positioning of the encryption enable signal in DVI.
  
  

• 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)
  
  
• the test reports will be saved in /card0/library/reports if there is a PCMCIA card inserted in the 882EA (/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 882EA (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 882EA'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 882882EA (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 882EA's Tx 1 port to the upstream port of the repeater



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



• make sure HdcpProd image is not selected on the 882882EA 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

Note: The release files can only be applied to the 882EA generator (not the 882CA/882C/881C, 882D, or 882E/881E generators).

The Release 2.12.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.10.0, 2.10.2, 2.10.5, or 2.11.0. To verify that your current generator is operating with one of these releases, enter the following command:

verf?

Release 2.10.0 should return the following information:

20.1884600, 01.04.11

Release 2.10.2 should return the following information:

20.1884602, 01.04.11

Release 2.10.5 should return the following information:

20.1884605, 01.04.11

Release 2.11.0 should return the following information:

20.1884800, 01.04.11

After verifying that the generator is operating with Release 2.10.0, 2.10.2, 2.10.5, or 2.11.0, upgrade your generator using the procedures below:

1. Download the 2.12.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.
   
3. After power cycling the generator, verify that the generator is running the current 2.12.0 version of the vxWorks file by entering the following command:
   
   verf?
   20.1885000, 01.04.11



4. Verify that the vxWorks file is: 20.1885000.
5. Verify that the BootRom version is: 01.04.11.
6. Verify that the generator is running the current 2.12.0 version of the gateware files by entering the following command:
   
   verg?
   405C,1029,8222007:450A,1,6202007:450B,2,9142007



7. The first listing is the Lattice FPGA gateware. The next two listings are the transmitter gateware files for the DVI and the HDMI output. The gatewares are separated by colons. Verify that the transmitter gateware files are: 450A,1,6202007:450B,2,9142007.

You can obtain Release Notes for past releases as follows:

882EA Release 2.11.0
882EA Release 2.10.5
882EA Release 2.10.2