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: TMS320C6657

Part Number: TMS320C6657


C6657 chip and EVM with SRIO external loop back.

Using the EVM with SRIO external loopback and running code based on Loopback DirectIO interrupt based (ISR) example


Inside  SrioDevice_init    

after setting up the SrioDevice we the port error status:


Uint32          errStatus;

    // Get the Port 1 Error Status
    CSL_SRIO_GetPortError(hSrio, 0, &errStatus);
    printf("Port 0 Err: %d\n",errStatus);


frequently we get errStatus = 4 instead of 0. But there are cases when we get errStatus = 0 .

Tried working with 1250 and 2500 data rate (ref clock 250MHz), both working in lane setup four 1x ports.

 

What is the meaning of errStatus = 4?

Thanks

  • Hello Technical support,

    Can you please answer the open question regarding the SRIO err#4 message?

    Thanks,

    Moshe

  • Moshe

    Sorry for the delay , unfortunately we have recently lost our key expert on SRIO and I am not yet able to find anyone else to provide further guidance on this. 

    Will see what I can find to provide you debug pointers. 

    If you search the forums for srio loopback you will see some other related posts , but none that gave me a clue to help give you some guidance, but since you are closer to the debug please see if any of them help. 

    Regards

    Mukul 

  • Hello Moshe

    Was there any progress from your side on this?

    Can you confirm what TI software you are using for your experimentation?

    SRIO support is limited - so I will see what help I can find for you on this. 

    Please see if the following E2E Posts gives you any pointers

    Including the pdf doc in the later threads. 

    Regards

    Mukul

  • Please note that this thread may get locked as it is an older thread (even though it was not addressed). In that case, please open a new E2E Thread and use this one as the "related" post , if you run into issues posting any follow up on this E2E thread.