I'm building support for the TL-WPA8630P V2, but I'm a little bit stuck with the sysupgrade functionality.
Debugging this is a bit awkward, because they removed the bootm addr parameter, so only booting from the default address in flash is possible.
When flashing an image created manually with tplink-safeloader -z xxxfactory -o yyysysupgrade via tftp in uboot, it works fine (however yet some small LED, WLAN and MAC address fixes to be done).
This works as the -z aligns the file system to 64k borders, and the firmware partition is successfully split into kernel and rootfs, then split further for rootfs and rootfs_data.
However flashing the automatically built sysupgrade image, either from uboot or from the sysupgrade functionality, fails recognizing the rootfs. In particular, the tplink-safeloader explicitely skips this alignment.
Other, similar hardware (RE450, Archer, etc) seems to work fine using the very same approach, and I cannot see any big difference there I'm afraid.
The sysupgrade image consists of an basic tplink v1 header (only kernel length and starting address filled), but the sqsh root appended straight to it. The tplink v1 header does not contain informtion about the rootfs (start/length), however this is the case for RE450 etc either.
Can anyone shed some light on this?
Should I be looking on why the appened rootfs is not detected, or is something wrong in the sysupgrade (I just added the new board id to the other tp-link boards)?