I downloaded version 03.04.03.01 of the 6457 CSL over the weekend. A co worker in Tuscon has version version 03.05.00.01. Wher can I obtain this newer version
Thank you,
Bob Coburn
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.
I downloaded version 03.04.03.01 of the 6457 CSL over the weekend. A co worker in Tuscon has version version 03.05.00.01. Wher can I obtain this newer version
Thank you,
Bob Coburn
Bob,
The link on the Wiki points to the link on TI.com, and that is 03.04.03.01.
I am not sure how to figure out what someone else has or where they got it from without talking with them. Please check with your contact in Tucson to find out what they have and what package it was part of.
Regards,
RandyP
No wonder I feel totally lost.
I have the release notes from a version that does not exist. I have trouble report numbers refering to the problems I am having in those release notes. I will follow up with details in the morning.
Bob Coburn
CSL 3.05.00 was part of the MCSDK 1.0.0.08
What can you tell me about IR# SDOCM00069515 "(Child) SRIO Initialization Sequence is incorrect" and
IR# SDOCM00058804 "(Child) SRIO Initialization Sequence is incorrect"
I have 2 TMDSEV6457LE boards that I am trying to get srio running on and I can only get one boards through Initiailazation. When running the same code on both boards using examples from DioLib, one board consistatly fails to initialize SPO_ERR_STAT.PORT_UNINITIALIZED =1. On the other board, the chip initiializes immediatly. I have multiple examples that behave this way, including a srio example from the CSL.
I need to understand what the expected behavior is. Should the chip initialize immediately. Does there need to be another srio device attached in order to achieve initialization?
This is the loop in question for the dioLib function RIO_Init
do {
/*BC added */
// CSL_srioHwControl (srioHandle, CSL_SRIO_CMD_SP_ERR_STAT_CLEAR, &response)
/* end add */
status = CSL_srioHwSetup (srioHandle->hCslObj, &srioHwSetup);
if (status != CSL_SOK) {
COM_doError(NULL,COM_ECODE_SRIOINIT,COM_EFATAL0,__LINE__,status);
}
RIO_waitForHw(100000);
/* Check Port Ok bit */
portNok = 0;
if ( srioHandle->portConfig == RIO_PORT_CONFIG_1X_4X_MODE) {
response.index = 0;
CSL_srioGetHwStatus (srioHandle->hCslObj, CSL_SRIO_QUERY_SP_ERR_STAT, &response);
portNok |= response.data;
}
else{
for (index=0; index<CSL_SRIO_MODULE_PORTS_MAX; index++) {
if (srioHandle->portEn[index]) {
response.index = index;
CSL_srioGetHwStatus (srioHandle->hCslObj, CSL_SRIO_QUERY_SP_ERR_STAT, &response); // on one board allways returns 1, oth the other never returns 1
portNok |= response.data;
}
}
}
if (srioTimeOut != 0) timeOut++;
}
while((portNok & 0x1)&&(timeOut<1000000));
if (portNok & 0x1) {
COM_doError(NULL,COM_ECODE_SRIOINIT,COM_EFATAL0,__LINE__,status);
}
Is the some sort of handshaking going on between srio devices at initialization?
My setup has lane 0 connected between the 2 eval boards, and I am placing them in 4x_1x mode and only enabling port 0.
Bob Coburn
Bob,
I cannot explain why there is a newer release of CSL for C6457 in the MCSDK 1.0.0.8 package. I have asked internally for any kind of explanation or future plan for this.
This does at least tell you where you can get the version 3.5 if you want to use it, by downloading and installing the MCSDK 1.0.0.8.
Since you have another thread going for the SRIO initialization problems at http://e2e.ti.com/support/dsp/tms320c6000_high_performance_dsps/f/112/p/199515/712152.aspx#712152 , we need to keep that discussion there. I believe Karthik asked a detailed question there that may sound redundant, but he needs to confirm the precise timing of when those bits were checked and that they were checked after enabling the Power and Clocks to the SRIO but before running any of the CSL initialization.
If you are satisfied with being able to get the CSL 3.5.x, please mark the answering post as Answered, then we can move to the other thread to continue the SRIO board problems. If you are not satisfied with the CSL question, we can continue that here.
Regards,
RandyP