On 29/01/16, Oliver Graute wrote: > On 28/01/16, Otavio Salvador wrote: > > On Thu, Jan 28, 2016 at 9:37 AM, Oliver Graute <[email protected]> > > wrote: > > > whats is the right way to adjust the flash partitions for my imx6ulevk? > > > > > > I need a bootstream partition, two rootfs partitions with 125 MB each > > > and a data partitions with 730 MB. > > > > > > during some code investigation I found image_types_fsl.bbclass where > > > some partitioning seems to happen. Is this the point to start? > > > > For this kind of use-case the wic is better. > > > wic create imx-test.wks -e fsl-image > > and get the follwing output: > > > Done. > Creating image(s)... > > Couldn't get 'bitbake -e rootfs1' output. > Bitbake failed with error: > Loading cache...done. > Loaded 2378 entries from dependency cache. > ERROR: Nothing PROVIDES 'rootfs1' > > Summary: There was 1 WARNING message shown. > Summary: There was 1 ERROR message shown, returning a non-zero exit code. > > Couldn't get 'bitbake -e rootfs1' output. > Bitbake failed with error: > Loading cache...done. > Loaded 2378 entries from dependency cache. > ERROR: Nothing PROVIDES 'rootfs1'
I updated my imx-test.wks file, I replaced rootfs1 and rootfs2 by my fsl-image # short-description: Create SD card image with a boot partition and two rootfs # long-description: # Create an image that can be written onto a SD card using dd for use # with i.MX SoC family # It uses u-boot # # The disk layout used is: # - --------- --------- ------------ ------------ ----------- # | | u-boot | /boot | rootfs 1 | rootfs 2 | data | # - --------- --------- ------------ ------------ ----------- # ^ ^ ^ ^ ^ # | | | | | # 0 1kiB 4MiB 4MiB + 8MiB 4MiB + 8Mib + rootfs 1 + rootfs 2 + data IMAGE_EXTRA_SPACE (default 10MiB) # part u-boot --source rawcopy --sourceparams="file=u-boot-imx6ulevk.img" --ondisk mmcblk --no-table --align 1 part /boot --source bootimg-partition --ondisk mmcblk --fstype=vfat --label boot --active --align 4096 --size 8M --extra-space 0 part / --source rootfs --rootfs-dir=fsl-image --ondisk mmcblk --fstype=ext4 --label platform --align 4096 part /rescue --source rootfs --rootfs-dir=fsl-image --ondisk mmcblk --fstype=ext4 --label secondary --align 4096 wic create imx-test.wks -e fsl-image Checking basic build environment... Done. Creating image(s)... Info: The new image(s) can be found here: /var/tmp/wic/build/imx-test-201601291301-mmcblk.direct The following build artifacts were used to create the image(s): ROOTFS_DIR: build-imx6ulevk/tmp/work/imx6ulevk-poky-linux-gnueabi/fsl-image/1.0-r0/rootfs ROOTFS_DIR["/rescue"]: build-imx6ulevk/tmp/work/imx6ulevk-poky-linux-gnueabi/fsl-image/1.0-r0/rootfs BOOTIMG_DIR: KERNEL_DIR: build-imx6ulevk/tmp/deploy/images/imx6ulevk NATIVE_SYSROOT: build-imx6ulevk/tmp/sysroots/x86_64-linux The image(s) were created using OE kickstart file: then I write the image to my sdcard with: dd if=imx-test-201601291200-mmcblk.direct of=sdb bs=4M && sync something is booting from that sd image. Is this the way to go? some further hints or corrections? how do I define the partition size? best regards, Oliver -- _______________________________________________ meta-freescale mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-freescale
