• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 97 subscribers
  • Views 407 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

DSP-side memory map does not match configuration?

miscellanea
Prodigy 220 points

Hi, I have encountered a error when running decode demo.

Error: DSP-side memory map does not match configuration.

Compare DSP-side TCF/MAP file with /dsplink/config/all/CFG_<PLATFORM>.c

I use dvsdk_2_10_00_15 including dsplink_1_61_03 and codec_engine_2_23_01 which are compatible in the dsplink roadmap.

I use codecs in dm6446_dvsdk_combos_2_03 and demos which are all from dvsdk_2_00_00_18.

Now I have encode and encodedecode demo running on my davinci evm board.

But when I ran the decode demo, I encounter the problem above.

I check the tcf in servers/encode and servers/decode, they are no different.

I found this on wiki "Engine_open failure seems to indicate that DSPLink is being used inside Codec Engine.

In such cases, modifying the default configuration file within DSPLink as mentioned above will not make any difference.

This file gets overwritten by Codec Engine, which provides a dynamic configuration to DSPLink.

The actual changes to ensure correct memory map need to be made as mentioned at this page"

But the http://wiki.davincidsp.com/index.php?title=Changing_the_DVEVM_memory_map is so long that I don't know

which section will be help for me for the error above.

So I came here for help.

Thanks.


  • 0
    Prodigy 220 points

    I found the problem.

    The .sysmem in decodeCombo.x64P is allocated in 0x10008000 named ARM_RAM which makes dsplink not working.

    And I think this is a bug of cgtools or a compatible problem of cgtools and CE.

    When I use cg6x_6_1_5 the .sysmem is allocated in DDR2 and the combos works correctly.

    The problem occurs when I use TI_CGT_C6000_6.1.10.

    I have solved the problem by specify a section for sysmem in link.cmd.

    But I still have a question - how does cgtools allocate the .sysmem without a section spefication?