Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Realtek Ameba not linking #4462
Note: This is just a template, so feel free to use/remove the unnecessary things
It should link the Cloud Client w/o update (to remove FlashIAP).
Steps to reproduce
Compile and link mbed Cloud Client example (available only to Cloud Client Partners, sorry).
as it was now merged to master, it was easier for me to compile it (last week was too busy), but it still unfortunately fails.
mbed-os master was now pointing to: f31ea01
So it had the fix in it. But, unfortunately
Now it's over by just 2,6 kilobytes anymore though. Close, but no cigar.
How are we using the memory in mbed OS? The hardware itself is extremely capable;
Quote from website says:
It's got more RAM than almost any board we've yet encountered in mbed OS domain - where is it now going?
Hi @Archcady ,
I think there is room to increase the limit even more since there is quite lot of unused user space left on the device.
Can you describe the problem in own separete issue? that would help.
@JanneKiiskila The tools don't need to understand linking sections at all, and don't understand linking sections. That's up to linker scripts for the individual compilers. You would have to look at GCC_ARM, IAR and ARMC5 to determine how to write a linker script for each of them to take advantage of the different regions.
referenced this issue
Jul 10, 2017
I think the fix proposed by Archcady should go into the next mbed OS 5.5.x patch release.