Anton Aftakhov Posted June 26, 2017 Share Posted June 26, 2017 Hello. I have my cubietruck (cubieboard 3) configured to boot from sd card, and other files stored on hdd (sata). Few weeks ago (~15.06.2017) I updated armbian by "apt-get dist-upgrade". It worked well until I switch power off. Now it can't boot from sd card. If I remove it - boot from nand is ok. Whet sd card installed - no activity on display, just blinkin LAN port. If I boot from nand, I cat mount both SD and HDD and explore filesystem. But I can't find any logs, updated since 17.06 (time then I switch it off). My guess problem is new kernel, from 4.11.4 to 4.11.5. Please help me fix this, I can take files and content from SD and HDD, but I don't know what exactly information needed to try to help me. Link to comment Share on other sites More sharing options...
Igor Posted June 26, 2017 Share Posted June 26, 2017 We haven't notice any problems - I am running Cubietruck with 4.11.5 for test, I made upgrade to latest kernel 4.11.6 and install to USB drive. http://sprunge.us/RePh Everything is o.k. Try to get some verbose logs from serial console - without is hard to find what went wrong. 1 Link to comment Share on other sites More sharing options...
Anton Aftakhov Posted June 26, 2017 Author Share Posted June 26, 2017 How can I connect to serial console without USB TTL cable? Can USB OTG handle this? Sorry, but I'm such a newbie in this things. Cubietruck works well for 1 year, until now. Link to comment Share on other sites More sharing options...
Igor Posted June 26, 2017 Share Posted June 26, 2017 14 minutes ago, Anton Aftakhov said: How can I connect to serial console without USB TTL cable? Can USB OTG handle this? Sorry, but I'm such a newbie in this things. Cubietruck works well for 1 year, until now. USB OTG can't handle this. Debugging without serial console is hard ... it cost around 1 USD and will save you a lot of time. Get one, get exactly this one. One option is to edit /boot/armbianEnv.txt on your SD card and change verbosity to 9 and console to display and boot. Than make a photo with your mobile and attach it here. We still might see something. 1 Link to comment Share on other sites More sharing options...
Anton Aftakhov Posted June 26, 2017 Author Share Posted June 26, 2017 I don't have /boot/armbianEnv.txt file on SD card https://monosnap.com/file/xdAUeTEBX6CzTPM3THbCPrldPJes8y (with hidden files there also .verbose and .next) boot.cmd https://gist.github.com/simple-elf/beb273eee7f6942a02f36666fff32c4d Can I change boot.cmd for displaing console to hdmi monitor? Link to comment Share on other sites More sharing options...
Igor Posted June 26, 2017 Share Posted June 26, 2017 You have some old build but still - it should work. Remove "console=ttyS0,115200" from uboot.cmd and rebuild it. For verbosity - you only need to create an empty file /boot/.verbose ... even u-boot should put something out on the HDMI screen, at least logo? If we don't have anything on the screen, this could look like u-boot trouble. With serial console we would already solve the problem Try updating it manually, from some archive one. http://apt.armbian.com/pool/main/l/linux-u-boot-cubietruck-next/ 1 Link to comment Share on other sites More sharing options...
Anton Aftakhov Posted July 9, 2017 Author Share Posted July 9, 2017 There is no logo on hdmi screen on boot (from sd card). I check u-boot version - it's 5.16 on sd card (also on hdd) So now I have USB TTL adapter (cp2102) with 5 pin connector, I connected 3 pins to cubieboard (GND, TX, RX, 3v and 5v pins not connected) and connected to COM3 (115200) from putty (windows 10 installs drivers automatically). Putty screen is kept blank. I tryied to boot system from nand (don't remember disto), from old sd card, from new sd card with fresh armbian image (it has /boot/armbianEnv.txt). Putty still showing blank On my cp2102 GND led is always on. After I unplug the AC connector from cubietruck I see some sumbols in putty screen - ▒▒▒ - until AC power connected back Link to comment Share on other sites More sharing options...
zador.blood.stained Posted July 9, 2017 Share Posted July 9, 2017 1 hour ago, Anton Aftakhov said: So now I have USB TTL adapter (cp2102) with 5 pin connector, I connected 3 pins to cubieboard (GND, TX, RX, 3v and 5v pins not connected) and connected to COM3 (115200) from putty (windows 10 installs drivers automatically). Putty screen is kept blank. How exactly did you connect the serial adapter to the cubietruck? GND-GND TX-RX RX-TX? 1 Link to comment Share on other sites More sharing options...
Anton Aftakhov Posted July 9, 2017 Author Share Posted July 9, 2017 Thanks a lot! I didn't notice that I need swap TX and RX =) Now Putty see all boot log. Link to comment Share on other sites More sharing options...
Anton Aftakhov Posted July 9, 2017 Author Share Posted July 9, 2017 So boot with old sd card show this log U-Boot SPL 2017.05-armbian (Jun 15 2017 - 02:38:14) DRAM: 2048 MiB CPU: 912000000Hz, AXI/AHB/APB: 3/2/2 Trying to boot from MMC1 And nothing else Link to comment Share on other sites More sharing options...
Igor Posted July 9, 2017 Share Posted July 9, 2017 Most likely your SD card did not survived upgrade. Do you have another (good and quality) SD card, that we can rule out this the most common issue - SD card failure. It's very very common. Edit: BTW in last 1-2 years I trashed Samsung EVO 32, Sandisk Ultra 8, Sandisk Extreme PRO and few no name which I use for testing. 1 Link to comment Share on other sites More sharing options...
Anton Aftakhov Posted July 9, 2017 Author Share Posted July 9, 2017 Ok now I try copy from old card to new. Same problem was on RPi2 Link to comment Share on other sites More sharing options...
Anton Aftakhov Posted July 9, 2017 Author Share Posted July 9, 2017 Boot from new sd card is OK! Thanks a lot. Now question about upgrade =) apt-get upgrade -y Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 0 B/323 kB of archives. After this operation, 0 B of additional disk space will be used. dpkg: error processing package linux-jessie-root-next-cubietruck (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration Errors were encountered while processing: linux-jessie-root-next-cubietruck E: Sub-process /usr/bin/dpkg returned an error code (1) Same output was before I faced my boot problem =) UPDATE: dpkg --remove --force-remove-reinstreq linux-jessie-root-next-cubietruck && apt-get install linux-jessie-root-next-cubietruck fixes my problem (also I renamed /usr/src/linux-headers-4.11.5-sunxi - it was in conflicts logs) Link to comment Share on other sites More sharing options...
Anton Aftakhov Posted July 9, 2017 Author Share Posted July 9, 2017 After upgrade I have some problem with boot, but I managed to fix it. USB TTL help this a lot. Spoiler U-Boot SPL 2017.05-armbian (Jun 15 2017 - 02:38:14) DRAM: 2048 MiB CPU: 912000000Hz, AXI/AHB/APB: 3/2/2 Trying to boot from MMC1 U-Boot 2017.05-armbian (Jun 15 2017 - 02:38:14 +0200) Allwinner Technology CPU: Allwinner A20 (SUN7I) Model: Cubietech Cubietruck I2C: ready DRAM: 2 GiB MMC: SUNXI SD/MMC: 0 *** Warning - bad CRC, using default environment Setting up a 1024x768 vga console (overscan 0x0) In: serial Out: vga Err: vga SCSI: SATA link 0 timeout. AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode flags: ncq stag pm led clo only pmp pio slum part ccc apst Net: eth0: ethernet@01c50000 Hit any key to stop autoboot: 0 6944 bytes read in 156 ms (43 KiB/s) switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 2442 bytes read in 181 ms (12.7 KiB/s) ## Executing script at 43100000 1 bytes read in 126 ms (0 Bytes/s) 0 bytes read in 130 ms (0 Bytes/s) ** File not found /boot/dtb/sun7i-a20-cubietruck.dtb ** ** Unrecognized filesystem type ** ** File not found /dtb/sun7i-a20-cubietruck.dtb ** 4307874 bytes read in 518 ms (7.9 MiB/s) 6264064 bytes read in 664 ms (9 MiB/s) ## Loading init Ramdisk from Legacy Image at 42000000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 4307810 Bytes = 4.1 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ERROR: Did not find a cmdline Flattened Device Tree Could not find a valid device tree SCRIPT FAILED: continuing... scanning bus for devices... timeout exit! Found 0 device(s). Device 0: not available starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 USB2: USB EHCI 1.00 USB3: USB OHCI 1.0 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 2 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found USB device 0: unknown device ethernet@01c50000 Waiting for PHY auto negotiation to complete..... done Speed: 1000, full duplex BOOTP broadcast 1 data abort pc : [<bef96974>] lr : [<0000ecc2>] reloc pc : [<4a04c974>] lr : [<8b0c4cc2>] sp : baf1fbc0 ip : 00000000 fp : befed0f8 r10: befecc4c r9 : baf29ee0 r8 : 0000000e r7 : befeef84 r6 : befeef8c r5 : 00000000 r4 : befed14e r3 : 00060101 r2 : 00000008 r1 : befed0fe r0 : 0000000e Flags: nZCv IRQs off FIQs off Mode SVC_32 Resetting CPU ... Problem was, that symlink 'dtb' was linked to deleted 'dtb-4.11.4-sunxi'. I changed symlink to 'dtb-4.11.5-sunxi' and also renamed 'sun7i-a20-cubietruck.dtb.dpkg-new' to 'sun7i-a20-cubietruck.dtb' (don't know why this folder contains only *.dpkg-new files, maybe because I was trying fix boot without ttl console before). Now all works ok (maybe until next upgrade), thanks a lot for help. 1 Link to comment Share on other sites More sharing options...
Recommended Posts