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.

SW support for moving DSP control path from Ethernet to PCIe?



We have a deployed architecture in place, using TI Tomahawk 6-core DSPs (6486).  We use the TI/Telogy stack and Ethernet path for the control interface (so using the DIM stack on my CPU to handle DSP communications).

We are moving to multi-core Shannon DSPs (66xx) and considering switching to a PCIe blade for the DSPs.  The blades I have seen only allow a control path to the DSPs via PCIe.  They still have an Ethernet path to public network for RTP streams of course, but it looks like that cannot be used for a control interface from the motherboard's CPU.

I do not think the Telogy stack has support for PCIe, and I am not sure what other options are available to switch from Ethernet to PCIe control path.  I hope I do not have to pull out the DIM stack.  What options do I have?

Thanks,

Greg in MA

  • I should have mentioned that  the stack and DSP firmware code we use (TI/Telogy) is to implement VoIP services on the DSPs.  I suppose that anybody that has any advice would already know that :)

  • Greg,

    The Telogy framework is not a general product by TI and is not supported on the e2e. Please used your dedicated support channel for all queries pertaining to it. The software products that are publicly available are the BIOS_MCSDK, voice and fax libraries (based on Telogy software), and media codecs, which can be found through the product folder.

    Thank you and best regards,

    Dave

     

  • Thanks Dave.  I have opened  an issue with eInfochips re: Telogy but thought there might be other solutions tha tpeople have used for PCIe and VoIP for TI DSPs.

    -Greg