• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 522 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.

CCS/TMS320F28379D: Possible errors in the TMS320F28379D datasheet memory map

Marko Gulin
Intellectual 430 points
Part Number: TMS320F28379D


Tool/software: Code Composer Studio

Hi all,

I'm using a command files 2837xD_RAM_lnk_cpu1.cmd and F2837xD_Headers_nonBIOS_cpu1.cmd supplied by example projects for TMS320F28379D (please find attached).

However, some parts are different in the two linker files and in the TMS320F28379D datasheet, section 6.3 Memory.

Can someone please check these things in the datasheet.

One more question about PAGE in the MEMORY part of a linker file. Is it absolutely necessary to use pages, or we use pages only because it is a good programming practice to (visually) separate data and program memory? I know that some microcontrollers have physically separated program and data memory, and there we must use pages, but when that is not the case it is not necessary to use pages?

Here is a complete list of memory locations that I found different:

Cla1Regs:

: origin = 0x001400, length = 0x000080 /* TMS320F28379D datasheet */
: origin = 0x001400, length = 0x000040 /* F2837xD_Headers_nonBIOS_cpu1.cmd */

DmaClaSrcSelRegs:

: origin = 0x007980, length = 0x000010 /* TMS320F28379D datasheet */
: origin = 0x007980, length = 0x000040 /* F2837xD_Headers_nonBIOS_cpu1.cmd */

ClbXbarRegs:

                                       /* Does not exist in TMS320F28379D datasheet */
: origin = 0x007A40, length = 0x000040 /* F2837xD_Headers_nonBIOS_cpu1.cmd */

SpidRegs:

                                       /* Does not exist in TMS320F28379D datasheet */
: origin = 0x006130, length = 0x000010 /* F2837xD_Headers_nonBIOS_cpu1.cmd */

RomPrefetchRegs:

: origin = 0x05E608, length = 0x000004 /* TMS320F28379D datasheet */
: origin = 0x05E608, length = 0x000002 /* F2837xD_Headers_nonBIOS_cpu1.cmd */

DcsmZ2Regs:

: origin = 0x05F040, length = 0x000020 /* TMS320F28379D datasheet */
: origin = 0x05F040, length = 0x000030 /* F2837xD_Headers_nonBIOS_cpu1.cmd */

  • 0
    TI__Guru** 115971 points

    Hi Marko,

    Datasheet provides full range for the peripheral address space which contains the reserved space as well where as the cmd file only has the locations which are actually used. As long as the start address is same, it's ok.

    About, PAGE it is recommended to split the memory section for data and program but memory blocks on 28x devices are typically unified. That means they can be accessed both in program space and data space hence it is not mandatory.

    You can find more detail on this here.

    Regards,

    Vivek Singh