| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |/
|
|
|
|
|
|
|
|
| |
To support new kernel, which use Device Tree for description of
hardware and machine, the image generation needs to be reworked.
U-Boot supports it out of box, so it just need to be available for
reading while the imx-bootlets we need to append the dtb file on the
very end of the zImage file.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
| |
linux_ivt.bd module is dependant of mx25 and cannot be used by i.MXS
family.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
| |
When updating to imx-bootlets 10.12.01 a leftover configuration from
previous release has been left by mistake.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
i.MXS SoC family has support to boot with imx-bootlets (the default
when using LTIB) and the only current supported way of booting i.MX23
machines.
The imx-bootlets has some quite specific requirements regaring the
partition layout and includes the kernel binary appended to the boot
stream so we drop the third partition reducing the wasted space of SD
card.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
| |
i.MXS generation is now handled completely separated so i.MX doesn't
every gets called for 'mxs' SoC family.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
| |
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
| |
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
|
| |
It looks like mkfs.vfat is using 1024B block size. The returned value
of BOOT_BLOCKS was in blocks of 512B. This needs to be changed in blocks
of 1024B.
Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
|
| |
|
|
|
|
|
| |
In awk the first cell/item is $1 not $0 in this way the size
of the partition from parted is actually $4 not $3.
Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
|
| |
|
|
| |
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
|
| |
i.MXS and i.MX SoC families has enough partition layout differences
that justify to have a specific code for each SoC family to easy
maintenance and readability of code.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
| |
The SoC image fstypes needs to be assigned in the machine definition
or the default ones are not used.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
|
| |
The 'sed' might fail in some systems due user right and restrictions
so we use 'dd' and 'echo' to do the same trick.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Reported-by: "John Passaniti" <jpassaniti@ashly.com>
|
| |
|
|
|
|
|
|
| |
This speeds up the generation of the sdcard and reduces the amount of
space used for it.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Reported-by: "John Passaniti" <jpassaniti@ashly.com>
|
| |
|
|
|
|
|
|
|
| |
The mxs SoC family requires use of a bootstream in bootloader but at
this moment only SDCard format is supported. The image for use is
'u-boot.mxsboot-sdcard' and this is also the file extension of the
generated file beside of regular u-boot binary.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
| |
u-boot-imx has padding by default and machines using it need to skip
it when generating the sdcard.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
| |
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The generation of SDCard has been completely refactored to work out of
box; now to use it you have to set, e.g:
SDCARD_ROOTFS = "${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.rootfs.ext3"
SDCARD_SIZE = "128"
IMAGE_TYPES += "ext3 sdcard"
Now the sdcard has following layout:
0 - 1M - reserved to bootloader and other data
1M - BOOT_SPACE - kernel
BOOT_SPACE - SDCARD_SIZE - rootfs
All current supported machines on BSP will work out of box and
generate a 2GB SDCard with an ext3 rootfs on it.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
|
|
| |
The IMAGE_BOOTLOADER variable allows to specific the bootloader to be
used. Currently it supports 'u-boot' and 'barebox' as option. Images
using the bbsdcard_image.bbclass need to change the image definition
to adapt to this.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
this class allows the generation of a ready to use SDCard image
using barebox bootloader.
example on how to use it (with angstrom distro) :
1- add these 3 lines to your local.conf :
ROOTFS = "${DEPLOY_DIR_IMAGE}/console-image-imx53qsb.ext3"
INHERIT += "bbsdcard_image"
BBSDIMG_SIZE = "512"
2- build the image
bitbake console-image
3- copy it to the sdcard (update device for you sdcard, take care to not erase your hard drive ;-)
sudo dd if=build/tmp-angstrom_2010_x-eglibc/deploy/images/imx53qsb/console-image-imx53qsb.bbsdimg of=/dev/mmcblk0
Signed-off-by: Eric Bénard <eric@eukrea.com>
|
|
|
This creates an image suitable for writting onto a SD card and use on
i.MX53 boards allowing for easy image testing.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
