• State Verified Answer
  • Locked Locked
  • Replies 3 replies
  • Subscribers 71 subscribers
  • Views 2221 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 112320
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How to get MBR version during runtime?

endnode

Hi guys,

As there are several minor and major versions of MBR in the wild I guess there could be useful function to get current MBR version during runtime. I haven't found anything in the API neither here on the forum. Is there at least some way (e.g. identification string at some fixed flash address) how to get this? I assume that you don't recommend to switch SD versions during DFU procedure (e.g. S110 => S130 or S130 V1 => S130 V2) but could it work at least in some cases? Or are you planning to fix MBR with S13x V2 for good without possibility of even minor fixes in it (and thus changing MBR version)?

Thanks for help Jan

Parents
  • 0

    Hi,

    There is not a documented way of reading the version name as far as I can see. However, the MBR is not updated when you do DFU, so the version number won't change after the device has been programmed during production.

    Note that the functional behavior of the MBR has stayed the same despite the minor version bump as mentioned in the comments here. In other words, you can update from S110 to s130 v.1.0.0 or s130 v.2.0.0. through bootloader DFU.

    Note that on 52 (s132) there was a major update to reduce the memory usage by 4KB (due to 4K flash page size), but requires and additional page to be allocated when DFU of bootloader is to be supported. More details can be found in the release notes for s132_nrf52_2.0.0-7.alpha.

  • 0 in reply to Vidar Berg

    Hi Vidar,

    Thanks for the answer! The fact that you can upgrade SD and APP on top of MBR was reson of my question: once you are running on the board you cannot assume from SD version what MBR version is there because simply you don't know what DFU path it went from original moment of MBR loading in production;) However if you are confident that on nRF51 all released SoftDevices and MBRs should be compatible then it eliminates necessity of tracking their versions. And if this keeps the same on nRF52 then again problem solved;)

    Cheers Jan

Reply
  • 0 in reply to Vidar Berg

    Hi Vidar,

    Thanks for the answer! The fact that you can upgrade SD and APP on top of MBR was reson of my question: once you are running on the board you cannot assume from SD version what MBR version is there because simply you don't know what DFU path it went from original moment of MBR loading in production;) However if you are confident that on nRF51 all released SoftDevices and MBRs should be compatible then it eliminates necessity of tracking their versions. And if this keeps the same on nRF52 then again problem solved;)

    Cheers Jan

Children
No Data
Related
Terms of service