Search results
From Yocto Project
Jump to navigationJump to search
- ED: Would it make sense to show only built images in the list of base images for customization? It would simplify UI even more. We are forcing user to b584 bytes (113 words) - 15:54, 16 July 2015
- ...ng a remotely built image is required. Such cases include testing official images for validation. For this purpose we made a script that: * fetches remote images required for testing3 KB (514 words) - 13:04, 15 July 2014
- ..."build" directory, something like "/home/<YOURUSER>/poky/build/tmp/deploy/images/qemu<MACHINE>/" ...(<code>$ mkdir images </code>); f) Access to images directory (<code> $ cd images </code>); g) create your qemu folder, for example if you are testing qemux83 KB (511 words) - 21:44, 29 September 2017
- * A BSP should contain a root level binary directory to contain binary images. Enough to get a board to boot with some level of functionality, keeping in * A BSP should contain *just* the meta-data needed to at least rebuild the images that exist in /binary. If your BSP repo contains support for 10 BSPs, the B3 KB (529 words) - 16:37, 4 December 2013
- ...ructions in the attached presentation [[https://wiki.yoctoproject.org/wiki/images/7/75/Toaster_Presentation_ELCE_2014_1.pdf]]357 bytes (48 words) - 11:43, 3 November 2014
- * A BSP should contain a root level binary directory to contain binary images. Enough to get a board to boot with some level of functionality, keeping in * A BSP should contain *just* the meta-data needed to at least rebuild the images that exist in /binary. If your BSP repo contains support for 10 BSPs, the B4 KB (727 words) - 22:42, 1 July 2014
- ...ux86 Sato-SDK build failure on autobuilder blocks qemux86 testing. All lsb images build failed because of a ghostscript checksum mismatch. Except for Crownb 1.Bug 802 - [mpc8315e-rdb] eeprom module not found in sato-sdk images (nightly build 20110301-4)2 KB (302 words) - 02:20, 1 July 2011
- ...//elinux.org/images/7/7c/Elc2011_zanussi_wold.odp Building Custom Embedded Images with Yocto (slides)] ...ussi-wold-custom-embedded-images-yocto-x450p.webm Building Custom Embedded Images with Yocto (450x800 video)]2 KB (257 words) - 20:37, 3 November 2011
- In general, the steps are very similar to those for generic images for BSP. The main difference, however, is that two poky repositories are ne "~/poky-run/build/tmp/deploy/images/qemux86/" (if "tmp/deploy/images/qemux86" does not exist, create new directories with this path)4 KB (640 words) - 16:03, 8 March 2017
- ...ree so that meta-x32 layer can work on top; so that one can build complete images with x32 abi binaries.452 bytes (67 words) - 11:55, 27 January 2016
- ...to put it on some media for use. Specifically the crazy stuff to get atom images on a usb stick.627 bytes (107 words) - 22:15, 27 May 2011
- "~poky/build/tmp/deploy/images/genericx86/" ( if "/tmp/deploy/images/genericx86" does not exist create new directories with this path) <p>NOTE: For QEMU images there are additional steps that need to be followed. They are detailed on</9 KB (1,552 words) - 15:57, 10 October 2017
- ...y image build failed. No space left on builder3 which cause the toolchains images build failed. Lttng-ust do_compile failed which cause Beagleboard image bui2 KB (269 words) - 09:01, 6 September 2011
- Images don't have to contain a full root file system and kernel, as they're constr972 bytes (152 words) - 16:20, 27 April 2018
- ...icons shown on X desktop with sato image still exist. For bug fixing, the images could be installed on Sugarbay and Jasperforest. Libsdl.so issue fixed on S Note:For different images, they are built against different commit/branch on autobuilder. You can ref3 KB (457 words) - 05:30, 6 September 2011
- ...icons shown on X desktop with sato image still exist. For bug fixing, the images could be installed on Sugarbay and Jasperforest. Libsdl.so issue fixed on S Note:For different images, they are built against different commit/branch on autobuilder. You can ref3 KB (457 words) - 09:02, 6 September 2011
- ...er qemu and runs tests against it. We've noticed occasional hangs of these images. A while ago we realised there was an entropy issue, particularly on qemupp c) We add rng-tools to the qemu images5 KB (732 words) - 18:06, 10 November 2017
- How to configure an OE-Core system to build images from shared artefacts. * Quickly build images from pre-existing artefacts on minimal hardware (e.g. laptops).3 KB (427 words) - 15:37, 15 June 2017
- The produced images will be deployed into the '''''tmp/deploy/images/intel-corei7-64/''''' directory. Two types of bootable images are produced by default, '''wic''' and '''hddimg'''.5 KB (776 words) - 18:04, 15 June 2017
- | Booting a board via serial connection and bootloader using Yocto images artifacts | Able to use Yocto images artifacts4 KB (552 words) - 13:16, 12 September 2014