I am facing a problem with NDK application when i am trying to add the IPC module for MessageQ creation to write the received data and pass it onto other cores.
I have modified the .cfg file and other changes so that i can run an NDK appl. with CCS Simulator. Then i tested the helloWorld_evmc6678l NDK example application in CCS Simulator and it was working absolutely fine.
Also, i have created two application using the IPC module so that one creates the MessageQ and reads messages from it and other application to write the data into the MessageQ. These two applications are also working absolutely fine and i have verified the received data.
Now, the problem comes when i try to integrate IPC MessageQ appl and helloWorld_evmc6678l NDK application. The intention here is, the data received by the NDK application is then written to a MessageQ and which in turn is then read by the application running on the other core. But it does not communicate, even after trying almost every possible thing. Frankly, now i have run out of ideas.
So my question is, Is there something about IPC and NDK modules that i have missed out? If not, then can somebody please help me figure out what is missing/going wrong here.I will be really grateful.
There maybe some internal resource conflict when you merge IPC-msgQ application with NDK.
Which IPC transport does your application use ?
In the integrated application, is NDK receiving messages ?
Kindly click the Verify Answer button on this post, if it answers your question.
Hello Varada. thanks for the reply
Varada Bellary In the integrated application, is NDK receiving messages?
Yes, the integrated application is receiving the UDP packets successfully and correctly.
Varada Bellary Which IPC transport does your application use ?
In the integrated application in using the QMSS transport module under IPC.
Varada BellaryThere maybe some internal resource conflict when you merge IPC-msgQ application with NDK.
Yes Varada, that was my first conclusion too. After a little bit of reading, i found that QMSS and MessageQ are conflicting when being used in the same application. Also, the other MessageQ application (which will read the data from the msgQ and runs on another core) uses MessageQ, not QMSS. So this mismatch is probably leading to the issue of non-communication. Correct me if i am wrong.
Yes. For core to core IPC, the underlying transport on both sides should be the same.
About resource conflict issue, since NDK also uses QMSS to communicate, there is very likelihood of some conflict. Or there could be incorrect/duplicate initialization on queue manager done by both applications.
I would recommend a slightly different approach. That is – using shared memory based IPC transport of messageQ
sample test code :
“ .. \pdk_C6678_xx_xx_x_x\packages\ti\transport\ipc\examples\shmIpcBenchmark"
Hope this helps.
I want add something I have observed about the recommended approach.
I also try to NDK example and IPC by using Shared Memory message passing. Core0 is the master running NDK application, and also communicates with the other cores over different queues at a rate of 50Hz. After sometime it gives an "A_invalidQueueId" exception. When I set the number of slave cores to 2, this error is not occurred.
If its not too much trouble, can u please post the .cfg file you are using in this post. It will help me tremendously.
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.