Age | Commit message (Collapse) | Author |
|
The script fails when -m is given but rootfs/etc/issue fails to provide
the version info.
While at it correct wrong text output on i.MX 6 based modules.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
Acked-by: Dominik Sliwa <dominik.sliwa@toradex.com>
|
|
update.sh guesses the module type from rootfs/etc/issue which works for images
created from our meta-toradex recipes.
If another rootfs is used one has to edit etc/issue.
Overcome that requirement by providing a -m parameter which allows forcing
the targeted module type.
Not giving -m or '-m 0' keeps the old behaviour.
see 'update.sh -h' for valid values.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
Acked-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
To be more in-line with all our other modules change update_dtb to
update_fdt also on all our NAND based modules and document it as such.
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
Acked-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
Acked-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
Acked-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
The binary/symlink mkfs.vfat seems to be considered outdated, it
is only deployed if one configures dosfstools with the flag
--enable-compat-symlinks.
Switch to mkfs.fat which seems to be the official binary to create
FAT filesystems now.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
Acked-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
Use static UBI volumes on Colibri T20.
Fix update over ethernet on Colibri Vybrid
Signed-off-by: Dominik Sliwa <dominik.sliwa@toradex.com>
Acked-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
Acked-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
Add exit trap to report unexpected exits (due to set -e). Note that
this traps every exit, also explicit calls to exit. Therefor register
the trap only during the sequencial image generating/coping part,
after the sanity checks...
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
Acked-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
If executing the command fails, the exit code will be <> 1 which
leads to an imeadiate exit (due to set -e). Avoid exiting by
adding "|| true" to the sanity check commands.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
Acked-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
By omitting an explicit exit code after the recovery command we
will get the exit code of the last command. This makes sense,
since we would be able to tell whether recovery actually succeeded
or not.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
Acked-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
Unix commands usually exit successfully when help was explicitly
asked for. However, in case arguments are incomplete or otherwise
wrong, exit with error.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
Acked-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
printf allows to print escape sequences (e.g. for colored output)
and is part of the POSIX standard.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
Acked-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
Write kernel and device tree into seperate UBI Volumes. This
allows to use a lot less UBI/UBIFS support in U-Boot, which
should lower the risk of hitting bugs in this area. Boot times
are also slightly faster (measurements showed an improvement of
~150ms).
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
Acked-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
With the cfgblock command in U-Boot we now have a better solution.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
Acked-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
Further clean-up and unify our update scripts:
- Universally mention Ethernet aka TFTP, SD card and USB flash drive as
possible update media.
- Universally mention detailed recovery/update procedures being
available on our developer website.
- Universally split usage and flashing instructions (-f).
- Make sure we don't exceed the 80 characters line length limit.
- Fix various spelling issues.
|
|
The following commit:
f463f754048ebc3325025f0e1506b03cf14203a5
update.sh: use moduletype specific folder for output files
moved the output folder check above the module type selection which now
fails in case of debug aka recovery mode only operation with the
following error:
does not exist, exiting
This patch fixes this by not erring out in the debug aka recovery mode
only operation if no output folder is set.
|
|
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.
|
|
|
|
While we were checking whether the mkfs.ubifs tool has the magic
--space-fixup option available we never actually enabled that option
to be used when generating our UBIFS root file system images.
Thanks Bhuvan for spotting this having actually been in our update
scripts for almost two years now!
|
|
U-Boot now has the command cfgblock which can be used to create a valid
configblock.
Alternatively one can be created with create_configblock.sh.
|
|
Fix and enhance messages durring Colibri VF50/VF61 upgrade.
Fix missing run command
|
|
Create the U-Boot scipts at image buildtime and remove the binary
script representation from version control.
|
|
|
|
The migration to BSP V2.4 is somewhat more complex due to ECC level
change. The scripts detect whether we are on a new or old module by
checking the NAND driver type (which probably reflects best which
ECC level has been used). In case the NAND driver has the old name
(fsl_nfc), then the script assumes that migration is required:
The migration script runs in two stages:
- The first part updates U-Boot, erases the root file system and
loads the config block into memory (upgrade_part1).
- After reboot, the second stage runs with the new U-Boot version.
The script update the boot configuration block (BCB), restores the
config block from memory and U-Boot is written again using the
new ECC level. Then, the script erases the UBI partition (which
contains the root filesystem) and recreates it using the new ECC
level too (upgrade_part2).
Since we keep the config block temporarly in RAM, the whole update
process should not be interrupted! In case it did, the new U-Boot
version is able to restore the configuration block from command
line.
In contrast to older update scripts, the standard upgrade procedure
does not erase the whole UBI partition anymore. This makes sure that
wear-leveling information can be preserved.
|
|
Update to latest version (SVN r671) of burnflash.
|
|
Update to latest version (r663) of Vybrid flash scripts.
|
|
Pull out common files of the module specific trees into the common library
directory and symlink the files.
|
|
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.
|