DSPLINK Problems about integrating new server on DM6467

Hi, all

I try to test our H264 encoder on DVSDK 2.00. First, I test the video_copy example under the codec engine 2_23_01, the memory copy example works well. And I then I begin to call our parameter initliazation function in function alg_initObj() and set the dynamic parameters in the alg_control()  function, and the process is only memcpy as the example. But this time, the appliction doesn't work, with the following error:

"Error: DSP-side memory map does not match configuration.
Compare DSP-side TCF/MAP file with /dsplink/config/all/CFG_<PLATFORM>.c"

. I googled the error information, found it the dsplink related error. So I checked the memory map of the tcf file of the server and *.cfg files for the apps. As the the declaration of createFromServer, I think there's no unmatch between the memory of the ARM and DSP side. And I try to modify the function calls in alg_initObj() and alg_control(), and if the calls are inliined in alg_initObj() and alg_control() without function calls, after rebuilding, there's no DSPLINK error as above. The function is the same except extra functions calls in alg_initObj() and alg_control(), but the run of the app generates so much difference. I used the 'CE_DEBUG=2' or 3 to trace the debug info, if using function calls in alg_initObj() and alg_control(), there would be an error info such as

 "Loading and starting DSP server '*x64P' FAILED,status=[0x8000
8013] (look for error code 'DSP_EBASE + 0x13' in dsplink*/packages/dsplink/gpp/inc/usr/errbase.h) This error code typically indicate
s a problem with the DSP memory map, i.e. it is different from what the Arm side specified; check the DSP server's memory map in you
r Arm application .cfg script, and make sure you have set 'armDspLinkConfig' configuration variable correctly (for details, refer to
 the documentation for ti.sdo.ce.Engine.xdc). Also, verify that the DSPLINKMEM segment on the DSP is large enough."

So this is also the DSP memory map unmatch between ARM and DSP. I checked the generated *.map file of the server package, and find if ther's function call in alg_initObj() and alg_control(), the ARM_RAM will be used. And the memory statistics is similar like this:

"         name            origin    length      used     unused   attr    fill
----------------------  --------  ---------  --------  --------  ----  --------
  ARM_RAM               10010000   00008000  00001898  00006768  RWIX
  IRAM                  11818000   00010000  00010000  00000000  RWIX"

I searched the ARM_RAM in the map file, and found only map like this "ffffffff   ARM_RAM".

So I'd like to know why the ARM_RAM is used if there's function call in alg_initObj() and alg_control(). How to solve this problem? Now I can inline the function call in alg_initObj() and alg_control(), but I couldn't avoid funciton calls in the alg_process. Any advice is appreciated. Thanks all.