Release mbed-os-5.1.5 and mbed lib v127 #2850
Conversation
8K RAM target is too small for "NUCLEO_L031K6" "NUCLEO_L053R8" "DISCO_L053C8" "NUCLEO_F030R8"
- Add support of cortex-M7 for cthunk. - Change the cthunk trampoline implementation to safer and quicker solutions: * thumb2, the behaviour was undefined. new implementation use now 2 instructions * thumb, The new implementation use 3 instructions instead of 6.
bugfixing the can loop test which failed after PR #2504
This patch modifies: * the Beetle GCC ARM linker script * the Beetle startup code in order to define the memory regions that enable uvisor. Signed-off-by: Vincenzo Frascino <vincenzo.frascino@arm.com>
This patch backports the virtual NVIC mechanish from CMSIS 5 for the Cortex M3 architecture in order to support uvisor in this MCU class. Signed-off-by: Vincenzo Frascino <vincenzo.frascino@arm.com>
This patch adds CMSIS 5 virtual NVIC compliancy in order to support uvisor. Signed-off-by: Vincenzo Frascino <vincenzo.frascino@arm.com>
This patch disables the fcache stats into mbed_sdk_init if uvisor is defined in order to prevent MEMMANAGEMENT faults during boot. Signed-off-by: Vincenzo Frascino <vincenzo.frascino@arm.com>
This patch adds Beetle platform to uvisor importer. Signed-off-by: Vincenzo Frascino <vincenzo.frascino@arm.com>
…checking link status
Build jobs are failing due build error "arm_hal_timer.cpp:50:5: error: reference to 'callback' is ambiguous". Fix the build error by renaming callback to arm_hal_callback to avoid collision with callback defined in ./mbed-os/hal/api/Callback.h
- Check if disconnected in socket open - Check if connected in interface connect - Check if disconnected in interface disconnect
Removed code that checks if the path to the map file matches with the selected toolchain.
The previous way of finding group names found the encompassing directory of each file. If the project is exported from the online compiler, this resulted in temporary folder names like tmpyKKWv_ showing up as group names. I propose defaulting to the project name if the file is in the project root.
|
/morph test-nightly |
|
LGTM @sg- please approve |
|
Thanks @adbridge . |
Result: FAILUREYour command has finished executing! Here's what you wrote!
|
|
WAIT on Merge!! tools.utils.InvalidReleaseTargetException: Target 'XDOT_L151CC' must set the 'default_build' to 'standard' to be included in the mbed OS 5.0 official release. |
|
Nevermind, it looks like that commit is actually in, need to see what's actually happening... |
|
The xdot ones had to come across via their original commits rather than the PR sha commit due to the rebasing |
|
Think I found the sucker: #2409 Any idea why this didn't come over? |
|
I suspect the error is due to the targets.json file being slightly wrong. I had to manually fix that up so may have got it slightly wrong! |
|
Nope that was pre-script territory ! ie when the process was still manual! |
|
Is it just a case of changing "default_build": "std", to "default_build": "standard", in targets.json ? |
|
@adbridge I think this is an error, as on master everything is named |
Don't forget that this is about backward compatibility, and it was standard up until this release. @adbridge please check with @screamerbg |
|
/morph test-nightly |
Result: FAILUREYour command has finished executing! Here's what you wrote!
Outputmbed Build Number: 1002 Build failed! |
|
/morph test-nightly |
Result: FAILUREYour command has finished executing! Here's what you wrote!
Outputmbed Build Number: 1004 Build failed! |
|
mmm looks like another rebasing issue!! Getting the commits directly from the PR just doesn't like it when a rebase has happened! This is fixed in the update to the script I've been working on in the background, but wasn't ready for this release! Argghh rebasing and backporting = nasty! |
|
/morph test-nightly |
Result: FAILUREYour command has finished executing! Here's what you wrote!
Outputmbed Build Number: null Examples Build failed! |
|
For mbed-os 5 now looks like all builds are passing and only the mbed-os uvisor example is failing. Just waiting on mbed-os 2 results now. |
Release candidate.