From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6543937367387930624 X-Received: by 10.28.144.147 with SMTP id s141mr503628wmd.16.1523629150389; Fri, 13 Apr 2018 07:19:10 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 10.223.187.19 with SMTP id r19ls1834852wrg.11.gmail; Fri, 13 Apr 2018 07:19:10 -0700 (PDT) X-Google-Smtp-Source: AIpwx4/W8f/Parn39DW30Fp+7zdU1CNxrXspUw3csDNR+Fu3fQnY75iM15okaCbzGI0OturnA3Xj X-Received: by 10.223.210.70 with SMTP id o6mr487803wri.13.1523629150073; Fri, 13 Apr 2018 07:19:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1523629150; cv=none; d=google.com; s=arc-20160816; b=aPid2ONgVbkFfzM/LMSsRM/wzALtWVGd9zccj4X/ShHbPZlr6RKJqt8wH4eSoQKqmb kO2BMDnGWfqZaXVXhGz0SCiE1TYzgweFGYU9UZ/oPiz391otiSGtjcyu9Xmn0KKZy/eb 1qpl6zivKK8tAOs6lC06sC6WGB8J5NmCVGO5b+NYGsWApy3KPDiMvqXZxnV7geOyenPs 5giq4qWrJ7GqhQniGtpBv7SbkIErD+GYjAOlc8kLJXUaUdcPLGgqM0M2Yucgj/Y3py6A efSHg8DEdRiukROiN58CRI4XDeaSQkxPFBRdZnOfohl/srXNfn228wc3hMge3Xguh/94 AtgA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=references:in-reply-to:references:in-reply-to:message-id:date :subject:cc:to:from:arc-authentication-results; bh=9QnXQBnFE+mx9o2uPyNShN62El1T2fPnADxSFFBZPvI=; b=n359N/y79EeGNa4gmYUhaUDT1WaxQIu/4NsHFN+umZpYEj0rMc8yAASYpfRKVpT+zS IcYlMAD5/2imQFhwdUK64B+UmTIj54doi+oLHv7BxAT/3sL3yRipUIFfTxPkfptKb1Cu QMcC7kzo2FUOm5FoMPFv9/8hj/3O8bi9VNTqH4rI/qHAYHvUVXLMWyJ3MqPuK+e0y6xw RbhzjlMsxEOHi5mEU2oHRvJo7XPwWddb4YDL5z3PuSpInQMD4bvjC8BzGToA6b+AznX7 mjWSmEx6g3+eGYtCaRSDiRs+Aszvphf3u0wLLE1rY9Zj/Qaf/mFnCk7gn1cUdIoOJ1Kg xLxw== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Return-Path: Received: from goliath.siemens.de (goliath.siemens.de. [192.35.17.28]) by gmr-mx.google.com with ESMTPS id g7si241145wrb.2.2018.04.13.07.19.09 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 13 Apr 2018 07:19:10 -0700 (PDT) Received-SPF: pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.28 as permitted sender) client-ip=192.35.17.28; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by goliath.siemens.de (8.15.2/8.15.2) with ESMTPS id w3DEJ9tu015951 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 13 Apr 2018 16:19:09 +0200 Received: from md1pvb1c.ad001.siemens.net (md1pvb1c.ad001.siemens.net [139.25.68.40] (may be forged)) by mail1.siemens.de (8.15.2/8.15.2) with ESMTP id w3DEJ8W8011006; Fri, 13 Apr 2018 16:19:09 +0200 From: Henning Schild To: isar-users@googlegroups.com Cc: Cedric Hombourger , Andreas Reichel , Henning Schild Subject: [PATCH v2 16/17] docs: Change according to recent patches Date: Fri, 13 Apr 2018 16:19:05 +0200 Message-Id: <7a3e04b07c02ad0e26a7ea58c6218d09107d723b.1523628814.git.henning.schild@siemens.com> X-Mailer: git-send-email 2.16.1 In-Reply-To: References: In-Reply-To: References: X-TUID: PeLRFfVxB+wv Update the section on wic to tell people how to build images using it. Signed-off-by: Henning Schild --- doc/technical_overview.md | 7 ++++--- doc/user_manual.md | 25 ++++++++++++------------- 2 files changed, 16 insertions(+), 16 deletions(-) diff --git a/doc/technical_overview.md b/doc/technical_overview.md index 83624a5..ab62de9 100644 --- a/doc/technical_overview.md +++ b/doc/technical_overview.md @@ -239,10 +239,11 @@ variable. Task `do_populate` performs the following: 4. Execute dpkg command in chroot for all the copied packages. -## 3.7 Generate Bootable Image +## 3.7 Generate an Image This process contains the following steps: -1. Task `do_ext4_image`: target filesystem is packed to extfs image. +1. Task `do_<..>_image`: creates filesystem or disk images -2. wic tool generates bootable image for dedicated platform. + 1.1. `do_ext4_image`: target filesystem is packed to extfs image. + 1.2. `do_wic_image`: a bootable disk image gets created for the platform diff --git a/doc/user_manual.md b/doc/user_manual.md index 7bd52f4..7bdfc1c 100644 --- a/doc/user_manual.md +++ b/doc/user_manual.md @@ -190,34 +190,33 @@ Created images are: ../build-2/tmp/deploy/images/isar-image-base-debian-jessie-qemuarm.ext4.img ../build-3/tmp/deploy/images/isar-image-base-debian-stretch-qemuarm.ext4.img ../build-4/tmp/deploy/images/isar-image-base-debian-jessie-qemui386.ext4.img -../build-5/tmp/deploy/images/isar-image-base-debian-stretch-qemui386.ext4.img +../build-5/tmp/deploy/images/isar-image-base-debian-stretch-qemui386.wic.img ../build-6/tmp/deploy/images/isar-image-base-debian-jessie-qemuamd64.ext4.img -../build-7/tmp/deploy/images/isar-image-base-debian-stretch-qemuamd64.ext4.img +../build-7/tmp/deploy/images/isar-image-base-debian-stretch-qemuamd64.wic.img ../build-8/tmp/deploy/images/isar-image-base.rpi-sdimg ``` -### Generate EFI disk images +### Generate full disk image -Once the image artifacts have been built (c.f. previous section), full EFI disk images can be generated using the `wic` utility. -Currently, only the `i386` and `amd64` target architectures are supported: +A bootable disk image is generated if you set IMAGE_TYPE to 'wic-img'. Behind the scenes a tool called `wic` is used to assemble the images. It is controlled by a `.wks` file which you can choose with changing WKS_FILE. Some examples in the tree use that feature already. ``` - # Generate an EFI image for the `i386` target architecture - $ wic create -D sdimage-efi -o . -e multiconfig:qemui386-stretch:isar-image-base - # Similarly, for the `amd64` target architecture - $ wic create -D sdimage-efi -o . -e multiconfig:qemuamd64-stretch:isar-image-base + # Generate an image for the `i386` target architecture + $ bitbake multiconfig:qemui386-stretch:isar-image-base + # Similarly, for the `amd64` target architecture, in this case EFI + $ bitbake multiconfig:qemuamd64-stretch:isar-image-base ``` -In order to run the images with `qemu`, an EFI firmware is required and available at the following address: +In order to run the EFI images with `qemu`, an EFI firmware is required and available at the following address: https://github.com/tianocore/edk2/tree/3858b4a1ff09d3243fea8d07bd135478237cb8f7 Note that the `ovmf` package in Debian jessie/stretch/sid contains a pre-compiled firmware, but doesn't seem to be recent enough to allow images to be testable under `qemu`. ``` -# AMD64 image -qemu-system-x86_64 -m 256M -nographic -bios edk2/Build/OvmfX64/RELEASE_*/FV/OVMF.fd -hda ./sdimage-* +# AMD64 image, EFI +qemu-system-x86_64 -m 256M -nographic -bios edk2/Build/OvmfX64/RELEASE_*/FV/OVMF.fd -hda tmp/deploy/images/isar-image-base-debian-stretch-qemuamd64.wic.img # i386 image -qemu-system-i386 -m 256M -nographic -bios edk2/Build/OvmfIa32/RELEASE_*/FV/OVMF.fd -hda ./sdimage-* +qemu-system-i386 -m 256M -nographic -hda tmp/deploy/images/isar-image-base-debian-stretch-qemui386.wic.img ``` --- -- 2.16.1