• State Not Answered
  • Replies 8 replies
  • Subscribers 91 subscribers
  • Views 540 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 360440
Options

Clarification on migrating from Partition Manager to Devicetree

Ken58

Hi,

I have a couple of questions on migrating from Partition Manager to Devicetree since a particular example was not provided.  Following the procedure in the SDK v3.3.0 release notes, an nrf52840dongle_nrf52840.overlay was created by pm_to_dts.py as shown here:

It is considerably different from the ..\v3.3.0\zephyr\boards\nordic\nrf52840dongle\nrf52840dongle_nrf52840.dts shown here:

Questions:

What would you recommend I do for the migration?

Will the default nrf52840dongle_nrf52840.dts in future versions of the SDK be modified for this partitioning?

How and where should I set CONFIG_PARTITION_MANAGER_ENABLED=n ?  I thought .config.sysbuild is generated by the SDK and should not be directly modified.

Thank you,

Ken

Parents
  • 0

    Hi Kenneth

    If your project is running on the nRF52840 Dongle, I'd recommend you use the default board/.dts file from the SDK version you're using after a merge. The python script doesn't seem to have made separate partitions for the MBR, Bootloader, and slot partitions.

    The built in USB bootloader is indeed not part of MCUBoot, please see the Dongle documentation for more information on that.

    We will also be getting back to you on the questions Maria is looking into.

    For your last question, there are no planse to change the Dongle DTS files further AFAIK. Do you see any reason they should be changed?

    Best regards,

    Simon

  • 0 in reply to Simonr

    Hi Simonr,

    Thanks for getting back to me.  It's summer and many people are on holiday.  The remaining questions I have regarding the default nrf52840dongle_nrf52840.dts:

    1. Why not list the partitions used for the MBR, USB bootloader, and last and second to last flash pages like the other partitions listed rather than only making this visible in the comments?  I think they can be specified as read only if needed.
    2. There are 2 pages of flash not accounted for in that file, specifically bytes at address 0x000FC000 through 0x000FDFFF.  Should this be corrected in the file?

    Also, I have not been able to build my application successfully with the Partition Manager disabled within nRF Connect for VS Code.  So, taking the Nordic blinky example, which still uses the Partition Manager in V3.3.0, how would I disable it and successfully build?

    Thank you,

    Ken

Reply
  • 0 in reply to Simonr

    Hi Simonr,

    Thanks for getting back to me.  It's summer and many people are on holiday.  The remaining questions I have regarding the default nrf52840dongle_nrf52840.dts:

    1. Why not list the partitions used for the MBR, USB bootloader, and last and second to last flash pages like the other partitions listed rather than only making this visible in the comments?  I think they can be specified as read only if needed.
    2. There are 2 pages of flash not accounted for in that file, specifically bytes at address 0x000FC000 through 0x000FDFFF.  Should this be corrected in the file?

    Also, I have not been able to build my application successfully with the Partition Manager disabled within nRF Connect for VS Code.  So, taking the Nordic blinky example, which still uses the Partition Manager in V3.3.0, how would I disable it and successfully build?

    Thank you,

    Ken

Children
Related
Terms of service