Mbed-os: LPC1114 doesn't compile with normal blinky

[MarceloSalazar]

Description of defect

LPC1114 fails to compile blinky application with latest version of Mbed OS 6 (master)

• GCC Error
  BUILD/LPC1114/GCC_ARM/.link_script.ld:77 cannot move location counter backwards (from 0000000010001c38 to 0000000010000c00)
• ARM
  Error: L6406E: No space in execution regions with .ANY selector matching BUILD/LPC1114/ARM/mbed-os

It's not expected to build
The tools should inform that this isn't supported or is a bare-metal only target

Target(s) affected by this defect ?

LPC1114

Toolchain(s) (name and version) displaying this defect ?

Arm Compiler 6.13 and GCC 9

What version of Mbed-os are you using (tag or sha) ?

mbed-os-6.0.0

What version(s) of tools are you using. List all that apply (E.g. mbed-cli)

Mbed CLI 1.10.4

How is this defect reproduced ?

mbed import https://github.com/ARMmbed/mbed-os-example-blinky
cd mbed-os-example-blinky
mbed compile -t <toolchain> -m LPC1114

@ARMmbed/team-switchscience @toyowata

[ciarmcom]

@MarceloSalazar thank you for raising this issue.Please take a look at the following comments:

We cannot automatically identify a release based on the version of Mbed OS that you have provided.
Please provide either a single valid sha of the form #abcde12 or #3b8265d70af32261311a06e423ca33434d8d80de
or a single valid release tag of the form mbed-os-x.y.z .
E.g. '(727cf54873a9)' has not been matched as a valid tag or sha.
NOTE: If there are fields which are not applicable then please just add 'n/a' or 'None'.This indicates to us that at least all the fields have been considered.
Please update the issue header with the missing information, the issue will not be mirroredto our internal defect tracking system or investigated until this has been fully resolved.

[evedon]

This target does not have enough memory for the rtos profile.
The supported_application_profiles configuration is only used for documentation purposes currently. This will be addressed by the new tools.

[ciarmcom]

Thank you for raising this detailed GitHub issue. I am now notifying our internal issue triagers.
Internal Jira reference: https://jira.arm.com/browse/MBOTRIAGE-2714

[MarceloSalazar]

I've realized this is not a target issue as it's not expected to work due to limited memory.
However, the tools should display a message indicating that the target doesn't support the full profile.

[evedon]

I've realized this is not a target issue as it's not expected to work due to limited memory.
However, the tools should display a message indicating that the target doesn't support the full profile.

This functionality should come in the new tools.
In the meantime, we could add some information in blinky's README to indicate which targets are supported. Targets which don't list full in supported_application_profiles configuration are not supported.

[LDong-Arm]

PR created: https://github.com/ARMmbed/mbed-os-example-blinky/pull/238

[LDong-Arm]

@MarceloSalazar The README update has been merged but this issue isn't automatically closed - presumably because it's a different project. Are you happy to close it?

[MarceloSalazar]

That's fine. Thanks!