Yes, you are right. It was not the IPC_start() that was preventing the overwrite of the other cores' LoggerSM state. So, I'm not sure why this was working in the past on TI816x. Looking at some old map files, though, it looks like on the M3's, a different autoinit function is being used: _TI_auto_init instead of auto_init_elf.
It looks like there may be another work around you can try. According to the LoggerSM documentation, there is a function called LoggerSM_setSharedMemory() that you could call to initialize the shared memory used by LoggerSM. You would need to configure the LoggerSM.sharedMemorySize to 0 for this to work. Here is the API documentation:
/*!
* ======== setSharedMemory ========
* Specify the shared memory to be used by LoggerSM
*
* This runtime API can be called once to initialize the shared memory
* that the all LoggerSM instances use. This API can only be called
* if '{@link #sharedMemorySize}' is set to zero. If
* '{@link #sharedMemorySize}' is non-zero, the shared memory is
* statically defined and initialized instead. Since the memory
* is already defined, this API cannot change it.
*
* @param(sharedMemory) Base address of the shared memory to be used
* by LoggerSM.
* @param(sharedMemorySize) Size of the shared memory.
*
* @a(returns)
* This function returns TRUE if successful. It returns FALSE if not.
* The reasons for failure are either '{@link #sharedMemorySize}' is
* non-zero or the API has been called multiple times.
*/
@DirectCall
Bool setSharedMemory(Ptr sharedMemory, Bits32 sharedMemorySize);
Could you try calling this function from main()?
Thanks,
Janet
