section .text make region `FLASH' overflowed (around 14ko)

RE: section .text make region `FLASH' overflowed (around 14ko)

Håkon Alseth — Tue, 03 Mar 2020 14:39:12 GMT

By verifying one of the answers, it'll be tagged with status "verified answer" - ie. closed. Pick one that looks the most informative ;)

Cheers,

Håkon

RE: section .text make region `FLASH' overflowed (around 14ko)

Ben34 — Tue, 03 Mar 2020 14:37:15 GMT

NRF_LOG_ENABLE is already 0, thank you for your advice, now I know I have to work on my code itself and not on gcc compilation options :)

Best regards

P.S : how do I set the topic to "solved" or something?

RE: section .text make region `FLASH' overflowed (around 14ko)

Håkon Alseth — Tue, 03 Mar 2020 14:05:32 GMT

[quote user="Ben34"]-Os is very efficient, but it still overflow 2704 bytes. Is there no way to have Keil's compilation performance in Eclipse? Or at least increase a little bit Eclipse's one?[/quote]

Different compilers, different behavior and compiled code, unfortunately. Try disabling logging (sdk_config.::NRF_LOG_ENABLED 0) and other modules that you do not need in the application, and see if you can shrink the code size.

Kind regards,

Håkon

RE: section .text make region `FLASH' overflowed (around 14ko)

Ben34 — Tue, 03 Mar 2020 13:38:51 GMT

Hi, thank you for support :)

-Os is very efficient, but it still overflow 2704 bytes. Is there no way to have Keil's compilation performance in Eclipse? Or at least increase a little bit Eclipse's one?

Thank you again

RE: section .text make region `FLASH' overflowed (around 14ko)

Håkon Alseth — Tue, 03 Mar 2020 11:55:27 GMT

Hi,

[quote user=""]Either I put LDFLAG += --library_type=standardlibrary or LDFLAG += --library_type=microlib, it doesn't change anything. How do I make gcc use microlib library like Keil seems to do ?[/quote]

That is specific to Keil, and gcc will just ignore that. GCC uses newlib nano, as provided with --specs=nano.specs

There are normally two things that shaves off bytes:

1. garbage collection in the linker (ie: drop unused functions and code)

2. Changing the optimization level

You already have GC set in the LDFLAGS: LDFLAGS += -Wl,--gc-sections

What you can do is try to change your optimization to optimize for size (your current is O2):

OPT = -Os -g3

Kind regards,

Håkon