restructure - Restructure cmsis directory

[geky]

Some lingering restructure changes related to #2878.

targets/cmsis -> cmsis
targets/cmsis/TARGET_* -> targets/TARGET_*/device
targets/cmsis/TARGET_*/mbed_rtx.h -> targets/TARGET_*/mbed_rtx.h

TODO:

• support mbed 5 builds
• support mbed 2 builds
• pass CI
• pass review

Reviews:

• @screamerbg
• @theotherjimmy
• @bridadan

[geky]

/morph test

[mbed-bot]

Result: SUCCESS

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

/morph test

Output

mbed Build Number: 1042

All builds and test passed!

[theotherjimmy]

Who do you want to review this, @geky?
I was thinking @screamerbg would be a good idea.

[screamerbg]

LGTM! This is awesome.

[bridadan]

@mbed-bot: TEST

HOST_OSES=ALL
BUILD_TOOLCHAINS=ALL
TARGETS=ALL

[bridadan]

/morph export-build

[bridadan]

I gotta say, I really like the way this restructure looks 👍 I always thought the cmsis folder was a bit weird. We'll have to wait and see what the mbed 2 bot says, but so far LGTM

[mbed-bot]

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

[bridadan]

mbed 2 bot was not a happy camper. @geky Let me know if you need help reproducing

[geky]

@mbed-bot: TEST

HOST_OSES=ALL
BUILD_TOOLCHAINS=ALL
TARGETS=ALL

[geky]

/morph export-build

[bridadan]

/morph test

[mbed-bot]

Result: FAILURE

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

/morph export-build

[mbed-bot]

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

[bridadan]

The export test has no regressions as of this PR: #2898

@sarahmarshy's PR will need to be merged to get the export test back to passing: #2708

So exporter tests look ok 👍

[mbed-bot]

Result: SUCCESS

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

/morph test

Output

mbed Build Number: 1056

All builds and test passed!

[screamerbg]

Is this ready for merge then @sg- @bridadan ?

[sg-]

lots of failing CI. Still work in progress

[geky]

@mbed-bot: TEST

HOST_OSES=ALL
BUILD_TOOLCHAINS=ALL
TARGETS=ALL

[geky]

/morph test

[mbed-bot]

[Build ${MBED_BUILD_ID}]
FAILURE: Something went wrong when building and testing.

[geky]

@mbed-bot: TEST

HOST_OSES=ALL
BUILD_TOOLCHAINS=ALL
TARGETS=ALL

[mbed-bot]

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

[mbed-bot]

Result: SUCCESS

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

/morph test

Output

mbed Build Number: 1064

All builds and test passed!

[bridadan]

@geky Saw this failure from the mbed 2 bot: http://10.118.12.43:8080/job/mbed-2-build-and-run-tests_hw/5852/testReport/test.NUCLEO_F334R8.GCC_ARM/RTOS_4/Signals_messaging/

The important line is here: mbed assertation failed: interrupts_disabled, file: C:\Jenkins\workspace\mbed-2-build-library\platform\mbed_critical.c, line 55 {{mbed_assert}}

Is this a known issue?