The size of that struct is implicitly built into the "ti.sdo.ce.examples.extensions.scale" package. Specifically, scale_stubs.c (the ARM-side code responsible for marshalling the args into a msg for the DSP-side) needs to be rebuilt if that struct changes.
I think you need to rebuild the extensions/scale directory - then the DSP Server - then the ARM-side application so the new stubs/skels know about the new size of that struct. One better - if you're using a new release of Codec Engine, I'd recommend the IUNIVERSAL interface for algs that don't match one of the existing interfaces, rather than the 'scale' approach: http://tiexpressdsp.com/index.php?title=Getting_started_with_IUNIVERSAL Chris ________________________________ From: davinci-linux-open-source-boun...@linux.davincidsp.com [mailto:davinci-linux-open-source-boun...@linux.davincidsp.com] On Behalf Of José María Cubero Muñoz Sent: Tuesday, May 26, 2009 12:48 PM To: davinci-linux-open-source@linux.davincidsp.com Subject: Add input arguments to codec_engine scale example Hi all. I would like to add an input parameter to the ISCALE_InArgs structure in codec_engine's scale example. I just added a: XDAS_Int32 newArg to the structure: typedef struct ISCALE_InArgs { XDAS_Int32 inBufSize; XDAS_Int32 outBufSize; XDAS_Int32 inBufValidBytes; XDAS_Int32 newArg ; } ISCALE_InArgs; in the iscale.h file. But it only works when I do not put it in the last place of the member list in the structure. Does it only works with 3 args? I think I'm missing something simple... Some place to define the number of arguments to be passed or the maximum size of the memory used in the message to the DSP, maybe? Thanks in advance. Best regards. José
_______________________________________________ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
