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.

CMD file

Other Parts Discussed in Thread: TMS320C6748, OMAPL138

1.How big can it be when i use a DDR memory to connect the c6748?

2.when i use the cmd to manager my code in the DDR, i find there is many "NOP" in the memory browser of the ccs, why this happen?

3.i think there is still many memory i can use ,but when i enlarge my arrary's index it seems that the code will go immidately when i download it to the ddr by a simulator. why this happen? Dose it means the leakage of memory? or overflow?

  • Long Gao,

    I strongly recommend you look through the training material for the C6000 Embedded Design Workshop. Go to TI.com and search for "c6748 training" (no quotes) and it will be one of the search items displayed. Or search for "C6000 Embedded Design Workshop" (no quotes). It will explain how to use the .cmd file and who to use memory in the device and board.

    long gao said:
    1.How big can it be when i use a DDR memory to connect the c6748?

    Please refer to the datasheet. Table 3-4 shows the C6748 Top Level Memory Map. Near the end of that table is the range of memory at which the DDR memory can be accessed. It shows 256MB addressable space. How big is the DDR physical memory on your board, or are you using a development board we might be aware of?

    long gao said:
    2.when i use the cmd to manager my code in the DDR, i find there is many "NOP" in the memory browser of the ccs, why this happen?

    There should not be any NOP display in the memory browser, since it only shows data-space interpretation of the displayed memory. Are you talking about the Disassembler Window? If that is the case, then the NOPs are showing what is found there. What should be there instead? You can refer to the .map file generated by the compiler/linker to see what locations in memory are allocated for the program and data space specifically.

    long gao said:
    3.i think there is still many memory i can use ,but when i enlarge my arrary's index it seems that the code will go immidately when i download it to the ddr by a simulator. why this happen? Dose it means the leakage of memory? or overflow?

    I do not understand what you are doing or describing. If you zip up your .cmd file and .map file and attach that .zip file, we might be able to understand more of what you are trying to do. Or you can paste a copy of those in the text of your next reply. Only include the first two parts of the .map file since the Symbols sections are very long and not needed for this discussion.

    Regards,
    RandyP

  • Hi long gao,

    Randy answered all the questions.

    3.i think there is still many memory i can use ,but when i enlarge my arrary's index it seems that the code will go immidately when i download it to the ddr by a simulator. why this happen? Dose it means the leakage of memory? or overflow?

    Do you have C6748 LCDK board or working with CCS + simulator without C6748 HW ?
  • Thank you for the reply

    1.i will go to learn it 

    2.yes the range on the mannual of the "TMS320C6748™ Fixed- and Floating-Point DSP (Rev. E)" is 0xc0000000~0xcffffff. But, when i give the DDR a range beyond thes, which i have tested it:0xc0000000~0xe0000000(512M). the address at the tail of this range can still work, this make me believe it can handle upto 

    512M memory, am i right? About this i will pend the cmd file, please check the accessory.  About the issue of 'NOP' thing,yes it's the disassembly window, i will cut a pic for you.

    cmd&the pic.rar

  • We use ourself HW, The ddr is 1GB
  • Long Gao,

    c6748.cmd said:
    DDR2         o = 0xC0001000  l = 0x17cb3400  /* 128MB  DDR2 ·ÖÅ䏸 DSP */

    The datasheet tells you what the device is designed and tested for. You are violating that specifications with your length field in the line above from c6748.cmd.

    long gao said:
    About the issue of 'NOP' thing,yes it's the disassembly window, i will cut a pic for you.

    The NOP is showing the instruction disassembled from the value 0x00000000 in the locations displayed in the Disassembler Window. Is there any reason to suspect these values are incorrect?

    Your .map file will show you what is allocated to a memory location.

    It is unusual for the value of 0 to be stored throughout memory unless it was manually cleared or loaded with 0's some other way. Normally, uninitialized memory would show random values.

    Regards,
    RandyP

  • Hi long gao,
    As per the OMAPL138/C6748 data sheet, you can interface 16bit DDR2 256MiB address space.
    Please do check the data sheet.
  • OK,i will abey to your advertisements。Yes,the mannual‘s is256’M, but i do accessed the 0xDxxxxxxx addrs, this confused me. thank you again

  • Yes, thank you. I had checked it carefully before.
  • Hi long gao ,
    Welcome.
    Glad to hear that you understood the DDR address space access.
    Please let us know for any issues/questions.
  • Hello, RandyP:

           Before i changed my array the "MEMORY CONFIGURATION" in my .map file is:"DDR:c0001000   cfffefff  06a29f51  c95d50ae  RWIX", this means i still have 147M ddr memory can use. but when i enlarge it & the left DDR is67M, which i think still reasonable, but when i download to the Hw it run immidately. My DDR

    is 1G, so i can't understand why this happens?

         the accessory is the .cmd,.gel&.map files after i enlarge the array, please help me.Desktop.rar