AM6548: IPC LLD not well integrated into TI-RTOS infrastructure

Hi Ruediger,

Please use the pdk tool chain for IPC LLD based application development.

User guide for the same is here:

https://software-dl.ti.com/processor-sdk-rtos/esd/AM65X/latest/exports/docs/pdk_am65xx_07_01_00_55/docs/userguide/am65xx/modules/ipc.html

Thanks & Regards,

Sunita.

Sunita,

our complete application development is based on Code Composer Studio, incl. build configuration management, compiler settings, including/excluding sources, packet contribution, debugging, automated build process and so on.
IPC LLD will be just a little component of our application.

We want for sure not change our complete way of application development just because of this component.
IPCv3 was also available as RTSC component, as well as all the drivers in the PDK. Why not IPC LLD?

The fact that we are forced to migrate from IPCv3 to IPC LLD is terrible enough for us, it just costs a lot of time and has only technical drawbacks (performance, memory).

For end user application development using Code Composer Studio (Eclipse) with all his features is sooo much easier than dealing with all those nested makefiles. There you have just a big source tree and do not even know which source files are going to be compiled and how.

So I appeal to you, that the TI team adds the RTSC support to this IPC driver.

Regards,
Ruediger

Hi Ruediger,

I'm checking internally with SDK team, will get back to you as soon as have the options.

Thanks & Regards,

Sunita.

Hi Ruediger,

Given that the communication is now switched to GPIO based and there is a separate thread for that, please let me know if we can close this thread.

Thanks & Regards,

Sunita.

Hi Sunita,

the GPIO issue is tracked in another thread, that is correct.
But this thread here is to request better integration of IPC LLD into TI-RTOS/RTSC.

I still request at least a minimal integration, so that it solves to link the IPC LLD library via

var IpcLLD = xdc.loadPackage('ti.drv.ipc); // does not work

Otherwise we are forced to mix linker library definition between TI-RTOS .cfg file and raw linker library options.
But: some libraries depend on each other!

When mixing the 2 approaches we get issues because we cannot freely choose the order of the libraries anymore.
Also the linker option --start_group --end_group does not help.
The only possibility we found is to specify some libaries twice, with both approaches: in TI-RTOS .cfg file and on the linker library options.

See attached screendump.
Here you can see that we need to specify OSAL and CSL libraries after IPC lib, even if they are also in the generated configPkg/linker.cmd

My opinion: If TI officially wants to substitute IPCv3 by IPC LLC, then TI should fully support IPC LLD, also for TI-RTOS usage.

Regards,
Ruediger

Unlocking the thread to allow discussions to continue.