Enable post build bootloader merging in uvision #10021
This PR enables the following:
Fairly confident this is now in working order after doing quite a bit of testing offline. There are some other issues with the uvision exporter at the moment. Some of them are being addressed in #10045 (which this PR depends on). I've raised #10045 separately because those fixes are higher priority than the feature added in this PR.
Pull request type
Offline projects that use the managed bootloader mode (as is the case for all Pelion Device Management projects using the update capability) should now be able to export and debug properly in uVision. A post build script is now enabled which takes care of the header generation, binary merging, and loading of the correct symbols for your application. This only allows debugging the application, not the bootloader.
Note: This feature is only enabled when exporting offline with Mbed CLI. This is because the post build script has a dependency on the Mbed OS tools and their Python dependencies. This means projects exported from the Online Compiler will not be able to use this capability.
@theotherjimmy, very true. Is this currently omitted when exporting Mbed OS 5 projects from the online compiler? I realize the tools directory would not be present in Mbed OS 2 projects, but those projects can't/shouldn't be using managed bootloader?
referenced this pull request
Mar 12, 2019
Actually that definitely wouldn't work as is, the post build script has dependencies in the rest of the config system. The way I see it, my options are:
Any thoughts on the above options?
@bridadan I'm down for 3. 1 would need to require that the script is actually not duplicated. I'm not sure that 2 is a good idea. Recent refactors have taken the direction of migrating files into the Resources style of working, so adding yet another way to do the same thing feels like adding tech debt to me.