Changing FLASH address causes compilation failure.

Nirav Patel2

Prodigy 130 points

Other Parts Discussed in Thread: EK-TM4C123GXL, TM4C123GH6PM, SYSBIOS

CCS version 5.4

EK-TM4C123GXL eval kit.

Using TI RTOS I have created a project. And tried to modified FLASH address in tm4c123gh6pm.cmd file as below.

#define APP_BASE 0x00000800
#define RAM_BASE 0x20000000

MEMORY
{
FLASH (RX) : origin = APP_BASE, length = 0x00040000
SRAM (RWX) : origin = 0x20000000, length = 0x00008000
}

But compilation give following error.

-l"./configPkg/linker.cmd" "./main.obj" -l"libc.a" "../tm4c123gh6pm.cmd"
<Linking>

"./configPkg/linker.cmd", line 132: warning #10096-D: specified address lies outside memory map
error #10264: DEFAULT memory range overlaps existing memory range FLASH
error #10264: DEFAULT memory range overlaps existing memory range SRAM
error #10010: errors encountered during linking; "my_rtos2.out" not built

linker.cmd file, line 132 is .resetVecs: load > 0x0

Problem is only when change the FLASH address otherwise its fine.

How can I change FLASH address of the application that I am compiling. I have flashed Serial Bootload at address 0x00000000. That jump to the 0x00000800 location and runs the application. Reason for this is to upgrade application firmware.

Please Suggest....

over 12 years ago

0 Sasha Slijepcevic over 12 years ago

TI__Mastermind 37985 points

Nirav,
when you changed the origin for FLASH, the address 0x0 fell out of the defined memory map. If you want to place .resetVecs to an address other than 0x0, this is what you can do in your CFG script:

Program.sectMap[".resetVecs"] = new Program.SectionSpec();

Program.sectMap[".resetVecs"].loadAddress = 0x800; // or any other address

0 ScottG over 12 years ago in reply to Sasha Slijepcevic

TI__Mastermind 26780 points

Also, if you are bumping the definition of the start of FLASH, you'll also need to reduce the lenth (to 0x3F800), because there is no flash from 0x40000 to 0x40800.

0 hiowatha over 11 years ago in reply to Sasha Slijepcevic

Intellectual 480 points

Sasha,

I tried this suggestion for my project and still I see the .resetVecs section at address 0x0000.0000. Is there more magic to this? I am on a TM4C1294XL eval board, using CCS v6.0, with TI RTOS 2.0.1.23 (sysbios 6.40.01.15). I am trying to move the reset vectors out of bootloader flash range but still see the reset vectors there:

map file

MEMORY CONFIGURATION

         name            origin    length      used     unused   attr    fill
----------------------  --------  ---------  --------  --------  ----  --------
  FLASH_VEC             00040000   00000400  00000000  00000400  R  X
  FLASH                 00040400   000bfc00  00017830  000a83d0  R  X
  SRAM                  20000000   00040000  000152ac  0002ad54  RW X


SEGMENT ALLOCATION MAP

run origin  load origin   length   init length attrs members
----------  ----------- ---------- ----------- ----- -------
00000000    00000000    0000003c   0000003c    r--
  00000000    00000000    0000003c   0000003c    r-- .resetVecs
00040400    00040400    00017838   00017838    r-x

any thoughts? Thanks!

0 Sasha Slijepcevic over 11 years ago in reply to hiowatha

TI__Mastermind 37985 points

Check this thread: http://e2e.ti.com/support/embedded/tirtos/f/355/t/340261.aspx

0 hiowatha over 11 years ago in reply to Sasha Slijepcevic

Intellectual 480 points

Thank you Sasha!

I am curios though, does this mean that

Program.sectMap[".resetVecs"] = new Program.SectionSpec();
Program.sectMap[".resetVecs"] = 0x00040000;

will NOT work anymore? Is that obsolete now?

I ran into the

ti_sysbios_family_arm_m3_Hwi.resetVectorAddress = 0x00040000;

option yesterday, so I am glad I am on the right track. Thanks again!

0 Sasha Slijepcevic over 11 years ago in reply to hiowatha

TI__Mastermind 37985 points

The old way will not work for Cortex-M. I suspect it won't work for other architectures either, but I haven't checked that.

Processors

Processors forum

Changing FLASH address causes compilation failure.