BLE OTA via matter.ota

[SunHuang]

Hi support team

Our company is processing BLE OTA through APP by ourself developing, here list some question:

1. is matter.ota be encrypt file?

2. could we process BLE OTA via matter.ota

3. is there any API for image exchange (moving from external FLASH to internal memory) after MCU receives matter.ota?

[Maria Gilje]

Hello,

You can read all about Matter OTA in NCS here: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/protocols/matter/overview/dfu.html. Some details are not described in our documentation, so please also refer to the Matter Specification. See this page for an overview of which Matter Specification the different NCS versions support.

2. could we process BLE OTA via matter.ota

DFU for Matter is possible with other methods, and Bluetooth LE is one of the possibilities:

(source: Matter OTA, linked above)

3. is there any API for image exchange (moving from external FLASH to internal memory) after MCU receives matter.ota?

You can see DFU related source code for Matter in NCS here: https://github.com/nrfconnect/sdk-nrf/tree/main/samples/matter/common/src/dfu.

Best regards,

Maria

[SunHuang]

Hi Maria

If we succeed to transfer data through BLE and write to EEPROM. How should I write to internal memory?

Pls refer to attached file of configuration for memory address, how could I set?

What I need is:
1 transfer encrypt file code via BLE (by our own app)
2. Receive data and write in EEPROM
3. Read and decode data By eeprom
4. Write in data to internal memory
5. Proceed McU boot

Now I’m using dfu_multi_image.bin to transfer and attach file to proceed OTA, is this correct?The picture below shows the error message

OTA.7z

[Maria Gilje]

Hello,

The error -14 is EFAULT (bad address). I recommend investigating pm_static.yml to make sure that the addresses are within the ranges for the nRF5340 memory (network core, application core).

Best regards,

Maria

[SunHuang]

Hi 

I have found the reason is that I executed PM_DEVICE_ACTION_SUSPEND