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.

512M DDR configuration for DM816x VS2 Demo

Hi All,

I am working on DM816X EVM. By default VS2 demo is running with 1GB DDR and I am able to compile it and run it.

I want to run my demo with 512MB DDR. So I had done some changes in omx_05_00_00_11.

My changes are as below to migrate to 512MBDDR.

1) omx_05_00_00_11/packages/ti/omx/build/config.bld

 set   var platFormMem = "512M";

2) omx_05_00_00_11/packages/makerules/build_config.mk

  set PLATFORM_MEM = 512M

And try to compile omx_05_00_00_11 package and getting compilation error at linking time.

Below is errors which are coming.

"/home/sweta/install/release/vs2/obj/ti816x-evm/m3vpss/debug/vs2_configuro/linker_mod.cmd", line 696: error:
   run placement fails for object ".bss:extMemNonCache:display", size 0xbaf2c
   (page 0).  Available ranges:
   OCMC_RAM1    size: 0x40000      unused: 0x3b910      max hole: 0x3b910
"/home/sweta/install/release/vs2/obj/ti816x-evm/m3vpss/debug/vs2_configuro/linker_mod.cmd", line 712: error:
   run placement fails for object ".bss:extMemNonCache:m2m", size 0x62a7c (page
   0).  Available ranges:
   OCMC_RAM0    size: 0x40000      unused: 0x236c0      max hole: 0x236c0
"/home/sweta/install/release/vs2/obj/ti816x-evm/m3vpss/debug/vs2_configuro/linker_mod.cmd", line 708: error:
   run placement fails for object ".systemHeap", size 0x1000007 (page 0).
   Available ranges:
   PRIVATE_CORE1_DATA   size: 0x6000000    unused: 0x3f1b04     max hole:
   0x3f1a00
error: errors encountered during linking;
   "/home/sweta/install/release/vs2/bin/ti816x-evm/vs2_m3vpss_debug.xem3" not
   built
make[1]: *** [/home/sweta/install/release/vs2/bin/ti816x-evm/vs2_m3vpss_debug.xem3] Error 1
make[1]: Leaving directory `/home/hitesh/ezsdk_5_11/omx_05_00_00_11/packages/ti/omx/demos/vs2'
make: *** [vs2dm3] Error 2


So what can be the issue over here. Is there any configuration missing?

Please reply me. If you need more details than let me know.


Thanks,

Hitesh Patel

 

  • Hello Hitesh,

    You might want to look at a forum post I ran into while researching a problem our team's been

    having trying to light up the video subsystem's CortexM3s on an alpha board using only 512MB

    or RAM instead of a full 1 GB.

    http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/717/t/119202.aspx

     

    The reply to that post indicates that a 512MB RAM setup will run into problems under the current

    [ti-ezsdk_dm816x-evm_5_01_01_80] when trying to talk to the Ducatis/CortexM3(s).

     

    I haven't had a reply from TI yet to my post requesting confirmation of this.

    We're trying ourselves to work on a procmgrapp loading issue for the M3 that we think is being caused

    by using only a 512MB memory map.

    [See http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/717/t/123276.aspx  for that description].

     

    Hope this helps or gives you some ideas for investigation.

    Please update the E2E community if you find out anything specific about this.

    Good Luck.

     

    - Juan