Hello all, Here are the versions of our environment:
DVSDK : DVEVM 1.10 dsplink_1_30_08_02 bios_5_30 codec_engine_1_02 cg6x_6_1_7 codec_servers_1_00 xdctools_1_21 xdais_5_00 framework_components_1_00_03 We still have one problem regarding the XDAIS and the C++ especially the dynamical memory where is situated the C++ object dynamical allocation!! Here is the .tcf var mem_ext = [ { comment: "DDRALGHEAP: off-chip memory for dynamic algmem allocation", name: "DDRALGHEAP", base: 0x88000000, // 128MB len: 0x07A00000, // 122MB space: "code/data" }, { comment: "DDR: off-chip memory for application code and data", name: "DDR", base: 0x8FA00000, // 250MB len: 0x00400000, // 4MB space: "code/data" }, { comment: "DSPLINK: off-chip memory reserved for DSPLINK code and data", name: "DSPLINKMEM", base: 0x8FE00000, // 254MB len: 0x00100000, // 1MB space: "code/data" }, { comment: "RESET_VECTOR: off-chip memory for the reset vector table", name: "RESET_VECTOR", base: 0x8FF00000, len: 0x00000080, space: "code/data" }, ]; In our code we implement a c++ objet with a New command (it need at least 64MB for the allocation) and what we are watching with CCS3.3 is that DSP try to allocate memory not on the DDRALGHEAP but on the DDR and then our code crash. How can we use the section DDRALGHEAP ? How does it worked on DAVINCI to automatically put the allocated objet in? Thanks in advance. Regards, Jerome. _______________________________________________ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source