Matter, New Era of Connection, Introduction & Certification

 Matter aims to build a universal IPv6-based communication protocol to make it easier for smart home devices to communicate with each other. The protocol defines the application layer that will be deployed on devices as well as the different link layers to help maintain interoperability. Matter protocol built from the best pieces of existing trustworthy protocols, including Google Weave, Apple HomeKit, and Zigbee.

Matter is using Thread, Wi-Fi, and Ethernet for transport and Bluetooth Low Energy (BLE) for device commissioning to support a host of smart home devices. Any smart home gadgets you have that use these technologies should be able to be bridged into Matter.

Overall, Matter 1.0 simplifies the process of connecting smart home devices and enables seamless communication between them, regardless of their brand or manufacturer.

Matter 1.0 specs already support a variety of common smart home products, including lighting and electrical, HVAC controls, window coverings and shades, safety and security sensors, door locks, media devices including TVs, controllers as both devices and applications, and bridges. Support for security cameras, smart speakers, home appliances and robotic vacuums is already planned for subsequent versions of Matter. With the ecosystem expansion, new use cases and applications are expected to emerge.

Certification Process

Matter Testing

 

The Matter 1.0 standard launches with test cases and comprehensive test tools for Alliance members and a global certification program including nine authorized test labs who are primed to test not only Matter, but also Matter’s underlying network technologies, Wi-Fi and Thread. Wi-Fi enables Matter devices to interact over a high-bandwidth local network and allows smart home devices to communicate with the cloud. Thread provides an energy efficient and highly reliable mesh network within the home.

 

Authorized Testing Providers

• Allion Labs, https://www.allion.com.cn/
• Bureau Veritas, https://www.cps.bureauveritas.com/
• CESI, http://www.cesi.cn/
• DEKRA, https://www.dekra-product-safety.com/
• Element Material Technology, https://www.element.com/
• Granite River Labs, https://www.graniteriverlabs.com/
• Resillion, https://www.resillion.com/
• TÜV Rheinland, https://www.tuv.com/
• UL Solutions, https://www.ul.com/
• 
  
  
  
  

Editor: Sales Manager: Mr. Neo Hsu

Raytac Corporation 勁達國際電子有限公司
A BT5.2 & BT5.1 & BT5 module maker based on Nordic nRF53 & nRF52 solution 
(nRF5340 & nRF52840 & nRF52833 & nRF52832 & nRF52820 & nRF52811 & nRF52810 & nRF52805)
www.raytac.com email: service@raytac.com Tel: +886.2.3234.0208

FCC Amends Equipment Authorization Program - A written and signed attestation Needed

 For protecting against National Security Threats reason, FCC newly announced a new request added in Equipment Authorization program. FCC Publication Number: 986446. date:01/24/2023.

FCC amends the rules related to equipment authorization program to prevent any unacceptable risk result from communications networks and supply chains from equipment. DA/FCC #: FCC-22-84. FCC Amends Equipment Authorization Program require applicants for certification need to provide a written and signed attestation. Also, any equipment certification needs to identify a agent, located in United States for service or the process.

Raytac Corporation has pointed US subsidiary, Raytac USA LLC., poses as the US agent for Raytac Corporation to fulfill the FCC new requirements. Customers has any issues to adopt this new regulation may contact Raytac for further support.

Raytac Corporation 勁達國際電子有限公司
A BT5.2 & BT5.1 & BT5 module maker based on Nordic nRF53 & nRF52 solution 
(nRF5340 & nRF52840 & nRF52833 & nRF52832 & nRF52820 & nRF52811 & nRF52810 & nRF52805)
www.raytac.com email: service@raytac.com Tel: +886.2.3234.0208

How To Get Started With nRF5340 Module Program Coding and Compiling

 Intro:

As the chipset of nRF5340 is built by Dual Core structure (net core and application core), we need to proceed the coding and compiling process individually to net core & application core.

After the coding and compiling process done, we could get the separate zephyr.hex file respectively which are used for BLE module FW.

 Firmware Development Steps : Code Building / Compiling

Case Study :　

    NON-Audio Project

　　nRFConnect SDK V2.1.2

    Nordic Example code -“hci_rpmsg” & “peripheral_uart”

1. Nordic example code of “hci_rpmsg” extracted for coding and we will get zephyr.hex file for net core
2. Nordic example code of “peripheral_uart” extracted for coding and we will get zephyr.hex file for application core

Step 1. Net core Layer

1a) Activate “Open VS Code” IDE in NCS V2.1.2

1b) Select “Add an existing application” and extract “hci_rpmsg” file moving forward

1c) Click “Add Build Configuration” icon

1d) Select “nrf5340dk_nrf5340_cpunet” and check Nordic boards, then Execute “Build Configuration”

1e) zephyr.hex file is successfully generated for net core layer if the coding process is properly executed

Step 2. Application core Layer:

2a) Activate “Open VS Code” IDE in NCS V2.1.2

2b) Select “Add an existing application” and extract “peripheral_uart” file moving forward

2c) Click “Add Build Configuration” icon

2d) Select “nrf5340dk_nrf5340_cpuapp” and check Nordic boards, then Execute “Build Configuration”

2e) zephyr.hex file is successfully generated for application core layer if the coding process is properly executed

 

 

 

 

 

 

 

 

Find more nRF5340 module development resources in below link

How To Get started with MDBT53/53V Demo Board Set up (MDBT53-DB-40/MDBT53V-DB-40)

How To USE Nordic Connect SDK (NCS) Flashing Built Code into nRF5340 Module

Raytac Corporation 勁達國際電子有限公司

A BT5.3 & BT5.2 & BT5.1 module maker based on Nordic nRF53 & nRF52 solution 
(nRF5340 & nRF52840 & nRF52833 & nRF52832 & nRF52820 & nRF52811 & nRF52810 & nRF52805)
www.raytac.com email: service@raytac.com Tel: +886.2.3234.0208

How to Get nRF52840 & nRF52833 Module Zephyr Project Started

 Zephyr is hosted by The Linux Foundation, which is an open source to build a small, scalable, real-time operating system (RTOS) across multiple architectures. Zephyr Project’s is aiming to provide a collaborative effort between technologies to reduce the cost and accelerate time to market for Internet of Things (IoT) industry.

Nordic, the leading wireless solution provider across Bluetooth, WiFI, LTE, NB-IOT, provides documentation for developers which are interested in starting Zephyr projects. Nordic Zephyr Project Support Page.

Raytac, a Taiwan base professional module maker built up various form factor modules based on Nordic solution, has listed both nRF52833 / MDBT50Q-DB-33 and nRF52840 / MDBT50Q-DB-40 module demo boards in Zephyr support boards data base. Believed these completed and comprehensive support boards reference design can provide all developers a break through path toward success.

 Raytac Corporation 勁達國際電子有限公司

A BT5.3 & BT5.2 & BT5.1 module maker based on Nordic nRF53 & nRF52 solution 
(nRF5340 & nRF52840 & nRF52833 & nRF52832 & nRF52820 & nRF52811 & nRF52810 & nRF52805)
www.raytac.com email: service@raytac.com Tel: +886.2.3234.0208

How To USE Nordic Connect SDK (NCS) Flashing Built Code into nRF5340 Module

Intro:  With the ready built code of zephyr.hex file for net core and application core individually, we would like to proceed code flashing into the MDBT53/53V Nordic nRF5340 BLE module.

Step1.  

Execute nRF Connect >>  Programmer  > > Open

、

Step2. 

Click “SELECT DEVICE” >> Find icon of “nRF5340 DK” which is detected by the programmer app

Step3. 

Click icon of “nRF5340 DK” >> “Erase All” to remove the flash memory from MDBT53/53V BLE Module

Step4.

Click “Add File” to load the net core zephyr.hex and application core zephyr.hex both into programmer

Step5.

Do “Erase & Write ” to execute the flashing process for both zephyr.hex into memory of MDBT53/53V Module.

Step6.

To validate the wireless broadcast of default name “Nordic_UART_Service” from MDBT53/53V Module, please check on the “nRF Connect for mobile” APP and do “Scan device” through your mobile.   Once the device name is detected in your mobile , the wireless connection is successfully done.

You may find more resources in below link:

Hardware set up works
"How To Get started with Nordic nRF5340 Project by Raytac MDBT53/MDBT53V Development Kit Demo Board"

Firmware development:
"How To Get Started With nRF5340 Module Program Coding and Compiling" (Click Me)

 Edited by Jocelyn Tsai / Account Manager

 Raytac Corporation 勁達國際電子有限公司

A BT5.3 & BT5.2 & BT5.1 module maker based on Nordic nRF53 & nRF52 solution 
(nRF5340 & nRF52840 & nRF52833 & nRF52832 & nRF52820 & nRF52811 & nRF52810 & nRF52805)
www.raytac.com email: service@raytac.com Tel: +886.2.3234.0208