Platform_do_upgrade_allnet issues

For Developers
1

Hi,
I am adding support for a device that does checksum verification of kernel and rootfs.
Unfortunately,it looks like platform_do_upgrade_allnet in OpenWRT is broken.
All goes good when sysupgrading until changes are supposed to be written in U-boot environment.
You can see that fw_setenv is allegedly missing but I can write using it manually without issues.
Has anybody encountered issue like this?

Watchdog handover: fd=3
- watchdog -
killall: telnetd: no process killed
killall: dropbear: no process killed
Sending TERM to remaining processes ... odhcpd ntpd dnsmasq udhcpc ubusd logd rpcd netifd 
Sending KILL to remaining processes ... 
Switching to ramdisk...
Performing system upgrade...
ash: fw_setenv: not found
failed to update U-Boot environment
Upgrade completed
Rebooting system...
umount: can't unmount /dev: Resource busy
umount: can't unmount /tmp: Resource busy
[ 1805.311523] reboot: Restarting system
1 Like
2

@robimarko Hi, I am adding this upgrade platform right now to ath79, but under a generic name

the problem you describe was fixed when Sven added Plasma Cloud PA300
(the binary and config for fw_setenv must be copied to the ramdisk)

I believe the similar ALLNET devices use exactly the same upgrade method as other brands that use boards / SDK from Senao

I used his script as a base to make one that works for boards with the "failsafe" partition instead of dualboot

3

Thanks,
I manually did a checksum generation and write and then flashed manually once the bug was fixed.

4

did you add support for this device already?

would you be able to test a factory.bin and sysupgrade.bin made from my commits?

5

Unfortunately not, the customer did not want to upstream and I did not have free time then.
It was a while ago and I don't have access to the devices anymore.