Hi everybody!
I create a new project and use .tcf file of EVM6474. Andthen, I use SRIO config as following this link:
"C:\CCStudio_v3.3\boards\evmc6474_v1\csl_C6474\example\srio\srio_evm_dio_example"
Unfortunately, when debugging the program gets infinite loop at following segment of code
do { delay(10000); //check the response every 100 cpu clcok = 100 ns CSL_srioGetHwStatus (hSrio, CSL_SRIO_QUERY_SP_ERR_STAT, &response); }while(response.data & 0x1);
Please help me resolve this issue.
Thank you very much.
You aren't getting a port_ok signal, which is the very first step needed for initialization between link partners before sending any packets. What is your board setup? Are you doing loopback or board to board? I'd suggest you start with a more recent example for the C6474. Please download and try the MCSDK at:
http://software-dl.ti.com/sdoemb/sdoemb_public_sw/bios_mcsdk/01_00_00_08/index_FDS.html
you should be able import the project into CCSv5. The example is installed to:
pdk_c64x_1_00_00_06\packages\ti\csl\c6474\csl_c6474\example\srio
Regards,
Travis
If you need more help, please reply back. If this answers the question, please click Verify Answer , below.
Thank Travis for responsing!
Actually, I create a new project using both RTDX and SRIO to propagate data between two cores of a EVM6474. RTDX is used to load data from PC to a core of DSP through visual basic interface and return data from another core to PC. SRIO is used to connect two cores. However, SRIO gets infinite loop as presented above. If I don't use RTDX and following the srio example is to be ok. I don't know how to resolve this problem.
Please help me!
Trinh,
If the example is working for you, and you are only having issues in your new project, something is not being handled correctly in the SRIO initialization of your project. It should not have anything to do with RTDX. Can you check that the SRIO initialization is handled exactly the same. So if you have one EVM, the SRIO should be configured for SerDes loopback. Is this being maintained? There should be no reason to not get port_ok in this setup. Usually, when you don't get port_ok, it points to a physical connection error of some sort.