• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 99 subscribers
  • Views 782 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TMS320C6655: SRIO Communication problem

Hui Cao22
Expert 1230 points
Part Number: TMS320C6655


SRIO communication problem between DSP master station and FPGA:

 The communication mode is SWRITE streaming mode, and the SRIO bus is 2x mode

Problems occurred:

1）. When the length of data sent by DSP is 512, it will be sent in two packets, but there will be a transmission interval of about 1 us between them;

2）. The program will stay in the uiCompletionCode read state all the time, and the FPGA will jump out normally after the number of times, but the SWRITE mode does not respond.

  • 0
    TI__Mastermind 25535 points

    ,

    Is it your custom board or Ti's C6657 EVM board?

    By any chance,  have you tried the working examples of SRIO which is part of Processor SDK 6.3

    1. SRIO_Loopback_evmc6657_C66BiosTestProject

    2. SRIO_LpbkDioIsr_evmc6657_C66BiosExampleProject

    3. SRIO_MulticoreLpbk_evmc6657_C66BiosExampleProject

    4. SRIO_TputBenchmarking_evmc6657_C66TestProject

    In the SRIO throughput example, I could see the type " case Srio_Ftype_SWRITE:"

    Regards

    Shankari G

  • 0
    Expert 1230 points

    it‘s not EVM Board。

    I can't see if there is a gap between the data in the self-loop DSP. There is no problem with FPGA self-loop. Data can be received between the DSP and FPGA, but there is a gap between two consecutive data packets. The problem is what happens when the interval is moved, and how to locate the problem?

    In SRIO's SWERIE mode, a packet of data can only be sent 256 bytes. The length I gave is 1024 bytes. It needs to be sent in four packets continuously. Normally, the interval of each packet is delayed by several clks, but we have about 1 us

  • 0 in reply to Hui Cao22
    TI__Mastermind 25535 points

    Hui,

    Rajan is working and checking on the SWRITE streaming mode on C6657 EVM board.

    He will experiment on changing the length of the data packet from the default-length and get back to you.

    Regards

    Shankari G

  • 0 in reply to Shankari G
    Expert 1230 points

    many thanks

  • +1 in reply to Hui Cao22
    TI__Mastermind 25535 points

    Hui Cao,

    I am able to run the SRIO throughput example, where in the SWRITE type is supported.

    The following is the SRIO throughput bench mark testing for type-5 - WRITE Class.....

    I recommend you to run this example for type SWRITE - Type-6 and check the results.

    Please refer this FAQ on CCS group-core settings to run the SRIO examples. [FAQ] TMS320C6657: How to build and run the IPC-SRIO example on C6657 EVM? - Processors forum - Processors - TI E2E support forums

    [C66xx_0] ********************************
[C66xx_1] ********************************
[C66xx_0] *********** CONSUMER ***********
[C66xx_1] *********** PRODUCER ***********
[C66xx_0] ********************************
[C66xx_1] ********************************
[C66xx_0] WARNING: Please ensure that the CONSUMER is executing before running the PRODUCER!!
[C66xx_1] WARNING: Please ensure that the CONSUMER is executing before running the PRODUCER!!
[C66xx_0] Debug: Waiting for module reset...
[C66xx_1] Debug(Core 1): Waiting for SRIO to be initialized.
[C66xx_0] Debug: Waiting for module local reset...
Debug: Waiting for SRIO ports to be operational...  
Debug: SRIO port 0 is operational.
Debug:   Lanes status shows lanes formed as one 4x port
Debug: AppConfig Tx Queue: 0x2a0 Flow Id: 0
Debug: SRIO Driver Instance 0x@008215b0 has been created
Debug: Running test in polled mode.
Debug: SRIO Driver handle 0x8215b0.


[C66xx_1] Debug: AppConfig Tx Queue: 0x2a1 Flow Id: 1
Debug: SRIO Driver Instance 0x@00821470 has been created
Debug: Running test in polled mode.
Debug: SRIO Driver handle 0x821470.


Latency: (DIO_NW, 5.000GBaud, 4X, tab delimited)
Core	Lanes	Speed	Conn	MsgType	PktSize	NumPkts	MnLCycs	AgLCycs	MxLCycs
1	4	5.000	C-I-C	DIO_NW	4	100	719	737	807
1	4	5.000	C-I-C	DIO_NW	8	100	719	736	751
1	4	5.000	C-I-C	DIO_NW	16	100	736	737	755
1	4	5.000	C-I-C	DIO_NW	32	100	771	781	790
1	4	5.000	C-I-C	DIO_NW	64	100	864	864	878
1	4	5.000	C-I-C	DIO_NW	128	100	993	1006	1030
1	4	5.000	C-I-C	DIO_NW	256	100	1289	1289	1309
1	4	5.000	C-I-C	DIO_NW	512	100	1492	1493	1511
1	4	5.000	C-I-C	DIO_NW	1024	100	1863	1880	1882
1	4	5.000	C-I-C	DIO_NW	2048	100	2621	2629	2641
1	4	5.000	C-I-C	DIO_NW	4096	100	4138	4157	4158
1	4	5.000	C-I-C	DIO_NW	8192	100	7191	7191	7209

[C66xx_0] Throughput: (RX side, DIO_NW, 5.000GBaud, 4X, tab delimited)
Core	Lanes	Speed	Conn	MsgType	OHBytes	PktSize	Pacing	Thruput	PktsSec.	NumPkts 	PktLoss	AgPCycs	AgLCycs	AgICycs	AgOCycs	Seconds
0	4	5.000	C-I-C	DIO_NW	16	4	0	85.33	2666666.75	12600000	No	375	21	354	0	4.73
0	4	5.000	C-I-C	DIO_NW	16	8	0	170.67	2666666.75	12600000	No	375	21	354	0	4.73
0	4	5.000	C-I-C	DIO_NW	16	16	0	341.33	2666666.75	12600000	No	375	21	354	0	4.73
0	4	5.000	C-I-C	DIO_NW	16	32	0	682.67	2666666.75	12600000	No	375	21	354	0	4.73
0	4	5.000	C-I-C	DIO_NW	16	64	0	1365.33	2666666.75	12600000	No	375	21	354	0	4.73
0	4	5.000	C-I-C	DIO_NW	16	128	0	2730.67	2666666.75	12600000	No	375	21	354	0	4.73
0	4	5.000	C-I-C	DIO_NW	16	256	0	5461.33	2666666.75	12600000	No	375	21	354	0	4.73
0	4	5.000	C-I-C	DIO_NW	16	512	0	10265.66	2506265.75	12600000	No	399	21	378	0	5.03
0	4	5.000	C-I-C	DIO_NW	16	1024	0	10750.66	1312336.00	6400000	No	762	21	741	0	4.88

0	4	5.000	C-I-C	DIO_NW	16	2048	0	10687.54	652315.75	3400000	No	1533	21	1512	0	5.21
0	4	5.000	C-I-C	DIO_NW	16	4096	0	10764.78	328515.13	1800000	No	3044	21	3023	0	5.48
0	4	5.000	C-I-C	DIO_NW	16	8192	0	10773.63	164392.56	1000000	No	6083	21	6062	0	6.08

[C66xx_1] Throughput: (TX side, DIO_NW, 5.000GBaud, 4X, tab delimited)
Core	Lanes	Speed	Conn	MsgType	OHBytes	PktSize	Pacing	Thruput	PktsSec.	NumPkts 	PktLoss	AgPCycs	AgLCycs	AgICycs	AgOCycs	Seconds
1	4	5.000	C-I-C	DIO_NW	16	4	0	85.33	2666666.75	12600000	No	375	315	45	15	4.73
1	4	5.000	C-I-C	DIO_NW	16	8	0	170.67	2666666.75	12600000	No	375	315	45	15	4.73
1	4	5.000	C-I-C	DIO_NW	16	16	0	341.33	2666666.75	12600000	No	375	315	45	15	4.73
1	4	5.000	C-I-C	DIO_NW	16	32	0	682.67	2666666.75	12600000	No	375	315	45	15	4.73
1	4	5.000	C-I-C	DIO_NW	16	64	0	1365.33	2666666.75	12600000	No	375	315	45	15	4.73
1	4	5.000	C-I-C	DIO_NW	16	128	0	2730.67	2666666.75	12600000	No	375	315	45	15	4.73
1	4	5.000	C-I-C	DIO_NW	16	256	0	5461.33	2666666.75	12600000	No	375	315	45	15	4.73
1	4	5.000	C-I-C	DIO_NW	16	512	2	10265.66	2506265.75	12600000	No	399	315	69	15	5.03
1	4	5.000	C-I-C	DIO_NW	16	1024	354	10750.66	1312336.00	6400000	No	762	314	433	15	4.88
1	4	5.000	C-I-C	DIO_NW	16	2048	1123	10687.54	652315.75	3400000	No	1533	315	1203	15	5.21
1	4	5.000	C-I-C	DIO_NW	16	4096	2636	10761.25	328407.22	1800000	No	3045	315	2715	15	5.48
1	4	5.000	C-I-C	DIO_NW	16	8192	5674	10771.86	164365.55	1000000	No	6084	316	5753	15	6.08

Latency: (DIO_NR, 5.000GBaud, 4X, tab delimited)
Core	Lanes	Speed	Conn	MsgType	PktSize	NumPkts	MnLCycs	AgLCycs	MxLCycs
1	4	5.000	C-I-C	DIO_NR	4	100	1006	1039	1080
1	4	5.000	C-I-C	DIO_NR	8	100	1006	1039	1080
1	4	5.000	C-I-C	DIO_NR	16	100	1006	1039	1099
1	4	5.000	C-I-C	DIO_NR	32	100	1006	1066	1113
1	4	5.000	C-I-C	DIO_NR	64	100	1006	1145	1204
1	4	5.000	C-I-C	DIO_NR	128	100	1006	1309	1337
1	4	5.000	C-I-C	DIO_NR	256	100	1006	1606	1638
1	4	5.000	C-I-C	DIO_NR	512	100	1006	1776	1843
1	4	5.000	C-I-C	DIO_NR	1024	100	1006	2166	2206
1	4	5.000	C-I-C	DIO_NR	2048	100	1006	2933	2952
1	4	5.000	C-I-C	DIO_NR	4096	100	1006	4534	4574
1	4	5.000	C-I-C	DIO_NR	8192	100	1006	8052	8090

Throughput: (TX side, DIO_NR, 5.000GBaud, 4X, tab delimited)
Core	Lanes	Speed	Conn	MsgType	OHBytes	PktSize	Pacing	Thruput	PktsSec.	NumPkts	PktLoss	AgPCycs	AgLCycs	AgICycs	AgOCycs	Seconds
1	4	5.000	C-I-C	DIO_NR	28	4	0	40.46	1264222.50	6400000	No	791	332	444	15	5.06
1	4	5.000	C-I-C	DIO_NR	28	8	0	80.91	1264222.50	6400000	No	791	332	444	15	5.06
1	4	5.000	C-I-C	DIO_NR	28	16	0	162.64	1270648.00	6400000	No	787	328	444	15	5.04
1	4	5.000	C-I-C	DIO_NR	28	32	0	312.96	1222493.88	6000000	No	818	327	476	15	4.91
1	4	5.000	C-I-C	DIO_NR	28	64	0	570.79	1114827.25	5400000	No	897	327	555	15	4.84
1	4	5.000	C-I-C	DIO_NR	28	128	0	972.46	949667.63	4600000	No	1053	327	711	15	4.85
1	4	5.000	C-I-C	DIO_NR	28	256	0	1523.81	744047.63	3800000	No	1344	326	1003	15	5.11
1	4	5.000	C-I-C	DIO_NR	28	512	0	2673.63	652741.50	3400000	No	1532	327	1190	15	5.21
1	4	5.000	C-I-C	DIO_NR	28	1024	0	4275.57	521920.66	2600000	No	1916	330	1571	15	4.98
1	4	5.000	C-I-C	DIO_NR	28	2048	0	6129.44	374111.50	2000000	No	2673	329	2329	15	5.35
1	4	5.000	C-I-C	DIO_NR	28	4096	0	7627.56	232774.67	1200000	No	4296	329	3952	15	5.16
1	4	5.000	C-I-C	DIO_NR	28	8192	0	8384.85	127942.68	800000	No	7816	328	7473	15	6.25

Latency: (Type-11, 5.000GBaud, 4X, tab delimited)
Error: (TX_1620)Invalid message received over control socket
TX_1620 Error: Failed to receive CTRL_SUCCESS control message within timeout period.
Core	Lanes	Speed	Conn	MsgType	PktSize	NumPkts	MnLCycs	AgLCycs	MxLCycs
1	4	5.000	C-I-C	Type-11	16	100	1911	1953	2098

    Regards

    Shankari G