Armbian for Amlogic S805

[balbes150]

Updated the images on the website. Added to the website image with simple system to create a full backup of the internal memory (ddBR) based on the console version Armbian + webmin. WebMin can be installed on any image independently.

 

https://yadi.sk/d/DnCkh3KBvAFES

 

 

P. S. I Propose to rename this topic "Armbian for Amlogic S805"

[mdel]

hello

 

i've tried to boot your lastest Armbian_5.20_Vegas805_Ubuntu_xenial_3.10.102_20160923.img image on my S85 box, from the sd card (same sd card i've been using for openelec on this box).

 

unfortunately the result is always the same, "google tv" splash for a few seconds then "no hdmi" output and no activity visible.

i've tried with my dtb and all the dtbs included in your image.

 

so i've soldered a serial and dumped the boot logs :

 

android boot log (ends with a proper "shutdown") : http://paste.ubuntu.com/23224373/

 

ubuntu image log : http://paste.ubuntu.com/23224374/

 

i wanted to test some commands to load my dtb and boot the kernel manually but for some reason i have a very hard time interrupting the boot, when i use "enter" it does nothing and boots, and when i use space, it stops the boot process but i don't get a prompt and can't type anything (i'm using screen).

 

i can interrupt with enter but then i can't type anything on the prompt, i'll try some different serial configurations.

 

i hope it helps.

Edited September 24, 2016 by mdel

[balbes150]

How have You organized multiboot ? In the log I don't see the activation script s805_autoscript. Which settings and which program (system) are You using for the UART ?

[mdel]

i believe i installed your aml_autoscript update through android

 

here's my /dev/block/env from adb :

 

 

 

root@m201:/ # strings /dev/block/env
1080ioutputheight=1047
1080ioutputwidth=1863
1080ioutputx=28
1080ioutputy=16
576ioutputheight=559
576ioutputwidth=699
576ioutputx=10
576ioutputy=8
720poutputheight=719
720poutputwidth=1279
720poutputx=0
720poutputy=0
baudrate=115200
bootcmd=run start_autoscript; run storeboot
bootdelay=1
bootfile=boot.img
bootfromnand=0
bootm_low=0x00000000
bootm_size=0x80000000
bootpath=u-boot.bin
bootsd=setenv bootargs ${bootargs} reboot_mode=${reboot_mode}; if test ${reboot_mode} != switch_system; then if mmcinfo; then if fatload mmc 0 ${loadaddr} kernel.img; then setenv bootargs ${bootargs} bootfromsd; bootm; fi;fi;fi;
bootsize=100000
bootstart=0
cecconfig=cec0
chipname=8726m8
console=ttyS0,115200n8
cvbs_drv=0
cvbsmode=576cvbs
digitaudiooutput=PCM
display_bpp=24
display_color_bg=0
display_color_fg=0xffff
display_color_format_index=24
display_height=1080
display_layer=osd2
display_width=1920
ethaddr=00:15:18:01:81:31
fb_addr=0x7900000
fb_height=720
fb_width=1280
firstboot=0
gatewayip=10.18.9.1
get_dt=checkhw
has.accelerometer=false
hdmimode=1080p50hz
hostname=arm_m8
initargs=init=/init console=ttyS0,115200n8 no_console_suspend storage=2
initrd_high=60000000
ipaddr=10.18.9.97
loadaddr=0x12000000
loadaddr_logo=0x13000000
mmcargs=setenv bootargs console=${console} boardname=m8_board
netmask=255.255.255.0
normalsize=400000
normalstart=1000000
outputmode=576cvbs
p0path=uImage
p0size=400000
p0start=1000000
p1path=android.rootfs
p1size=8000000
p1start=1400000
partnum=2
preboot=if itest ${upgrade_step} == 3; then run prepare; run storeargs; run update; fi; if itest ${upgrade_step} == 1; then defenv; setenv upgrade_step 2; saveenv;fi; run prepare;run storeargs;get_rebootmode; clear_rebootmode; echo reboot_mode=${reboot_mode};run update_key; run switch_bootmode
preloaddtb=imgread dtb boot ${loadaddr}
prepare=logo size ${outputmode}; video open; video clear; video dev open ${outputmode};imgread res logo ${loadaddr_logo}; unpackimg ${loadaddr_logo}; logo source ${outputmode}; bmp display ${bootup_offset}; bmp scale;
reboot_mode=normal
recovery=echo enter recovery;if mmcinfo; then if fatload mmc 0 ${loadaddr} recovery.img; then bootm;fi;fi; if usb start 0; then if fatload usb 0 ${loadaddr} recovery.img; then bootm; fi;fi;if imgread kernel recovery ${loadaddr}; then bootm; else echo no recovery in flash; fi;
sdc_burning=sdc_burn ${sdcburncfg}
sdcburncfg=aml_sdc_burn.ini
serverip=10.18.9.113
start_autoscript=if usb start; then run start_usb_autoscript; fi; if mmcinfo; then run start_mmc_autoscript; fi;
start_mmc_autoscript=if fatload mmc 0 11000000 s805_autoscript; then autoscr 11000000; fi;
start_usb_autoscript=if fatload usb 0 11000000 s805_autoscript; then autoscr 11000000; fi;
store=2
storeargs=setenv bootargs ${initargs} cvbsdrv=${cvbs_drv} vdaccfg=${vdac_config} logo=osd1,loaded,${fb_addr},${outputmode},full hdmimode=${hdmimode} cvbsmode=${cvbsmode} androidboot.firstboot=${firstboot} hdmitx=${cecconfig}
storeboot=echo Booting...; if unifykey get usid; then setenv bootargs ${bootargs} androidboot.serialno=${usid};fi;run bootsd;imgread kernel boot ${loadaddr};bootm;run recovery
switch_bootmode=if test ${reboot_mode} = factory_reset; then run recovery;else if test ${reboot_mode} = update; then run update;else if test ${reboot_mode} = usb_burning; then run usb_burning;else if test ${wipe_data} = failed; then echo wipe_data=${wipe_data}; run recovery;else fi;fi;fi;fi
testaddr=0x12400000
update=run usb_burning; if mmcinfo; then if fatexist mmc 0 ${sdcburncfg}; then run sdc_burning; else if fatload mmc 0 ${loadaddr} aml_autoscript; then autoscr ${loadaddr}; fi;run recovery;fi;else run recovery;fi;
update_key=saradc open 0; if saradc get_in_range 0 0x50; then msleep 50; if saradc get_in_range 0 0x50; then echo update by key...; run update; fi;fi
upgrade_step=0
usb_burning=update 1000
vdac_config=0x10
video_dev=tvout
wipe_data=success 

 

 

 

i can see :

bootcmd=run start_autoscript; run storeboot

start_autoscript=if usb start; then run start_usb_autoscript; fi; if mmcinfo; then run start_mmc_autoscript; fi;

start_mmc_autoscript=if fatload mmc 0 11000000 s805_autoscript; then autoscr 11000000; fi;

start_usb_autoscript=if fatload usb 0 11000000 s805_autoscript; then autoscr 11000000; fi;

 

should it echo anything ? maybe inside the s805_autoscript, i haven't checked that.

 

For the serial i'm using the basic command :

screen /dev/ttyUSB0 115200 8N1

 

i can interrupt boot by slamming "enter", then i get to a prompt but can't type anything, tried to disconnect / reconnect the terminal but no luck.

 

i haven't tried booting from usb yet, i will this afternoon.

[balbes150]

Yes, the variables I see that all necessary settings are present. Here's a piece of fragment download from external media to S905. It doesn't matter what the other chip. When you start from external media should be a line indicating that the uploaded script s805_autoscript and lists the commands that are executed. If there are errors in the script, they the same will show that the command cannot be executed. In Your log I don't see any indication that the script is loaded. It is advisable to try to use a USB drive, they are usually slower, but better and more stable start. For tests they are better suited. Through what program You control the console UART ? In Linux you can use "minicom -D /dev/ttyUSB0 -b 115200"

Bus Width: 4-bit
reading s905_autoscript
618 bytes read in 4 ms (150.4 KiB/s)
## Executing script at 01020000
########## cmd=setenv m "720p60hz"
setenv mbpp "32"
setenv bootargs "root=LABEL=rootfs rootwait rw console=ttyS0,115200n8 console=tty0 no_console_suspend hdmimode=${m} m_bpp=${mbpp} net.ifnames=0"
setenv boot_start booti 0x11000000 0x13000000 0x1000000
if fatload mmc 0:1 0x13000000 uInitrd; then if fatload mmc 0:1 0x11000000 Image; then if fatload mmc 0:1 0x1000000 img.dtb; then run boot_start;fi;fi;fi;
if fatload usb 0:1 0x13000000 uInitrd; then if fatload usb 0:1 0x11000000 Image; then if fatload usb 0:1 0x1000000 img.dtb; then run boot_start;fi;fi;fi;

reading uInitrd
8559168 bytes read in 747 ms (10.9 MiB/s)
reading Image
12812704 bytes read in 1110 ms (11 MiB/s)
reading img.dtb
32991 bytes read in 7 ms (4.5 MiB/s)
## Loading init Ramdisk from Legacy Image at 13000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (uncompressed)
   Data Size:    8559104 Bytes = 8.2 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
      Amlogic multi-dtb tool
      Single dtb detected
load dtb from 0x1000000 ......
## Flattened Device Tree blob at 01000000
   Booting using the fdt blob at 0x1000000
   Loading Ramdisk to 73698000, end 73ec1a00 ... OK
   Loading Device Tree to 000000001fff4000, end 000000001ffff0de ... OK
signature: 
fdt_instaboot: get header err

Starting kernel ...
uboot time: 6513208 us

[mdel]

okay i managed to boot from usb stick, using my box dtb.img (stripped), haven't tried other dtbs.

 

here's the serial log of that boot :

 

http://paste.ubuntu.com/23228629/

 

unfortunately the system became unresponsive during apt-get update and ended up freezing, can't ssh.

 

i will try again from another sd card, i will also try your minicom command thx.

 

-- edit fixed pastebin --

 

sorry there seem to be an interrupted boot in that pastebin, the usb boot should show a dtb.img of "45056 bytes read"

which is my "stripped" dtb.img bin and somehow almost twice the size of your dtbs ??

Edited September 25, 2016 by mdel

[balbes150]

The update from a USB takes a long time, sometimes up to 10 minutes. At this time there is an active exchange and may stop responding. Keep in mind that when you first start the system, you need a lot of time to expand the second partition to the whole drive and create the initial settings. It may take a lot of time and need to logon under the root login, wait until you see the text about creating a swap partition. This is usually the final line in the log on screen when you first start. You have , in the end of the log "kernel panic". This is possible with the right parameters in the DTB. Try hq18 dtb from the dtb from the catalog.

[mdel]

which one is the hq18, the mxq one ?

 

With my dtb i get a kernel panic, with the HD180 it seems to have booted the firstrun, i get to the linux prompt but can't type.

I don't know if it's because the system is unresponsive or because my serial is not correctly soldered as i can never type anything when i manage to interrupt the boot..

 

there's a massive S85 thread on 4PDA : http://4pda.ru/forum/index.php?showtopic=621980

but i can't read russian and haven't found a picture of the serial connector yet.

 

I didn't plug the network cable for the first boot but plugging it now, the network won't dhcp.

So i will leave it and wait for a message.

 

Also i know why my dtb is twice as big, it's because there are in fact 2 dtb inside, one m8b_m201_1G and one m8b_m201C_512M, i will try to split it correctly, or do you know how that works ?

[mdel]

i've split my dtb to keep only the m8b_m201_1G part, but i still get kernel panics.

with some of your dtb i can get to the linux prompt but then it also ends up with a kernel panic a few moments later..

 

I can try to check which openelec image did work fine on that box and see if there's something interesting there ?

[dilligaf]

This is a common mistake. Usually it is associated with a media error. Sometimes this error is related to a bad download of the file (error when downloading). First check how to prepare the media. Must be FAT system. The media is better to have no more than 2 GB. For the S805 is better to use SD card, because in many models of u-boot S805 not working install updates from a USB. They can only use the SD card activate the multi-boot. Alternatively, download the special image at the link. Burn it to the media. To replace the files on those that are designed to S805. PLEASE NOTE the files in the original image state is designed to S905 they need to replace the files for the S805.

 

Hi, @balbes150, i've got the same problem, as @mdel on my mxq nexbox.

This box has  Amlogic S805 and 512mb RAM. Looks like: http://forum.alexelec.in.ua/download/file.php?id=1250

And also i run AlexELEC-S805.MXQ_V31.arm-1.0.6-20160515.img, as is bellad.

 

What is the correct aml_autoscript for my board?

I already try this and this, and both got "E:footer is wrong E:signature verification failed"

[balbes150]

mdel

The correct command to UART

 

minicom -D /dev/ttyUSB0 -b 115200 -8

 

If you can interrupt the start-up, the signal from the keyboard to the TV box is transmitted. If the text is displayed correctly, the contacts are connected correctly. The first time I see such behavior that would interrupt the start and then there was the reaction. You can show pictures as the connected contacts to the PCB and the module for UART. And it is desirable to see output at the moment of stopping the run. By the way, interruption of the run, you can do the "space" key, just press it repeatedly since the start of u-boot.

 

What kind of system is used on a PC ?

 

If you can, try to pull out of working system OE, the configuration of the kernel.

 

 

dilligaf

The activation script (aml_autoscript) multi-boot same for the entire line s805.

 

v06 is a script to S905 (that's another architecture). It is not suitable for the s805.

 

Describe more precisely what steps You are doing.

[mdel]

tried your minicom command but it didn't make a difference, i can still interrupt boot by spamming "enter" and get to the prompt but then can't input anything. I tried soldering the tx wire to the last header pin but then i can't interrupt boot anymore so i guess the tx wire is correct.

I'll try to take pictures tomorrow. My adapter is working fine, i've used it on a beelink x2 and i can type okay.

 

Anyways i've tested a libreelec image this morning so you can have a source of a working linux on my device :

 

freaktab thread : http://freaktab.com/forum/tv-player-support/amlogic-based-tv-players/23766-rom-unofficial-openelec-for-mk808b-and-mxq

the image i installed on sd card : http://sx05.eu/libreelec/7.0.2.5/SD/LibreELEC-S805.MXQ.arm-7.0.2.5.img.gz

kszaq github : https://github.com/kszaq/LibreELEC.tv

 

the device name on his github is "MXQ", this is my beelink s85 (Nexteon board)

 

he has various builds for different boards, and other members also have many other (oe/le) separate builds for other devices, so i guess there's no "universal" build for s805 ..

 

here's a serial log of that libreelec firstboot (no mention of dtb loading ??) :

http://paste.ubuntu.com/23246244/

[balbes150]

If you add on the SD card with LE this file, You will receive a run of images kszaq with the use of universal multi-boot. Ie can use images of LE and Linux.

 

https://yadi.sk/d/tmcGzE2NuoozK

[mdel]

okay i have put your s805_autoscript on the LE BOOT partition, here's the serial log :

 

http://paste.ubuntu.com/23249899/

 

Your s805_autoscript was loaded and LE booted to kodi without problem, i did a proper "kodi shutdown" at the end.

i'm not sure i understand what you wanted to do here, i see you have only copied the "setenv librefromsd" from their aml_autoscript.

 

But can you explain what's going on with the dtb on that LE image ?

i renamed the dtb.img, present in the BOOT partition, to something else and it booted fine, so the boot is not really using any dtb.img file.

 

i see they are using a dtd patch in projects/S805/patches/linux/meson8b_mxq_dtd.patch, so is it built into the kernel image ?

[dilligaf]

 

dilligaf

Describe more precisely what steps You are doing.

 

1) format my sd 2gb (also try USB 2gb/4gb) to FAT

2) boot MXQ to android

3) run backup&update app

4) select aml_autoscript.zip

5) reboot to repair

5) E:footer is wrong E:signature verification failed

 

Try another SD/USB, also got the same error.

[balbes150]

okay i have put your s805_autoscript on the LE BOOT partition, here's the serial log :

 

http://paste.ubuntu.com/23249899/

 

Your s805_autoscript was loaded and LE booted to kodi without problem, i did a proper "kodi shutdown" at the end.

i'm not sure i understand what you wanted to do here, i see you have only copied the "setenv librefromsd" from their aml_autoscript.

 

But can you explain what's going on with the dtb on that LE image ?

i renamed the dtb.img, present in the BOOT partition, to something else and it booted fine, so the boot is not really using any dtb.img file.

 

i see they are using a dtd patch in projects/S805/patches/linux/meson8b_mxq_dtd.patch, so is it built into the kernel image ?

 

There are two use cases dtb data. They can be in a separate file (it is convenient to support different boards). And can be integrated directly into the kernel image when building. This kernel can only run on those devices which are designed either with similar parameters (perhaps stops working part is not main equipment).

 

 

1) format my sd 2gb (also try USB 2gb/4gb) to FAT

2) boot MXQ to android

3) run backup&update app

4) select aml_autoscript.zip

5) reboot to repair

5) E:footer is wrong E:signature verification failed

 

Try another SD/USB, also got the same error.

 

Under normal start activate the multi-boot, there should be output in RECOVERY mode. The system should run the script aml_autoscript and once finished, reboot. If You find yourself in RECOVERY mode (picture with the robot), it means the system could not read the script aml_autoscript from the media. In almost all cases that were described by users, the reason was in the media. If I'm not mistaken, S805 to run the script activate the multi-boot is possible only with SD card (not to be confused with the launch of external systems that can be run from the SD card and USB media). Therefore, most likely, You have a problem with the media is not correctly formatted, error etc. view message 27 in this thread.

[mdel]

@@dilligaf

 

try a small FAT partition on your SD card, 32MB for example

 

when it worked for me i used the very small "BOOT" partition from one of my armbian SD Card (it has nothing to do with the aml_autoscript update, but i just grabbed a SD card with a FAT partition).

[dilligaf]

@@dilligaf

 

try a small FAT partition on your SD card, 32MB for example

 

Yeah, thnx @[member=mdel] it seems to work.

Box just reboot twice without errors. 

@balbes150, may i ask some more help

1) Now how i can check, that multiboot update worked successfully?

 

2) I try to boot linux img and got bootloop(create my boot sd card with rufus). I test my box with all available dtb.img in here and this system - Armbian_5.20_Vegas805_Ubuntu_xenial_3.10.102_20160923

You wrote upthere, that you can create dtb.img, if i capture settings from my firmware. How i can do this?  

 

[mdel]

1) Now how i can check, that multiboot update worked successfully?

 

2) I try to boot linux img and got bootloop(create my boot sd card with rufus). I test my box with all available dtb.img in here and this system - Armbian_5.20_Vegas805_Ubuntu_xenial_3.10.102_20160923

You wrote upthere, that you can create dtb.img, if i capture settings from my firmware. How i can do this?  

 

 

1) you can boot android and use adb to connect to your android shell or use a terminal app directly in android but i like adb

 

then

adb connect ip.of.your.box
adb shell
box>su (to make sure you're root)
box>strings /dev/block/env

this will print your current uboot env and there you can see if s805_autoscript is present, that means the multiboot has been installed.

 

2)

then you can also grab your dtb with some additional tools.

box>dd bs=1M if=/dev/block/boot of=/path/of/your/sdcard/boot.img
(wait it can be long)
box>exit

your box dtb is inside that boot.img blob, on linux i use a script to extract it, i don't know how it works on windows.

 

to make sure your dtb is properly extracted you should try to decompile it with an appropriate tool and get the text dtc version without errors.

[mdel]

@@dilligaf

 

i also have problems with balbes150's s805 images (kernel panic), so if it fails on your box it may be normal.

 

i have libreelec working fine on my s805 box so (not with my own dtb) i think balbes150 will be able to fix it, i will also try to build his git for my box.

[dilligaf]

Tnx to all!

I'll try this next week!

[balbes150]

Yeah, thnx @[member=mdel] it seems to work.

Box just reboot twice without errors. 

@balbes150, may i ask some more help

1) Now how i can check, that multiboot update worked successfully?

 

2) I try to boot linux img and got bootloop(create my boot sd card with rufus). I test my box with all available dtb.img in here and this system - Armbian_5.20_Vegas805_Ubuntu_xenial_3.10.102_20160923

You wrote upthere, that you can create dtb.img, if i capture settings from my firmware. How i can do this?  

 

 

 

You used one SD card ? What happens on the screen ? You have the option to write the image to a USB flash drive (need at least 4 GB for the console versions of the image) ? What kind of TV You have connected to the console ? To get the right dtb file from the archive firmware. Do You have a link to the archive with the firmware for Your TV box ? By the way, for the finished files dtb (dts), you can use a tool to unpack firmware. After his work, You will have finished the dtb file.

 

http://freaktab.com/forum/tv-player-support/allwinner-tv-players/freaktab-tools-utulities-collection

[dilligaf]

@mdel

So, I check my box:

1) strings /dev/block/env:

multiboot seems to exist in my /dev/nand_env: https://yadi.sk/i/BnYRrmOkw7RVk

2) I capture my boot.img blob: https://yadi.sk/d/RoEp4iTSw7RVY. What next? I need to extract dtb file? 

 

@balbes150

I use another sd card to create linux bootdisk. I try 16g sd card and 16gb usb flash. Box start normaly, display first splash screen, and then, when start reeading flash drive, reboot.

I use my pc hdmi monitor with box.

I have link for AlexELEC linux img for my box: https://yadi.sk/d/LmcDKKy3w7UKy

Also my box described here: http://mysku.ru/blog/china-stores/41504.html

I don't have firmware archive, but may extract it from box, if it need?

[mdel]

@@dilligaf

 

here's your dtb and dts files : https://mega.nz/#F!CNcBgZqY!j4PqPItAj5XPOYr5VaQHgA

"dilligaf-boot.img-second.gz" is actually your "dtb.img" file (simply rename it), it is named after the boot sequence of the arm cpu.

 

i have used the "split_bootimg.pl" script on linux, you can learn more about it here : 

http://www.cnx-software.com/2014/05/12/how-to-extract-a-device-tree-file-from-android-firmware-files/

http://www.cnx-software.com/2015/12/06/how-to-run-headless-linux-on-amlogic-s905-devices-such-as-mini-mx-or-k1-plus/

 

the dts file is an uncomplied text version of your dtb.img, it's of no direct use to you, but a good test to make sure that your dtb.img is correct. I use the dtc tool from the "device-tree-compiler" package.

 

It describes your board hardware so if at some point your have a doubt you can always check in there, so far it was only helpful to me to fix some gpio (leds) problems on some boxes.

[dilligaf]

@mdel

Thanks a lot!

Renamed dilligaf-boot.img-second.gz to dtb.img, burn Armbian_5.20_Vegas805_Ubuntu_xenial_3.10.102_20160923 to SDcard one more time, paste dtb.img to root directory of boot partition...

Sad, but i got bootloop again. I think it's kernel panik, as you got. Do you use serial connection to check boot logs?

[balbes150]

@mdel

So, I check my box:

1) strings /dev/block/env:

multiboot seems to exist in my /dev/nand_env: https://yadi.sk/i/BnYRrmOkw7RVk

2) I capture my boot.img blob: https://yadi.sk/d/RoEp4iTSw7RVY. What next? I need to extract dtb file? 

 

@balbes150

I use another sd card to create linux bootdisk. I try 16g sd card and 16gb usb flash. Box start normaly, display first splash screen, and then, when start reeading flash drive, reboot.

I use my pc hdmi monitor with box.

I have link for AlexELEC linux img for my box: https://yadi.sk/d/LmcDKKy3w7UKy

Also my box described here: http://mysku.ru/blog/china-stores/41504.html

I don't have firmware archive, but may extract it from box, if it need?

 

Do I understand correctly that the system starts from an external USB media ? And when you first start, after a while rebooted ? What message was on the screen ? You have tried to use this dtb file ?

[dilligaf]

Do I understand correctly that the system starts from an external USB media ? And when you first start, after a while rebooted ? What message was on the screen ? You have tried to use this dtb file ?

Correct. I try to start system from SD. It does not boot. Then I burn image to external usb flash and it also does not boot.

There are no messages on screen, only logo MXQ for 5 sec. and then reboot in cycle.

 

For my dtb.img from @mdel i create new boot SD card(16gb micro sd). Burn Armbian_5.20_Vegas805_Ubuntu_xenial_3.10.102_20160923 with rufus, then paste dtb.img to root directory of created SDcard's boot partition.

But i also got bootloop...

[mdel]

@@dilligaf

yes to get messages from the boot, if you don't get anything on screen, you need to solder a serial to usb adapter (3.3v version).

 

All the boards should have the serial header somewhere, if it's a well known board you'll probably find pictures on forums, otherwise you can take a picture of both sides and we'll find that right away.

[balbes150]

You tried to use USB media, all site the dtb files ? When using the dtb file not from the website, there is some probability that they will not work correctly with the kernel image. Sometimes these files work, sometimes not, it depends on the kernel version for which was assembled such a dtb file. What would be guaranteed the right to use dtb files in the Linux kernel in the image Armbian, they must be properly collected through the armbian build system (using kernel source). When building the dtb file using the kernel sources, the resulting file will specify the correct data, which are described in the kernel sources. I was faced with a situation where, taken from the firmware dtb file, didn't work with the way Armbian. This is due to different changes in the kernel. For example, now there is a new version of the LE that are not compatible with old dtb files of the existing firmware TV box. And for that, they would work, they have to rebuild with the kernel source.

[dilligaf]

You tried to use USB media, all site the dtb files ? 

 

Yes, i try all dtb files from this folder. 

I'll try to connect serial console to my box, to capture boot log, but i think my problem the same as @mdel. 

 

P.S. may be you got im(on mysku, for example), i may write you in russian.