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.

PCI bus lock-up with continuous retry

Other Parts Discussed in Thread: TMS320C6412

We are experiencing an intermittent issue with the TMS320C6412 DSP used as a PCI target. Occasionally upon power-on, the DSP's PCI interface does not initialize properly and causes the host PC to lockup upon communication. Here is the scenario:

The PCI bus gets into "permanent retry" mode which locks up the PC (no TRDY#). According to the documentation, the DSP's PCI interface causes a retry if its internal PCI FIFO buffer is full. Internal DSP memory transfers are supposed to continue until the FIFO is empty. Unfortunately, it appears that the FIFO is not being emptied upon getting into a bad state due to some power-on sequence.   

We found two ways to improve this problem:

1) holding the power-on hard reset low for 4 seconds after the power supplies have stabilized makes the problem much less frequent.
2) Writing the "Warm Reset" bit in the HDCR register after power-on fixes the problem (without the 4 second wait).

Some questions:

1) Is there any way to detect a bad PCI state from either the DSP or the PCI side?
2) Is there any way to issue a warm reset from the DSP side? The memory-mapped HDCR register is host-write only.
3) Is there any way to soft reset the PCI interface separately from an entire warm reset?
4) Any other thoughts on root cause correction?

Thanks,

Chris
  • Chris,

    It has been much too long without a reply to your post. Have you found a solution to your problem?

    My hope is that you have solved this, and we would like to know your solution if that is the case.

    If not, the best recommendations are to review the errata for the device to see if there are any known issues that might lead to similar behavior, then to double-check the power sequencing and reset and clock sequencing of the board to make sure it all matches the datasheet requirements.

    Regards,
    RandyP

  • RandyP,

    We only have the work-around that I describe above. We have not been able to identify and fix root cause.

    There are a few other posts with similar symptoms and they do not appear to have solutions either.

    And, yes we have thoroughly checked data sheets, errata, etc. and believe that we are meeting all requirements.

    Thank you for responding,

    Chris