LAUNCHXL-F28379D: Question about Hole in 2837xD_RAM_Ink_cp1.cmd

Biagio Pervenuto

Hi,

I have a question about the default file 2837xD_RAM_Ink_cp1.cmd used for the project examples.

In the file there are two holes of 0x800 words, between RAMLS0 and RAMD0 of page 0 (hole of 0x800), and between RAMLS5 and RAMD1 of page 1(hole of 0x800):

___________________________________________________

RAMLS0 : origin = 0x008000, length = 0x002800 (end 0xA800)

RAMD0 : origin = 0x00B000, length = 0x000800

_________________________________________________

RAMLS5 : origin = 0x00A800, length = 0x000800 (end 0xB000)

RAMD1 : origin = 0x00B800, length = 0x000800

__________________________________________________

Can I increase the memory areas RAMLS0/RAMLS5 by 0x800 and then use the two holes correctly? or are the two holes inaccessible memory areas?

Best Regards,

Biagio

over 6 years ago

0 Baskaran Chidambaram over 6 years ago

TI__Genius 17370 points

With the existing linker command file there is no holes as such. Basically RAMLS0 is followed by RAMLS5 and then RAMD0 and RAMD1.

If you wish you can remove RAMLS5 and increase the size of RAMLS0 to 0x3000.

Also you can combine RAMD0 and RAMD1 as they are contiguous memories.

0 Biagio Pervenuto over 6 years ago in reply to Baskaran Chidambaram

Prodigy 250 points

So page 0 and page 1 refer to the same memory area and not to two different memory areas?
Why in the file .cmd are divided into two different pages?

0 Baskaran Chidambaram over 6 years ago in reply to Biagio Pervenuto

TI__Genius 17370 points

they may be segregated to cater for different application needs.
Internally they are different hardware blocks, but nothing prevents you from using them as contiguous memory locations from SW perspective.

C2000™︎ microcontrollers

C2000 microcontrollers forum

LAUNCHXL-F28379D: Question about Hole in 2837xD_RAM_Ink_cp1.cmd