JBraun

Hello martinayotte, thanks for the fast reply. I modified the file /boot/armbianEnv.txt with verbosity=7 and console=serial as suggested. I used putty on an other device. This is connected to the UART0 on cubietruck (4 pin header close to the USB ports). I think, that this is the serial-debug. Right? No luck. The kernel is not starting. The output is still the same. See attachment. armbianEnv.txt log_from_putty_with_verbosity=7_console=serial.txt

On my cubietruck I have tried the Armbian_5.75_Cubietruck_Debian_stretch_next_4.19.20. For me it looks that u-boot loads the files, but the kernel will/can not start. Attached the output from the console. Rarly I get some additional output on the console like "Uncompressing Linux... done, booting the kernel." but nothing happens, or some wild output from wrong instructions which leads to a reset. I have also tried "Armbian_5.59_Cubietruck_Ubuntu_xenial_default_3.4.113_desktop" to exclude some mainline / legacy kernel issues. But no luck. With some older versions (e.g. 5.20) I have no luck also. From my feeling there is a basic thing, may be: timing (RAM, SD-card) RTC / empty batterie problem with the NAND in the background / or the bootloader from there interferes missing some requirements After reading dozens of topics from the forum and spending a lot of hours for a search in the web, a have no idea how to go further to solve this issue. Any hints what I can check / do? What works: I am able to boot an old armbian (legacy kernel) from NAND. There , I can mount the SD-card and read and write. I am able to boot an linaro (older) from SD-card without problems. I have seen that the clock is not up to date. The time started an bootup. How I have tested: To the cubietruck I have only connected SD-card, HDMI, network, power supply and UART0 console with putty. I have burned image with win32imager (version 1.0) and verified. I have used different SD-cards (brands, sizes, classes). I have used different power supplies on the power connector => same result. Regards, Joerg printenv.txt u-boot_log.txt

I have an similar issue. I am using an Cubietruck. It works fine with an older NAND image. I am trying to start ARMBIAN (different versions, e.g. Armbian_5.75_Cubietruck_Debian_stretch_next_4.19.20) from a SD card (2 different ones). I have also used different power supplies. The last message on HDMI and Console is "starting kernel" but nothing happens. Sometimes with an reboot sometimes not. Also an USB mouse and keyboard will not activated. So I assume the kernel is not started. So I reboot to the old installation. After that I can read and manipulate some files. So I assume the card is OK. So have the feeling, that there is something not fine with the configuration or with the NAND (what should not be involved). I have read a lot of web pages, but with no luck to find a solution I have no idea what I can do / check. Best regards Jörg from my console: after the last line will nothing happen (at least some minutes)