Chip uses new Mbed

[tymoteuszblochmobica]

Problem

Chip uses new Mbed
Quick PR

Change overview

What's in this PR

Testing

How was this tested? (at least one bullet point required)

• If unit tests were added, how do they cover this issue?
• If unit tests existed, how were they fixed/modified to prevent this in future?
• If new unit tests are not added, why not?
• If integration tests were added, how do they verify this change?
• If new integration tests are not added, why not?
• If manually tested, what platforms controller and device platforms were manually tested, and how?
• If no testing is required, why not?

[tymoteuszblochmobica]

This is initial. Im going to clean and add lockapp and shell

[lukgni]

I didn't see any change here which modifies mbed-os version to something newer.
Have we already switched to the newer mbed-os version on development branch?

[lukgni]

I updated mbed-os branch in third_party directory - it looks like CI is happy now (at least for ours workflows).

Here is some notes (or required steps) for changing/updating submodule branch:

1. edit manually .gitmodules file
2. execute git submodule sync (only if submodule url has been changed - we need to synchronize .gitmodules with .git/config in that case)
3. execute git submodule update --init --remote ./third_party/mbed-os/repo to pull changes
4. commit changes in .gitmodules and ./third_party/mbed-os/repo

[pan-]

Approved but ARMmbed/mbed-os#14847 must be merged first. @ATmobica can you look at the PR and address remaining comments ?

[pan-]

I don't think we can use it until ARMmbed/mbed-os#14847 has been merged

[pan-]

It should work with the code we have now but it won't with what's present upstream.

[ATmobica]

Sure, I think we can merge it to the current development but check it again before upstreaming.

[pan-]

Ok, worst case, we can extract patch master with the PR, put it in a branch and reference it from here.