john.glasson Posted December 25, 2017 Posted December 25, 2017 Armbian documentation on Overlays refers to /boot/armbianEnv.txt. But in the version of Armbian that I'm running (on a Cubietruck, ARMBIAN 5.36 user-built Debian GNU/Linux 8 (jessie) 4.13.16-sunxi) there is no such file. There is however a copy in directory /usr/share/armbian. Is this the overlay file that is processed at start-up? If so, it would be good if the documentation was updated.
tkaiser Posted December 25, 2017 Posted December 25, 2017 Quoting the documentation: DT overlays are a Work-in-Progress (WIP) feature, present only in fresh images starting with 5.30, nightly and user made images For older images (even upgraded to 5.30 or later) manual update of the u-boot and the boot script is required
john.glasson Posted December 30, 2017 Author Posted December 30, 2017 I'm still puzzled by the boot sequence for my CubieTruck (Armbian 5.36, 4.13.16-sunxi). As discussed above, it has no armbianEnv.txt so it's clearly not using the DT overlays. But nor does it have a valid copy of script.bin: the link points to a file in non-existent directory /boot/bin (see below). Grateful for an explanation! root@fs:/boot# ls -al total 30512 drwxr-xr-x 4 root root 4096 Dec 24 16:10 . drwxr-xr-x 24 root root 4096 Aug 15 09:34 .. -rw-r--r-- 1 root root 6944 Sep 15 2016 boot.bmp -rw-r--r-- 1 root root 2796 Sep 15 2016 boot.cmd -rw-r--r-- 1 root root 2868 Sep 15 2016 boot.scr -rw-r--r-- 1 root root 156631 Nov 24 18:51 config-4.13.16-sunxi lrwxrwxrwx 1 root root 17 Nov 29 18:41 dtb -> dtb-4.13.16-sunxi drwxr-xr-x 3 root root 12288 Nov 29 18:34 dtb-4.13.16-sunxi drwxr-xr-x 2 root root 4096 Jun 15 2017 dtb-4.9.12-sunxi lrwxrwxrwx 1 root root 16 Jun 24 2017 dtb.old -> dtb-4.11.6-sunxi -rw-r--r-- 1 root root 4449039 Dec 8 16:33 initrd.img-4.13.16-sunxi -rw-r--r-- 1 root root 4163902 Feb 14 2017 initrd.img-4.8.4-sunxi -rw-r--r-- 1 root root 4075334 May 14 2017 initrd.img-4.9.12-sunxi -rw-r--r-- 1 root root 4086657 Feb 14 2017 initrd.img-4.9.7-sunxi -rw-r--r-- 1 root root 0 Nov 29 18:43 .next lrwxrwxrwx 1 root root 18 Sep 15 2016 script.bin -> bin/cubietruck.bin -rw-r--r-- 1 root root 3015924 Nov 24 18:51 System.map-4.13.16-sunxi lrwxrwxrwx 1 root root 21 Dec 8 16:33 uInitrd -> uInitrd-4.13.16-sunxi -rw-r--r-- 1 root root 4449103 Dec 8 16:33 uInitrd-4.13.16-sunxi -rw-r--r-- 1 root root 0 Jun 15 2017 .verbose -rwxr-xr-x 1 root root 6790944 Nov 24 18:51 vmlinuz-4.13.16-sunxi lrwxrwxrwx 1 root root 21 Nov 29 18:43 zImage -> vmlinuz-4.13.16-sunxi root@fs:/boot#
martinayotte Posted December 30, 2017 Posted December 30, 2017 It looks like you are using an old u-boot from Sept 2016. Is this a system that you've upgraded only the kernel without upgrading the u-boot ?
john.glasson Posted December 30, 2017 Author Posted December 30, 2017 If I run apt-get install linux-u-boot-cubietruck-next, response is that I already have latest version installed.
martinayotte Posted December 30, 2017 Posted December 30, 2017 Ok ! I was asking because I don't own any cubietruck, and on almost all boards I own, the u-boot version is now 2017.11.
john.glasson Posted December 31, 2017 Author Posted December 31, 2017 On 06/09/2017 at 9:26 PM, tkaiser said: --- My version 22-Nov-2017 so that looks ok.
Recommended Posts