Build error

[matszi]

Hi, 

I'm getting an error when building the example program blinky that says: ".text is larger than specified size" and ".rodata is larger than specified size".

I'm using version 17.1.0 of the nRF5 SDK, and version 6.32 of SES for ARM (64 bit).

[inw]

Hi,

Please look at the file "flash_placement.xml" in your project folder.

you shoule see: 

    <ProgramSection alignment="4" load="Yes" name=".text" sizeof="0x4"/>

and

    <ProgramSection alignment="4" load="Yes" name=".rodata" sizeof="0x4" />

Just delete "sizeof="0x4" from both of them then it should fix your problem.

Or you just go back to older SDK version such as 16.0.0

Regards,

Noom.

[gcb]

Hello I faced the same problem as the op. So I have two questions:

1. Why SES 6.30 doesn't have this problem and SES 6.32 does.
2. In SES 6.32 works if we do what you suggested.. What are we doing and what does it affect the build system when we delete "sizeof="0x4" from the file.

Thanks

[inw]

Hi,

I just reply to  Steve.Klinkon. I think is similar question.

Regards,

[ChrisApple]

A minor clarification...

Look in flash_placement.xml in the ses subdirectory.

You should see:

 <ProgramSection alignment="4" load="Yes" name=".text" size="0x4" />

and

<ProgramSection alignment="4" load="Yes" name=".rodata" size="0x4" />

Remove: size="0x4" from both lines resulting in:

<ProgramSection alignment="4" load="Yes" name=".text" />

and

<ProgramSection alignment="4" load="Yes" name=".rodata" />

I have no idea why this works.

[inw]

Hi,

You remove size="0x4" and it work because.

.text is related to the code size and .rodata is related to the constant data size.

So, when you put size="0x4", that mean you limit your code size to 4 bytes and limit your constant data  to 4 bytes also., 

even a simple code like the blinky example. it take about 4Kbytes

So, If you need to set the size of this code, you have to set the size bigger than your code such as size="0x1000" (1024 * 4 = 4096 bytes, 4Kbytes). It will work. 

Regards,

[Dwight Fowler]

I imagine that it might have something to do with packing the data. Could it be that if you align everything on 4-byte boundaries, it uses too much padding? Just a thought.