gustavonihei commented on a change in pull request #929:
URL:
https://github.com/apache/incubator-nuttx-apps/pull/929#discussion_r773125860
##########
File path: boot/mcuboot/README.md
##########
@@ -22,9 +22,7 @@ The NuttX port of MCUboot is implemented at application-level
and requires minim
## Creating MCUboot-compatible application firmware images
-One common use case for MCUboot is to integrate it to a firmware update agent,
which is an important component of a secure firmware update subsystem. Through
MCUboot APIs an application is able to install a newly received application
firmware image and, once this application firmware image is assured to be
valid, the application may confirm it as a stable image. In case that
application firmware image is deemed bogus, MCUboot provides an API for
invalidating that update, which will induce a rollback procedure to the most
recent stable application firmware image.
-
-The `CONFIG_MCUBOOT_UPDATE_AGENT_EXAMPLE` example demonstrates this workflow
by downloading an application firmware image from a webserver, installing it
and triggering the firmware update process for the next boot after a system
reset. There is also the `CONFIG_MCUBOOT_SLOT_CONFIRM_EXAMPLE`, which is a
fairly simple example that just calls an MCUboot API for confirming the
executing application firmware image as stable.
+See `examples/mcuboot` examples.
Review comment:
```suggestion
One common use case for MCUboot is to integrate it to a firmware update
agent, which is an important component of a secure firmware update subsystem.
Through MCUboot APIs an application is able to install a newly received
application firmware image and, once this application firmware image is assured
to be valid, the application may confirm it as a stable image. In case that
application firmware image is deemed bogus, MCUboot provides an API for
invalidating that update, which will induce a rollback procedure to the most
recent stable application firmware image.
The `CONFIG_EXAMPLES_MCUBOOT_UPDATE_AGENT` example demonstrates this
workflow by downloading an application firmware image from a webserver,
installing it and triggering the firmware update process for the next boot
after a system reset. There is also the `CONFIG_EXAMPLES_MCUBOOT_SLOT_CONFIRM`,
which is a fairly simple example that just calls an MCUboot API for confirming
the executing application firmware image as stable.
```
Actually, since the examples still exist, I see no reason to remove it. Just
update the reference to the Kconfig keys.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
