All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Dahl <ada@thorsis.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Most appropriate and scriptable way of creating partition image files
Date: Fri, 15 Nov 2019 11:39:59 +0100	[thread overview]
Message-ID: <4664154.8cfxjC1jBK@ada> (raw)
In-Reply-To: <CALDr4Cjf9g2ipQ18W7LksTt5zxkccfF+bSirq0_Sje3zxRHR4w@mail.gmail.com>

Hei hei,

Am Donnerstag, 14. November 2019, 20:54:15 CET schrieb Arji Cot:
> I'm new at this, my problem is that I have the kernel, busybox and u-boot
> already build for my target platform, I'm not sure what is the most
> appropriate way of creating the final ".img" file out of the files that I
> already have .

ptxdist [1] uses genimage [2]. It's available for buildroot [3], too, however 
I don't know if they actually use it.

> I need to create 2 partitions, 1 vfat/fat32 for the boot and 1 partition
> for the rootfs, the resulting 2 .img files will be burned on an eMMC using
> the software provided by the vendor, so burning it's not the issue here .

Sounds like a usual usecase for genimage.

> I would like to have a more "scriptable" alternative to using dd, mounting,
> writing and sync and then unmount the partition each time I need to create
> an img file .

Well genimage works with config files, but that should work for you.

> I'm using a linux 64 bit box .

Who doesn't? ;-)

Greets
Alex

[1] https://www.ptxdist.org/
[2] https://github.com/pengutronix/genimage
[3] https://buildroot.org/

      reply	other threads:[~2019-11-15 10:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-14 19:54 [U-Boot] Most appropriate and scriptable way of creating partition image files Arji Cot
2019-11-15 10:39 ` Alexander Dahl [this message]

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=4664154.8cfxjC1jBK@ada \
    --to=ada@thorsis.com \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.