BLE DFU Over SMP With Matter

RE: BLE DFU Over SMP With Matter

Hieu — Tue, 17 Sep 2024 16:08:54 GMT

You misunderstood. You can still use the SMP Service. That is not a part of Matter BLE Service.

You then have a module of your own that can deregister the service by default, and register/deregister the service as you see fit.

RE: BLE DFU Over SMP With Matter

SubuMuthu — Tue, 17 Sep 2024 12:02:46 GMT

Thank you! It will be helpful if you can explain little bit. I believe you are asking me to make a copy and create our own services. I was planning to do that already.

However it defeats the purpose here. when ever Nordic updates the SDK and any improvements, we will have to migrate with additional efforts.

Thanks.

RE: BLE DFU Over SMP With Matter

Hieu — Tue, 17 Sep 2024 08:36:18 GMT

My apology for the late response.

I was able to consult some Matter colleagues, and they explained that the BLE Manager Implementation mostly deal with Matter BLE servieces.

The DFU service is outside of that, so you can implement the registering and deregistering of the service in a custom module of your own.

RE: BLE DFU Over SMP With Matter

SubuMuthu — Wed, 04 Sep 2024 20:36:51 GMT

This option is not possible for us because the product does not have any physical buttons.

RE: BLE DFU Over SMP With Matter

Hieu — Fri, 30 Aug 2024 12:03:49 GMT

Hi Subu,

I am still looking into the issue. My apology for the wait.

[quote user="SubuMuthu"]Currently, the DFU service will not be usable because it allows anyone to upload a file. So what I am asking will be useful for everyone.[/quote]

Would an alternative solution be to limit BLE accessibility to only user with physical access?

Regards.

Hieu

RE: BLE DFU Over SMP With Matter

SubuMuthu — Mon, 26 Aug 2024 21:09:56 GMT

Hi Hieu, I don't think the information that you provided will be enough for me to continue the project.

As you mentioned, all the BLE operations are done via BLEManagerImpl and BLEAdvertising Arbiter singltons.

I already tried adding a code/call for shutting down the BLE DFU services using the BLE advertising Arbiter (BLE NUS services has an example) and when I do that, it messes up the Matter BLE advertisement also.

The code for shutting down the BLE service is already there. Nordic needs to add that to the DFU service.

The API for starting and stopping Matter BLE advertisement is also there. All we need is that someone from Nordic Matter team to look and specify it. It will help not only me but every company. Currently, the DFU service will not be usable because it allows anyone to upload a file. So what I am asking will be useful for everyone.

Can please ask the Matter team for what changes will be required to shutdown, and start the BLE services carefully without impacting Matter BLE?

Thanks.

Subu

RE: BLE DFU Over SMP With Matter

Hieu — Thu, 22 Aug 2024 13:13:20 GMT

Hi Subu,

Sorry it took a long time. I would like to be more certain before I reply to you, but since it's so late already, here is what I have found:

[quote user=""]Can you please let me know how we can achieve the below?

The DFU over SMP is not started at power up.
The service is started and stopped by our Application code.

[/quote]

First, you need CONFIG_BT_GATT_DYNAMIC_DB and CONFIG_MCUMGR_TRANSPORT_BT_DYNAMIC_SVC_REGISTRATION , though the latter config selects the first one.

Note that the SMP Server is still registered after initialization regardless, so you need to unregister it first, if you want the device to start without SMP Server by default.

After that, you just register and unregister the service as needed.

Next comes the part where I am not sure, which is where all of that should be done. I am new to Matter and C++, so I am not 100% sure, but it seems all BLE operations are done via the BLEManagerImpl and BLEAdvertisingArbiter singletons.

However, I don't see how to register and unregister service using the existing Matter APIs yet.

[quote user=""]How do we add security and bonding (it is my understanding that Matter standard prohibits bonding)?[/quote]

Matter spec, section 5.4.2.5, requires that BLE Advertising be done with Random Static Address, and that this must be changed every boot.

However, in BLE, if bonding happens, the Random Static Address is treated as an Identity Address. Then if the Identity Address is changed, then the peer will not be able to find the device anymore.

I think this is what has led you to understand that Matter prohibits bonding.

If so, note that section 5.4.2.5 says this:

5.4.2.5. Using BLE
This section provides details of how a device announces its commissionable status using BLE technology.
Nodes currently commissioned into one or more fabrics SHALL NOT employ this method.
NOTE Need to add link(s) to BLE specification.

So, the Random Static Address requirement is only applicable to the Matter BLE Service for Commissioning purposes.

Therefore, if we create a separate BLE identity, and setup the other BLE services on that ID, then bonding can happen.

It's here that I also arrived at the same issue: I don't know how to implement the additional ID with Matter's setup yet.

Do you think that these are sufficient tips for you to continue your project yet?

RE: BLE DFU Over SMP With Matter

SubuMuthu — Wed, 21 Aug 2024 14:53:22 GMT

Hi Hieu,

Can you please let me know the updates? Thank you.

RE: BLE DFU Over SMP With Matter

Hieu — Thu, 15 Aug 2024 19:45:47 GMT

Hi Subu,

I will need some time to look into your questions. I will follow-up with you next week.

Hieu