Hello,
I am attempting use swupdate. I had a "uboot|roota|rootb|data" deployment working on an SD card, but then I ported it to do the same on the boards eMMC storage. Well not entirely the same because uboot is now in the special block device, mmcblk0boot0.
Now swupdate seems to choose the wrong partition when I chuck a swu at the mongoose server. If I am running, "stable,copy1" on /dev/mmcblk0p1, it seems to want to raw copy a new image over top of the running
mmcblk0p1 instead of the choosing /dev/mmcblk0p2. If I manually run "stable,copy2" on /dev/mmcblk0p2 and give mongoose a swu it seems to write over top of
/dev/mmcblk0p2.
What drives the selection of the destination partition when you upload a swu through mongoose? I assumed it would choose the non-active stable entry and use the images -> device path.
Any insights would be appreciated.
Thanks,
Nathan