Ten64’ s built in the initial production run were shipped with the ‘v0.8’ firmware.
The first firmware update (v0.8.5) includes:
-
Introduction of ‘legacy’ mode toggle for Gigabit Ethernet ports and SFP+, see PHY management / ethernet link status in the documentation.
-
Support for gigabit SFPs. Currently requires flashing a different BL2 binary but no further user configuration will be required.
-
Update recovery firmware
- Improvements to bare metal appliance store (note: due to schema change, ‘RTM’ firmware is no longer compatible with the live registry)
- Able to fetch manipulator scripts automatically
- Set locale and default ‘WAN’ interface for cloud-init appliances (among other settings)
- Set legacy/managed mode correctly for each appliance/distribution (most distributions require legacy mode for SFP, some require legacy mode for 1GBASE-T as well)
- Add some missing packages (most notably, u-boot envtools/fw_setenv/fw_printenv)
- Improvements to bare metal appliance store (note: due to schema change, ‘RTM’ firmware is no longer compatible with the live registry)
-
Device Tree: remove broken RTC alert interrupt and change RTC compatible string to “epson,rx8035” explicitly, as drivers which are not aware of the RX8035 will not properly interpret the ‘oscillator stop’ bit. (Requires dkms/update for distributions, TODO, patch here)
-
U-Boot: fix setting of RTC time using the ‘date’ command
-
U-Boot: support booting from SATA drives attached to a PCIe controller (not recommended and not default at this stage, U-Boot has issues working with SATA drives after a warm reboot)
Version v0.8.6 adds:
- Fix deployment of openSUSE from
baremetal-deploy -
baremetal-deploywill not set environment variables (for legacy network modes) if the U-Boot environment appears to be empty or corrupted -
./flash.sh(when flashing from recovery) will prompt you to reset the U-Boot environment to default
Version v0.8.7 updates the recovery image to fix a driver issue with the real time clock (Epson RX-8035) and oscillator stop errors. You should no longer need to do a ‘date reset’ in U-Boot after flashing the firmware.
Version v0.8.8 includes kernel 5.10 based versions of the recovery firmware, OpenWrt for NAND and a workaround for errors seen when writing large amounts of data to SD cards.
Version v0.8.9 includes a performance enhancement for the default network configuration (DPL), device tree fix for kernel 5.15 and improvement to the set-wan command in Recovery
Version v0.8.10 incorporates changes for NAND based OpenWrt. If you are not using OpenWrt from NAND, there is no need to upgrade.
We expect the next major firmware release (v1.0) to update to U-Boot 21.07 among others.
v0.8.10 (2022-03-15) download links
- Tarball for flashing from recovery
- Recovery sdcard image (bzipped)
- Release directory on archive server
- Gitlab release info
The best way to flash the firmware package is to use the recovery firmware. Alternatively, you can write the sdcard image to a card and start your Ten64 in sd-boot mode.
Please see “Firmware Update” in the manual for flashing instructions.
TL;DR?:
- Turn on Ten64, boot into recovery mode from menu
- Set your outgoing network interface with
set-wan ethX(note: best to choose an interface other thaneth0, which is setup as LAN by default) - Download and flash:
root@recovery000afa2424xx:/tmp# curl https://archive.traverse.com.au/pub/traverse/ls1088firmware/firmware-builds/branches/v0.8.10/492260694/firmware-v0.8.10-492260694.tar.xz -O
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 54.4M 100 54.4M 0 0 9937k 0 0:00:05 0:00:05 --:--:-- 11.6M
Note: older recovery firmware versions may have issues downloading due to LetsEncrypt certificate chain issue. If this happens, append -k to the curl command line
root@recovery000afa2424xx:/tmp# tar -Jxf firmware-v0.8.10-492260694.tar.xz
root@recovery000afa2424xx:/tmp# cd firmware-v0.8.10-492260694/
root@recovery000afa2424xx:/tmp/firmware-v0.8.9-413571944# ./flash.sh
Unlocking bl2 ...
Erasing bl2 ...
Unlocking bl2 ...
Writing from arm-trusted-firmware/build/ten64/debug/bl2_qspi.pbl to bl2 ...
Unlocking bl3 ...
Erasing bl3 ...
Unlocking bl3 ...
Writing from arm-trusted-firmware/build/ten64/debug/fip.bin to bl3 ...
Unlocking mcfirmware ...
Erasing mcfirmware ...
Unlocking mcfirmware ...
Writing from qoriq-mc-binary/ls1088a/mc_10.20.4_ls1088a.itb to mcfirmware ...
Unlocking dpl ...
Erasing dpl ...
Unlocking dpl ...
Writing from dpaa2/dpl/eth-dpl-all.dtb to dpl ...
Unlocking dpc ...
Erasing dpc ...
Unlocking dpc ...
Writing from dpaa2/dpc/dpc.0x1D-0x0D.dtb to dpc ...
Unlocking devicetree ...
Erasing devicetree ...
Unlocking devicetree ...
Writing from dtb/fsl-ls1088a-ten64.dtb to devicetree ...
Unlocking recovery ...
Erasing recovery ...
Unlocking recovery ...
Writing from recovery.itb to recovery ...
Do you wish to reflash the OpenWrt-NAND version (do not say "y" if you are currently using it) [y/n] y
ubiformat: mtd9 (nand), size 113246208 bytes (108.0 MiB), 864 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 863 -- 100 % complete
ubiformat: 864 eraseblocks have valid erase counter, mean value is 11
ubiformat: flashing eraseblock 274 -- 100 % complete
ubiformat: formatting eraseblock 863 -- 100 % complete
Do you wish to reset the U-Boot environment to default? [y/n] y
Unlocking ubootenv ...
Erasing ubootenv ...
Warning: Bad CRC, using default environment
But one day I might not have any of USB/SSD options available