pel.hu

Yay! It works! Thank you! Tried Armbian_5.24_S9xxx__Ubuntu_xenial_3.14.29_20170217_kh.img wih h96plus.dtb and it booted, I give root password and then the system restarted http://pel.hu/down/20170223202203.log Edit: Also tried with Armbian_5.26_S9xxx_Ubuntu_xenial_3.14.29_mate_20170222.img and the new dtb.img and it works too, So probably the dtb was the problem. The desktop started, no lan, no wifi, no sound.

Should I do something with the fbset file?

Where do you find these images? I would like to try the same image but I couldn't find the same ones. Today morning I tried Armbian_5.24_S9xxx_mate_Ubuntu_xenial_3.14.29_desktop_20170220.img with vegas96 dtb - > kernel didn't start and the same image with my extracted dtb.img -> kernel started and then stopped after 7 sec.

I tried to get the dtb info from the android I've got the boot.img from the box (http://pel.hu/down/H96Pro3GBboot.img) But the perl script is not running on the box, there is no /usr/bin/perl (not even /usr folder) Edit1: I see the dtb info from around 0x7dd7e0-0x7e7740 but I don't know which is the exact start and end position. I took a guess and extract this: http://pel.hu/down/dtbpart as the dtb.img Edit2: I put this to the Armbian_5.24_Amlogic-s905x_Ubuntu_xenial_3.14.29_20161125.img and the kernel starts but stops after 7 second... http://pel.hu/down/20170222223925.log I put this to the Armbian_5.24_S9xxx_server_Debian_jessie_3.14.29_20170220.img and the kernel starts but stops after 7 second... http://pel.hu/down/20170222224754.log

Unfortunately I'm not sure if this image is fit for my box because I couldn't flash it with USB burning tool. After 'Start' it just doesn't do anything. I can flash all of my boxes except this one (the only one wich has S912). OK, I reread all this thread and try to get the dtb info from my box.

Yes, you do. The kernel didn't start with neither of the two dtb files.

Yes I checked both you provided. OK, so I need 3.14.29, thanks.

I tried it with the same two images but the kernel didn't start. Summary: All the images with 3.14.79 kernel cannot start (with or without dtb.img) All the images with 3.14.29 kernel without dtb.img starts but after 7 seconds stops. All the images with 3.14.29 kernel with dtb.img for H96 pro cannot start.

You can try the same images I tried in the last few days. I wonder if you can start any of them because your box is very similar to mine.

Thank you! I've tried it with Armbian_5.24_Amlogic-s905x_Debian_jessie_3.14.29_20161210.img with s96 dtb -> kernel didn't start http://pel.hu/down/20170221143741.log I've tried it with Armbian_5.24_S9xxx_server_Debian_jessie_3.14.29_20170220.img with s96 dtb -> kernel didn't start. http://pel.hu/down/20170221144312.log

Another link to the firmware: https://mega.nz/#!U5NQASgZ!WSUivH5juSspjZoDBEAt3wRBq2VJEoi6OsTd4YhpWuY I've tried the latest Armbian_5.24_S9xxx_server_Debian_jessie_3.14.29_20170220.img with s96 dtb -> kernel didn't start. (http://pel.hu/down/20170220194046.log) I've tried Armbian_5.24_Amlogic-s905x_Debian_jessie_3.14.29_20161210.img with s96 dtb -> kernel didn't start

I've just tried Armbian_5.24_Vegas95_Debian_jessie_3.14.79_20170125.img without dtb. The kernel didn't start at all. (http://pel.hu/down/20170219183427.log) I also tried to get dtb from the latest firmware update (https://drive.google.com/file/d/0BzXEB6cWJatKbjJzYXJkTURLMzQ/view) but I cannot open the image with 7-zip.

There is no dtb.img file on the pendrive as you suggested in your earlier post. E:\>dir Volume in drive E is BOOT Volume Serial Number is BE02-DDE9 Directory of E:\ 2017. 02. 02. 12:47 <DIR> dtb-3.14.29.old 2017. 02. 02. 12:51 <DIR> dtb-3.14.29 2017. 02. 02. 12:51 <DIR> dtb 2017. 02. 02. 12:51 1 589 amlogics905x_init.sh 2017. 02. 02. 12:51 0 .verbose 2017. 02. 02. 12:47 3 347 318 System.map-3.14.29 2017. 02. 02. 12:51 533 aml_autoscript 2017. 02. 02. 12:51 395 aml_autoscript.zip 2017. 02. 02. 12:51 1 557 armbian_first_run.txt 2017. 02. 02. 12:51 6 944 boot.bmp 2017. 02. 02. 12:47 103 369 config-3.14.29 2017. 02. 02. 12:51 3 930 879 initrd.img-3.14.29 2017. 02. 02. 12:51 871 s905_autoscript 2017. 02. 02. 12:51 799 s905_autoscript.cmd 2017. 02. 02. 12:51 3 930 943 uInitrd 2017. 02. 02. 12:51 3 930 943 uInitrd-3.14.29 2017. 02. 02. 12:47 16 385 208 vmlinuz-3.14.29 2017. 02. 02. 12:47 16 385 208 zImage 15 File(s) 48 026 556 bytes 3 Dir(s) 51 230 720 bytes free Should I delete the dtb folders? I see this: reading dtb.img ** Unable to read file dtb.img **

I tried again this morning and I was able to stop the boot process with CTRL-C so I can type printenv and help. This is the result: gxm_q200_v1#printenv EnableSelinux=enforcing baudrate=115200 bootargs=rootfstype=ramfs init=/init console=ttyS0,115200 no_console_suspend earlyprintk=aml-uart,0xc81004c0 ramoops.pstore_en=1 ramoops.record_size=0x8000 ramoops.console_size=0x4000 androidboot.selinux=permissive androidboot.selinux=enforcing logo=osd1,loaded,0x3d800000,576cvbs maxcpus=8 vout=576cvbs,enable hdmimode=1080p60hz cvbsmode=576cvbs hdmitx= cvbsdrv=0 androidboot.firstboot=0 jtag=apee androidboot.hardware=amlogic mac=78:c2:c0:92:9e:0a androidboot.mac=78:c2:c0:92:9e:0a bootcmd=run start_autoscript;run storeboot; bootdelay=1 bootfromnand=0 bootfromrecovery=0 bootup_offset=0x1080240 bootup_size=0x3f4846 cmdline_keys=if keyman init 0x1234; then if keyman read usid ${loadaddr} str; then setenv bootargs ${bootargs} androidboot.serialno=${usid};fi;if keyman read mac ${loadaddr} str; then setenv bootargs ${bootargs} mac=${mac} androidboot.mac=${mac};fi;if keyman read deviceid ${loadaddr} str; then setenv bootargs ${bootargs} androidboot.deviceid=${deviceid};fi;fi; cvbs_drv=0 cvbsmode=576cvbs display_bpp=16 display_color_bg=0 display_color_fg=0xffff display_color_index=16 display_height=576 display_layer=osd1 display_width=720 dtb_mem_addr=0x1000000 ethact=dwmac.c9410000 ethaddr=00:15:18:01:81:31 factory_reset_poweroff_protect=echo wipe_data=${wipe_data}; echo wipe_cache=${wipe_cache};if test ${wipe_data} = failed; then run init_display; run storeargs;if mmcinfo; then run recovery_from_sdcard;fi;if usb start 0; then run recovery_from_udisk;fi;run recovery_from_flash;fi; if test ${wipe_cache} = failed; then run init_display; run storeargs;if mmcinfo; then run recovery_from_sdcard;fi;if usb start 0; then run recovery_from_udisk;fi;run recovery_from_flash;fi; fb_addr=0x3d800000 fb_height=1080 fb_width=1920 fdt_high=0x20000000 firstboot=0 gatewayip=10.18.9.1 hdmimode=1080p60hz hostname=arm_gxbb identifyWaitTime=750 init_display=osd open;osd clear;imgread pic logo bootup $loadaddr;bmp display $bootup_offset;bmp scale initargs=rootfstype=ramfs init=/init console=ttyS0,115200 no_console_suspend earlyprintk=aml-uart,0xc81004c0 ramoops.pstore_en=1 ramoops.record_size=0x8000 ramoops.console_size=0x4000 androidboot.selinux=permissive ipaddr=10.18.9.97 jtag=apee loadaddr=1080000 mac=78:c2:c0:92:9e:0a maxcpus=8 netmask=255.255.255.0 outputmode=576cvbs preboot=run factory_reset_poweroff_protect;run upgrade_check;run init_display;run storeargs;run upgrade_key;forceupdate;run switch_bootmode; reboot_mode=cold_boot recovery_from_flash=setenv bootargs ${bootargs} aml_dt=${aml_dt} recovery_part={recovery_part} recovery_offset={recovery_offset};if imgread kernel ${recovery_part} ${loadaddr} ${recovery_offset}; then wipeisb; bootm ${loadaddr}; fi recovery_from_sdcard=setenv bootargs ${bootargs} aml_dt=${aml_dt} recovery_part={recovery_part} recovery_offset={recovery_offset};if fatload mmc 0 ${loadaddr} aml_autoscript; then autoscr ${loadaddr}; fi;if fatload mmc 0 ${loadaddr} recovery.img; then if fatload mmc 0 ${dtb_mem_addr} dtb.img; then echo sd dtb.img loaded; fi;wipeisb; bootm ${loadaddr};fi; recovery_from_udisk=setenv bootargs ${bootargs} aml_dt=${aml_dt} recovery_part={recovery_part} recovery_offset={recovery_offset};if fatload usb 0 ${loadaddr} aml_autoscript; then autoscr ${loadaddr}; fi;if fatload usb 0 ${loadaddr} recovery.img; then if fatload usb 0 ${dtb_mem_addr} dtb.img; then echo udisk dtb.img loaded; fi;wipeisb; bootm ${loadaddr};fi; recovery_offset=0 recovery_part=recovery 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 1020000 s905_autoscript; then autoscr 1020000; fi start_usb_autoscript=if fatload usb 0 1020000 s905_autoscript; then autoscr 1020000; fi stderr=serial stdin=serial stdout=serial storeargs=setenv bootargs ${initargs} androidboot.selinux=${EnableSelinux} logo=${display_layer},loaded,${fb_addr},${outputmode} maxcpus=${maxcpus} vout=${outputmode},enable hdmimode=${hdmimode} cvbsmode=${cvbsmode} hdmitx=${cecconfig} cvbsdrv=${cvbs_drv} androidboot.firstboot=${firstboot} jtag=${jtag}; setenv bootargs ${bootargs} androidboot.hardware=amlogic;run cmdline_keys; storeboot=if imgread kernel boot ${loadaddr}; then bootm ${loadaddr}; fi;run update; switch_bootmode=get_rebootmode;if test ${reboot_mode} = factory_reset; then run recovery_from_flash;else if test ${reboot_mode} = update; then run update;else if test ${reboot_mode} = cold_boot; then run try_auto_burn; fi;fi;fi; try_auto_burn=update 700 750; update=run usb_burning; run sdc_burning; if mmcinfo; then run recovery_from_sdcard;fi;if usb start 0; then run recovery_from_udisk;fi;run recovery_from_flash; upgrade_check=echo upgrade_step=${upgrade_step}; if itest ${upgrade_step} == 3; then run init_display; run storeargs; run update;else fi; upgrade_key=if gpio input GPIOAO_2; then echo detect upgrade key; sleep 3;if gpio input GPIOAO_2; then run update; fi;fi; upgrade_step=2 usb_burning=update 1000 wipe_cache=successful wipe_data=successful Environment size: 5248/65532 bytes gxm_q200_v1#help ? - alias for 'help' aml_sysrecovery- Burning with amlogic format package from partition sysrecovery amlmmc - AMLMMC sub system amlnf - aml nand sub-system amlnf_test- AMLPHYNAND sub-system autoscr - run script from memory base - print or set address offset bmp - manipulate BMP image data booti - boot arm64 Linux Image image from memory bootm - boot application image from memory bootp - boot image via network using BOOTP/TFTP protocol cbusreg - cbus register read/write clkmsr - measure PLL clock cmp - memory compare cp - memory copy crc32 - checksum calculation cvbs - CVBS sub-system dcache - enable or disable data cache defenv_reserv- reserve some specified envs after defaulting env dhcp - boot image via network using DHCP/TFTP protocol echo - echo args to console efuse - efuse read/write data commands efuse_user- efuse user space read write ops emmc - EMMC sub system env - environment handling commands exit - exit script false - do nothing, unsuccessfully fatinfo - print information about filesystem fatload - load binary file from a dos filesystem fatls - list files in a directory (default /) fatsize - determine a file's size fdt - flattened device tree utility commands forceupdate- forceupdate get_rebootmode- get reboot mode go - start application at address 'addr' gpio - query and control gpio pins hdmitx - HDMITX sub-system help - print command description/usage i2c - I2C sub-system icache - enable or disable instruction cache imgread - Read the image from internal flash with actual size itest - return true/false on integer compare jtagoff - disable jtag jtagon - enable jtag keyman - Unify key ops interfaces based dts cfg keyunify- key unify sub-system loop - infinite loop on address range macreg - ethernet mac register read/write/dump md - memory display mm - memory modify (auto-incrementing address) mmc - MMC sub system mmcinfo - display MMC info mw - memory write (fill) mwm - mw mask function nm - memory modify (constant address) open_scp_log- print SCP messgage osd - osd sub-system phyreg - ethernet phy register read/write/dump ping - send ICMP ECHO_REQUEST to network host printenv- print environment variables rarpboot- boot image via network using RARP/TFTP protocol read_temp- cpu temp-system reboot - set reboot mode and reboot system reset - Perform RESET of the CPU rsvmem - reserve memory run - run commands in an environment variable saradc - saradc sub-system saradc_12bit- saradc sub-system saveenv - save environment variables to persistent storage sdc_burn- Burning with amlogic format package in sdmmc sdc_update- Burning a partition with image file in sdmmc card set_trim_base- cpu temp-system set_usb_boot- set usb boot mode setenv - set environment variables showvar - print local hushshell variables silent - silent sleep - delay execution for some time store - STORE sub-system systemoff- system off temp_triming- cpu temp-system test - minimal test like /bin/sh tftpboot- boot image via network using TFTP protocol true - do nothing, successfully unpackimg- un pack logo image into pictures update - Enter v2 usbburning mode usb - USB sub-system usb_burn- Burning with amlogic format package in usb usb_update- Burning a partition with image file in usb host usbboot - boot from USB device version - print monitor, compiler and linker version vout - VOUT sub-system vpu - vpu sub-system wipeisb - wipeisb write_trim- cpu temp-system write_version- cpu temp-system gxm_q200_v1#

I tried to run a 20161218 jessi image. I also tried without the dtb.img -> same result. On the uart console there is no response to anything I type. When should I type printenv or help? During the boot? I preparing an usb stick right now to try it. (Armbian_5.24_Amlogic-s905x_Debian_jessie_3.14.29_CPU_OVER_20170202.img) Edit: OK, I tried from an USB stick. The log looks similar to me: http://pel.hu/down/20170218220646.log It stucks at the same place. The log when the android boots: http://pel.hu/down/20170218222630.log At the end there is a printenv too.

I would like to use a H96 Pro S912 box with armbian. It's the same hardware as the R-BOX reviewed here I've opened the box, soldered the serial connector and connect to my laptop. The log file is here. There is no HDMI signal and nothing happens even if I wait half an hour. What could I try to get it boot to armbian?

Thank you, next time I'll try with USB pendrive. (I use sandisk microsd cards which worked until now in several different box without any problem.) Unfortunately the next couple of days I have to work countryside so I'll continue to test when I come back. Maybe I'll sacrifice the box top cover and solder the serial uart if it is easier to find the problem. Or maybe easier to sell it and buy a GT1...

I've changed the bpp to 16 and got full screen. Also tried bpp 32 and it was half screen too but not cutted but shrinked. bpp 16 working fine.

OK, I tried the desktop version booted fine but in 720p. I edited the s905x.sh in the boot and got 1920x1080 video output but the lower half is black. How can i fix that?

Wow! How could you see that? You are right I had to press enter and I got the login stuff. Thank you!

I tried to run the 12.13 debian cli version on Mini M8S II (S905X, 2GB/16GB) and got this: Should I wait more or it is done with these errors? I haven't copy any dtb to the root folder. I've read some post about working debian on the same device so obviously I do something wrong. Could you suggest which version I try? After a few minutes I'v got another line, picture updated.

I didn't wait that much so I tried again, waited 15 minutes, but nothing happened. I've checked if I can ssh to the box, but no answer. I've tried with and without the dtb file. Edit: I tried the newest armbian image on a Mini M8S II (S905x, 2GB/16GB) but it's not started even on that box but at least I got a bunch of error message. https://forum.armbian.com/index.php/topic/2419-armbian-for-amlogic-s905-and-s905x/page-12#entry21395

Thank you, I tried but nothing changed (boot logo, then no signal on HDMI). Is this file just a trimmed version of mine? The file came from /dev/dtb I've found another ones: /sys/devices/virtual/dtb /sys/devices/virtual/dtb/dtb /sys/devices/virtual/dtb/dtb/dev /sys/devices/virtual/dtb/dtb/power /sys/devices/virtual/dtb/dtb/subsystem /sys/devices/virtual/dtb/dtb/uevent /sys/class/dtb /sys/class/dtb/dtb /sys/class/dtb/emmcdtb Which one do you think is worth to check? Edit: Checked all but they contain only version info: 243:0

I tried to copy this file to the sd card's root folder and rename it to dtb.img After the boot logo ("H96 Pro") just black screen and no signal on HDMI.

I noticed that the box is rooted. Is it help? With a terminal app I can see /dev/dtb crw------- root root 243, 0 2015-01-01 dtb root@q6330:/ # cat /dev/dtb > /storage/dtb.file root@q6330:/ # ls -l storage/dtb.file -rw------- root root 262144 2016-12-12 08:58 dtb.file root@q6330:/ # head /storage/dtb.file ???!8?,( amlogic, Gxmlogic gxm_q200_2g0?t82x@d00c00008arm,malit602arm,malit60xarm,malit6xxarm,mali-midgardKPZ? ... You can see the file here: http://pel.hu/down/dtb.file So how can I make a dtb.img from this?