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.

Want to run on the external DDR memory using XDS510 Emulator

Other Parts Discussed in Thread: TMS320C6455

Want to measure, the TMS320C6455 CPU Cycle using CCS5.3.

 XDS510 USB Emulator used to raise the output file (.out) on the DSP Device.

stack, heap size of the output file(.out) is larger than the  C6455 internal memory, Want to run on the external DDR memory.

All areas, including .stack, .data, .sysmem of the linker command file (.cmd) have been set to the external DDR memory.

The resulting, execute file(.out) has been running on DDR automatic.

if use the Emulator, Without the initialization code for external DDR memory Using only the information of the linker command file (.cmd)

Execute file(.out) to load and run on the external DDR memory automatically?

 

CPU cycle is wrong information and results are expected.

stack, heap size of Properties set to less,

Compile, link without error behavior.

 At Runing, CCS's break on stack overflow function can know stack size.

 but can not find the function.

How to check stack size at runing?

  • Jeong Sang Gi,

    Before any program or data may be loaded into the external DDR memory, the DDR memory interface must be initialized. When using CCSv5.3 and the XDS510 USB emulator, this initialization is usually done by executing a GEL file that will automatically initialize the DDR interface when the Target Connect command is issued.

    Jeong Sang Gi said:

    At Runing, CCS's break on stack overflow function can know stack size.

    but can not find the function.

    I am not familiar with this. What is the "CCS break on stack overflow" feature? Is this related to SYS/BIOS or a feature of the emulator?

    Jeong Sang Gi said:
    How to check stack size at runing?

    The stack size is set in the linker command file and that amount of space is allocated for the .stack section. What specifically do you want to know about the stack, total size or remaining space?

    You may want to check the CCS Help Search facility for functions related to the stack.

    Regards,
    RandyP

  • Thank you very much.
    DSP code that attempts to measure the amount of CPU computation time image processing algorithms.
    FFT(fast fourier transform) perform 16 times, about the size of the image 128X128.
    Perform results in about 2 seconds (2,000,000,000 cycle) cpu computation time came.
    CCS clock function have been used.

    Results are hard to believe.
    CCS clock function accuracy to what extent ambiguities?

  • Please explain what you mean by "CCS clock function". It is not clear what you are using, and it may not be the right function to use.

    Please search this forum for "tscl tsch" (no quotes) to find discussions and examples for making accurate performance measurements. Please reply back with a link to the thread that you found most helpful for doing your performance measurements.

    Regards,
    RandyP

  • I'm sorry.

    i'll Explain about CCS clock function.
    Enable the clock item from the Debug menu in CCS v5.3
    CPU cycle count during the run, so I have been confirmed.
    The resulting value is greater than the expected. I wonder how accurate the clock item of the debug menu to check the cpu cycle.
    and i'll check it tscl tsch forum.

    Thank you.

  • Jeong Sang Gi: said:
    How to check stack size at runing?

    Please check whether the below threads have any relevant answers for your question.

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/211186.aspx

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/158893.aspx

     

    Regards,

    Shankari.

    --------------------------------------------------------------------------------------------------------
    Please click the Verify Answer button on this post if it answers your question.

    --------------------------------------------------------------------------------------------------------