2014-07-13 22:12:56 +00:00
|
|
|
#
|
2015-05-27 19:03:22 +00:00
|
|
|
# Copyright (C) 2014-2015 OpenWrt.org
|
2014-07-13 22:12:56 +00:00
|
|
|
#
|
|
|
|
|
|
|
|
linksys_get_target_firmware() {
|
mtd: base-files: Unify dual-firmware devices (Linksys)
Consistently handle boot-count reset and upgrade across
ipq40xx, ipq806x, kirkwood, mvebu
Dual-firmware devices often utilize a specific MTD partition
to record the number of times the boot loader has initiated boot.
Most of these devices are NAND, typically with a 2k erase size.
When this code was ported to the ipq40xx platform, the device in hand
used NOR for this partition, with a 16-byte "record" size. As the
implementation of `mtd resetbc` is by-platform, the hard-coded nature
of this change prevented proper operation of a NAND-based device.
* Unified the "NOR" variant with the rest of the Linksys variants
* Added logging to indicate success and failure
* Provided a meaningful return value for scripting
* "Protected" the use of `mtd resetbc` in start-up scripts so that
failure does not end the boot sequence
* Moved Linksys-specific actions into common `/etc/init.d/bootcount`
For upgrade, these devices need to determine which partition to flash,
as well as set certain U-Boot envirnment variables to change the next
boot to the newly flashed version.
* Moved upgrade-related environment changes out of bootcount
* Combined multiple flashes of environment into single one
* Current-partition detection now handles absence of `boot_part`
Runtime-tested: Linksys EA8300
Signed-off-by: Jeff Kletsky <git-commits@allycomm.com>
Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
[checkpatch.pl fixes, traded split strings for 80+ chars per line]
2019-04-10 15:28:01 +00:00
|
|
|
|
|
|
|
local cur_boot_part mtd_ubi0
|
|
|
|
|
2014-07-13 22:12:56 +00:00
|
|
|
cur_boot_part=`/usr/sbin/fw_printenv -n boot_part`
|
mtd: base-files: Unify dual-firmware devices (Linksys)
Consistently handle boot-count reset and upgrade across
ipq40xx, ipq806x, kirkwood, mvebu
Dual-firmware devices often utilize a specific MTD partition
to record the number of times the boot loader has initiated boot.
Most of these devices are NAND, typically with a 2k erase size.
When this code was ported to the ipq40xx platform, the device in hand
used NOR for this partition, with a 16-byte "record" size. As the
implementation of `mtd resetbc` is by-platform, the hard-coded nature
of this change prevented proper operation of a NAND-based device.
* Unified the "NOR" variant with the rest of the Linksys variants
* Added logging to indicate success and failure
* Provided a meaningful return value for scripting
* "Protected" the use of `mtd resetbc` in start-up scripts so that
failure does not end the boot sequence
* Moved Linksys-specific actions into common `/etc/init.d/bootcount`
For upgrade, these devices need to determine which partition to flash,
as well as set certain U-Boot envirnment variables to change the next
boot to the newly flashed version.
* Moved upgrade-related environment changes out of bootcount
* Combined multiple flashes of environment into single one
* Current-partition detection now handles absence of `boot_part`
Runtime-tested: Linksys EA8300
Signed-off-by: Jeff Kletsky <git-commits@allycomm.com>
Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
[checkpatch.pl fixes, traded split strings for 80+ chars per line]
2019-04-10 15:28:01 +00:00
|
|
|
if [ -z "${cur_boot_part}" ] ; then
|
|
|
|
mtd_ubi0=$(cat /sys/devices/virtual/ubi/ubi0/mtd_num)
|
|
|
|
case $(egrep ^mtd${mtd_ubi0}: /proc/mtd | cut -d '"' -f 2) in
|
|
|
|
kernel1|rootfs1)
|
|
|
|
cur_boot_part=1
|
|
|
|
;;
|
|
|
|
kernel2|rootfs2)
|
|
|
|
cur_boot_part=2
|
|
|
|
;;
|
|
|
|
esac
|
|
|
|
>&2 printf "Current boot_part='%s' selected from ubi0/mtd_num='%s'" \
|
|
|
|
"${cur_boot_part}" "${mtd_ubi0}"
|
2014-07-13 22:12:56 +00:00
|
|
|
fi
|
|
|
|
|
mtd: base-files: Unify dual-firmware devices (Linksys)
Consistently handle boot-count reset and upgrade across
ipq40xx, ipq806x, kirkwood, mvebu
Dual-firmware devices often utilize a specific MTD partition
to record the number of times the boot loader has initiated boot.
Most of these devices are NAND, typically with a 2k erase size.
When this code was ported to the ipq40xx platform, the device in hand
used NOR for this partition, with a 16-byte "record" size. As the
implementation of `mtd resetbc` is by-platform, the hard-coded nature
of this change prevented proper operation of a NAND-based device.
* Unified the "NOR" variant with the rest of the Linksys variants
* Added logging to indicate success and failure
* Provided a meaningful return value for scripting
* "Protected" the use of `mtd resetbc` in start-up scripts so that
failure does not end the boot sequence
* Moved Linksys-specific actions into common `/etc/init.d/bootcount`
For upgrade, these devices need to determine which partition to flash,
as well as set certain U-Boot envirnment variables to change the next
boot to the newly flashed version.
* Moved upgrade-related environment changes out of bootcount
* Combined multiple flashes of environment into single one
* Current-partition detection now handles absence of `boot_part`
Runtime-tested: Linksys EA8300
Signed-off-by: Jeff Kletsky <git-commits@allycomm.com>
Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
[checkpatch.pl fixes, traded split strings for 80+ chars per line]
2019-04-10 15:28:01 +00:00
|
|
|
case $cur_boot_part in
|
|
|
|
1)
|
|
|
|
fw_setenv -s - <<-EOF
|
|
|
|
boot_part 2
|
|
|
|
bootcmd "run altnandboot"
|
|
|
|
EOF
|
|
|
|
printf "kernel2"
|
|
|
|
return
|
|
|
|
;;
|
|
|
|
2)
|
|
|
|
fw_setenv -s - <<-EOF
|
|
|
|
boot_part 1
|
|
|
|
bootcmd "run nandboot"
|
|
|
|
EOF
|
|
|
|
printf "kernel1"
|
|
|
|
return
|
|
|
|
;;
|
|
|
|
*)
|
|
|
|
return
|
|
|
|
;;
|
|
|
|
esac
|
2014-07-13 22:12:56 +00:00
|
|
|
}
|
|
|
|
|
2014-07-14 15:00:36 +00:00
|
|
|
linksys_get_root_magic() {
|
|
|
|
(get_image "$@" | dd skip=786432 bs=4 count=1 | hexdump -v -n 4 -e '1/1 "%02x"') 2>/dev/null
|
|
|
|
}
|
|
|
|
|
2014-07-13 22:12:56 +00:00
|
|
|
platform_do_upgrade_linksys() {
|
|
|
|
local magic_long="$(get_magic_long "$1")"
|
|
|
|
|
|
|
|
mkdir -p /var/lock
|
|
|
|
local part_label="$(linksys_get_target_firmware)"
|
|
|
|
touch /var/lock/fw_printenv.lock
|
|
|
|
|
|
|
|
if [ ! -n "$part_label" ]
|
|
|
|
then
|
|
|
|
echo "cannot find target partition"
|
|
|
|
exit 1
|
|
|
|
fi
|
|
|
|
|
2014-07-14 15:00:36 +00:00
|
|
|
local target_mtd=$(find_mtd_part $part_label)
|
|
|
|
|
|
|
|
[ "$magic_long" = "73797375" ] && {
|
|
|
|
CI_KERNPART="$part_label"
|
|
|
|
if [ "$part_label" = "kernel1" ]
|
|
|
|
then
|
|
|
|
CI_UBIPART="rootfs1"
|
|
|
|
else
|
|
|
|
CI_UBIPART="rootfs2"
|
|
|
|
fi
|
|
|
|
|
|
|
|
nand_upgrade_tar "$1"
|
|
|
|
}
|
2018-05-13 13:29:30 +00:00
|
|
|
[ "$magic_long" = "27051956" -o "$magic_long" = "0000a0e1" ] && {
|
2014-07-14 15:00:36 +00:00
|
|
|
# check firmwares' rootfs types
|
|
|
|
local target_mtd=$(find_mtd_part $part_label)
|
|
|
|
local oldroot="$(linksys_get_root_magic $target_mtd)"
|
|
|
|
local newroot="$(linksys_get_root_magic "$1")"
|
|
|
|
|
|
|
|
if [ "$newroot" = "55424923" -a "$oldroot" = "55424923" ]
|
|
|
|
# we're upgrading from a firmware with UBI to one with UBI
|
|
|
|
then
|
|
|
|
# erase everything to be safe
|
|
|
|
mtd erase $part_label
|
|
|
|
get_image "$1" | mtd -n write - $part_label
|
|
|
|
else
|
|
|
|
get_image "$1" | mtd write - $part_label
|
|
|
|
fi
|
|
|
|
}
|
2014-07-13 22:12:56 +00:00
|
|
|
}
|
|
|
|
|
2017-06-01 16:39:12 +00:00
|
|
|
platform_copy_config_linksys() {
|
2019-09-04 14:57:40 +00:00
|
|
|
cp -f "$CONF_TAR" "/tmp/syscfg/$BACKUP_FILE"
|
2017-06-01 16:39:12 +00:00
|
|
|
sync
|
2014-07-13 22:12:56 +00:00
|
|
|
}
|