Anton Aftakhov

After upgrade I have some problem with boot, but I managed to fix it. USB TTL help this a lot. 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.

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)

Ok now I try copy from old card to new. Same problem was on RPi2

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

Thanks a lot! I didn't notice that I need swap TX and RX =) Now Putty see all boot log.

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

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?

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.

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.