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.

MessageQ and hardware interrupts

Hi,

I use the Inter-Processor Communication 1.25 on C6678 with CCS5.2.1+SYSBIOS6.34

When I use the MessageQ for the multicore communication, is the hardware interrupts will used?

If yes, how can I know which vector be used?

If no, can you teach me how the message be send from a core to other core?

Thanks!

  • Have you seen the IPC User's Guide?   This should provide some good background on how IPC works.   For the 6678, IPC is done using shared memory between the cores.   One core updates the shared memory with message contents and then triggers an interrupt on the other core.  The receiving core, then looks in shared memory for the message.  This is a big simplification of the details.  The IPC docs should provide more info.

    Regards,
    -Karl-

  • Hi Karl

    Thanks for reply!

    I have seen the IPC User's Guide, and I know when the message be send by messageQ, The hardware interrupt do not be used. Is that  correct?

    And I understand the Notify module use the hardware interrupt.Is that  correct?

    But in the IPC User's Guide,I can not find How the vector id (4-15)can be set. If I don't know the vector id, I can not set the vector id for other hwi.

    Can you teach me where can I find the related information?

     

    Thanks!

     

  • Yi Yin,

    You see the IPC package and get the example code for messageQ as per below path,
    C:\ti\ipc_1_xx_xx_xx\packages\ti\sdo\ipc\examples\multicore\evm667x
    C:\ti\ipc_1_xx_xx_xx\packages\ti\sdo\ipc\examples\singlecore

    And some additional IPC examples at PDK,
    C:\ti\pdk_C6678_1_1_2_6\packages\ti\transport\ipc\examples

  • I have the same question in too. :)

    If you define a HWI where its interrupt number is already used by something else, the build should tell you.  (The same happens with timer interrupts, BTW.  The "Clock" module sets up its own timer HWI, which you don't find out about until you happen to tread on its tail.)  So if you're not getting build errors, you probably don't need to worry too much about it.

    The only time it matters is if you *really* need to set up interrupt pre-empting, when you have a problem.  Otherwise though it's not a big deal.

  • I suggest you use CCS / RTSC Object Viewer (ROV) to inspect the Hwi module. It will show you all the interrupts that are currently in use. Look in the Tools menu.

    ~Ramsey