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.

Codec Engine migration from EZSDK 5.03 to 5.05



I have a Codec Engine based DSP application that was working fine in EZSDK 5.03.01.15. Now I am migrating the application to EZSDK 5.05.02.00 and am facing issues as below:

1) If I run the M3 executables first and then attempt to run the DSP executable, the latter just fails to load.

2) If I directly run the DSP executable (not running the M3 executables), it loads and runs but fails in syslink assert soon after launching server. Prints with CE_DEBUG=3 are as below:

[t=0x001b23e7] [tid=0x400bc330] ti.sdo.ce.Engine: [+1] Engine_initFromServer engine->server = 0x47b7a0

[t=0x001b2413] [tid=0x400bc330] ti.sdo.ce.Engine: [+X] Engine_initFromServer> Returning 0

[t=0x001b2438] [tid=0x400bc330] ti.sdo.ce.Engine: [+X] Engine_open> return(0x47bab8)

Assertion at Line no: 452 in /home/is100170/work/nc_gen2/ti_ezsdk_5_05_02_00/component-sources/syslink_2_20_02_20/packages/ti/syslink/utils/hlos/knl/Linux/../.. /../../../../ti/syslink/ipc/hlos/knl/Linux/SharedRegionDrv.c: (status >= 0) : failed

 

 Are there any known migration steps for CE from SDK 5.03 to 5.05, especially regarding memory placement? The CE version in the two SDKs is codec_engine_3_21_02_25 and codec_engine_3_22_01_06 respectively.

Thanks and regards