2016-05-13 06:13:15 +00:00
|
|
|
#
|
|
|
|
# Copyright (C) 2014-2015 OpenWrt.org
|
|
|
|
#
|
|
|
|
|
|
|
|
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
|
|
|
|
|
|
|
|
cur_boot_part=$(/usr/sbin/fw_printenv -n boot_part)
|
|
|
|
if [ -z "${cur_boot_part}" ] ; then
|
2023-02-15 03:06:05 +00:00
|
|
|
mtd_ubi0=$(cat /sys/class/ubi/ubi0/mtd_num)
|
2022-02-05 17:42:42 +00:00
|
|
|
case $(grep -E ^mtd${mtd_ubi0}: /proc/mtd | cut -d '"' -f 2) in
|
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
|
|
|
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}"
|
2016-05-13 06:13:15 +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
|
|
|
|
auto_recovery yes
|
|
|
|
EOF
|
|
|
|
printf "kernel2"
|
|
|
|
return
|
|
|
|
;;
|
|
|
|
2)
|
|
|
|
fw_setenv -s - <<-EOF
|
|
|
|
boot_part 1
|
|
|
|
auto_recovery yes
|
|
|
|
EOF
|
|
|
|
printf "kernel1"
|
|
|
|
return
|
|
|
|
;;
|
|
|
|
*)
|
|
|
|
return
|
|
|
|
;;
|
|
|
|
esac
|
2016-05-13 06:13:15 +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
|
|
|
|
|
|
|
|
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
|
|
|
|
|
2016-12-08 08:41:58 +00:00
|
|
|
|
|
|
|
# remove "squashfs" vol (in case we are flashing over a stock image, which is also UBI)
|
|
|
|
|
|
|
|
local mtdnum="$( find_mtd_index "$CI_UBIPART" )"
|
|
|
|
if [ ! "$mtdnum" ]; then
|
|
|
|
echo "cannot find ubi mtd partition $CI_UBIPART"
|
|
|
|
return 1
|
|
|
|
fi
|
|
|
|
|
|
|
|
local ubidev="$( nand_find_ubi "$CI_UBIPART" )"
|
|
|
|
if [ ! "$ubidev" ]; then
|
|
|
|
ubiattach -m "$mtdnum"
|
|
|
|
sync
|
|
|
|
ubidev="$( nand_find_ubi "$CI_UBIPART" )"
|
|
|
|
fi
|
|
|
|
|
|
|
|
if [ "$ubidev" ]; then
|
|
|
|
|
|
|
|
local squash_ubivol="$( nand_find_volume $ubidev squashfs )"
|
|
|
|
|
|
|
|
# kill volume
|
|
|
|
[ "$squash_ubivol" ] && ubirmvol /dev/$ubidev -N squashfs || true
|
|
|
|
fi
|
|
|
|
|
|
|
|
|
|
|
|
# complete std upgrade
|
2023-03-27 01:12:48 +00:00
|
|
|
if nand_upgrade_tar "$1" ; then
|
|
|
|
nand_do_upgrade_success
|
|
|
|
else
|
|
|
|
nand_do_upgrade_failure
|
|
|
|
fi
|
|
|
|
|
2016-05-13 06:13:15 +00:00
|
|
|
}
|
|
|
|
[ "$magic_long" = "27051956" ] && {
|
2021-03-20 10:48:26 +00:00
|
|
|
get_image "$1" | mtd write - $part_label
|
2016-05-13 06:13:15 +00:00
|
|
|
}
|
|
|
|
}
|