From: michael.opdenacker@rootcommit.com
To: docs@lists.yoctoproject.org
Cc: Michael Opdenacker <michael.opdenacker@rootcommit.com>
Subject: [PATCH v3 3/3] dev-manual/bmaptool.rst: simplify and fix instructions
Date: Wed, 18 Dec 2024 14:47:03 +0000 (UTC) [thread overview]
Message-ID: <20241218144654.852310-4-michael.opdenacker@rootcommit.com> (raw)
In-Reply-To: <20241218144654.852310-1-michael.opdenacker@rootcommit.com>
From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
- Remove duplicate instructions
- Detail how to run bmaptool directly if you installed it on your host
instead of building it through the ``bmaptool-native`` recipe,
as running "oe-run-native bmaptool-native bmaptool ..." won't work
in this case.
- Use "chmod a+w" instead of "chmod 666", better advice,
and only run "chmod" in the option that runs "oe-run-native"
Signed-off-by: Michael Opdenacker <michael.opdenacker@rootcommit.com>
---
documentation/dev-manual/bmaptool.rst | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/documentation/dev-manual/bmaptool.rst b/documentation/dev-manual/bmaptool.rst
index 37083c9c64..87162a49c9 100644
--- a/documentation/dev-manual/bmaptool.rst
+++ b/documentation/dev-manual/bmaptool.rst
@@ -43,14 +43,13 @@ any type of image. Use these steps to flash an image using `bmaptool`:
depending on your particular setup. The following commands assume the
image resides in the :term:`Build Directory`'s ``deploy/images/`` area:
- - If you have write access to the media, use this command form::
+ - If you installed the package for `bmaptool`, you can directly run::
- $ oe-run-native bmaptool-native bmaptool copy build-directory/tmp/deploy/images/machine/image.wic /dev/sdX
+ $ sudo bmaptool copy build-directory/tmp/deploy/images/machine/image.wic /dev/sdX
- - If you do not have write access to the media, set your permissions
- first and then use the same command form::
+ - Otherwise, if you built `bmaptool` with BitBake, run::
- $ sudo chmod 666 /dev/sdX
+ $ sudo chmod a+w /dev/sdX # get write access to the media, needed only once after booting
$ oe-run-native bmaptool-native bmaptool copy build-directory/tmp/deploy/images/machine/image.wic /dev/sdX
For help on the ``bmaptool`` command, use the following command::
next prev parent reply other threads:[~2024-12-18 14:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 14:46 [PATCH v3 0/3] Improvements to "bmaptool" usage documentation michael.opdenacker
2024-12-18 14:47 ` [PATCH v3 1/3] dev-manual: fix styling of references to bmaptool michael.opdenacker
2024-12-18 14:47 ` [PATCH v3 2/3] dev-manual/bmaptool.rst: correct command for bmaptool-native michael.opdenacker
2024-12-18 14:47 ` michael.opdenacker [this message]
2024-12-18 15:36 ` [docs] [PATCH v3 0/3] Improvements to "bmaptool" usage documentation Antonin Godard
2024-12-23 9:02 ` antonin.godard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241218144654.852310-4-michael.opdenacker@rootcommit.com \
--to=michael.opdenacker@rootcommit.com \
--cc=docs@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox