home products information contact us tech support order resources 16-bit PC Card Test Tools 16-bit PC Card Dev Tools CardBus Test Tools CardBus Dev Tools USB CompactFlash SmartMedia PCI Software PCMCIA Developer's Guide Extenders Secure Digital
sycard logo banner
navbar
FAQs gif product list  

PCCtest 450/460

Technical Support Questions and Answers

Last Updated May 4, 2005

Topic Categories

General PCCtest 450/460 questions
PCT450.EXE - 16-bit test software questions
TESTCB.EXE - CardBus test software questions
ZVTEST.EXE - Zoomed Video test software questions

General PCCtest 450/460 Questions

  1. Does your software support the 02 Micro OZ-711E1 chip? Can you test the SmartCard portion of the chip?
  2. I'm using a Ricoh R5C551 or R5C552 FireWire + CardBus controller and I can't find this chip under your test options. Do you support these chips?
  3. I'm using a Ricoh 5C522 FireWire + Cardbus controller but I can't find this chip under your test options. Do you support this chip?
  4. I ordered a PCCtest 450 and received a PCCtest 460. Why?
  5. Are there any differences between the two units?
  6. Why was the PCCtest 450 discontinued?
  7. Will I require different software for the PCCtest 460?
  8. We used to use the PCCtest 460 that had individual CardBus and 16-bit headers. Do you sell this anymore?
  9. The PCT450, ZVTEST, TESTCB software fail slot x, but pass slot y. What's the problem?
  10. We are trying to test a cardBus slot in a docking station; how do we get the test software to recognize the controller in the docking station?
  11. Does Sycard Technology supply any unreleased test software for evaluation?
  12. The test times for TESTCB and PCT450 are too long. What can I do about it?
  13. The test time for the ZVTEST application is too long. What can I do?
  14. I'm using a Ricoh R5C811, R5C812, R5C821, R5C822, R5C841, R5C842, R5C851 or R5C852 CardBus controllers but I can't find this chip under your test options. Do you support this chip?
 Back to top

PCT450.EXE - 16-bit Test Software Questions

  1. We are seeing intermittent failures with the PCT450 software and they always occur during the power-up delay or basic operational test.
 Back to top

TESTCB.EXE - CardBus Test Software Questions

  1. I'm using the PCCtest 450/460 in an AGP based system and I'm having problems testing slot 0; slot 1 passes all tests. What's the problem?
  2. The TESTCB.EXE software fails the following basic test: Error! Error reading PCCtest Vendor/Device ID (5555AAAA)=4C421002 It fails on slot 0, but passes fine on slot 1. What's the problem?
  3. One of the TESTCB tests is failing intermittently. How do I go about debugging the problem?
  4. We are seeing random failure on the data pattern test and some of the control/status signals. Where do I start looking?
 Back to top

ZVTEST.EXE - Zoomed Video Test Software Questions

  1. I run the ZVTEST.EXE program and I get 320 error during the pattern test. What is the problem?
  2. he monitor (or LCD) is blank during the Zoomed Video pattern test. Is this a problem?
  3. Do you support the Neomagic NM2200 or NMG5?
  4. Does your Zoomed Video test support ATI video controllers?
  5. Does your Zoomed Video test support ESS Maestro 2E family of audio controllers?
  6. Do you support Silicon Motion (SMI) controllers?
 Back to top
  1. Does your software support the O2 Micro OZ-711E1 chip? Can you test the SmartCard portion of the chip?

    2. The OZ-711E1 chip is based on the OZ-6933 CardBus controller. Use the test options for the OZ-6933 to test the CardBus/PC Card interface. Our test hardware is not capable of testing the SmartCard portion of the chip.

     Back to top
  2. I'm using a Ricoh R5C551 or R5C552 FireWire + CardBus controller and I can't find this chip under your test options. Do you support these chips?

    3. Yes, both the R5C552 (two slot) and the R5C551 (one slot) controllers are supported. The R5C552 uses the same CardBus controller as the 5C476MII. The R5C551 uses the 5C475MII CardBus controller. Use -b46 switch for the 5C552 and -b45 for the 5C551.

     Back to top
  3. I'm using a Ricoh 5C522 FireWire + CardBus controller but I can't find this chip under your test options. Do you support this chip?

    4. Yes, both the 5C522 (two slot) and the 5C521 (one slot) controllers are supported. The 5C522 uses the same CardBus controller as the 5C478. The the 5C521 uses the 5C475 CardBus controller. Use -b45 switch for the 5C522 and -b46 for the 5C521.

     Back to top
  4. I ordered a PCCtest 450 and received a PCCtest 460. Why?

    5. The PCCtest 450 has been discontinued and is being replaced by the PCCtest 460.

     Back to top
  5. Are there any differences between the two units?

    6. The PCCtest 460 is fully compatible with the PCCtest 450 and will perform the same test functions and operate with the same software. The test coverage is identical.

     Back to top
  6. Why was the PCCtest 450 discontinued?

    7. A major component of the PCCtest 450 was being discontinued by the manufacturer. Since there was no second source for the component we decided to redesign the product.

     Back to top
  7. Will I require different software for the PCCtest 460?

    8. No, all versions of our PCCtest 450 software released in 2000 and after will support the PCCtest 450 and 460.

     Back to top
  8. We used to use the PCCtest 460 that had individual CardBus and 16-bit headers. Do you sell this anymore?

    9. Because of lack of demand we decided to discontinue the seperate CardBus and 16-bit headers. Our PCCtest 460-01 includes the PCCtest 457 switchable configuration header that performs the same function as the two headers.

     Back to top
  9. The PCT450, ZVTEST, TESTCB software fail slot x, but pass slot y. What’s the problem?

    10. All three test programs use different memory test windows for slot 0 and slot 1. Problems that only occur on one slot may be the result of upper memory conflicts. The upper memory requirements of the three PCCtest applications are as follows:

    Application
    Slot 0
    Slot 1
    PCT450.EXE + ZVTEST
    D000:0-D000:7FFF Memory 150H-15FH I/O
    D000:0-D000:7FFF Memory 150H-15FH I/O
    TESTCB.EXE (version 2.04)
    D800:0-DBFF:F D400:0-D7FFF:F 160H-16FH
    D000:0-D3FF:F DC00:0-DFFF:f 150H-15FH

    TESTCB.EXE in its default mode requires a full 64K segment in upper memory. Because of high upper memory usage in current computer products, we have added a –jsxxxx option to reduce the upper memory requirements to 16K bytes. For example, by using the –jsd000 switch the memory requirements have been reduced to the following:

    Application
    Slot 0
    Slot 1
    TESTCB.EXE (version 2.0) (with -jsd000 switch) D000:0-D0FF:F D200:0-D2FF:F 160H-16FH D100:0-D1FF:F D300:0-D3FF:F 150H-15FH

    In versions 2.05 of TESTCB.EXE and above, the default memory and I/O usage will be changed to the following:

    Application
    Slot 0
    Slot 1
    TESTCB.EXE (version 2.05+ D000:0-D0FF:F D200:0-D2FF:F 160H-16FH D100:0-D1FF:F D300:0-D3FF:F 150H-15FH

     Back to top
  10. We are trying to test a CardBus slot in a docking station. How do we get the test software to recognize the controller in the docking station?

    11. If the controller in the docking station is different than the one in the main computer, simply select it by entering the chip designation with the –bxx switch. If the controller is the same as the one in the main computer, use the –s2 option to select the second instance of the selected controller. If the docking station is located on a secondary bus it may be necessary to use a -k2 switch when running TESTCB.EXE. This switch forces the TESTCB program to place slot 0 on PCI Bus 2 and slot 1 on PCI bus 3.

     Back to top
  11. Does Sycard Technology supply any unreleased test software for evaluation?

    12. We do not currently have any beta releases.

     Back to top
  12. The test times for TESTCB and PCT450 are too long. What can I do about it?

    13. Our TESTCB and PCT450 applications have options to modify certain test and delay parameters on the command line. The following application notes describe these changes:

    TESTTIME.PDF - Application note describing ways to reduce test time with the TESTCB application.

    TIME16.PDF - Application note describing ways to reduce test time with the PCT450 application. The updated applications are available in Beta release elsewhere on this page.

     Back to top
  13. The test time for the ZVTEST application is too long. What can I do?

    14. This problem is a bit more difficult than our TESTCB and PCT450 software. Since most of the test time is in the VGA chip specific test code, it is difficult for Sycard to provide a speed up solution. However, Sycard can provide source code for many of the VGA specific modules. The user can then request assistance from the VGA chip vendor to reduce the ZV capture delays. In addition, some of the same delays that were in the PCT450 software are present in the ZVTEST software. The following application note describes how to reduce these delays: TIMEZV.PDF - Application note describing ways to reduce test time with the ZVTEST application.

     Back to top
  14. I'm using a Ricoh R5C811, R5C812, R5C821, R5C822, R5C841, R5C842, R5C851 or R5C852 CardBus controllers but I can't find this chip under your test options. Do you support this chip?

    15. Yes, all these controller contain a R5C476MKII controller macro. Use the -b46 option.

 Back to top

PCT450.EXE - 16-bit Test Software Questions

  1. We are seeing intermittent failures with the PCT450 software. The failures always occur during the power-up delay or basic operational test.

There are several possible areas that can cause this problem. We have seen the following:

  1. The PC Card-16 header is not plugged-in all the way or the header or mating connector on the PCCtest is damaged/worn.
  2. There is noise on the system’s Card Detect and/or Voltage sense pins. On card insertion, a state machine in the CardBus controller tries to determine what kind of card has been inserted.  If there is excessive noise on these lines the card will not be correctly identified. Try adding a -r switch to the command line (software versions 1.17 and later). This will force the CardBus controller to re-inquire the card type prior to running the test.
  3. The voltage switch that controls the power to the slot is not completely turning the power off or there is some leakage onto the slot power bus. When the PCCtest is plugged and slot power off, measure the voltage on the slot power pins.  The voltage should be around 0 volts. If not, then the PCCtest may not properly reset.
  4. In most CardBus host designs there are several pull-up resistors on the slot signal pins. These pull-up resistors can either pull up the signal to system Vcc or slot Vcc.  Card Detect (CD1- and CD2-) and Voltage Sense (VS1, VS2) should be pulled-up to System Vcc, while any other signal should be pulled-up to slot Vcc.  If resistors are not connected to the proper power source power-on problems may occur.
 Back to top

TESTCB.EXE - CardBus Test Software Questions

  1. I'm using the PCCtest 450/460 in an AGP based system and I'm having problems testing slot 0. Slot 1 passes all tests. What's the problem?

    2. There is probably a conflict on the second PCI bus with the PCCtest 450/460 and the AGP controller. See the following question for a solution:

     Back to top
  2. The TESTCB.EXE software fails the following basic test:
    3. Error!
    Error reading PCCtest Vendor/Device ID (5555AAAA) = 4C421002.

    It fails on slot 0, but passes fine on slot 1. What’s the problem?

    If the value of 4C421002 is the vendor and device ID of another PCI device in the system, then there is a conflict on the secondary bus.  The TESTCB software assigns slot 0 of CardBus controller to PCI Bus 1 and slot 1 to PCI Bus 2.  If there is another device on Bus 1 or 2, the test will fail.  The -kx option will force the TESTCB software to use another bus for Slot1/Slot2.  For example the -k2 switch will place slot 0 on Bus 2 and slot 1 on Bus 3.

    Note: Future versions (V2.05 and later) of the TESTCB software will configure slot 0 on Bus 2 and slot 1 on Bus 3 (-k2 option is default).

     Back to top
  3. One of the TESTCB tests is failing intermittently. How do I go about debugging the problem?

    4. The TESTCB software contains a special debug menu mode. This mode allows the user to run a single test for scope or logic analyzer debug. Another mode allows the user to place the test into a continuous loop. To enter this mode just add a "-m$" to the command line.

    For example, to debug a problem with the CSTSCHG signal on the TI PCI1130 enter the following:

    testcb –b60 –v –0 –m$
    1. Then power up and initialize slot by entering "3"
    2. Enter the slave debug sub-menu by entering "6" Run the CSTSCHG test by entering "7"   If no error is returned then the test passes. If this test passes, then I would like you to run a loop test on CSTSCHG.
    3. To enter the loop test sub-menu, enter "L" to enter special tests.
    4. Enter "6" to loop on the CSTSCHG test. This test will loop until a failure is detected.
     Back to top
  4. We are seeing random failure on the data pattern test and some of the control/status signals. Where do I start looking?

    5. The first place to check is the quality of the CardBus signals. This is most easily checked by putting one of the tests into a continuous loop (see previous question). Once placed in a loop the signals may be examined with an oscilloscope. Check the following:

    1. Does the CardBus clock on slot 1 meet specifications? Check overshoot, undershoot and duty cycle.
    2. Is the power supply within tolerances?
    3. Check the overshoot/undershoot on all signal pins. A negative undershoot of more than 0.5 volts on any I/O pin may cause problems on the PCCtest’s FPGA.
 Back to top

ZVTEST.EXE - Zoomed Video test software questions

  1. I run the ZVTEST.EXE program and I get 320 error during the pattern test, what is the problem?

    2. The pattern test is the main portion of the Zoomed Video test. The ZVTEST software tests the zoomed video interface by sending 320 different patterns across the ZV bus and verifies that it is written into video memory. If the pattern test fails with 320 errors, then the test is failing completely. The first thing to verify is that the ZVTEST.CMD file is configured for the correct video controller chip. Another item to check is to make sure any external Zoomed Video buffers are enabled.

     Back to top
  2. The monitor (or LCD) is blank during the Zoomed Video pattern test. Is this a problem?

    3. No, the Zoomed Video test only tests the data path between the PC Card slot and the video controller’s ZV bus and memory. Displaying the captured video is usually another function of the video chip and is not tested by the PCCtest software.

     Back to top
  3. Do you support the Neomagic NM2200 or NMG5?

    4. The NM2200 ZV port implementation is similar to the NM2160. However, the NM2200 contains two ZV ports. The current ZV_NEO.EXE support zoomed video operation on the first ZV port.  Contact Sycard Technology for a test module to support the second ZV port.

     Back to top
  4. Does your Zoomed Video test support ATI Video Controllers?

    5. ATI has created a zoomed video test module that works without ZVTEST program. ATI maintains and distributes this module. Contact your ATI applications engineer for more information.

     Back to top
  5. Does your Zoomed Video test support ESS Maestro 2E family of Audio Controllers?

    6. Contact Sycard Technical Support for the latest information on ESS M2E support at:
    In an effort to spam proof our website, we ask that you type this email address into your email program. Thanks.

     Back to top
  6. Do you support Silicon Motion (SMI) Controllers?

    7. We currently support Silicon Motion SM910, SM810, SM710 and SM811. The ZV_SMI.EXE file is locate in the ZVTEST.ZIP package located on the Support page.

Back to top  
    Home| Products | More Information| Contact Us | Support| Order | Links |

Updated January 24, 2005

Copyright© 1995-2008 Sycard Technology
In an effort to spamproof our website, we ask that you key in this email address into your email program. Thanks.