Mike, LOOP is just a DSPLink sample application. It is self-contained and generates its own DSP executable that works alongwith the corresponding GPP-side LOOP application. Hence it needs to have its own configuration information.
When you write your own application, you can simply use the DSPLink sample applications as reference code and configuration. In fact, we usually don't expect anyone to directly include the full sample code in their application, but just pick up snippets of code from the sample app and modify as per your needs. All configuration will, for sure, have to be changed to meet the needs of your application. For example, the LOOP sample's needs are very minimal, and the configuration reflects that. You will need to discard the LOOP sample's configuration and use your own system config for your application's requirements. Regards, Mugdha ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Dragojevic Sent: Monday, May 19, 2008 11:22 AM To: [email protected] Subject: LOOP sample in DSPLINK Hi, Does anyone know why the LOOP sample contains its own POOL_Config object defined in loop_config.c? I'm trying to use this sample in my DSP application but I get the linker error that POOL_Config has been defined multiple times: in my_app_x64P.c and loop_config.c. The values this object is initialized to look the same for both if CHNL_ZCPY_LINK is defined. I'm using the DM6446 platform. Thanks, Mike This email has been processed by SmoothZap - www.smoothwall.net<http://www.smoothwall.net/>
_______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
