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.

What does "Ipc_writeConfig"?

In syslinks MessageQ example, I saw this call:

 

Ipc_writeConfig (rProcId, APP_INFO_TAG, (Ptr) &aInfo, sizeof (App_Info));

 

 

It seems this is completely undocumented. At least google doesn't know it, sprugo6c doesn't know it and the (un)famous doxygen tells me this:

 

Writes the config entry to the config area.

Parameters:
remoteProcId remote processor's MultiProc id
tag tag to identify a config entry
cfg address where the entry will be copied
size size of config entry
Returns:
Status

 

Great. Now I know almost as much as before :s

I always thought, examples exist so that I can learn something. Ti manages to confuse me with them... Oh, there's no comment for this call in the example, BTW.

 

Could someone enlighten me, please?

  • The SysLink MessageQ sample application uses the Ipc_writeConfig and Ipc_readConfig APIs to pass information from the slave (RTOS) to the host (HLOS) that has been statically configured on the salve side regarding MessageQ (e.g. message name, message heap sizes, etc.).

    The APIs will write into SharedRegion0 (SR0) and will use the tag to uniquely identify the structure (cfg) and size written into SR0 which both side must agree on.

    Similar idea could have been used with a simple shared header file across processors with the elimination of static configuration altogether on slave side.

  • Thank you!

    Could you point me to some (any...) documentation where this is mentioned?

  • Unfortunately, there is not much more information other than the Ipc module doxygen output,  you previously referred to.

    I have filed a documentation issue to ensure this is corrected in future Ipc releases.