[
https://issues.apache.org/jira/browse/MYNEWT-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16048184#comment-16048184
]
ASF subversion and git services commented on MYNEWT-752:
--------------------------------------------------------
Commit d17c1dd6c152ee4907b077dbe7ece3210ccad667 in incubator-mynewt-core's
branch refs/heads/master from [~ccollins476]
[ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=d17c1dd ]
MYNEWT-752 Allow confirm of tentative slot.
> Error in setting the "permanent" flag upon confirm with hash during image
> upgrade
> ---------------------------------------------------------------------------------
>
> Key: MYNEWT-752
> URL: https://issues.apache.org/jira/browse/MYNEWT-752
> Project: Mynewt
> Issue Type: Bug
> Security Level: Public(Viewable by anyone)
> Reporter: Aditi Hilbert
> Assignee: Christopher Collins
> Fix For: v1_1_0_rel
>
>
> This is an issue seen during image upgrade. When doing a "confirm" with a
> hash, newtmgr always marks the "permanent" flag for Slot 1 image to "true",
> irrespective of which image the hash matches.
> This works fine when we skip the "test" step during image upgrade and we
> issue a "confirm" with a hash of the new image in Slot 1.
> However, if we do the "test" step (when the new image is swapped into Slot
> 0), and we then do a "confirm" with a hash of the new image and reboot, the
> device marks the old image in Slot 1 as "permanent" and swaps it back to Slot
> 0.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
