From: lucavermei <lucavermei@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot post-image script error
Date: Sun, 28 Mar 2021 12:31:58 -0500 (CDT) [thread overview]
Message-ID: <1616952718209-0.post@n4.nabble.com> (raw)
Hi all,
I am new to buildroot and I am trying to build a system for my beaglebone
black wireless.
The build exit with an error:
>>> Executing post-image script support/scripts/genimage.sh
board/beaglebone/genimage.cfg:34: no sub-section title/index for 'config'
INFO: cmd: "mkdir -p "/home/luca/buildroot/output/build/genimage.tmp""
(stderr):
INFO: cmd: "rm -rf "/home/luca/buildroot/output/build/genimage.tmp"/*"
(stderr):
INFO: cmd: "mkdir -p "/home/luca/buildroot/output/build/genimage.tmp""
(stderr):
INFO: cmd: "cp -a "/tmp/tmp.PeR17MSHjT"
"/home/luca/buildroot/output/build/genimage.tmp/root"" (stderr):
INFO: cmd: "find '/home/luca/buildroot/output/build/genimage.tmp/root'
-depth -type d -printf '%P\0' | xargs -0 -I {} touch -r
'/tmp/tmp.PeR17MSHjT/{}'
'/home/luca/buildroot/output/build/genimage.tmp/root/{}'" (stderr):
ERROR: file(am335x-evm.dtb):
stat(/home/luca/buildroot/output/images/am335x-evm.dtb) failed: No such file
or directory
ERROR: vfat(boot.vfat): could not setup am335x-evm.dtb
make[1]: *** [Makefile:836: target-post-image] Error 1
make: *** [Makefile:84: _all] Error 2
In my config I set the option build a device tree blob and In-tree device
tree source file names "am335x-boneblack-wireless"
If a do ls in /buildroot/output/images I get:
am335x-boneblack-wireless.dtb MLO rootfs.tar u-boot.img uEnv.txt zImage
How can I fix the problem with the post image script?
--
Sent from: http://buildroot-busybox.2317881.n4.nabble.com/
next reply other threads:[~2021-03-28 17:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-28 17:31 lucavermei [this message]
2021-03-28 20:28 ` [Buildroot] Buildroot post-image script error Peter Seiderer
2021-03-31 18:32 ` lucavermei
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=1616952718209-0.post@n4.nabble.com \
--to=lucavermei@gmail.com \
--cc=buildroot@busybox.net \
/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.