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

[Vidar Berg]

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.

[Vidar Berg]

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.