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.

66ak2h14与K7的SRIO链接

Other Parts Discussed in Thread: 66AK2H14

K7芯片和66AK2H14的DSPcore0通过x1链路连接,链路速率为设置为2.5Gbps。DSP端为noloopback模式,dspnum设置为1。FPGA端采用xilinx的SRIO gen2 1.6 ,通过NWRITE向DSP的core0 L2空间发送数据,但DSP端没有检测到数据输入。DSP端报文给出的链路状态如下:

Input port 0 next expected ackID value: 0x2
Output port 0 unacknowledged ackID: 0x0
Output port 0 next transmitted ackID value: 0x0
The output port 0 has encountered a failed condition. The failed port error threshold has been reached in the Port n Error Rate Threshold Register.
The output port 0 has encountered a degraded condition. The degraded port error threshold has been reached in the Port n Error Rate Threshold Register.
The output port 0 has encountered (and possibly recovered from) a transmission error. This bit is set when bit 16 is set.
The input port 0 has encountered (and possibly recovered from) a transmission error. This bit is set when bit 8 is set.
The input port 0 is in the input error-stopped state.
Port 0 OK condition. The input and output ports are initialized, and the port is exchanging error-free control symbols with the attached device.
The port 0 received a packet-not-accepted acknowledge control symbol.
The port 0 detected a delineation error. The port received an unaligned /SC/ or /PD/ or undefined code-group. The capture registers do not have valid information during this error detection.
The port 0 experienced a link timeout. The port did not receive an acknowledge or link-response control symbol within the specified time-out interval. The capture registers do not have valid information during this error detection.
Type of information logged: 2 (0 - packet, 1 - control symbol)
captured error bit in the Port Error Detect Register: 11
control symbol or Bytes 0 to 3 of the packet header that correspond to the error: 0x1c40ff00
Bytes 4 to 7 of the packet header that corresponds to the error: 0x0
Bytes 8 to 11 of the packet header that corresponds to the error: 0x0
Bytes 12 to 15 of the packet header that corresponds to the error: 0x0
15 8b/10b deconding error have occurred


SP[0]_ERR_STAT = 0x03020102
SP[0]_ERR_DET = 0x00100005
Corrected Error Stop Condition. SP[0]_ERR_STAT = 0x03020101
Clearing Errors.

FPGA端chipscope能够检查到port_initialized和link_initialized信号为高,但多采集几次偶尔能发现它们被拉低之后再置高。这是否表明物理层链路上存在问题?检查过板卡布局布线,还没发现有什么大的错误。请各位高手们不吝赐教!

  • 再次求教!希望高人能够提供思路。这些天我用过xilinx srio gen2 的1.6、1.2以及3.3版本的ip核,它们例化的GTX输入数据宽度都为32bit,经过8b/10b编码之后为40bit,而DSP这边的serdes貌似最多只能配置到20bit的宽度。这会导致SRIO链路出现上诉的错误么?之前调试过6678和V6的SRIO,用到的IP核是SRIO gen1 v5.6,它的GTX输入数据宽度为16bit,8b/10b编码之后为20bit,这两款芯片间的调试就没有出现过上诉报文体现的问题。

    FPGA和DSP分别在两块板卡上,但是中间没有switch,是通过samtec的插件连接起来的,基本相当于直连。两块同样的FPGA板卡间SRIO互联经过检查调试没有问题,由于板卡结构设计原因,DSP只做了内回环测试,也顺利通过。同时仔细检查该板卡的SRIO的PCB走线,没发现能够受到太大串扰的地方。接下来打算飞两根线测试一下外回环,如果飞线的外回环都能过……那我就不说什么了。

    分析过报文后我的感受是:

    1.链路上出现误码,而且误码率超高,可能是链路干扰,目前觉得最大可能是串行链路两端数据宽度都不一样。

    2.8b/10b编解码出现问题,反映出来还是高误码率,可能还是串行链路两端数据宽度不一样导致。

    不知道我的思路对不对?FPGA的ip核不好改,DSP端能否把位宽调整到40bit?跪求TI的高人们能够指点一二!

  • 帮顶下 不知道楼主的问题解决没有。