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.

TMS320C6657: PICE

Part Number: TMS320C6657
Other Parts Discussed in Thread: AM5728

Hi,TI

The system contains a RC+7 EP,connected by PCIE Swich.The master MCU is TI AM5728, EP0 is TI DSP C6657, and EP1-EP6 is the media chip of Hess.

Phenomenon of the problem:

The RC connects 7 EP through IDT bridge, and the RC dies after running for a period of time, with a low recurrence probability (more than 20 devices, randomly reappearing one each day).In case of an exception, the main control cannot be connected with the emulator, and the CPU is in the pipeline suspended state.According to the strong correlation between multi-party positioning and PCIE, reset the master pCIE module or reset the PCIE SWITCH, and the master control can be connected by the simulator.

The preliminary analysis:

1.Attempt to reset in the normal operation of the PCIE SWITCH, hang dead phenomenon is consistent with the phenomenon of baking machine, emersion record 100%, due to the reduction and PCIE SWITCH makes master sent PCIE TLP possible packet loss on the deal, so the suspected reason for the kao machine problems is due to the PCIE TLP package packet loss on the deal, consulting bridge piece, doubt is PCIE signal has a problem.

2.through to the PCIE SWITCH register contrast analysis, find that DSP along the PCIE downstream, surprise down the error, the error, may have just started, also may be running for a period of time did not appear, but this error is not a problem to 100% have master hung dead, we suspect is currently just met with surprise when communication down, lead to the RC hanging to death.

At present, we have tested the PCIE signal eye map between the bridge and 6657 by ourselves. The Sdk version we used is as follows:

The main problem: Please help to solve how to eliminate the surprise Down error.Whether in hardware or software

  • Hi 

    You attachments are not visible. Additionally since the problem seems to be a bit sporadic and is in a relatively complex setup up, we will need your help to further isolate the issue to hardware/software and which device on the bus is causing an issue etc. 

    There are no known issues, so not sure if you are running into some boundary condition in your system /hardware or software handling

    Regards

    Mukul 

  • Hi,Mukul

    We want to know now what causes the "surprise down error" to be reported,How to solve it

  • Dominic

    Can you please re-share your attachments you had in your original post? They are not visible 

  • Dominic

    I have not heard back from you, so will keep this thread closed, it can will re-open as and when you respond. 
    In general this looks like a system level issue and we have very little information to help.

    I did discuss this with the PCIe experts , and recommendation would be if you can share additional context on when you see the issue would be further useful to see if we can help you narrow this down. 

    Most of the times when this error is reported it is typically a result of signal integrity issues pushing the BER beyond recoverable range. It is also common in topologies where the EP can be powered off separately from RC. As well as hot (un) plugging of add-in cards, which we do not recommend doing. 

    Hope this helps. Regards

    Mukul