| commit | 5dc7463473789347527109be2e6b8b7c3d35f9e4 | [log] [tgz] |
|---|---|---|
| author | Kamil Kasperczyk <66371704+kkasperczyk-no@users.noreply.github.com> | Tue Mar 07 18:02:45 2023 +0100 |
| committer | GitHub <noreply@github.com> | Tue Mar 07 18:02:45 2023 +0100 |
| tree | 3f4fd94019a5067939fcaa6b4ee26473b0298fef | |
| parent | ab3d68082b6f25ebede0bde7a239a23b5affa2fd [diff] |
[nrfconnect] Updated nRF Connect SDK to 2.3.0 (#25432)
* [nrfconnect] Removed IPC priority workaround from overlays
Removed a workaround regarding IPC priority, which is
not needed anymore in Matter samples.
* [nrfconnect] Aligned DFU implementation to new mcumgr API
With nRF Connect SDK 2.3.0 mcumgr API changed and DFU over SMP
implementation required updating.
* [nrfconnect] Updated nRF Connect SDK to 2.3.0
Bumped recommended nRF Connect SDK version to 2.3.0
and bring in list of commits including mainly Wi-Fi
support fixes:
1. Implemented most of the Wi-Fi DiagnosticDataProvider.
Added PHY statistics:
* multicast RX/TX
* unicast RX/TX
* beacons lost/TX
Signed-off-by: Marcin Kajor <marcin.kajor@nordicsemi.no>
2. wifi: map supplicant WiFi version into what Matter expects
This is needed to return proper Wi-Fi version code to the Matter
controller when querying wifinetworkdiagnostic cluster.
Signed-off-by: Marcin Kajor <marcin.kajor@nordicsemi.no>
3. Fix the 'disconnected' status appearing after scan is issued.
Restore the connection state which was set before requesting scan.
Note that the connection was not really dropped, only the status
reporting was broken.
Signed-off-by: Marcin Kajor <marcin.kajor@nordicsemi.no>
4. Fix ram_report and rom_report
Stop filtering out gdwarf-4 when passing flags from Zephyr
to Matter's GN build system. Older pyelftools versions are
not able to parse DWARF5 format, so ram and rom report
would not be generated.
Signed-off-by: Damian Krolik <damian.krolik@nordicsemi.no>
5. wifi: fixed the connection callback initialization
This fixes the misbehavior when attempting to establish a connection
with the network that is not added to the networkcommissioning cluster.
Signed-off-by: Marcin Kajor <marcin.kajor@nordicsemi.no>
6. Fixed the timeout when connecting to the WPA3 secured AP.
Set the WiFi MFP (management frame protection) as at least optional.
The current WiFi driver does not support this parameter within the
scan result, so it must the hard coded for the time being
(made it mandatory for secure associations, just in case).
Signed-off-by: Marcin Kajor <marcin.kajor@nordicsemi.no>
7. Switch to statically allocated heap
* Use malloc/free replacements based on statically allocated
Zephyr's sys_heap to provide better control of RAM usage.
* Fixed hard fault once advertising mdns records
In mDNS code there isn't a check that would verify if
memory was allocated successfully. In case heap is too small
the application will fall into hard fault due to usage of
non-allocated memory.
* Increased heap size for Wi-Fi.
Empirically it was measured that heap size needed to pass the
Wi-Fi commissioning is ~25k. To be on the safe side let's set it
to 28k.
8. Disabled NFC thread callback
NFC lib introduced new callbacks that are not needed by the
Matter samples and increase flash usage.
9. Update required MCUmgr config
Updates required MCUmgr configuration for zephyr upmerge changes.
Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
10. [nrfconnect] Disable unnecessary shell features
Save more flash by disabling shell wildcard, colors, stats
and kernel commands.
Signed-off-by: Damian Krolik <damian.krolik@nordicsemi.no>
11. Increased the default net_mgmt stack size.
Once we were hit by the net_mgmt thread stack overflow
while show casing the Matter over WiFi solution in
WiFi RF congested environment. Increase the default
stack size of net_mgmt from 768 to 1k.
Signed-off-by: Marcin Kajor <marcin.kajor@nordicsemi.no>
12. Use generic channel when connecting.
Currently using the specific channel number does not work
reliably in WiFi driver, so use the generic channel screening.
Signed-off-by: Marcin Kajor <marcin.kajor@nordicsemi.no>
13. Rework net_mgmt WiFi event handling to offload CHIP thread.
In the case there are many networks available, the scan result
events may saturate the CHIP work queue which has lower priority
then the net_mgmt and main threads. So, collect the scan results
in the main thread and only ping the CHIP thread when the scan is done.
Signed-off-by: Marcin Kajor <marcin.kajor@nordicsemi.no>
14. Enable runtime PA gain control when FEM is active
Output power at the antenna port can be controlled
automatically after setting
MPSL_FEM_NRF21540_RUNTIME_PA_GAIN_CONTROL config.
After enabling it the user can use the
CONFIG_OPENTHREAD_DEFAULT_TX_POWER config to control OpenThread
radio output power.
15. [nrfconnect] Introduce the WiFi connection recovery feature
The WiFi connection recovery feature allows device re-scanning
and re-connecting to the known WiFi network after the device's reboot
and when the known SSID has not been found during the last scan.
The connection recovery interval is doubled with
every occurrence to the defined maximum value and then its value
depends on the maximum value +- the defined random jitter.
After restoring the connection, the Connection Recovery
Interval is restored to the defined minimum value after elapsing
of the defined delay to avoid frequent reconnections to a
poor link quality network.
[nrfconnect] WiFi connection recovery refinements:
* simplify recovery time resetting (due to connection status
reporting limitations)
* remove CHIP_WIFI_CONNECTION_RECOVERY_RESET_DELAY (not needed now)
* avoid duplicated recovery timeout bumps
* always start the recovery with kConnectionRecoveryMinIntervalMs
* fixed some edge cases and memory leaks
* minor cleanup
* logging refinements
* Kconfig description fixes after tech writer review
* Move new Kconfig definitions to the Kconfig.features
Signed-off-by: Marcin Kajor <marcin.kajor@nordicsemi.no>
16. Fixed several Wi-Fi issues
* Disabled Wi-Fi/BLE coex as it was not stable and caused issues
in CI tests
* Increased sockets poll and net mgmt stack to fix crash on the
application boot due to no space to alloc all sockets
* Added generating kDnssdInitialized event after getting Wi-Fi
connected event to re-start mDNS server
Fix the unused variable error.
This is warning propagated to an error in the CI.
Signed-off-by: Marcin Kajor <marcin.kajor@nordicsemi.no>
17. Mapped the WiFi security type from Zephyr to Matter
The Security type attribute was wrongly cast in the WiFi Manager.
Used switch-case-based mapping between two enum types
(Zephyr-Matter) to make sure that we properly cast between
two different types.
* [nrfconnect] Fixed incorrect DNSSD event name
In Wi-Fi platform, the obsolete kDnssdPlatformInitialized
event name is used for event generation.
Updated name to kDnssdInitialized.
* [nrfconnect] Fixed Wi-Fi version and security getters
The Wi-Fi platform uses obsolete EMBER_ZCL macros for Wi-Fi
version and security getters.
Replaced EMBER macros with enums from WiFiNetworkDiagnostics.
* [nrfconnect] Fixed restyler diff in DiagnosticDataProviderImplNrf
* [nrfconnect] Addressed code review comments
* Aligned default configs
* Refactored WiFiInfo struct to use SecurityTypeEnum instead of
uint8_t.
* Fix native_posix tests
---------
Co-authored-by: Damian Krolik <damian.krolik@nordicsemi.no>
Matter (formerly Project CHIP) creates more connections between more objects, simplifying development for manufacturers and increasing compatibility for consumers, guided by the Connectivity Standards Alliance.
Matter is a unified, open-source application-layer connectivity standard built to enable developers and device manufacturers to connect and build reliable, and secure ecosystems and increase compatibility among connected home devices. It is built with market-proven technologies using Internet Protocol (IP) and is compatible with Thread and Wi-Fi network transports. Matter was developed by a Working Group within the Connectivity Standards Alliance (Alliance). This Working Group develops and promotes the adoption of the Matter standard, a royalty-free connectivity standard to increase compatibility among smart home products, with security as a fundamental design tenet. The vision that led major industry players to come together to build Matter is that smart connectivity should be simple, reliable, and interoperable.
Matter simplifies development for manufacturers and increases compatibility for consumers.
The standard was built around a shared belief that smart home devices should be secure, reliable, and seamless to use. By building upon Internet Protocol (IP), Matter enables communication across smart home devices, mobile apps, and cloud services and defines a specific set of IP-based networking technologies for device certification.
The Matter specification details everything necessary to implement a Matter application and transport layer stack. It is intended to be used by implementers as a complete specification.
The Alliance officially opened the Matter Working Group on January 17, 2020, and the specification is available for adoption now.
Visit buildwithmatter.com to learn more and read the latest news and updates about the project.
Matter is developed with the following goals and principles in mind:
Unifying: Matter is built with and on top of market-tested, existing technologies.
Interoperable: The specification permits communication between any Matter-certified device, subject to users’ permission.
Secure: The specification leverages modern security practices and protocols.
User Control: The end user controls authorization for interaction with devices.
Federated: No single entity serves as a throttle or a single point of failure for root of trust.
Robust: The set of protocols specifies a complete lifecycle of a device — starting with the seamless out-of-box experience, through operational protocols, to device and system management specifications required for proper function in the presence of change.
Low Overhead: The protocols are practically implementable on low compute-resource devices, such as MCUs.
Pervasive: The protocols are broadly deployable and accessible, by leveraging IP and being implementable on low-capability devices.
Ecosystem-Flexible: The protocol is flexible enough to accommodate deployment in ecosystems with differing policies.
Easy to Use: The protocol provides smooth, cohesive, integrated provisioning and out-of-box experience.
Open: The Project’s design and technical processes are open and transparent to the general public, including non-members wherever possible.
Matter aims to build a universal IPv6-based communication protocol for smart home devices. The protocol defines the application layer that will be deployed on devices and the different link layers to help maintain interoperability. The following diagram illustrates the normal operational mode of the stack: 
The architecture is divided into layers to help separate the different responsibilities and introduce a good level of encapsulation among the various pieces of the protocol stack. The vast majority of interactions flow through the stack captured in the following Figure:
Security: An encoded action frame is then sent down to the Security Layer to encrypt and sign the payload to ensure that data is secured and authenticated by both sender and receiver of a packet.
Message Framing & Routing: With an interaction encrypted and signed, the Message Layer constructs the payload format with required and optional header fields; which specify the message's properties and some routing information.
Matter’s design and technical processes are intended to be open and transparent to the general public, including to Working Group non-members wherever possible. The availability of this GitHub repository and its source code under an Apache v2 license is an important and demonstrable step to achieving this commitment. Matter endeavors to bring together the best aspects of market-tested technologies and redeploy them as a unified and cohesive whole-system solution. The overall goal of this approach is to bring the benefits of Matter to consumers and manufacturers as quickly as possible. As a result, what you observe in this repository is an implementation-first approach to the technical specification, vetting integrations in practice. The Matter repository is growing and evolving to implement the overall architecture. The repository currently contains the security foundations, message framing and dispatch, and an implementation of the interaction model and data model. The code examples show simple interactions, and are supported on multiple transports -- Wi-Fi and Thread -- starting with resource-constrained (i.e., memory, processing) silicon platforms to help ensure Matter’s scalability.
We welcome your contributions to Matter. Read our contribution guidelines here.
Instructions about how to build Matter can be found here .
The Matter repository is structured as follows:
| File/Folder | Content |
|---|---|
| build | Build system support content and built output directories |
| build_overrides | Build system parameter customization for different platforms |
| config | Project configurations |
| credentials | Development and test credentials |
| docs | Documentation, including guides |
| examples | Example firmware applications that demonstrate use of Matter |
| integrations | 3rd Party integrations |
| scripts | Scripts needed to work with the Matter repository |
| src | Implementation of Matter |
| third_party | 3rd party code used by Matter |
| zzz_generated | zap generated template code - Revolving around cluster information |
| BUILD.gn | Build file for the gn build system |
| CODE_OF_CONDUCT.md | Code of conduct for Matter and contribution to it |
| CONTRIBUTING.md | Guidelines for contributing to Matter |
| LICENSE | Matter license file |
| REVIEWERS.md | PR reviewers |
| gn_build.sh | Build script for specific projects such as Android, EFR32, etc. |
| README.md | This File |
Matter is released under the Apache 2.0 license.