TI E2E Community
MessageQ over SRIO [chip to chip communication] and QMSS [Core to Core communication]
If i want to use MessageQ over SRIO and QMSS, how to configure the .CFG file
If i look at a SRIO [Producer Consumer SRIO Project] example [CHIP to CHIP communication], it says
/* Set SRIO as the transport */MessageQ.SetupTransportProxy = xdc.useModule(Settings.getMessageQSetupDelegate());var TransportSrioSetup = xdc.useModule('ti.transport.ipc.srio.transports.TransportSrioSetup');MessageQ.SetupTransportProxy = TransportSrioSetup;
If i look at IPC_QMSS_benchmark example [core to core communication], it says
/* use IPC over QMSS */MessageQ.SetupTransportProxy = xdc.useModule(Settings.getMessageQSetupDelegate());var TransportQmssSetup = xdc.useModule('ti.transport.ipc.qmss.transports.TransportQmssSetup');MessageQ.SetupTransportProxy = TransportQmssSetup;
so how to make sure that MessageQ uses SRIO as Transport for CHIP to CHIP and QMSS for Core to Core communication in this .cfg file. please help me in setting/writing the .cfg file.
Right now MessageQ does not provide the ability to specify different transport proxies, via MessagQ.SetupTransportProxy, in the application .cfg file. You'll need to specify the SRIO IPC transport as the proxy in the .cfg file.
Then in the application itself you'll have unregister the SRIO transport for all core to core situations. After unregistering the SRIO transport for all core to core situations you'll need to register the QMSS transport. Please note you can register a new transport with the same priority as the one set in the .cfg file after you've unregistered the original transport.
Example code for unregistering the original SRIO transport then registering the QMSS transport in its place.
TransportQmss_create(remoteProcId, &transportQmssParams, &eb);
____________________Don't forget to verify answers to your forum questions by using the green "Verify Answer" button.
Thanks for quick answer. I will venture into coding for that part in coming days. I will post back any questions and verify the answer [what you suggested] then.
I also want to point out that if you don't need MessageQ (IPC), you can still use SRIO messaging between DSP using the LLD. There is an example showing how to do this in the MCSDK. After you install: http://software-dl.ti.com/sdoemb/sdoemb_public_sw/bios_mcsdk/latest/index_FDS.html
find the example in the following directory assuming you are using C6678:
If you need more help, please reply back. If this answers the question,
please click Verify Answer , below.
My required functionality is only thing
between master core [CORE0] in chip c6670 and another master core in ANOTHER chip c6670 communication.
1. establish chip level communication using IPC over SRIO.
2. establish core level communication using IPC over qmss [qpend] or IPC over shared memory.
please let me know what steps i need to follows, i followed steps suggested by justin, i was able to detach all core communicaiton on SRIO and was able to achieve core communication using qmss [i was able to see qmss transport instance in ROV tool], but when i do put MessageQ, other side message is not received.
before that, at any given point of transportqmss can exists between one core to one core only [this is the basic requirement in code]...say CORE0 if attached to CORE1 on qmss transport, cannot transport_attach itself to another CORE2 again. how to over come this?
For the QMSS transport, when you do the MessageQ put it follows below flow. If you don't get any message on the receiving core then the first thing which you should check whether the receiving core received the interrupt or not.
If you are not getting the ISR then it might happen that descriptor is not getting pushed to the respective queue. I am preparing a GEL function which can help you find the number of descriptors in a perticular queue. I will send you that by tomorrow.
Also I could not conclude about your SRIO tranport query. Are you facing the same problem for your SRIO transport query between two devices?
Please find attached is the GEL file which i was mentioning. 3348.Shannon_SystemDebug_v0.3.gel
Please use the first function C6678 CPPI Queue Status. It will give you options for start queue to end queue. There are lots of other debugging functions in that GEL file. You can use those as per your use case.
We are able to reproduce issue similar to yours. Justin should be able to provide you more details on it.
Are you running the code on Simulator or any hardware Board.,
I was able to use Qpend Comm on Hardware but it didn't work on Simulator (was not getting ISR invoked on receiver core) if u do successive message push.
Inserting delay between push solved that problem on Simulator too.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.