• State Suggested Answer
  • Replies 16 replies
  • Answers 1 answer
  • Subscribers 68 subscribers
  • Views 2485 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 296206
Options

Bootloader from SDCard

warcomeb-am

Hi, 

I need to add to my project that uses NRF5340 a bootloader that reads new firmware from SDCard. Is there an example where I can find information? Someone has just encountered this kind of issue and can tell me some tips?

Thanks

Marco

  • 0 in reply to Vidar Berg

    Dear Vidar,

    Yesterday I implemented this solution but seems not work.
    The firmware copy the file into image_1 without any errors, but when the microcontroller reboots the firmware is not updated. The output is:

    *** Booting Zephyr OS build v3.1.99-ncs1-1  ***
I: Starting bootloader
I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Swap type: none
I: Bootloader chainload address offset: 0xc000
*** Booting Zephyr OS build v3.1.99-ncs1-1  ***
Hello from AM Microsystems!

    Do I need to add something to notify the new firmware to mcuboot? 

    Best

    Marco

  • 0 in reply to warcomeb-am

    Dear Marco,

    The magic word should be set to "good", not "unset", if the secondary image has been stored correctly. 

    As a test, can you try to program the 'app_moved_test_update.hex' with nrfjprog without going through the SD?

    $ nrfjprog --program build/zephyr/app_moved_test_update.hex --sectorerase --verify --reset

    Another thing is to check if the start address used to store the update candidate in flash matches the secondary address shown in the 'memory report'.

    Best,

    Vidar

  • 0 in reply to Vidar Berg

    Hi Vidar, 

    By using the nrfjprog the update works:

    *** Booting Zephyr OS build v3.1.99-ncs1-1  ***
I: Starting bootloader
I: Primary image: magic=good, swap_type=0x2, copy_done=0x1, image_ok=0x3
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Swap type: revert
I: Starting swap using move algorithm.
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Bootloader chainload address offset: 0xc000
*** Booting Zephyr OS build v3.1.99-ncs1-1  ***
Hello from AM Microsystems!

    I also checked the address and it is correct. Why doesn't work with SD? Maybe need I to enable some flag after copy the firmware?

    Best

    Marco 

  • 0 in reply to warcomeb-am

    Hi Marco,

    Can you read the memory content in the secondary slot after loading it from the sd card and after programming the .hex to see if there is any difference? 

    $ nrfjprog --memrd <secondary slot start address> --n <size of secondary slot in bytes > secondary_slot.txt

    Best,

    Vidar

  • 0 in reply to Vidar Berg

    Hi Vidar, 

    sorry, I need to fix my last answer: yes, I can send the new firmware by using your command into the second partition and mcuboot recognize it (the code of my last answer), but the firmware is not updated! Sob

    Anyway, I try to read the secondary partition and the two version differ only on the last 256Byte. But I don't know why!

    Best,

    Marco

Related