我认为你可以做到这一点，但我遇到了麻烦，社区不能让我走出去，是写的元数据总是失败。看来我应该能做到这一点。
只是无法获得元数据。在Bootloader中有两个静态调用，我将去静态并尝试它。还没有适应它。
其他的东西都坏了：
我要求通过应用程序控制切换到另一个图像。如果我不能写入元数据，我仍然不知道如何满足这一点。
但当我查看引导加载程序时，我决定跟着它去。
1。在加载前进行完整性检查
2。如果闪光灯坏了，它会自动切换到另一个希望的好图像。
3或它会挂在Bootloader上。
我必须把所有的东西都建在应用程序中，然后调试它。
在我的申请中，我决定不做这些努力。
我认为元数据存储图像的起始位置。APP1被定义为在引导加载程序之后的下一行中。但是APP2位置存储在元数据中（在DOCS中读取）。
以上来自于百度翻译
以下为原文
I think you can do that, but I ran into trouble that the community could not get me out of which is that writes to the metadata always failed. It seems I should be able to do it..
just could not get the metadata written.There are a couple of static calls in the bootloader that I was going to Unstatic and try it. Have not gotten around to it.
Other things broke :-(
I had the requirement to switch to the other image by application control. I still don't know how I will satisfy this if I can't write to the metadata.
But when I looked at what the bootloader does, I decided to go with that because
1. It does integrity check before loading
2. If the flash is bad, it automatically switches to the other hopefully good image
3 or it will hang out at the base bootloader.
I would have to build all that into the application, and debug it.
I decided not to put that effort into doing all of this in my application.
I think the metadata stores the start location of the images. App1 is defined to be in the next row after the bootloader. But App2 location is stored in metadata (read that in the docs).
我认为你可以做到这一点，但我遇到了麻烦，社区不能让我走出去，是写的元数据总是失败。看来我应该能做到这一点。
只是无法获得元数据。在Bootloader中有两个静态调用，我将去静态并尝试它。还没有适应它。
其他的东西都坏了：
我要求通过应用程序控制切换到另一个图像。如果我不能写入元数据，我仍然不知道如何满足这一点。
但当我查看引导加载程序时，我决定跟着它去。
1。在加载前进行完整性检查
2。如果闪光灯坏了，它会自动切换到另一个希望的好图像。
3或它会挂在Bootloader上。
我必须把所有的东西都建在应用程序中，然后调试它。
在我的申请中，我决定不做这些努力。
我认为元数据存储图像的起始位置。APP1被定义为在引导加载程序之后的下一行中。但是APP2位置存储在元数据中（在DOCS中读取）。
以上来自于百度翻译
以下为原文
I think you can do that, but I ran into trouble that the community could not get me out of which is that writes to the metadata always failed. It seems I should be able to do it..
just could not get the metadata written.There are a couple of static calls in the bootloader that I was going to Unstatic and try it. Have not gotten around to it.
Other things broke :-(
I had the requirement to switch to the other image by application control. I still don't know how I will satisfy this if I can't write to the metadata.
But when I looked at what the bootloader does, I decided to go with that because
1. It does integrity check before loading
2. If the flash is bad, it automatically switches to the other hopefully good image
3 or it will hang out at the base bootloader.
I would have to build all that into the application, and debug it.
I decided not to put that effort into doing all of this in my application.
I think the metadata stores the start location of the images. App1 is defined to be in the next row after the bootloader. But App2 location is stored in metadata (read that in the docs).
举报
