You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mynewt.apache.org by then yon <yz...@free2move.se> on 2017/02/22 06:11:36 UTC
image upload error 2
Dear Support,
I'm followed the tutorial below:
https://mynewt.apache.org/latest/os/modules/split/split/
But i'm stuck at image upload step; it gave me the following error:
$ newtmgr -c mynewt_serial image list Images: slot=0 version: 1.0.0
<http://1.0.0.0/>bootable: true flags: active confirmed hash:
493c5e78e76a9c1b9e574ab38b7bbf0d342d928ffd0111400dbe8c2c952da68e slot=1
version: 1.0.0 <http://1.0.0.0/>bootable: false flags: active confirmed
hash: 4d26a0d1596e12dab9059df3a13b4ffd54f96836cd9080d579c6afc167d58e81
Split status: matching $ newtmgr -c mynewt_serial image upload s
plitty.img <http://plitty.img/>Error: Target error: 2
Please help.
Thank you.
Regards,
Then Yoong Ze
Re: image upload error 2
Posted by then yon <yz...@free2move.se>.
Dear Chris,
If not mistaken the app will be my project firmware.
And what i doing is a firmware upgrade method?
Cause in the previous support, they said this tutorial is the best
starter for firmware upgrade.
Please let me know if i made a terrible mistake here.
Regards,
Then Yoong Ze
On 24/2/2017 9:57 AM, Christopher Collins wrote:
> On Fri, Feb 24, 2017 at 09:39:37AM +0800, then yon wrote:
>> Dear Chris,
>>
>> i've double enter on each line but it still mix up into 1 line, most
>> probably is my email sw problem.
>>
>> Below is all the step i did:
>>
>> 1. By using slinky app(no changes); build a split_slinky target.
> Stop right there :). What are you using for a loader and what are you
> using for an app?
>
> Chris
> .
>
Re: image upload error 2
Posted by Christopher Collins <ch...@runtime.io>.
On Fri, Feb 24, 2017 at 09:39:37AM +0800, then yon wrote:
> Dear Chris,
>
> i've double enter on each line but it still mix up into 1 line, most
> probably is my email sw problem.
>
> Below is all the step i did:
>
> 1. By using slinky app(no changes); build a split_slinky target.
Stop right there :). What are you using for a loader and what are you
using for an app?
Chris
Re: image upload error 2
Posted by then yon <yz...@free2move.se>.
Dear Chris,
i've double enter on each line but it still mix up into 1 line, most
probably is my email sw problem.
Below is all the step i did:
1. By using slinky app(no changes); build a split_slinky target.
2. "newt load split_slinky".
3. newtmgr -c mynewt_serial image list. (slot 1 flags: empty, able to do
image upload here)
4. Enabling the app by, "newtmgr -c mynewt_serial image test". (slot 1
flags: pending)
5. "newtmgr -c mynewt_serial image reset". (Here is where is need to
reset the power, only the first time)
6. After power reset (slot 1 flags: active); sent "newtmgr -c
mynewt_serial iamge confirm" (slot 1 flags: active confirmed; now the
LED start blinking)
7. Now try to do image upgrade; "newtmgr -c mynewt_serial image test",
here i get "Error: rc =6"
Thank you.
Regards,
Then Yoong Ze
The empty flag for slot 1 is only happen after i load the image using "newt load split_slinky".
Then from the tutorial the next step is enabling a split application, here is where the test command came in. (slot 1 flags: active confirmed)
So after the app is running; now i wanted to do image upgrade.
So i sent test command in step 1. (slot 1 flags: active pending; and after many many tried it gave me Error: rc=6)
Thank you.
Regards,
Then Yoong Ze
On 24/2/2017 12:56 AM, Christopher Collins wrote:
> On Thu, Feb 23, 2017 at 06:05:44PM +0800, then yon wrote:
>> Dear Chris,
>>
>> Yes, i've followed the step you given; but after step 2 it gave me
>> "Error: Timeout reading from serial connection".
>>
>> It only recover after i reset nrf52dk power and it show the result i
>> sent to you previously.
>>
>> And when i tried to do step 1 again, it gave me "Error: rc=6"
> Is there anything you can do to preserve the newtmgr output in your
> emails? For some reason, the entire newtmgr response gets joined into a
> single line, making it difficult to read. I have reformatted the
> responses below.
>
> $ newtmgr -c mynewt_serial image list
> Images:
> slot=0
> version: 1.0.0
> bootable: true
> flags: active confirmed
> hash: 6d1b9bb73f9cf223145a28e4e0d7702a1b2aaf60a7a6d66497e02a841cd72c8c
> slot=1
> version: 1.0.0
> bootable: false
> flags:
> hash: 0fd6f020a3ff70d4cd150e6233185c6e9b8b93f60af97fb67bc728daa6573f0b
> Split status: matching
>
> The empty flags field in slot 1 indicates that the device is in
> loader-only mode (i.e., only slot 0 is running). It appears you have
> completed step 3. With slot 1 unused, you can overwrite it with a new
> app.
>
> $ newtmgr -c mynewt_serial image test 0fd6f020a3ff70d4cd150e6233185c6e9b8b93f60af97fb67bc728daa6573f0b
> Images:
> slot=0
> version: 1.0.0
> bootable: true
> flags: active confirmed
> hash: 6d1b9bb73f9cf223145a28e4e0d7702a1b2aaf60a7a6d66497e02a841cd72c8c
> slot=1
> version: 1.0.0
> bootable: false
> flags: pending
> hash: 0fd6f020a3ff70d4cd150e6233185c6e9b8b93f60af97fb67bc728daa6573f0b
> Split status: matching
>
> The "test" command does not come until step 5. What about step 4,
> uploading the new loader? By testing the original app image, you will
> just put the device back into its original state.
>
> $ newtmgr -c mynewt_serial reset
> Done
>
> $ newtmgr -c mynewt_serial image list ^C (cause it hang here indefinitely so i cancel it)
>
> It seems like your app (slot 1) doesn't support newtmgr or lacks a
> newtmgr transport.
>
> $ newtmgr -c mynewt_serial image upload splitty.img
> Error: Timeout reading from serial connection
> [...]
>
> Which procedure are you following? In the split upgrade procedure (the
> one I pasted in my previous email), you only upload after issuing the
> "image confirm" command.
>
> Can you please do the following:
>
> 1. Tell me something about the target you are upgrading. What loader
> and app combo are you using? From the above, it appears your app may
> not support newtmgr.
>
> 2. Start from step 1 in the procedure I quoted, please indicate which
> step you are currently on, and don't skip any steps :).
>
> Thanks,
> Chris
>
>> $ newtmgr -c mynewt_serial image list Images: slot=0 version: 1.0.0
>> <http://1.0.0.0/> bootable: true flags: active confirmed hash:
>> 6d1b9bb73f9cf223145a28e4e0d7702a1b2aaf60a7a6d66497e02a841cd72c8c slot=1
>> version: 1.0.0 <http://1.0.0.0/> bootable: false flags: hash:
>> 0fd6f020a3ff70d4cd150e6233185c6e9b8b93f60af97fb67bc728daa6573f0b Split
>> status: matching $ newtmgr -c mynewt_serial image test 0fd
>> 6f020a3ff70d4cd150e6233185c6e9b8b93f60af97fb67bc728daa6573f0b Images:
>> slot=0 version: 1.0.0 <http://1.0.0.0/> bootable: true flags: active
>> confirmed hash:
>> 6d1b9bb73f9cf223145a28e4e0d7702a1b2aaf60a7a6d66497e02a841cd72c8c slot=1
>> version: 1.0.0 <http://1.0.0.0/> bootable: false flags: pending
>> hash: 0fd6f020a3ff70d4cd150e6233185c6e9b8b93f60af97fb67bc728daa6573f0b
>> Split status: matching $ newtmgr -c mynewt_serial reset Done $
>> newtmgr -c mynewt_serial image list ^C (cause it hang here indefinitely
>> so i cancel it) $ newtmgr -c mynewt_serial image upload splitty.img
>> <http://plitty.img/>Error: Timeout reading from serial connection
>> upload - Upload image to target Usage: newtmgr image upload [flags]
>> Examples: newtmgr -c olimex image upload <image_file newtmgr -c
>> olimex image upload bin/slinky_zero/apps/slinky.img
>> <http://slinky.img/> Global Flags: -c, --conn string connection profile
>> to use. -l, --loglevel string log level to use (default INFO.)
>> <http://info.%29/>(default "info") -t, --trace print all bytes
>> transmitted and received
>>
>>
>> Thank you.
>>
>> Regards,
>>
>> Then Yoong Ze
>>
>>
>> On 23/2/2017 12:44 AM, Christopher Collins wrote:
>>> Hi Then,
>>>
>>> On Wed, Feb 22, 2017 at 02:11:36PM +0800, then yon wrote:
>>>> Dear Support,
>>>>
>>>> I'm followed the tutorial below:
>>>> https://mynewt.apache.org/latest/os/modules/split/split/
>>>>
>>>> But i'm stuck at image upload step; it gave me the following error:
>>> [...]
>>>> Error: Target error: 2
>>> Error 2 indicates that there is no free slot for the new image. In your
>>> email, the "image list" output is a bit touch to read because it got
>>> collapsed into a single line. Here is my attempt to unravel it:
>>>
>>>> $ newtmgr -c mynewt_serial image list
>>>> Images:
>>>> slot=0
>>>> version: 1.0.0
>>>> bootable: true
>>>> flags: active confirmed
>>>> hash: 493c5e78e76a9c1b9e574ab38b7bbf0d342d928ffd0111400dbe8c2c952da68e
>>>>
>>>> slot=1
>>>> version: 1.0.0
>>>> bootable: false
>>>> flags: active confirmed
>>>> hash: 4d26a0d1596e12dab9059df3a13b4ffd54f96836cd9080d579c6afc167d58e81
>>>>
>>>> Split status: matching
>>> Notice that both slots have the "active" and "confirmed" flags set.
>>> This indicates that both slots are currently running. You need to run
>>> the image in loader-only mode in order to replace the app in slot 1.
>>> This is described in the "Image Upgrade - Split" section of the page you
>>> linked to (https://mynewt.apache.org/latest/os/modules/split/split/).
>>> Specifically:
>>>
>>>
>>> 1. Disable split functionality; we need to deactivate the application
>>> image in slot 1 (newtmgr image test <current-loader-hash>).
>>> 2. Reboot device (newtmgr reset).
>>> 3. Make above change permanent (newtmgr image confirm).
>>> 4. Upload new loader to slot 1 (newtmgr image upload <filename>).
>>> 5. Tell device to "test out" the new loader on next boot (newtmgr image
>>> test <new-loader-hash>).
>>> 6. Reboot device (newtmgr reset).
>>> 7. Make above change of loader permanent (newtmgr image confirm).
>>> 8. Upload new application to slot 1 (newtmgr image upload <filename>).
>>> 9. Tell device to "test out" the new application on next boot (newtmgr
>>> image test <new-application-hash>).
>>> 10. Reboot device (newtmgr reset).
>>> 11. Make above change of application permanent (newtmgr image confirm).
>>>
>>> Steps 1 and 2 will leave the device in a state such that the app in slot
>>> 1 can be replaced.
>>>
>>> Chris
>>> .
>>>
> .
>
Re: image upload error 2
Posted by Christopher Collins <ch...@runtime.io>.
On Thu, Feb 23, 2017 at 06:05:44PM +0800, then yon wrote:
> Dear Chris,
>
> Yes, i've followed the step you given; but after step 2 it gave me
> "Error: Timeout reading from serial connection".
>
> It only recover after i reset nrf52dk power and it show the result i
> sent to you previously.
>
> And when i tried to do step 1 again, it gave me "Error: rc=6"
Is there anything you can do to preserve the newtmgr output in your
emails? For some reason, the entire newtmgr response gets joined into a
single line, making it difficult to read. I have reformatted the
responses below.
$ newtmgr -c mynewt_serial image list
Images:
slot=0
version: 1.0.0
bootable: true
flags: active confirmed
hash: 6d1b9bb73f9cf223145a28e4e0d7702a1b2aaf60a7a6d66497e02a841cd72c8c
slot=1
version: 1.0.0
bootable: false
flags:
hash: 0fd6f020a3ff70d4cd150e6233185c6e9b8b93f60af97fb67bc728daa6573f0b
Split status: matching
The empty flags field in slot 1 indicates that the device is in
loader-only mode (i.e., only slot 0 is running). It appears you have
completed step 3. With slot 1 unused, you can overwrite it with a new
app.
$ newtmgr -c mynewt_serial image test 0fd6f020a3ff70d4cd150e6233185c6e9b8b93f60af97fb67bc728daa6573f0b
Images:
slot=0
version: 1.0.0
bootable: true
flags: active confirmed
hash: 6d1b9bb73f9cf223145a28e4e0d7702a1b2aaf60a7a6d66497e02a841cd72c8c
slot=1
version: 1.0.0
bootable: false
flags: pending
hash: 0fd6f020a3ff70d4cd150e6233185c6e9b8b93f60af97fb67bc728daa6573f0b
Split status: matching
The "test" command does not come until step 5. What about step 4,
uploading the new loader? By testing the original app image, you will
just put the device back into its original state.
$ newtmgr -c mynewt_serial reset
Done
$ newtmgr -c mynewt_serial image list ^C (cause it hang here indefinitely so i cancel it)
It seems like your app (slot 1) doesn't support newtmgr or lacks a
newtmgr transport.
$ newtmgr -c mynewt_serial image upload splitty.img
Error: Timeout reading from serial connection
[...]
Which procedure are you following? In the split upgrade procedure (the
one I pasted in my previous email), you only upload after issuing the
"image confirm" command.
Can you please do the following:
1. Tell me something about the target you are upgrading. What loader
and app combo are you using? From the above, it appears your app may
not support newtmgr.
2. Start from step 1 in the procedure I quoted, please indicate which
step you are currently on, and don't skip any steps :).
Thanks,
Chris
>
> $ newtmgr -c mynewt_serial image list Images: slot=0 version: 1.0.0
> <http://1.0.0.0/> bootable: true flags: active confirmed hash:
> 6d1b9bb73f9cf223145a28e4e0d7702a1b2aaf60a7a6d66497e02a841cd72c8c slot=1
> version: 1.0.0 <http://1.0.0.0/> bootable: false flags: hash:
> 0fd6f020a3ff70d4cd150e6233185c6e9b8b93f60af97fb67bc728daa6573f0b Split
> status: matching $ newtmgr -c mynewt_serial image test 0fd
> 6f020a3ff70d4cd150e6233185c6e9b8b93f60af97fb67bc728daa6573f0b Images:
> slot=0 version: 1.0.0 <http://1.0.0.0/> bootable: true flags: active
> confirmed hash:
> 6d1b9bb73f9cf223145a28e4e0d7702a1b2aaf60a7a6d66497e02a841cd72c8c slot=1
> version: 1.0.0 <http://1.0.0.0/> bootable: false flags: pending
> hash: 0fd6f020a3ff70d4cd150e6233185c6e9b8b93f60af97fb67bc728daa6573f0b
> Split status: matching $ newtmgr -c mynewt_serial reset Done $
> newtmgr -c mynewt_serial image list ^C (cause it hang here indefinitely
> so i cancel it) $ newtmgr -c mynewt_serial image upload splitty.img
> <http://plitty.img/>Error: Timeout reading from serial connection
> upload - Upload image to target Usage: newtmgr image upload [flags]
> Examples: newtmgr -c olimex image upload <image_file newtmgr -c
> olimex image upload bin/slinky_zero/apps/slinky.img
> <http://slinky.img/> Global Flags: -c, --conn string connection profile
> to use. -l, --loglevel string log level to use (default INFO.)
> <http://info.%29/>(default "info") -t, --trace print all bytes
> transmitted and received
>
>
> Thank you.
>
> Regards,
>
> Then Yoong Ze
>
>
> On 23/2/2017 12:44 AM, Christopher Collins wrote:
> > Hi Then,
> >
> > On Wed, Feb 22, 2017 at 02:11:36PM +0800, then yon wrote:
> >> Dear Support,
> >>
> >> I'm followed the tutorial below:
> >> https://mynewt.apache.org/latest/os/modules/split/split/
> >>
> >> But i'm stuck at image upload step; it gave me the following error:
> > [...]
> >> Error: Target error: 2
> > Error 2 indicates that there is no free slot for the new image. In your
> > email, the "image list" output is a bit touch to read because it got
> > collapsed into a single line. Here is my attempt to unravel it:
> >
> >> $ newtmgr -c mynewt_serial image list
> >> Images:
> >> slot=0
> >> version: 1.0.0
> >> bootable: true
> >> flags: active confirmed
> >> hash: 493c5e78e76a9c1b9e574ab38b7bbf0d342d928ffd0111400dbe8c2c952da68e
> >>
> >> slot=1
> >> version: 1.0.0
> >> bootable: false
> >> flags: active confirmed
> >> hash: 4d26a0d1596e12dab9059df3a13b4ffd54f96836cd9080d579c6afc167d58e81
> >>
> >> Split status: matching
> > Notice that both slots have the "active" and "confirmed" flags set.
> > This indicates that both slots are currently running. You need to run
> > the image in loader-only mode in order to replace the app in slot 1.
> > This is described in the "Image Upgrade - Split" section of the page you
> > linked to (https://mynewt.apache.org/latest/os/modules/split/split/).
> > Specifically:
> >
> >
> > 1. Disable split functionality; we need to deactivate the application
> > image in slot 1 (newtmgr image test <current-loader-hash>).
> > 2. Reboot device (newtmgr reset).
> > 3. Make above change permanent (newtmgr image confirm).
> > 4. Upload new loader to slot 1 (newtmgr image upload <filename>).
> > 5. Tell device to "test out" the new loader on next boot (newtmgr image
> > test <new-loader-hash>).
> > 6. Reboot device (newtmgr reset).
> > 7. Make above change of loader permanent (newtmgr image confirm).
> > 8. Upload new application to slot 1 (newtmgr image upload <filename>).
> > 9. Tell device to "test out" the new application on next boot (newtmgr
> > image test <new-application-hash>).
> > 10. Reboot device (newtmgr reset).
> > 11. Make above change of application permanent (newtmgr image confirm).
> >
> > Steps 1 and 2 will leave the device in a state such that the app in slot
> > 1 can be replaced.
> >
> > Chris
> > .
> >
>
Re: image upload error 2
Posted by then yon <yz...@free2move.se>.
Dear Chris,
Yes, i've followed the step you given; but after step 2 it gave me
"Error: Timeout reading from serial connection".
It only recover after i reset nrf52dk power and it show the result i
sent to you previously.
And when i tried to do step 1 again, it gave me "Error: rc=6"
$ newtmgr -c mynewt_serial image list Images: slot=0 version: 1.0.0
<http://1.0.0.0/> bootable: true flags: active confirmed hash:
6d1b9bb73f9cf223145a28e4e0d7702a1b2aaf60a7a6d66497e02a841cd72c8c slot=1
version: 1.0.0 <http://1.0.0.0/> bootable: false flags: hash:
0fd6f020a3ff70d4cd150e6233185c6e9b8b93f60af97fb67bc728daa6573f0b Split
status: matching $ newtmgr -c mynewt_serial image test 0fd
6f020a3ff70d4cd150e6233185c6e9b8b93f60af97fb67bc728daa6573f0b Images:
slot=0 version: 1.0.0 <http://1.0.0.0/> bootable: true flags: active
confirmed hash:
6d1b9bb73f9cf223145a28e4e0d7702a1b2aaf60a7a6d66497e02a841cd72c8c slot=1
version: 1.0.0 <http://1.0.0.0/> bootable: false flags: pending
hash: 0fd6f020a3ff70d4cd150e6233185c6e9b8b93f60af97fb67bc728daa6573f0b
Split status: matching $ newtmgr -c mynewt_serial reset Done $
newtmgr -c mynewt_serial image list ^C (cause it hang here indefinitely
so i cancel it) $ newtmgr -c mynewt_serial image upload splitty.img
<http://plitty.img/>Error: Timeout reading from serial connection
upload - Upload image to target Usage: newtmgr image upload [flags]
Examples: newtmgr -c olimex image upload <image_file newtmgr -c
olimex image upload bin/slinky_zero/apps/slinky.img
<http://slinky.img/> Global Flags: -c, --conn string connection profile
to use. -l, --loglevel string log level to use (default INFO.)
<http://info.%29/>(default "info") -t, --trace print all bytes
transmitted and received
Thank you.
Regards,
Then Yoong Ze
On 23/2/2017 12:44 AM, Christopher Collins wrote:
> Hi Then,
>
> On Wed, Feb 22, 2017 at 02:11:36PM +0800, then yon wrote:
>> Dear Support,
>>
>> I'm followed the tutorial below:
>> https://mynewt.apache.org/latest/os/modules/split/split/
>>
>> But i'm stuck at image upload step; it gave me the following error:
> [...]
>> Error: Target error: 2
> Error 2 indicates that there is no free slot for the new image. In your
> email, the "image list" output is a bit touch to read because it got
> collapsed into a single line. Here is my attempt to unravel it:
>
>> $ newtmgr -c mynewt_serial image list
>> Images:
>> slot=0
>> version: 1.0.0
>> bootable: true
>> flags: active confirmed
>> hash: 493c5e78e76a9c1b9e574ab38b7bbf0d342d928ffd0111400dbe8c2c952da68e
>>
>> slot=1
>> version: 1.0.0
>> bootable: false
>> flags: active confirmed
>> hash: 4d26a0d1596e12dab9059df3a13b4ffd54f96836cd9080d579c6afc167d58e81
>>
>> Split status: matching
> Notice that both slots have the "active" and "confirmed" flags set.
> This indicates that both slots are currently running. You need to run
> the image in loader-only mode in order to replace the app in slot 1.
> This is described in the "Image Upgrade - Split" section of the page you
> linked to (https://mynewt.apache.org/latest/os/modules/split/split/).
> Specifically:
>
>
> 1. Disable split functionality; we need to deactivate the application
> image in slot 1 (newtmgr image test <current-loader-hash>).
> 2. Reboot device (newtmgr reset).
> 3. Make above change permanent (newtmgr image confirm).
> 4. Upload new loader to slot 1 (newtmgr image upload <filename>).
> 5. Tell device to "test out" the new loader on next boot (newtmgr image
> test <new-loader-hash>).
> 6. Reboot device (newtmgr reset).
> 7. Make above change of loader permanent (newtmgr image confirm).
> 8. Upload new application to slot 1 (newtmgr image upload <filename>).
> 9. Tell device to "test out" the new application on next boot (newtmgr
> image test <new-application-hash>).
> 10. Reboot device (newtmgr reset).
> 11. Make above change of application permanent (newtmgr image confirm).
>
> Steps 1 and 2 will leave the device in a state such that the app in slot
> 1 can be replaced.
>
> Chris
> .
>
Re: image upload error 2
Posted by Christopher Collins <ch...@runtime.io>.
Hi Then,
On Wed, Feb 22, 2017 at 02:11:36PM +0800, then yon wrote:
> Dear Support,
>
> I'm followed the tutorial below:
> https://mynewt.apache.org/latest/os/modules/split/split/
>
> But i'm stuck at image upload step; it gave me the following error:
[...]
> Error: Target error: 2
Error 2 indicates that there is no free slot for the new image. In your
email, the "image list" output is a bit touch to read because it got
collapsed into a single line. Here is my attempt to unravel it:
> $ newtmgr -c mynewt_serial image list
> Images:
> slot=0
> version: 1.0.0
> bootable: true
> flags: active confirmed
> hash: 493c5e78e76a9c1b9e574ab38b7bbf0d342d928ffd0111400dbe8c2c952da68e
>
> slot=1
> version: 1.0.0
> bootable: false
> flags: active confirmed
> hash: 4d26a0d1596e12dab9059df3a13b4ffd54f96836cd9080d579c6afc167d58e81
>
> Split status: matching
Notice that both slots have the "active" and "confirmed" flags set.
This indicates that both slots are currently running. You need to run
the image in loader-only mode in order to replace the app in slot 1.
This is described in the "Image Upgrade - Split" section of the page you
linked to (https://mynewt.apache.org/latest/os/modules/split/split/).
Specifically:
1. Disable split functionality; we need to deactivate the application
image in slot 1 (newtmgr image test <current-loader-hash>).
2. Reboot device (newtmgr reset).
3. Make above change permanent (newtmgr image confirm).
4. Upload new loader to slot 1 (newtmgr image upload <filename>).
5. Tell device to "test out" the new loader on next boot (newtmgr image
test <new-loader-hash>).
6. Reboot device (newtmgr reset).
7. Make above change of loader permanent (newtmgr image confirm).
8. Upload new application to slot 1 (newtmgr image upload <filename>).
9. Tell device to "test out" the new application on next boot (newtmgr
image test <new-application-hash>).
10. Reboot device (newtmgr reset).
11. Make above change of application permanent (newtmgr image confirm).
Steps 1 and 2 will leave the device in a state such that the app in slot
1 can be replaced.
Chris