Skip to content

Release candidate for mbed-os-5.3.4 #3660

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

Merged
merged 57 commits into from
Jan 31, 2017
Merged

Release candidate for mbed-os-5.3.4 #3660

merged 57 commits into from
Jan 31, 2017

Conversation

adbridge
Copy link
Contributor

No description provided.

adustm and others added 30 commits January 30, 2017 11:16
This commit improves consistency between different platforms' linker
scripts. In particular, we use "__UVISOR_SRAM_START" instead of
"__UVISOR_BSS_START" as the uVisor BSS sections might be outside of the
SRAM (for example, when using a tightly-coupled memory).
* Add support for uVisor own SRAM.
    * This enables targets where uVisor sits in a TCM.
* Distinguish between uVisor and public SRAMs.
gpio_object.h is included from common_objects.h,
so no need to have it here.
Let's make the code more common for gpios.

The only difference between STM32 families is that BRR register may
not be available. In case BRR is not available, we use the 16 left bits
of BSRR instead. We could always use BSRR, but BRR saves one left-shift
operation, so let's use it when available.

By default we will consider using BRR, except for platforms that define
GPIO_IP_WITHOUT_BRR.
Simple effort to avoid duplicate code.
- correct clock for USB
- add ARM micro support
- add OS5 release support
- add TRNG support
- add ARDUINO form factor support
Assert that the length is greater than one rather than the value
itself. This bug was introduced in the commit:
329be06 -
"exporters - group by directories in prj root"
Commit 19d56fd removed the default file
paths for the toolchains. This was done under the assumption that the
top-level compile scripts were properly checking that the toolchain
executable was availble. The build.py script was doing this in the wrong
place. This commit rearranges the script a bit so the check is performed
properly.
Fix tracebacks from trying to read dictionary values that don't exist
and from incorrect variable names.
Signed-off-by: Mahadevan Mahesh <[email protected]>
Delete page because duplicate page exists in Handbook
@adbridge
Copy link
Contributor Author

retest uvisor

@adbridge
Copy link
Contributor Author

mbed-os 2 results look fine.

@adbridge
Copy link
Contributor Author

@marhil01 @SeppoTakalo Hi guys, looks like Oulu CI is failing again:
[8003] 14:46:25.227 | TC MainThread: Test Case fails because of: dut1 cmd: 'ifconfig mesh0 up',retcode: -1
Could you take a look please?

@adbridge
Copy link
Contributor Author

/morph test-nightly

@adbridge
Copy link
Contributor Author

/morph export-build

@mazimkhan
Copy link

retest uvisor

@mbed-bot
Copy link

Result: SUCCESS

Your command has finished executing! Here's what you wrote!

/morph export-build

Output

mbed Build Number: 96

All exports and builds passed!

@mbed-bot
Copy link

Result: SUCCESS

Your command has finished executing! Here's what you wrote!

/morph test-nightly

Output

mbed Build Number: 1476

All builds and test passed!

@0xc0170
Copy link
Contributor

0xc0170 commented Jan 31, 2017

All CI fixed.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.