Skip to content

Update uVisor to v0.20.0-alpha #2228

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 4 commits into from
Jul 23, 2016
Merged

Conversation

AlessandroA
Copy link
Contributor

This release brings the support of Keil RTX with uVisor on mbed OS, plus several other improvements.

New features

  • Integration in Keil RTX in mbed OS.
  • Secure dynamic allocation APIs.
  • Box initialization routines.
  • Register gateway.
  • vMPU recovery generalized for both Kinetis and ARMv7-M MPUs.
  • APIs for per-box interrupts disablement and re-enablement.

Work in progress

  • Remote Procedure Call (RPC). New API signatures have been published. The alpha-level implementation will follow soon.

Deprecated features

  • Secure gateway. Cross-box communication will be implemented with RPC gateways.

Bugfixes

  • Several ARMv7-M-specific bug fixes.
  • Fixed a bug that sent the device into lock-up after a hard fault.
  • Fixed checks on revision numbers for Cortex-M devices.

Miscellaneous improvements

  • Optimized memory protection for ARMv7-M devices with shared SRAM.
  • Build artifacts are grouped into the target/build option/configuration-specific folder.
  • Documents have been grouped into API vs. core documents.
  • Improved style and consistency.

@mjs-arm @sg- @meriac @c1728p9 @geky

This release brings the support of Keil RTX with uVisor on mbed OS, plus
several other improvements.

**New features**

* Integration in Keil RTX in mbed OS.
* Secure dynamic allocation APIs.
* Box initialization routines.
* Register gateway.
* vMPU recovery generalized for both Kinetis and ARMv7-M MPUs.
* APIs for per-box interrupts disablement and re-enablement.

**Work in progress**

* Remote Procedure Call (RPC). New API signatures have been published.
* The alpha-level implementation will follow soon.

**Deprecated features**

* Secure gateway. Cross-box communication will be implemented with RPC
* gateways.

**Bugfixes**

* Several ARMv7-M-specific bug fixes.
* Fixed a bug that sent the device into lock-up after a hard fault.
* Fixed checks on revision numbers for Cortex-M devices.

**Miscellaneous improvements**

* Optimized memory protection for ARMv7-M devices with shared SRAM.
* Build artifacts are grouped into the target/build
* option/configuration-specific folder.
* Documents have been grouped into API vs. core documents.
* Improved style and consistency.
@AlessandroA
Copy link
Contributor Author

@mbed-bot: TEST

HOST_OSES=windows,linux
BUILD_TOOLCHAINS=GCC_ARM,ARM,IAR
TARGETS=K64F

1 similar comment
@bridadan
Copy link
Contributor

@mbed-bot: TEST

HOST_OSES=windows,linux
BUILD_TOOLCHAINS=GCC_ARM,ARM,IAR
TARGETS=K64F

@bridadan
Copy link
Contributor

@AlessandroA Sorry about that, not sure why the bot didn't fire. It's going now.

@mbed-bot
Copy link

[Build 675]
FAILURE: Something went wrong when building and testing.

@bridadan
Copy link
Contributor

/morph test

@AlessandroA
Copy link
Contributor Author

@bridadan Thanks for triggering the tests! Are these failures related to the PR or independent from it?

@mbed-bot
Copy link

Result: FAILURE

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

/morph test

@bridadan
Copy link
Contributor

bridadan commented Jul 22, 2016

@AlessandroA [Build 675] is not failing due to the PR, there was an underlying tool issue in mbedls. That should be resolved now.

The last failure seems to be existing failures in the code base. This PR was the first PR used with the new bot, so sorry for the hiccups! I'm looking at it now.

@sg-
Copy link
Contributor

sg- commented Jul 22, 2016

@mbed-bot: TEST

HOST_OSES=windows
BUILD_TOOLCHAINS=GCC_ARM,ARM,IAR
TARGETS=K64F,NRF51_DK,NUCLEO_F411RE

@mbed-bot
Copy link

[Build 678]
SUCCESS: Building succeeded and tests were run! Be sure to check the test results

@bridadan
Copy link
Contributor

/morph export-build

@mbed-bot
Copy link

Result: SUCCESS

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

/morph export-build

@sg-
Copy link
Contributor

sg- commented Jul 22, 2016

/morph test

@mbed-bot
Copy link

Result: FAILURE

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

/morph test

Output

mbed Build Number: 482

A build failure occurred!

@sg-
Copy link
Contributor

sg- commented Jul 22, 2016

/morph test

@mbed-bot
Copy link

Result: ABORTED

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

/morph test

@sg-
Copy link
Contributor

sg- commented Jul 23, 2016

/morph test

@mbed-bot
Copy link

Result: FAILURE

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

/morph test

Output

mbed Build Number: 488

A test failure occurred!

@sg-
Copy link
Contributor

sg- commented Jul 23, 2016

All green for K64F. Failures are known testing failures.

@sg- sg- merged commit a4fb649 into ARMmbed:master Jul 23, 2016
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.

4 participants