DietPi OS for VisionFive 2

I found and added the ESWIN ECR6600U firmware to our kernel package: CI | Add ESWIN ECR6600U USB WiFi adapter firmware · MichaIng/linux@eaf275b · GitHub
If this works, I’ll at least try to enable 5 GHz support with the config key you found.
EDIT: 5 GHz does not work: ECR6600U firmware


Also bumped to Linux 5.15.104.


To update the kernel:

cd /tmp
curl -O 'https://dietpi.com/downloads/binaries/linux-image-visionfive2.deb'
dpkg -i linux-image-visionfive2.deb
rm linux-image-visionfive2.deb

I also tested the fixed U-Boot env QSPI address and it works fine now:

apt install libubootenv-tool
echo '/dev/mtd2 0x00000 0x10000 0x10000' > /etc/fw_env.config
# EDIT: With Linux 6.1 it became /dev/mtd1!
fw_printenv

If the command still returns an error or nothing, the (custom) environment is still empty and the U-Boot internal defaults are used. To add the defaults to this space, abort boot via serial console, hitting CTRL+C to enter U-Boot console and run:

env save
boot

Now fw_printenv will show the whole U-Boot environment as result, which can be also stored, so it will show it even if it has been erased from SPI:

fw_printenv > /etc/u-boot-initial-env

But this is not needed to change it via fw_setenv, e.g. to generally add support for compressed kernel images:

fw_setenv kernel_comp_addr_r '0x90000000'
fw_setenv kernel_comp_size '0x10000000'
fw_printenv kernel_comp_addr_r kernel_comp_size
cd /boot
gzip vmlinuz-5.15.104
mv vmlinuz-5.15.104.gz vmlinuz-5.15.104
reboot

=>

Retrieving file: /boot/vmlinuz-5.15.104
7490517 bytes read in 323 ms (22.1 MiB/s)
append: root=PARTUUID=c3534437-01 rootfstype=ext4 rootwait earlycon=sbi console=tty1 console=ttyS0,115200 consoleblank=0 net.ifnames=0
Retrieving file: /usr/lib/linux-image-visionfive2/starfive/jh7110-visionfive-v2.dtb
47949 bytes read in 12 ms (3.8 MiB/s)
   Uncompressing Kernel Image
## Flattened Device Tree blob at 46000000
   Booting using the fdt blob at 0x46000000
   Using Device Tree in place at 0000000046000000, end 000000004600eb4c

Starting kernel ...

Not practicable of course, since our packages ship the kernel necessarily uncompressed, just to show the concept.

1 Like