Slave core boot on C6678 using a SYS/BIOS application

Hi Anand,

You cannot use Notify event to boot slave cores. Like you mentioned, Notify APIs cannot be called until an Ipc_start()/Ipc_attach() has been called which requires the slave cores to be already running (booted up).

I will loop in the MCSDK team to help you with booting the slave cores from core 0.

Best,

Ashish

It turned out that I simply had to move the IPCGR write into main() because SYS/BIOS enables HWIs only after main is called.

This info is in spru403r in the description for HWI_enable.

I presume writing directly to the IPCGR registers is identical to using BIOS_APIs to write them.

Thanks.

Hi anand,

i am not sure that the using the IPCGR and IPC notify are one and the same. I asked the IPC folks to confirm that they indeed use IPC registers for the IPC notufy and I don't think I got a clear answer that they do. And RBL recognizes only IPC registers.

Thanks,
Arun. 

Arun,

Could you get a confirmation that there are no issues with completing the slave core boot this way with a sys/bios application? Also, could you point me to info on what is needed on the IPC when a slave core recovers from crash.

Thanks.

Hi Anand,

What transport you are using. If you are using the shared memory transport, then it uses the IPC. but SRIO and QM transport uses QPEND. So you cannot use them to wake the slave cores.

Thanks,

Arun.

Arun,

We are using the shared region transport over IPC. When the application starts, the cores synchronize using Ipc_start. Question is if a slave core crashes and the host has re-downloaded it (LL2 sections), what IPC API calls need to be used on the master core to (a) pull the slave core out of reset and (b) put it back into job allocation

Thanks

-Anand