Error: exec_cmd: install -m 0644 -D /home/richard/yocto/build/tmp/deploy/images/overo/uImage /var/tmp/wic/build/boot/uImage returned '1' instead of 0
It appears that the image was created with a zImage file, but wic wants to copy a uImage file.
Where did I go wrong? I used master branch. That should just work, yes?
I think I could use my script to partition & copy across the relevant files in the /deploy/ directory to produce a bootable SD card, but since the wic process seems to be the recommended way I thought I would give it a go.
We are investigating how much work would be involved in getting a custom
kernel which boots in no more than ~5s (networking not needed immediately
after boot) which can start encoding recording video at something like
640x480, 50fps. Subsequently, networking (Bluetooth, wifi, IPV4) fired up
to transfer recorded files etc.
Currently we capture BT656 video and process using GStreamer on a custom
Angstrom kernel. We used to use WaterSTORM boards, then upgraded to
IronSTORM for extended temperature rating (with BT/wifi disabled), then
thought about actually using BT/wifi. We switched to IronStorm-Y for
availability reasons. That's the only flavour I can get the BT running on
(using your pre-compiled kernel - Fido).
From: General mailing list for gumstix users.
Sent: 12 April 2017 21:03
To: [hidden email] Subject: Re: [Gumstix-users] Gumstix Repo Manifests for the Yocto Project
Can you send me the link of the getting started project/tutorial that you're
working through? I'm worried that it's an out of date one that should be
So I can help guide you, what is your end goal? You want to build a custom
image for your Gumstix COM? Do you know what Linux kernel you'd like? Do
you want a console or desktop image?
Re: Gumstix Repo Manifests for the Yocto Project Build System
My apologies Richard, I was trying to do too many things at once.
Have you tried the "dev" branch of that repo? It uses the a much new kernel version (4.5 vs 3.18) and uses yocto Krogoth instead of Fido. Either should work but if you're starting from scratch, why not use the newer kernel unless you have to stick with the older one.
When you're all done building, you should find in your build/tmp/deploy/images/overo/ directory several files. You'll need MLO, u-boot.img and console-image.tar.bz2 (or whatever image you bitbaked). From there you'll need to copy the MLO and u-boot.img to the first partition on your SD card and the *.tar.bz2 to the second partition on your SD card.
Your SD card creation instructions look out of date. What instructions are you following? Try following the instructions here. You shouldn't need to copy over the "uImage" ... newer builds have switched to "zImage".