Tomte Posted July 14, 2021 Posted July 14, 2021 Hello, I was running Armbian on my cubietruck, I believe Bionic Ubuntu. I wanted to upgrade to latest kernel, so I did a - apt-get update - apt-get upgrade - ambian-config and selected the lastest kernel And that was it. When rebooting, I end up with a try to contact a tftp server. The cubietruck has an SDCard and an SSD. Is there an easy fix or do I need to reinstall it completely, please? If I need to reinstall, do I have to backup all data, or is existing data preserved? (Traccar installation) Regards, Tomte
Werner Posted July 14, 2021 Posted July 14, 2021 Cubietruck is A20 SoC? If so IIRC there was some issue with boot loop. Not sure if related. Without full serial log there is pretty much nothing we can do about.
Tomte Posted July 14, 2021 Author Posted July 14, 2021 (edited) Hello, yes, it is a A20. thanks for your answer, here you go: => boot switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3708 bytes read in 21 ms (171.9 KiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 202 bytes read in 17 ms (10.7 KiB/s) ** File not found /boot/uInitrd ** 7967848 bytes read in 692 ms (11 MiB/s) Found mainline kernel configuration 43983 bytes read in 41 ms (1 MiB/s) 5532 bytes read in 123 ms (43 KiB/s) Applying kernel provided DT fixup script (sun7i-a20-fixup.scr) ## Executing script at 44000000 Wrong Ramdisk Image Format Ramdisk image is corrupt or invalid SCRIPT FAILED: continuing... Card did not respond to voltage select! scanning bus for devices... Device 0: (0:0) Vendor: ATA Prod.: SanDisk SDSSDP12 Rev: 2.0. Type: Hard Disk Capacity: 122104.3 MB = 119.2 GB (250069680 x 512) Found 1 device(s). Device 0: (0:0) Vendor: ATA Prod.: SanDisk SDSSDP12 Rev: 2.0. Type: Hard Disk Capacity: 122104.3 MB = 119.2 GB (250069680 x 512) ... is now current device Scanning scsi 0:1... Device 0: device type unknown ... is now current device ** Bad device usb 0 ** ** Bad device usb 0 ** Speed: 1000, full duplex BOOTP broadcast 1 DHCP client bound to address 192.168.180.97 (15 ms) Using ethernet@01c50000 device TFTP from server 192.168.180.1; our IP address is 192.168.180.97 Filename 'boot.scr.uimg'. Load address: 0x43100000 Loading: * Edited July 14, 2021 by Tomte missing Info
Tomte Posted July 15, 2021 Author Posted July 15, 2021 So I reflashed the SDCard with a current buster, but I can not boot. It is ending up in a boot loop. Please, what can I do? U-Boot SPL 2021.04-armbian (May 06 2021 - 17:01:36 +0000) DRAM: 2048 MiB CPU: 912000000Hz, AXI/AHB/APB: 3/2/2 Trying to boot from MMC1 U-Boot 2021.04-armbian (May 06 2021 - 17:01:36 +0000) Allwinner Technology CPU: Allwinner A20 (SUN7I) Model: Cubietech Cubietruck I2C: ready DRAM: 2 GiB MMC: mmc@1c0f000: 0, mmc@1c12000: 1 Loading Environment from FAT... Card did not respond to voltage select! : -110 HDMI connected: Setting up a 1600x1200 dvi console (overscan 0x0) In: serial Out: vga Err: vga Allwinner mUSB OTG (Peripheral) Net: eth0: ethernet@1c50000, eth1: usb_ether 230454 bytes read in 22 ms (10 MiB/s) starting USB... Bus usb@1c14000: USB EHCI 1.00 Bus usb@1c14400: USB OHCI 1.0 Bus usb@1c1c000: USB EHCI 1.00 Bus usb@1c1c400: USB OHCI 1.0 scanning bus usb@1c14000 for devices... 1 USB Device(s) found scanning bus usb@1c14400 for devices... 2 USB Device(s) found scanning bus usb@1c1c000 for devices... 1 USB Device(s) found scanning bus usb@1c1c400 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3967 bytes read in 3 ms (1.3 MiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 154 bytes read in 3 ms (49.8 KiB/s) 9932361 bytes read in 848 ms (11.2 MiB/s) 7973464 bytes read in 681 ms (11.2 MiB/s) Found mainline kernel configuration 43983 bytes read in 8 ms (5.2 MiB/s) 5532 bytes read in 9 ms (599.6 KiB/s) Applying kernel provided DT fixup script (sun7i-a20-fixup.scr) ## Executing script at 45000000 ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 9932297 Bytes = 9.5 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 data abort pc : [<bef89cec>] lr : [<00000011>] reloc pc : [<4a013cec>] lr : [<8b08a011>] sp : baf4aa18 ip : 00000000 fp : befdd678 r10: 00000020 r9 : baf55ec0 r8 : befea28c r7 : 6c616972 r6 : 00000010 r5 : 2756f9ea r4 : baf59070 r3 : baf59078 r2 : baf59068 r1 : baf9f920 r0 : 00000019 Flags: nzCv IRQs off FIQs off Mode SVC_32 (T) Code: d005 f027 0501 441d (686d) 07ed Resetting CPU ... resetting ... U-Boot SPL 2021.04-armbian (May 06 2021 - 17:01:36 +0000) DRAM: 2048 MiB CPU: 912000000Hz, AXI/AHB/APB: 3/2/2 Trying to boot from MMC1
Werner Posted July 15, 2021 Posted July 15, 2021 Boot loop is a known issue. Either wait for next release or build an image yourself from master which has a workaround included.
Tomte Posted July 15, 2021 Author Posted July 15, 2021 Wow, that was quick. Ok, how long would I have to wait? Can I use an old release? which one? I don't have a running build environment. Regards, Tomte
Werner Posted July 15, 2021 Posted July 15, 2021 Release is expected by end of August. Check here: https://armbian.systemonachip.net/archive/cubietruck/archive/ No idea though which was last working. If you find one make sure to freeze firmware via armbian-config so you dont run into the same bootloop again once kernel packages are upgraded via standard apt upgrade.
Tomte Posted July 15, 2021 Author Posted July 15, 2021 I went back to: Armbian_21.02.3_Cubietruck_buster_current_5.10.21.img.xz That one is booting. Did "Freeze" Thanks!
Recommended Posts