• State Verified Answer
  • Replies 11 replies
  • Subscribers 75 subscribers
  • Views 994 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 321824
Options

Firmware Upgrade known bug in MCUBOOT with nrf5340 and SDK 2.5.x

Riccardo Gaiati

Hi, 

according to the known issues list for the SDK release 2.5.x x=[0,1,2] and others previous ones, the bug NCSDK-21379 exists (see the link below)

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/releases_and_maturity/known_issues.html?v=v2-5-2#dfu-and-fota

A workaround is also described.

Questions:

  1. Would you be so kind to be more specific by explaining in details what needs to be done in order to have the single slot netcore update working ? I remember that there was a similar bug in version 1.9.1 and also in 2.1.1, which we solved by applying a patch (there were some tickets regarding this topic). Is the known issue for the 2.5.x related to that in somehow ?
  2. An appcore built with sdk 2.5.x can work with a netcore built with 2.1.1 ?

Thanks in advance for your kind  availability !

Regards

Riccardo Gaiati

Parents
  • 0

    Hello,


    Sorry for the delay

    An appcore built with sdk 2.5.x can work with a netcore built with 2.1.1 ?

    For BLE to work properly, the rpmsg version needs to be the same for both cores. Sometimes it goes well with different versions, but it's always recommended to upgrade the netcore too for proper communication between the cores.

    Would you be so kind to be more specific by explaining in details what needs to be done in order to have the single slot netcore update working ? I remember that there was a similar bug in version 1.9.1 and also in 2.1.1, which we solved by applying a patch (there were some tickets regarding this topic). Is the known issue for the 2.5.x related to that in somehow ?

    Are you trying the OTA DFU or only the serial recovery here? I am still having some confusion regarding the workaround mentioned here (that's why it's taking time from my side). I am discussing this with my colleagues. I will get back to you with a more concrete answer.

     

    Kind Regards,

    Abhijith

Reply
  • 0

    Hello,


    Sorry for the delay

    An appcore built with sdk 2.5.x can work with a netcore built with 2.1.1 ?

    For BLE to work properly, the rpmsg version needs to be the same for both cores. Sometimes it goes well with different versions, but it's always recommended to upgrade the netcore too for proper communication between the cores.

    Would you be so kind to be more specific by explaining in details what needs to be done in order to have the single slot netcore update working ? I remember that there was a similar bug in version 1.9.1 and also in 2.1.1, which we solved by applying a patch (there were some tickets regarding this topic). Is the known issue for the 2.5.x related to that in somehow ?

    Are you trying the OTA DFU or only the serial recovery here? I am still having some confusion regarding the workaround mentioned here (that's why it's taking time from my side). I am discussing this with my colleagues. I will get back to you with a more concrete answer.

     

    Kind Regards,

    Abhijith

Children
Related
Terms of service