• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 434 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.

TMS320C6474 SRIO with SRIO Switch(TSI578)

pubesh r
Prodigy 210 points
Other Parts Discussed in Thread: TMS320C6474

Hi All,

we are developing custom board using TMS320C6474 DSP,SRIO implementation with IDT TSI578 SRIO Switch.
We have used 6 TMS320C6474 dsp's on board and they are connected to one SRIO switch.

Assuming Dev id of DSP 1 as 0x01,DSp 2 as 0x02....dsp 6 as 0x06
and based on our schematic connections of the DSP's(all dsp's port0 SRIO only used) to the corresponding port of the SRIO switch
we have formed the LUT for the dsp inside the SRIO switch  as follows

Destid    SRIO Port#5621.8-bit-SRIO.zip
6    15
5    1
4    0
3    7
2    6
1    14

My goal is to use DSP3 which is connected to port 7 of SRIO switch as Source(tx)
and DSP1 which is connected to port 14 of SRIO switch as target(RX).

I have used the attached code and tested
But I could not able to receive any data on the target dsp.



Have anybody tried TMS320C6474 SRIO interfacing with TSI578 srio switch ?


Can anybody give me some suggestions ?

 

Thanks & Regards,

Pubesh

  • 0
    TI__Mastermind 23525 points

    Pubesh,

    Yes, the C6474 has been used with the TSI578 many times by our customers.  Assuming you have the LUT setup correctly, for the correct tt size, make sure you are getting port_ok asserted before trying to send anything.  Also, what does the LSU completion code indicate as the problem?  Just a very quick glance at your code, indicates that the LSU is being programmed to send the data out on port 1, not port 0. 

     

    #define SRIO_PORT_NUMBER     1 //1 //rp

     

    Make sure it is using port 0.

     

    Do the switch statistics indicate any packet was received? 

    If yes, use a packet type like Nwrite_r to give us more clues if the problem is on the TX or RX side.

     

    Regards,

    Travis