-
Notifications
You must be signed in to change notification settings - Fork 8.2k
intel_s1000: doc: Update doc with MCUbootloader support #12355
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
All checks are passing now. Review history of this comment for details about previous failed status. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
replace MCUbootloader with MCUBoot Bootloader
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, it's Zephyr on Intel S1000, not Intel S1000 on Zephyr.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Corrected.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, it's Zephyr on Intel S1000, not Intel S1000 on Zephyr.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
USB DFU is not exactly over the "air", please remove "over the air". Also change "upgradation" to "upgrades".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will this procedure (and upgrading the S1000 firmware) work on the board referenced at the top of this doc (https://software.intel.com/en-us/iot/speech-enabling-dev-kit)? I suspect not, and we need to be more explicit at the top of this doc about the board and procedures being documented here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dbkinder This procedure will work on the board referenced at the top of this doc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This block is similar to the app build and should be able to use the zephyr-app-commands directive. See around line 136
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
zephyr-app-commands are applicable only to those apps which are within the zephyr tree. mcubootloader is outside of it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see :app: directive (vs :zephyr-app:) at https://docs.zephyrproject.org/latest/documentation/doc-guidelines.html#zephyr-app-commands-directive
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
modified as suggested.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
create_spi_flash utility is not available publicly. need to make it or a variant of it as part of the build system before updating the document.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok. noted. I will keep this for the time being while i work on the utility
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed this now. #12662 addresses this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So, when the active image is switched to image1, will the DFU capability be lost? If the DFU capability is part of the image, then both image0 and image1 should have the capability.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's correct. updated the doc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
add one more space on the indent...
| `MCUboot with Zephyr`_ documentation for details.) | |
| `MCUboot with Zephyr`_ documentation for details.) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given the comment below, this title should likely be MCUBoot bootloader support (and adjust the title underline)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
... and change all references to MCUBoot bootloader
| MCUbootloader in conjuntion with USB DFU (Device Firmware Upgrade) | |
| MCUBoot bootloader, in conjunction with USB DFU (Device Firmware Upgrade), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| over the air can be used for Field upgradation of Intel S1000 Firmware. | |
| can be used to upgrade Intel S1000 firmware. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| The MCUbootloader source code itself is hosted in the | |
| The MCUBoot bootloader source code is hosted in the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| looking at boards/xtensa/intel_s1000_crb/intel_s1000_crb.dts. Refer to | |
| looking at ``boards/xtensa/intel_s1000_crb/intel_s1000_crb.dts``. Refer to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| In order to build an MCUboot-compatible Intel S1000 Firmware image | |
| Build an MCUboot-compatible Intel S1000 Firmware image |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| (image0/image1), you need to do the following: | |
| (image0/image1), by following these steps: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need to indent the code-block directives to be within the bullet list items.
How about more simply:
1. Edit your application's :file:`.conf` file to enable the
:option:`CONFIG_BOOTLOADER_MCUBOOT` option.
2. Use the ``scripts/imagetool.py`` script from the MCUboot GitHub repo`_
to sign the ``image0`` image (see `MCUboot with Zephyr`_ documentation for details):
.. code-block:: console
scripts/imgtool.py sign \
--key root-rsa-2048.pem \
--header-size 0x100 \
--align 8 \
--version 1.2 \
--slot-size 0x1D0000 \
./zephyr/zephyr.bin \
signed-zephyr0.bin
3. Sign the ``image1`` upgrade image with the ``--pad`` option:
.. code-block:: console
scripts/imgtool.py sign \
--key root-rsa-2048.pem \
--header-size 0x100 \
--align 8 \
--version 1.2 \
--slot-size 0x1D0000 \
--pad
./zephyr/zephyr.bin \
signed-zephyr1.bin
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will this procedure (and upgrading the S1000 firmware) work on the board referenced at the top of this doc (https://software.intel.com/en-us/iot/speech-enabling-dev-kit)? I suspect not, and we need to be more explicit at the top of this doc about the board and procedures being documented here.
|
@dbkinder @sathishkuttan addressed your comments. Plz have a look. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Docs look better, but still need to resolve use of ./create_spi_flash
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, but it's still here in this version of the documentation being reviewed.
The reference to create_spi_flash is now removed. Please review again. |
6da0dc5 to
92eeccc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 for docs, thanks!
The documentation for intel_s1000 is updated with the steps to use it with MCUbootloader. Signed-off-by: Rajavardhan Gundi <[email protected]>
|
@nashif .. please check if this can be merged. Shippable failures seem to be unrelated. |
|
stale |
The documentation for intel_s1000 is updated with the steps
to use it with MCUbootloader.
Signed-off-by: Rajavardhan Gundi [email protected]