Compiler/TMS320F28377D: Linker file (.cmd) memory page regarding

Subash Sundaresan

Part Number: TMS320F28377D

Tool/software: TI C/C++ Compiler

In the compiler linker file memory page has to be mentioned as Page: 0 for executable and Page : 1 for data, nevertheless all the memory has been mentioned as Page: 0. Is there any consequences due to this declaration. if not the what is significance of using Page: 0 or Page: 1 in the memory declaration.

over 6 years ago

0 MEGHANA MANAVAZHI over 6 years ago

TI__Genius 10345 points

hi ,

Are you referring to the files in ccsv\ccs_base\c2000\include\2837x_RAM_lnk_cpu1.cmd ?

Where do you see all the memory has been mentioned as Page: 0?

Regards.

0 Subash Sundaresan over 6 years ago in reply to MEGHANA MANAVAZHI

Intellectual 650 points

we are using our own project specific linker file, there it has been mentioned that Page: 0 for all the memories ( Data and executable), could you clarify is there any impact? also please explain me the significance of Page: 0 and Page: 1

0 Subash Sundaresan over 6 years ago in reply to Subash Sundaresan

Intellectual 650 points

Do you have any updates on this query?

0 MEGHANA MANAVAZHI over 6 years ago in reply to Subash Sundaresan

TI__Genius 10345 points

hi ,

By convention PAGE 0 is ideally used for Program and PAGE 1 is used for DATA .

This is needed by the compiler and CCS backend to understand which page the contents are being mapped to.

Also to view registers on the memory browser we use the PAGE information today.

Expectation is that peripherals are on PAGE 1 when using F2837xD_Headers_nonBIOS.cmd files.

Regards.

0 Subash Sundaresan over 6 years ago in reply to MEGHANA MANAVAZHI

Intellectual 650 points

Hi Meghana,

Thank you so much for your response. I'm just wondering if I set Page: 0 for Data what will happen, is there any impact (especially in TMS320F28377D) ?

0 MEGHANA MANAVAZHI over 6 years ago in reply to Subash Sundaresan

TI__Genius 10345 points

hi ,

Yes to view registers in CCS we map peripherals to the PAGE 1 today in the module / peripheral xmls.

This would not be accessible .

Also device registers/ structures used in the code would not be visible on the memory browser due to conflict with the device/ peripheral xmls.

Any issues with setting this to PAGE 1 ?

I believe Page: 0 is expected to be non- volatile vs PAGE 1 which is volatile.

Regards.

C2000™︎ microcontrollers

C2000 microcontrollers forum

Compiler/TMS320F28377D: Linker file (.cmd) memory page regarding