• State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 73 subscribers
  • Views 1472 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 118142
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

Secure Bootloader SDK V12 and SD310

AD1170

Hello,

can the secure bootloader from SDK12 be used with the SD310? And if yes, what must be take care about?

THX

  • 0

    Hi AD1170,

    I am assuming that you're using a nRF51422 with 256kB Flash and 32kB RAM. The S310 v3.0.0 is not compatible with our SDK v12.x.0 and I am not sure when Dynastream will release the next version, but it should be possible to compile the Secure Bootloader against the v3.0.0 headers.

    You will only be able to perform application updates due to the limited flash size. It is not possible to perform SoftDevice + Bootloader updates since the bootloader requires 24kB, the Softdevice 112kB and the MBR 4kB, a total of 140kB. This leaves only 120kB that can be used for the application, which is also the same area that is used to store the combined S310 + BL image before the switch is performed.

    Best regards

    Bjørn

  • 0 in reply to bjorn-spockeli

    Hi Bjørn,

    thank you. Yes your are right with your assumtion. Currently i use the modified SD130 single bank bootloader with SD310. This works so far for application and bootloader update (since the application size is below 100KB). The application must send again after BL update. But this is ok. I have tried to compile the V12 secure BL against the V3.0.1 headers. But this is currently not feasible for me, because i can not spend so much time with this. I look for a way to prevent the upload of illegal or modified firmware or bootloader code.

    Best Regards,

    Bernd

  • 0 in reply to bjorn-spockeli

    Compiling the Secure Bootloader from SDK v12.x.0 against the S310 v3.01 headers is what I reckon is the easiest solution. Otherwise you will have to backport the nrf_crypto library( its used to create signatures and hashes) to your SDK version and implement your own signature check.

  • 0 in reply to bjorn-spockeli

    Is there a short desription wich files must be taken from SDK12 and wich from SDK 9 or SD310? I have tried this but there many compilation errors du to incompatibility of the headers.

  • 0 in reply to bjorn-spockeli

    @AD1170 : I closed this question as it has been moved to Mypage.

Related
Terms of service