Need RAM and ROM size for compilation

[jeromecoutant]

Summary of changes

Previously ROM and RAM sizes comes as linker predefine during mbed build.

Confirmed by:
Looking at https://os.mbed.com/docs/mbed-os/v5.14/porting/porting-bootstrap.html
/* Tools provide -DMBED_ROM_START=xxx -DMBED_ROM_SIZE=xxx -DMBED_RAM_START=xxx -DMBED_RAM_SIZE=xxx */

1 commit is reverted in order to get the expected behavior.

Thx

Impact of changes

Migration actions required

Documentation

---

Pull request type

[x] Patch update (Bug fix / Target update / Docs update / Test update / Refactor)
[] Feature update (New feature / Functionality change / New API)
[] Major update (Breaking change E.g. Return code change / API behaviour change)

---

Test results

[] No Tests required for this change (E.g docs only update)
[x] Covered by existing mbed-os tests (Greentea or Unittest)
[] Tests / results supplied as part of this PR

---

Reviewers

---

[ciarmcom]

@jeromecoutant, thank you for your changes.
@ARMmbed/mbed-os-tools @ARMmbed/mbed-os-maintainers please review.

[0xc0170]

100755 → 100644

Please revert file attributes change

[jeromecoutant]

Please revert file attributes change

done

[0xc0170]

@jeromecoutant Trying to understand for this revert. Can you add a reason to the commit msg (what is actual behavior, that is causing a problem) and how it fixes it ?

[0xc0170]

Previously ROM and RAM sizes comes as linker predefine during mbed build.

Is this true? If bootloader is not supported, does a target have defined rom/ram sizes ? This could be one of the things I am not completely certain how this information is connected to bootloader (if it actually is).

[jeromecoutant]

@jeromecoutant Trying to understand for this revert. Can you add a reason to the commit msg (what is actual behavior, that is causing a problem) and how it fixes it ?

As indicated in the description:
https://os.mbed.com/docs/mbed-os/v5.14/porting/porting-bootstrap.html
/* Tools provide -DMBED_ROM_START=xxx -DMBED_ROM_SIZE=xxx -DMBED_RAM_START=xxx -DMBED_RAM_SIZE=xxx */

[jeromecoutant]

Is this true? If bootloader is not supported, does a target have defined rom/ram sizes ?

Region sizes doesn't come from bootloader info, they comes from pack manager tool.

[0xc0170]

Yes from the manager but they are used/defined only if bootloder is there? My assumption might be wrong, thus asking .

[0xc0170]

@ARMmbed/mbed-os-tools Please review

I'll run CI meanwhile

updateed

[mbed-ci]

Test run: FAILED

Summary: 1 of 11 test jobs failed
Build number : 1
Build artifacts

Failed test jobs:

• jenkins-ci/mbed-os-ci_cloud-client-pytest

[jeromecoutant]

Yes from the manager but they are used/defined only if bootloder is there? My assumption might be wrong, thus asking .

I would like to have some "generic" linker scripts. So having these region values helps.

[adbridge]

NOTE the ci last ran several days ago and thus this will need to be run again before it can be merged, to ensure no conflicts etc due to other merges in the interim!

[adbridge]

CI restarted

[mbed-ci]

Test run: SUCCESS

Summary: 11 of 11 test jobs passed
Build number : 2
Build artifacts

[mergify]

This PR does not contain release version label after merging.