How to get MBR version during runtime?

RE: How to get MBR version during runtime?

Vidar Berg — Fri, 04 Mar 2016 10:26:19 GMT

No problem. Yes, I'm quite confident that the MBR will stay compatible. It would be very undesirable for us to break compatibility unless we are forced to do so. Don't think that's likely considering the maturity of the MBR. There has only been minor changes since the initial MBR version included in s110 v.7.0.0.

RE: How to get MBR version during runtime?

endnode — Fri, 04 Mar 2016 10:08:14 GMT

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

RE: How to get MBR version during runtime?

Vidar Berg — Fri, 04 Mar 2016 10:01:47 GMT

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.