Closed botischroeder closed 2 years ago
@chunkeey: You recently made some changes for that target related to partitions. Could you please check if your changes are causing the boot loop? Thank you!
very likely yes. The vr2600v ran out of space for its kernel partition on the flash. From you bootlog, I can see that the uImage mtdsplitter doesn't pick up on the uImage header. I didn't notice this earlier, but there's an 512-byte padding in front of the sysupgrade production rule under image/generic.mk. I "think" this fixed it?
Can you apply this patch, compile an image for your vr2600v and report back whenever this helped?
diff --git a/target/linux/ipq806x/files/arch/arm/boot/dts/qcom-ipq8064-vr2600v.dts b/target/linux/ipq806x/files/arch/arm/boot/dts/qcom-ipq8064-vr2600v.dts
index 8fa0a5d291..a3fd867e2a 100644
--- a/target/linux/ipq806x/files/arch/arm/boot/dts/qcom-ipq8064-vr2600v.dts
+++ b/target/linux/ipq806x/files/arch/arm/boot/dts/qcom-ipq8064-vr2600v.dts
@@ -257,7 +257,8 @@
partition@320000 {
label = "firmware";
reg = <0x320000 0xc60000>;
- compatible = "denx,uimage";
+ compatible = "openwrt,uimage";
+ openwrt,offset = <512>; /* account for pad-extra 512 */
};
/* hole 0xf80000 - 0xfaf100 */
Thank you for your super fast response! The patch fixes both problems.
The same fix was just merged.
The TP-Link Archer VR2600v is stuck in a boot loop on written snapshot image. It's able to boot using the snapshot uimage though, but there ath10k firmware can't be found. 21.02.2 release version doesn't have either problem. @chunkeey: You recently made some changes for that target related to partitions. Could you please check if your changes are causing the boot loop? Thank you!
Log from openwrt-ipq806x-generic-tplink_vr2600v-squashfs-sysupgrade.bin
Log from openwrt-ipq806x-generic-tplink_vr2600v-initramfs-uImage