Export uVision linker flags so that bootloader projects build correctly #5030
Conversation
|
/morph export-build |
|
@chrissnow What is the current behavior without these flags? How to reproduce this issue? |
|
It will build but will be linked to the defaults in the linker script. Which would be where the bootlooader lives. |
|
Here is a correctly formed pair of projects Before the "Misc controls" would be empty. the linker then should have something like this. #if !defined(MBED_APP_START)
#define MBED_APP_START 0x00000000
#endif
#if !defined(MBED_APP_SIZE)
#define MBED_APP_SIZE 0x80000
#endif
LR_IROM1 MBED_APP_START MBED_APP_SIZE { ; load region size_region
ER_IROM1 MBED_APP_START MBED_APP_SIZE { ; load address = execution address
*.o (RESET, +First)
*(InRoot$$Sections)
.ANY (+RO)
}which will correctly move the regions around. |
Result: FAILUREYour command has finished executing! Here's what you wrote!
Outputmbed Build Number: 135 Exporter Build failed! |
|
:-( Please could someone share the reason it failed. |
|
IAR died hard. @studavekar The CI should be able to find iccarm and the other tools in the path for executing the make_iar exporter. Could a machine switch have caused the boat load of IAR error here? |
|
@chrissnow It looks like your patch is working, well not breaking CI (no uVision failures at all), and we need to repair the IAR installation or something like that. |
|
One of the machine didn't had path set, re-triggering /morph export-build |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
Outputmbed Build Number: 136 All exports and builds passed! |
Description
Bootloader projects require DMBED_APP_START and DMBED_APP_SIZE flags passing to the linker, CLI does this but export did not.
Status
READY
Migrations
NO
Related PRs
Deploy notes
Steps to test or reproduce
Export a bootloader project and it does not have the linker flags set.