[ https://issues.apache.org/jira/browse/MYNEWT-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christopher Collins updated MYNEWT-519: --------------------------------------- Description: Currently, to permanently run the alternate image, Mynewt requires the following sequence: 1. image test <slot-01-hash> 2. reboot 3. image confirm The new feature is to remove the need for the third step. The user should be able to permanently switch images with this sequence: 1. image confirm <slot-01-hash> 2. reboot This ticket only represents the img_mgmt and newtmgr changes. Required boot loader changes are captured in a separate ticket. was: Currently, to permanently run the alternate image, the boot loader requires the following sequence: 1. image test <slot-01-hash> 2. reboot 3. image confirm The new feature is to remove the need for the third step. The user should be able to permanently switch images with this sequence: 1. image confirm <slot-01-hash> 2. reboot This ticket only represents the boot loader changes. Required img_mgmt and newtmgr changes are captured in a separate ticket. Component/s: (was: Bootloader) Image Mgmt Summary: img_mgmt - Allow test+confirm as single action (was: imgmgmt - Allow test+confirm as single action) > img_mgmt - Allow test+confirm as single action > ---------------------------------------------- > > Key: MYNEWT-519 > URL: https://issues.apache.org/jira/browse/MYNEWT-519 > Project: Mynewt > Issue Type: New Feature > Components: Image Mgmt > Reporter: Christopher Collins > Assignee: Christopher Collins > Fix For: v1_0_0_rel > > > Currently, to permanently run the alternate image, Mynewt requires the > following sequence: > 1. image test <slot-01-hash> > 2. reboot > 3. image confirm > The new feature is to remove the need for the third step. The user should be > able to permanently switch images with this sequence: > 1. image confirm <slot-01-hash> > 2. reboot > This ticket only represents the img_mgmt and newtmgr changes. Required boot > loader changes are captured in a separate ticket. -- This message was sent by Atlassian JIRA (v6.3.4#6332)