• State Suggested Answer
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 73 subscribers
  • Views 892 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 205642
Options
Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Serial DFU bootloader in SDK13 and migration to SDK14/15

LeonWu

Hi team,

My customer wants to apply Serial DFU in their product, but when they are developing with SDK13, they find our release notes with:

** DFU **
- Added support for serial/UART and an example for a secure DFU
  bootloader using UART (experimental).

They want to know what is it mean for the "experimental", is it pending qualified? What is the risk if they apply this code?

BTW, in SDK14, we actually see it is listed as:

** DFU **
- Serial DFU has been updated to be production quality.

Is it a must that they need to migrate to SDK14/15? If so, what they need to do is to follow our DFU migration node in Infocenter, right? Any else need to take care?

Thanks!

Leon

  • 0

    Sorry for the late reply.

    Examples marked as experimental does not have a full testing procedure designed to uncover all flaws we can imagine, so there may be unknown bugs. We generally do not recommend using experimental examples as stable code in end-user products without testing the implementation very well yourself. For a proof of concept or for use in early development experimental examples are well suited.

    In the end it's the customers choice if you want to use the experimental version in SDK 13 or migrate to SDK 14. I recommend migrating to SDK14, and this is not too hard to do if you follow the migration guide here. You may want to consider moving directly to SDK14.2.0 since it's API compatible, but has some minor bugfixes which may be nice to have.

    Best regards,
    Rune Holmgren

Related
Terms of service