• State Not Answered
  • Replies 11 replies
  • Subscribers 62 subscribers
  • Views 2228 views
  • Users 0 members are here
Attachments (3) Download All
Nordic Case Info
  • Case ID: 252915
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF Connect SDK 1.3.0 multi-image build stuck

rerickson

I am switching from standard Zephyr and I am trying out nRF connect SDK v1.3.0. When I am building my app for mcuboot, it hangs after configuring the child image (mcuboot).  If I build mcuboot or the app by itself it works just fine.  It seems like something is hanging in the partition_manager script.  I see a python process spinning in Activity Monitor forever, when I kill it, then the build process fails out.  See my output here:


Any ideas on how to solve this?

Parents
  • 0

    When is Simon back from vacation?  In short, am having the same issue, but the conflict is between NVS and something else (not sure what).

    In the meantime, how does one "define a static nvs_storage partition", ideally without manually setting up and entire pm_static.yml?

  • 0 in reply to psychogenic

    Hi .

     

    psychogenic said:
    When is Simon back from vacation? 

     Simon will be back next week.

     

    psychogenic said:
    In the meantime, how does one "define a static nvs_storage partition", ideally without manually setting up and entire pm_static.yml?

     What I did to create the pm_static I posted earlier was to build the application without either NVS or littlefs. I then looked at the generated pm.yml files in the build folders and used those to create the pm_static.yml file. What it ended up with, was me copying the lifflefs_storage partition into the pm.yml file created with only NVS, then adjusting the size and starting positions of the other partitions. As the size of the littlefs_storage partition was 0x6000, I shrank the two mcuboot partitions with 0x3000, then I worked from the beginning of the flash (0x0) to find new start addresses.

     

    psychogenic said:
    In short, am having the same issue, but the conflict is between NVS and something else (not sure what).

     Could you share your prj.conf (or <your build folder>/zephyr/.config file? That should show what else you have included.

    Are you able to build without NVS? How does the pm.yml file look then?

    Best regards,

    Didrik

Reply
  • 0 in reply to psychogenic

    Hi .

     

    psychogenic said:
    When is Simon back from vacation? 

     Simon will be back next week.

     

    psychogenic said:
    In the meantime, how does one "define a static nvs_storage partition", ideally without manually setting up and entire pm_static.yml?

     What I did to create the pm_static I posted earlier was to build the application without either NVS or littlefs. I then looked at the generated pm.yml files in the build folders and used those to create the pm_static.yml file. What it ended up with, was me copying the lifflefs_storage partition into the pm.yml file created with only NVS, then adjusting the size and starting positions of the other partitions. As the size of the littlefs_storage partition was 0x6000, I shrank the two mcuboot partitions with 0x3000, then I worked from the beginning of the flash (0x0) to find new start addresses.

     

    psychogenic said:
    In short, am having the same issue, but the conflict is between NVS and something else (not sure what).

     Could you share your prj.conf (or <your build folder>/zephyr/.config file? That should show what else you have included.

    Are you able to build without NVS? How does the pm.yml file look then?

    Best regards,

    Didrik

Children
No Data
Related