| Age | Commit message (Collapse) | Author |
|---|
|
The legacy update procedure was not deploying the proper hardware
specific device tree.
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
Acked-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
Switch to the generic compressed Kernel image type (zImage) instead of
the U-Boot specific uImage format.
Signed-off-by: Bhuvanchandra DV <bhuvanchandra.dv@gmail.com>
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
Unfortunately as loadaddr is equal to fdt_addr_r on some modules and
equal to kernel_addr_r on others using it together with any of the
others may cause issues. Therefore no longer make use of loadaddr and
consistently use fdt_addr_r instead.
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
Acked-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
The config block check aka check_configblock may fail during update
depending on the size of the hardware area boot partition which may
lead to the config block not getting properly migrated or updated if
still using parts of the legacy update procedure. This patch fixes
this by iterating over various sizes.
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
Acked-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
Use ext4 by default for TK1 modules.
Signed-off-by: Sanchayan Maity <maitysanchayan@gmail.com>
Acked-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
If an image creates a rootfs which is exactly a multiple of 64 MByte then
the scripts never detects that the last chunk has been read and
'run update' never completes.
Fix that by explicitely setting filesize to 0 when a file read fails.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
Acked-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
Our current update procedure reads the rootfs payload in pre
split files of 64 MB size. However due to the workaround for
u-boot counting in hex and split did in decimal, the number of
chunks is limited to 89 resulting in a maximum size of 5.5GB.
Update the u-boot counting procedure to count in 3 digits from
the current 2 digits. This allows more than 800 plus chunks
which should take care of rootfs size and any future eMMC
update requirements.
Signed-off-by: Sanchayan Maity <sanchayan.maity@toradex.com>
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
Our current update procedure requires the rootfs payload to fit in
one file on a FAT filesystem. This limits its usable size to 4GB.
Use the process of splitting up the files in 64MB chunks and then
doing the update which is also what the Ethernet update scripts
currently follow.
However due to the workaround for u-boot counting in hex and split
did in decimal, the number of chunks is limited to 89 resulting in
a maximum size of 5.5GB. We will remove the limitation in a follow
up patch.
Signed-off-by: Sanchayan Maity <sanchayan.maity@toradex.com>
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
This requires to adjust the path to include files, e.g.:
-require recipes/images/trdx-image-fstype.inc
+require recipes-images/images/trdx-image-fstype.inc
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
Acked-by: Stefan Agner <stefan.agner@toradex.com>
|
