• State Verified Answer
  • Replies 2 replies
  • Subscribers 65 subscribers
  • Views 81 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 329742
Options

Does the MCUMGR have a foolproof feature?

Yoshihiro Goto

I am learning how to use MCUMGR. I generally understand it, but I have some concerns.

- The firmware with the private key can also be overwritten. Then it will not boot.
(By the way, we call this a paperweight.)

- It is possible to write even if the model (e.g. nRF52832 and nRF52840) is different. Of course, it will not boot.

Is there any way to avoid these foolproofs?

In addition, it is not foolproof,

- I don't know how to write to slot 1. Adding -n1 options doesn't work.

Best Regards,
Yoshihiro Goto

Parents
  • 0

    Hi, 

    The bootloader will skip the invalid image and boot the valid image in the other slot if using the dual-slot configuration. If using the recovery mode with the single-slot configuration, you could upload the correct image again. 

    - I don't know how to write to slot 1. Adding -n1 options doesn't work.

    Which sample are you using? Are you using external flash? Could you post the command you are using? 

    The doc said:

    The mcumgr image upload command may be provided optional -e -n <image> parameter that will select target image for upload; when parameter is no provided, 0 is assumed, which means “default behaviour”, and it performs upload to the “image-1”, the MCUboot secondary slot.

    Try to upload without -e -n <image> parameter to see if it can work or not. 

    Regards,
    Amanda H.

Reply
  • 0

    Hi, 

    The bootloader will skip the invalid image and boot the valid image in the other slot if using the dual-slot configuration. If using the recovery mode with the single-slot configuration, you could upload the correct image again. 

    - I don't know how to write to slot 1. Adding -n1 options doesn't work.

    Which sample are you using? Are you using external flash? Could you post the command you are using? 

    The doc said:

    The mcumgr image upload command may be provided optional -e -n <image> parameter that will select target image for upload; when parameter is no provided, 0 is assumed, which means “default behaviour”, and it performs upload to the “image-1”, the MCUboot secondary slot.

    Try to upload without -e -n <image> parameter to see if it can work or not. 

    Regards,
    Amanda H.

Children
Related