Chip uses new Mbed - Githubissues

ARMmbed / connectedhomeip

Project Connected Home over IP is a new Working Group within the Zigbee Alliance. This Working Group plans to develop and promote the adoption of a new connectivity standard to increase compatibility among smart home products, with security as a fundamental design tenet.

https://www.connectedhomeip.com

Apache License 2.0

10 stars 4 forks source link

Chip uses new Mbed #179

Closed tymoteuszblochmobica closed 3 years ago

tymoteuszblochmobica commented 3 years ago

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 commented 3 years ago

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

lukgni commented 3 years ago

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 commented 3 years ago

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:

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