Age | Commit message (Collapse) | Author |
|
Don't write the eMMC twice on Apalis in the not migrate case.
|
|
Update our U-Boot update scripts to accommodate our new unified eMMC
layout:
boot area partition 1 aka primary eMMC boot sector:
with U-Boot boot loader and the U-Boot environment before the
configblock at the end of that boot area partition
Handle migration of boot loader and configblock on Apalis/Colibri iMX6.
When doing a full update also explicitly flash kernel and FDT from the
update medium in order to allow for easy updating thereof.
|
|
With update.sh one creates files on e.g. a SD-card or a tftp server
which enables updating the SW on a module from U-Boot running on
said module.
This commit adds a module type specific directory on that output media
so that update data for multiple module types can be stored on one media.
Generic U-Boot scripts in the media's root directory do select the
matching update data depending on module type.
|
|
To flash a large rootfs over tftp the rootfs must be split into chunks
of 64MB on the tftp server.
Add the option '-c' to the update.sh script which does this automatically.
Use 64MB chunks on all module types.
|
|
iMX6: Always do use a secondary argument for the 'mmc dev' command.
T30: Do rootfs update of eMMC in chunks as well. Requires pre-splitting
file in Ethernet case. As an advantage allows flashing rootfs bigger
than RAM plus avoids timeouts during flashing. Added wrapper flash_mmc
script as well for backwards compatibility reason.
While at it cleanup various whitespaces throughout the update scripts.
|
|
Drop the burnflash.tar.bz2 tarball and put the individual files under
version control.
Only create minimal set for colibri-t20 for now and move it with the
change to tegra-uboot-flasher.
|