• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 32 subscribers
  • Views 435 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

PCI6410 doesn't Work. The

Xin Dong Chen
Prodigy 50 points
Other Parts Discussed in Thread: PCI1510, PCI1520

We use PCI6410 to support 16bit  CF card on board. It does't work and we are debugging the issue.

There are two questions based on our findings.

1. The WP signal from the CF card is measured zero by multimeter but bit 4 of ExCA Interface Status Register is read out 1 indicating the CF card is write protected.  My understanding is it should not be 1 in any way because it reflects the status of the WP signal of the CF card interface. So at what cases this abnormal can happen? The card is working at memory mode.

2. The Ready signal from CF card is held to low when powered up indicating it is busy. But when we hot insert the CF card when the board is powered, the Ready signal becomes high. Is there anything triggered the behavior of the CF card like that from PCI6412?

3. The software we developped is working on the PCI1510 to support the same CF card. I don't know if there is any difference between PCI1510 and PCI6410 in the function to support CF card, which causes the needs of software modification. 

BTW, the board is designed to always power the CF card without using the power switch interface.

Thanks.

  • 0
    Prodigy 50 points

    Today we verified PCI6410 worked when the CF card was hot inserted, but it didn't work when the CF card is powered from cold board. 

    When hot inserted, the WP and Ready signal are ok.

    Another question:

    Must the pin 17 of PCI6412 (signal PHY_TEST_MA) be pulled up by a 4.7Kohm resistor?  Is 4.75Kohm resistor OK?

  • 0 in reply to Xin Dong Chen
    Prodigy 50 points

    Correct a typo above. The device is PCI6412, not PCI6410.

    One more question,

    Is there any errata for the PCI6412?

  • 0 in reply to Xin Dong Chen
    TI__Guru* 76130 points

    Hello,

    The 4.7K pull up resistor is OK for pin PHY_TEST_MA.

    Your problem sounds like a power up timing issue. I will dig on this.

    Have you tried using the power switch interface?

    The power switch interface is required by specification.

    Does your design with PCI1520 uses the power switch interface?

     

    Regards.

  • 0 in reply to Elias Villegas M.
    Prodigy 50 points

    Thanks for the information. We have more investigation today and have some findings which may be useful for analysis.

    We have a tested design for PCI1510 and the PCI6412 is a new design we are debugging. We find when powered up, the Ready signal is measured high for PCI1510 when the CF card is not plugged, but it is measured low for  PCI6412 at the same case. We tried to place a 1k pull up to the Ready signal on PCI6412, but it was still low. It looks like the Ready signal on PCI6412 is stuck to low when powered up and behaves like an output instead of an input pin. Could you help to check if the behavior of the Ready signal is correct or if there is register to configure the Ready pin for PCI6412?

    We tested the CF card from two vendors, STEC and SANDISK. STEC failed at power up and passed after hot plug. If you don't power off after the hot plug, it can work continously. SANDISK passed for both cases.  But when measured the Ready signal when SANDISK was used, we found sometimes the high level of the signal became 2.5V instead of 3.3V. It is really strange.

    Another issue: Is pin 15 of PCI6412  NC or VDDPLL_15? We checked it varied from 1.5V to 1.7V if no capacitor is connected. But in datasheet at figure 2-2 Package Terminal Diagram is marked NC.

    We have not use the power switch interface for both PCI1510 and PCI6412. The CF card is always powered on because our design is for network infrastructure applications, not consumer product.