Feasibility of Using SPI as Transport Layer for mcumgr Firmware Updates on nRF52820

[Lezhi]

Hello,

I am considering implementing SPI communication as the transport layer for mcumgr in my application. The setup involves an nRF52820 as an SPI slave and an nRF52840 as the SPI master. The goal is to transmit the new firmware image via SPI, using the SMP protocol to facilitate firmware updates.

Given that the SPI slave functionality in nRF Connect SDK(2.7.0) is currently marked as experimental, I would like to know more about the feasibility of this approach. Specifically:

1. Are there known limitations or stability issues when using SPI as the transport layer for mcumgr in this configuration?
2. Does the experimental status of the SPI slave in NCS imply potential issues or limitations with data integrity or reliability during firmware updates?
3. Any recommendations or best practices for setting up SPI-based mcumgr firmware updates with this hardware configuration?

P.S. The implementation of the nRF52840 is not involved in this discussion, it uses a different stack. 

Thank you in advance for any insights or guidance.

Lezhi

[Menon]

Hello,

I recommend that you test and validate it. As I mentioned before, I haven't used SPI for a firmware update. However, when you do the testing, I suggest using large files. This will help you see how well your system handles data transfer, buffering, and any potential issues that may arise during lengthy operations.

Kind regards,
Abhijith

[Lezhi]

Hello,

OK, thank you for your advices.

Regards,

Lezhi