Star64: 4GB on 8GB boards
06-06-2023, 12:19 AM
This is due to u-boot not updating the dtb file.
The current flow is
1) uboot reads the eeprom and determines which model you have (4/8gb)
2) uboot finds your dts file through various means (distroboot, extlinux etc)
3) uboot updates the dts file with the correct memory: "fdt memory ${memory_addr} ${memory_size};"
4) uboot "saves" the updated dtb file to /dtbs/${fdtfile}
5) uboot boots the kernel
If your distro doesn't follow the boot process exactly like starfive images, then the above wont happen, and you will be left with 4Gb ram.
You can see the uboot commands executed on boot here:
https://github.com/Fishwaldo/u-boot/blob...r64.h#L141
(also, another thread talked about instability with ethernet - thats also due to uboot commands not executing correctly to setup the ethernet ports - it was a issue on VF2, but doesn't exist on Star64 - until someone "ports" uboot properly to Star64, we are stuck with that).
The current flow is
1) uboot reads the eeprom and determines which model you have (4/8gb)
2) uboot finds your dts file through various means (distroboot, extlinux etc)
3) uboot updates the dts file with the correct memory: "fdt memory ${memory_addr} ${memory_size};"
4) uboot "saves" the updated dtb file to /dtbs/${fdtfile}
5) uboot boots the kernel
If your distro doesn't follow the boot process exactly like starfive images, then the above wont happen, and you will be left with 4Gb ram.
You can see the uboot commands executed on boot here:
https://github.com/Fishwaldo/u-boot/blob...r64.h#L141
(also, another thread talked about instability with ethernet - thats also due to uboot commands not executing correctly to setup the ethernet ports - it was a issue on VF2, but doesn't exist on Star64 - until someone "ports" uboot properly to Star64, we are stuck with that).
