You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am unsure whether it is a bug in the web managment or in the base/build system/buils management. However, while the linked factory images for the cpe510/520 device on the device website:
Unlike the factory image, the sysupgrade image is a raw flash image. It starts with the kernel, which happens to be in ELF format on this platform. The size difference between the images is also expected.
We had to change the flash layout for CPE210/CPE510/... with OpenWrt 18.06.0, requiring some adjustments to the sysupgrade code that checks image validity as well. The validation code update was backported to LEDE 17.01.5.
You have two options for the update:
First upgrade to 17.01.5, then to a newer OpenWrt release
Use sysugrade -F to skip the validation (somewhat more dangerous)
In both cases, the sysupgrade image is the correct one - the factory image has different format that is only understood by TP-Link's stock firmware.
frufo:
Dear openwrt Team,
I am unsure whether it is a bug in the web managment or in the base/build system/buils management. However, while the linked factory images for the cpe510/520 device on the device website:
https://openwrt.org/toh/tp-link/cpe510
seem to be valid images (size 4MB), there seems to be something wrong with the linked sysupgrade images, e.g:
http://downloads.openwrt.org/releases/19.07.3/targets/ar71xx/generic/openwrt-19.07.3-ar71xx-generic-cpe510-520-v1-squashfs-sysupgrade.bin
they are almost 8MB in size and seem to be rather ELF-binaries than flash-images or am I mistaken?
Flashing in my case from: LEDE Reboot 17.01.4
consequently fails with the error message:
The uploaded image file does not contain a supported format. Make sure that you choose the generic image format for your platform.
I did not dare to try the factory-image instead as according to posts in the forum this is not advisable (risk of bricking the device).
Thank you very much
Frufo
The text was updated successfully, but these errors were encountered: