The official firmware upgrade procedure is given on http://www.thecus.com/dl.php
Notes of what is done during firmware upgrade by TBM:
"upgrade to debian" firmware
- create a tarball with d-i kernel and d-i initramfs
- create upgrade/version with contents 6.0.0 ?
- create upgrade/up.sh;
create /var/lock/upgrade.lock
flash d-i kernel to "kernel" mtd partition (see nslu2-utils)
flash d-i initramfs to "ramdisk" mtd partition
echo "Buzzer 0" > /proc/thecus_io
sleep 1
echo "Buzzer 1" > /proc/thecus_io
echo success >> /tmp/upgrade/message
remove /var/lock/upgrade.lock
trap exit and fail
- encrypt the tarball so the existing firmware can decrypt it properly.
d-i mods
- pretty much similar to nslu-2 d-i
- flash new kernel/initramfs automatically
- add i2c modules to /etc/modules (if not handled by platform_devices in kernel)
checklist:
- /img/htdocs/adm/setupdfw.html progressbar is timer-based? no chances of showing real progress?
- fcp vs cat? fcp is
- once we have the fintek driver, what is the proper way to start the fan?
- should we generalize nslu2-utils or create thecus_utils?
preferrably generalize, but it needs to be implemented in a way nslu2 changes cannot POSSIBLY break thecus flashing and vice verse!