 |
Notice: For this release, the CA platform cannot
perform HDCP compliance test for source or repeater
The following features have been added in the Release 2.22.0.
- Added Regulate test pattern.
- Added 3D output menu.
- HDMI 1.4 CEC CT updates.
- About menu shows firmware version and model name
- Improved precision of chromaticity value in EDID Editor. EDID Editor version is now 1.2.
The following anomalies have been corrected in the Release
2.22.0.
- Fixed issue in which EDID Compliance Test did not show 3D 4K x 2K pass descriptions.
- Fixed various issues with HDMI 1.4 CEC Compliance Test.
- Fixed various issues with HDMI 1.3 CEC Compliance Test.
- Improvements to XML parser.
- Improved EDID Formats format list for better IT format coverage.
- Improved Auto-CDF function of HDMI EDID Compliance Test
- Improved boot sequence messages to show additional hardware information
HDCP Compliance Test notes (only applicable to 882CA with HDCP Compliance Test option)
Test coverage limitations of the HDCP Compliance Test
- 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.
Applicable to all tests
- 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)
Applicable to the sink tests
- you can monitor the transactions on Tx port 1 using the ACA
Applicable to the source tests
- 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
Applicable to the repeater AB tests
- 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
Applicable to the repeater C tests
- 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
Sink test procedure via the command line interface
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
Source test procedure via the command line interface
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
Repeater AB test procedure via the command line interface
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
Repeater C test procedure via the command line interface
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
882CA/882C/881C (not the 882D/881D, 882E/881E, 882EA, or 882E-DP/881E-DP
generators).
The Release 2.22.0 is comprised of the following software components.
| Software Component |
Version |
Change Status |
| Boot Rom |
01.04.11 |
no change |
| vxWorks |
20.1887000 |
new with 2.22.0 |
CPLD gateware (outdated) |
256C,39,2222006 |
882s prior to 5/06 |
CPLD gateware (without HDCP Compliance Test option) |
One of: 255C,41,5312006 256C,41,5312006 |
no change |
CPLD gateware (with HDCP Compliance Test option) |
One of: 257C,41,1222007 258C,41,1232007 |
no change |
| Transmitter gateware |
253F,85,7062009 |
no change |
| Receiver gateware |
253A,18,9222009 |
no change |
Java JRE required |
1.5.06 |
no change |
Note: 882CA/882C/881C units with CPLD gateware 253C,36,1272005 will not support monitoring of the DDC Tx ports with the Auxiliary Channel Analyzer. Contact Customer Support for information on how to upgrade these units.
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.4 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, 2.15.0, 2.16.3, 2.18.1, 2.19.0, 2.19.2, 2.20.0, or 2.21.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
Release 2.16.3 should return the following information:
20.1885803, 01.04.11
Release 2.18.1 should return the following information:
20.1886201, 01.04.11
Release 2.19.0 should return the following information:
20.1886400, 01.04.11
Release 2.19.2 should return the following information:
20.1886402, 01.04.11
Release 2.20.0 should return the following information:
20.1886600, 01.04.11
Release 2.21.0 should return the following information:
20.1886800, 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, 2.15.0, 2.16.3, 2.18.1, 2.19.0, 2.19.2, 2.20.0, or 2.21.0, upgrade your generator using
the procedures below:
- Download the 2.22.0 Zip file to your PC and unzip the
file. There will be a System and a Library directory.
- Upgrade the generator using "Upgrading without using PC Card" procedure at this link.
- After power cycling the generator, verify that the generator
is running the current 2.22.0 version of the vxWorks file
by entering the following command:
verf?
20.1887000, 01.04.11
- Verify that the vxWorks file is: 20.1887000.
- Verify that the BootRom version is: 01.04.11.
- Verify that the generator is running the current 2.22.0
version of the gateware files by entering the following
command:
verg?
256C,41,5312006:253F,85,7062009:253A,18,9222009
- 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,85,7062009.
- Verify that the Rx gateware file (the third item listed) is: 253A,18,9222009.
You can obtain Release Notes for past releases as follows:
88xC(A) Release 2.21.0
88xC(A) Release 2.20.0
88xC(A) Release 2.19.2
88xC(A) Release 2.19.0
88xC(A) Release 2.18.1
88xC(A) Release 2.16.3
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
|
 |