-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inconsistent symbol generation with target.mbed_ram_start override #9716
Labels
Comments
@mprse Something you could review? |
Internal Jira reference: https://jira.arm.com/browse/MBOCUSTRIA-870 |
This was referenced Mar 8, 2019
I think the tools team should review this. |
@ARMmbed/mbed-os-tools |
@ccli8 Please can you retest? |
They don't fix the issue. Actually, #10008 is raised to fix the issue. |
Still a problem on the latest master. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Enviroonment
mbed-os-example-blinky
7cc5542 Merge pull request #161 from adbridge/master
mbed-os
f2abdcb Merge pull request #9639 from michalpasztamobica/esp8266_connect_timeout
Description
I would like to override memory spec of cmsis pack on NUMAKER_PFM_M2351 but meet inconsistent symbol generation behavior when overriding
target.mbed_ram_start
/target.mbed_ram_start
. To re-produce my test results, runmbed compile -m NUMAKER_PFM_M2351 -t ARMC6
under mbed-os-example-blinky directory.No override and then compile
Get:
BUILD/NUMAKER_PFM_M2351/ARMC6/.profile-c:
MBED_RAM_START
/MBED_RAM_SIZE
are generated from cmsis pack.Override and then compile
Override rom/ram spec:
mbed_app.json:
Get:
BUILD/NUMAKER_PFM_M2351/ARMC6/.profile-c:
APPLICATION_RAM_ADDR
/APPLICATION_RAM_SIZE
are generated fromtarget.mbed_ram_start
/target.mbed_ram_size
overrides, butMBED_RAM_START
/MBED_RAM_SIZE
are not generated.Override + change to
get_all_active_memories
In mbed-os/tools/config/init.py, if I comment out
if (self.has_ram_regions):
indef get_all_active_memories
:mbed-os\tools\config_init_.py:
Get:
BUILD/NUMAKER_PFM_M2351/ARMC6/.profile-c:
Both
APPLICATION_RAM_ADDR
/APPLICATION_RAM_SIZE
andMBED_RAM_START
/MBED_RAM_SIZE
are generated fromtarget.mbed_ram_start
/target.mbed_ram_size
overrides. ButMBED_RAM_START
/MBED_RAM_SIZE
are duplicated in BUILD/NUMAKER_PFM_M2351/ARMC6/.profile-ld:What I expect is that
MBED_RAM_START
/MBED_RAM_SIZE
are available in both .profile-c (for source files) and .profile-ld (for linker files) regardless of override.Issue request type
The text was updated successfully, but these errors were encountered: