Forums

RC,

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.

/* Set SRIO as the transport */
MessageQ.SetupTransportProxy = xdc.useModule(Settings.getMessageQSetupDelegate());
var TransportSrioSetup = xdc.useModule('ti.transport.ipc.srio.transports.TransportSrioSetup');
MessageQ.SetupTransportProxy = TransportSrioSetup;

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.

If (TransportSrioSetup_isRegistered(remoteProcId))

{

    TransportSrioSetup_detach(remoteProcId);

    TransportQmss_create(remoteProcId, &transportQmssParams, &eb);

}

Justin

Hi Justin,

               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.

Thanks

RC Reddy

Hi tscheck,

                                   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?

Thanks

RC Reddy

RC,

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?

Regards,

Bhavin

RC,

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.

Regards,

Bhavin

Hi RC

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.

Regards 

Rahul