Hi,
While integrating AER with the codec engine in EZSDK I encountered the follwoing problem with building.
======== all [.] ========
configuring bin/ti_platforms_evmTI816X/all_DSP.pe674 from package/cfg/bin/ti_platforms_evmTI816X/all_DSP_pe674.cfg ...
platformName = 'ti.platforms.evmTI816X:DSP'
js:
"./all_syslink.cfg", line 238: XDC runtime error:
ti.sdo.ce.Server/algs/1: incompatible assignment to mod
:xdc.services.intern.xsr.Value$Obj@79ed7f::ti.mas.aer.Version
I obtained the ti/mas/ folder from TI. Then I 'mkdir mas' in codec_engine_3_21_00_19/ti directory. Add the ti/mas folder to /usr/local/ezsdk/component-sources/codec_engine_3_21_00_19/examples/ti/.
Then I modify /usr/local/ezsdk/component-sources/codec_engine_3_21_00_19/examples/ti/sdo/ce/examples/servers/all_codecs/all_syslink.cfg.
var Version=xdc.useModule('ti.mas.aer.Version');
and
{name: "aer", mod: Version, threadAttrs: {
stackMemId: 0, priority: Server.MINPRI + 1}
},
I am attaching the screen shot of the directory structure.
The aer directory includes:
The aer/package.xdc content:
requires ti.mas.types[5,0,7,0];
requires ti.mas.fract[2,0,7,0];
requires ti.mas.util[4,0,8,0];
requires ti.mas.vpe[2,0,6,0];
requires internal ti.mas.swtools[2,0,4,0];
package ti.mas.aer[4.2, 0, 2, 0] {
module Version;
}
I compare AER with other codes package. I found that AER package is very diffrent from other codec packages.
(1)Other codec packages locate in ti.sdo.ce.example.codecs;but AER must locate in ti.mas as "package ti.mas.aer[4.2, 0, 2, 0]" in package.xdc.
(2)I can't understand the types,fract,util,vpe,swtools folders in mas directory.
(3)Other codecs blong to one of VISA,but I don't know whether AER blong to VISA.
(4)Other codecs module name is similar to package name,but AER module is “Version”.
(5)The module.xdc of other codecs is diffrent from Version.xdc of AER. For example G711ENC.xdc:
* ======== G711ENC ========
* G711 Encoder specification
*
* This file specifies information necessary to integrate with the Codec
* Engine.
*
* By inheriting ti.sdo.ce.speech.ISPHENC, G711ENC declares that it "is a"
* speech encoder algorithm. This allows the codec engine to automatically
* supply simple stubs and skeletons for transparent execution of DSP
* codecs by the GPP.
*
* In addition to declaring the type of the G711 algorithm, we declare
* the external symbol required by xDAIS that identifies the algorithms
* implementation functions.
*/
metaonly module G711ENC inherits ti.sdo.ce.speech1.ISPHENC1
{
/*!
* ======== ialgFxns ========
* name of this algorithm's xDAIS alg fxn table
*/
override readonly config String ialgFxns = "G711ENC_SUN_IG711ENC";
}
I doubt that AER can't use same integrating way with other codecs.
Can AER use by codec engine? If yes, then how should AER integrate with codec engine? If not, then how should AER integrate with EZSDK?
The CPU is CA8168.
Golden