BDX transfer timeout in Matter OTA DFU

[Oide Brett]

Hi

I followed the youtube tutorial ( How to go to market with Matter ) from the Nordic Semiconductors youtube channel. I have followed all the instructions on testing the matter OTA device firmware update. I am using

- Nrf52840 DK with the matter lock app built and flashed

- Openthread Border router on Raspberry Pi 3B+ and Nrf52840 dongle as RCP

    - v2.3.0 nrf toolchain and rcp coprocessor code

    - hash a892bf7 for otbr-posix

- A laptop running the OTA provider linux app

    - sudo out/chip-ota-provider-app -f ./examples/lock-app/nrfconnect/build/zephyr/matter.ota -p 5

- Same laptop running chip-tool

    - sudo out/chip-tool otasoftwareupdaterequestor announce-otaprovider 1 0 0 0 2 0

I can commission the end device and the ota provider and I can start the DFU process. However, I am constantly running into a BDX transfer timeout issue which I suspect is being caused by sending such BDX over thread.

Are there any recommendations to prevent the timing out of the BDX transfer? By the way, I really want to get the matter standard way working not the proprietary method from Nordic Semi

Many thanks

[AHaug]

Hi,

I've picked up your case and I've brought your issue up with the developers. I'll get back to you when I hear from them

We could benefit from any runtime logs that shows the fault your observing. Could you provide them in a comment in this thread?

Kind regards,
Andreas

[Oide Brett]

Hi Andreas,

I ran it again and it worked. This time restarted my OTBR (on a RPi) and moved the NRF52840 closer to the border router. I dont have the logs from the times it didnt work but I did see some Duplicate Chip message errors. Could this be a problem with my otbr not processing the messages quickly enough? Is there any way I can adjust the timeout for each BDX message receipt?

Many thanks

Ivo

[AHaug]

Hi,

Oide Brett said:

I ran it again and it worked. This time restarted my OTBR (on a RPi) and moved the NRF52840 closer to the border router. I dont have the logs from the times it didnt work but I did see some Duplicate Chip message errors. Could this be a problem with my otbr not processing the messages quickly enough? Is there any way I can adjust the timeout for each BDX message receipt?

Glad to hear you got it to work!

Just speculation, but it could be an issue caused by dropped messages or with processing speed, but I can't say anything for sure. It might also be another issue that we can't solve without the log for the issue, so if it ever shows up again, please upload them and we'll have another look at the issue

Kind regards,
Andreas