klamath123 Posted January 15, 2019 Posted January 15, 2019 On 1/15/2019 at 11:25 AM, balbes150 said: Add your version of DTS sources to the source code of the main kernel and build your version of dtb there. Expand tried but fails see https://pastebin.com/8ufHHbwa
balbes150 Posted January 16, 2019 Posted January 16, 2019 On 1/15/2019 at 5:54 PM, klamath123 said: tried but fails see Expand You have not added the desired file to the media or incorrectly specified it in the settings. reading /dtb/mxiii.dtb ** Unable to read "/dtb/mxiii.dtb" from mmc 0:1 **
klamath123 Posted January 16, 2019 Posted January 16, 2019 On 1/16/2019 at 7:03 AM, balbes150 said: You have not added the desired file to the media or incorrectly specified it in the settings. reading /dtb/mxiii.dtb ** Unable to read "/dtb/mxiii.dtb" from mmc 0:1 ** Expand Thanks for prompt reply.. will try again.. also another quick question if i may.. I'm trying to copy system to nand my box has /dev/data /dev/boot /dev/system /dev/recovery /dev/cache I managed to copy / to /dev/data and modified uenv.ini to use /dev/data as /, is there a way to make it boot entirely from nand? coudl you give me some quick pointers. Thanks !
balbes150 Posted January 16, 2019 Posted January 16, 2019 You need to build your version of s805_script (the name can be any), specify where to load the kernel, initrd and DTB. Write it in NAND. To edit variables of u-boot, add after the check run the script with USB and SD, run your new script. Then when you run u-boot, it will run a new script from NAND, and the script will already run the system from NAND with the specified parameters.
gtiberio Posted January 27, 2019 Posted January 27, 2019 I can run, on my MXIII Plus box (S812), the Armbian_5.44_S812_Ubuntu_bionic_3.10.108_server_20180521 image, using MXIIIPlus dtb file. It runs fine: eth0 network, HDMI video etc. But, when I upgrade (sudo apt upgrade) and system reboots, device doesn't work. Screen flickers, I wait for hours, but no boot. Tried to run any newer image (from 5.64 on), Ubuntu and Debian, but no boot too. Tried using other dtb files, always fail. Help please!
RaptorSDS Posted January 27, 2019 Posted January 27, 2019 i all On 1/27/2019 at 4:05 PM, gtiberio said: I can run, on my MXIII Plus box (S812), the Armbian_5.44_S812_Ubuntu_bionic_3.10.108_server_20180521 image, using MXIIIPlus dtb file. It runs fine: eth0 network, HDMI video etc. But, when I upgrade (sudo apt upgrade) and system reboots, device doesn't work. Screen flickers, I wait for hours, but no boot. Tried to run any newer image (from 5.64 on), Ubuntu and Debian, but no boot too. Tried using other dtb files, always fail. Help please! Expand you can update only single paket with " apt-get [Option(s)] install PAKET1 [PAKET2] " maybe you find the one that doesnt work ( my banana pi had some problems with the cups update sometime) @balbes150 After over 1 1/2 year with your s812 Armbian 5.27 ubuntu 16.0 Rom i´m still happy that it works perfect but i have two questions 1. is the motd login message static ? Because i got today armbian 5.6 Firmware update and my login say 5.27? 2. also i look at your yandisk folder and see 5.67 with ubuntu bionix ; is it worth to change ? is the default the server image? can i use the old dtb to boot or do i need a new one ? can i use the broadcom chip AP6330 (like the in the 5.27 image where i change the blacklist.conf) @balbes150
balbes150 Posted January 28, 2019 Posted January 28, 2019 On 1/27/2019 at 4:05 PM, gtiberio said: But, when I upgrade (sudo apt upgrade) and system reboots, device doesn't work. Screen flickers, I wait for hours, but no boot. Tried to run any newer image (from 5.64 on), Ubuntu and Debian, but no boot too. Tried using other dtb files, always fail. Expand Are you setting up the DTB correctly in the new versions ? On 1/27/2019 at 7:15 PM, RaptorSDS said: 1. is the motd login message static ? Because i got today armbian 5.6 Firmware update and my login say 5.27? Expand I didn't understand the question. Write more about the problem. On 1/27/2019 at 7:15 PM, RaptorSDS said: 2. also i look at your yandisk folder and see 5.67 with ubuntu bionix ; is it worth to change ? is the default the server image? can i use the old dtb to boot or do i need a new one ? can i use the broadcom chip AP6330 (like the in the 5.27 image where i change the blacklist.conf) Expand In new versions, the kernel has been updated and you need to check whether it will work on your hardware or not. Run from external media and see how it will work.
RaptorSDS Posted January 28, 2019 Posted January 28, 2019 On 1/28/2019 at 8:01 AM, balbes150 said: I didn't understand the question. Write more about the problem. Expand i have the box as headless server with shh login. After Login i get the Armbian S812 MOTD Screen with IP ; Stay-Alive Time and CPU Usage at this MOTD Screen the text say Armbian 5.27 Ubuntu 16.0 LTS ... ; Yesterday my box get the armbian-5.6-Firmware-full update from apt-get update command , and i ask is the MOTD message static or is the firmware-full update not the Armbian 5.6 version update ? (should the MOTD screen print text Armbian 5.6 Ubuntu 16.0 LTS ?)
balbes150 Posted January 28, 2019 Posted January 28, 2019 On 1/28/2019 at 5:10 PM, RaptorSDS said: i have the box as headless server with shh login. After Login i get the Armbian S812 MOTD Screen with IP ; Stay-Alive Time and CPU Usage at this MOTD Screen the text say Armbian 5.27 Ubuntu 16.0 LTS ... ; Yesterday my box get the armbian-5.6-Firmware-full update from apt-get update command , and i ask is the MOTD message static or is the firmware-full update not the Armbian 5.6 version update ? (should the MOTD screen print text Armbian 5.6 Ubuntu 16.0 LTS ?) Expand Judging by the message, it is information on emergence of new packages. This is not an update Armbian. You can get more information about the packages that will be updated if you run the "apt" command with the necessary options.
gtiberio Posted January 29, 2019 Posted January 29, 2019 On 1/28/2019 at 8:01 AM, balbes150 said: Are you setting up the DTB correctly in the new versions ? Expand You mean, setting uEnv.ini with the dtb file? Yes, I am.
balbes150 Posted January 30, 2019 Posted January 30, 2019 New Ubuntu Server image 5.73 for S812 with kernel 5.0-rc4. HDMI does not work. Control via UART or SSH. I checked on Tronsmart MXIII Plus running from SD card and USB flash drive. Installation in eMMC was not checked.
Xelor Posted February 7, 2019 Posted February 7, 2019 @balbes150 WiFi does not seem to be working in this version, i cannot load the dhd module for WiFi and Ethernet does not seem to work either . My board is MX III with gigabit Ethernet (S812) , WiFi chip is ap6330 . Boot logs did not suggest anything was going wrong. The old 3.10.108 kernel had everything working except the GPIO interface... which i needed for my project .The GPIO interface works on the newer next kernel but everything else doesn't .
Xelor Posted February 19, 2019 Posted February 19, 2019 Has there been a massive change to the Armbian build script for s812 ? , i can no longer get WiFi or Ethernet in any kernel version . I noticed i no longer see amlogic drivers in the make config.
balbes150 Posted February 19, 2019 Posted February 19, 2019 On 2/19/2019 at 1:15 AM, Xelor said: Has there been a massive change to the Armbian build script for s812 ? , i can no longer get WiFi or Ethernet in any kernel version . I noticed i no longer see amlogic drivers in the make config. Expand For WiFi on kernel 3.x, install the FIRMWARE package deb from the 5.73 directory (to site). The build environment now uses packages for the main kernel (they are not suitable for the old kernel).
lcmg Posted February 20, 2019 Posted February 20, 2019 Hi, First of all many thanks for this work @balbes150!! I've give this OS a try on my minix x8h-plus (S812) this weekend and worked out of the box and is great! To give this box a 2nd life I was trying to install docker on it using the Armbian 5.73 image, but so far I've been unable to do it. I've tried a couple of methods I've found on internet with no success, docker is unable to start. Running the command "journalctl" the issue I've found with docker is related with cgroup, please see below. I've found some possible causes and solutions on google that I've tried to implement but without success. I've also saw some comments saying that this is only solved by changing kernel. Can anyone share is experience with Docker on this OS/Kernel/HW? Are you able to run it? if is possible to run on it, this means that the issue is the usual one = me , and I will keep looking and trying. As a side note I've also tried Armbian with Kernel 4.20 and 5.0 available on repository (using meson8m2-mxiii-plus.dtb) but Minix did not boot, got stuck on minix logo screen. -- Unit docker.service has begun starting up. Feb 18 13:45:27 aml dockerd[5681]: time="2019-02-18T13:45:27.333966089Z" level=info msg="libcontainerd: new containerd process, pid: 5687" Feb 18 13:45:28 aml dockerd[5681]: time="2019-02-18T13:45:28.402673425Z" level=info msg="[graphdriver] using prior storage driver: overlay" Feb 18 13:45:28 aml dockerd[5681]: time="2019-02-18T13:45:28.419603143Z" level=info msg="Graph migration to content-addressability took 0.00 seconds" Feb 18 13:45:28 aml dockerd[5681]: time="2019-02-18T13:45:28.420095164Z" level=warning msg="Your kernel does not support cgroup memory limit" Feb 18 13:45:28 aml dockerd[5681]: time="2019-02-18T13:45:28.420187168Z" level=warning msg="Your kernel does not support cgroup cfs period" Feb 18 13:45:28 aml dockerd[5681]: time="2019-02-18T13:45:28.420237170Z" level=warning msg="Your kernel does not support cgroup cfs quotas" Feb 18 13:45:28 aml dockerd[5681]: time="2019-02-18T13:45:28.420292173Z" level=warning msg="Unable to find blkio cgroup in mounts" Feb 18 13:45:28 aml dockerd[5681]: time="2019-02-18T13:45:28.420322174Z" level=warning msg="Unable to find cpuset cgroup in mounts" Feb 18 13:45:28 aml dockerd[5681]: time="2019-02-18T13:45:28.420462180Z" level=warning msg="mountpoint for pids not found" Feb 18 13:45:28 aml dockerd[5681]: Error starting daemon: Devices cgroup isn't mounted Feb 18 13:45:28 aml systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE Feb 18 13:45:28 aml systemd[1]: Failed to start Docker Application Container Engine. -- Subject: Unit docker.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit docker.service has failed.
ntux Posted February 27, 2019 Posted February 27, 2019 On 2/20/2019 at 11:07 AM, lcmg said: Can anyone share is experience with Docker on this OS/Kernel/HW? Are you able to run it? if is possible to run on it, this means that the issue is the usual one = me , and I will keep looking and trying. Expand Hi, I managed to have docker running on a S812 box (Minix X8-H Plus model same as you), you need to recompile the kernel with all the required flags set for docker to work. I started from Balbes150's latests images with 4.x kernel (but should be good as well using 5.0), downloaded the kernel sources from Kevin Hilman's repo (https://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-amlogic.git), made the .config changes required for docker to work (you can have a look at docker's site, or to the script that validates current kernel flags for docker), build the kernel uImage, headers and modules, installed everything and rebooted. After that the docker service runs fine (even in swarm mode). The only thing I didn't managed to get working was wifi, but since I'm plugged in ethernet i didn't investigate that much to get the ap6335 to work. I'm using the default mxiii dtb from balbes' release, it works fine. 2
lcmg Posted February 28, 2019 Posted February 28, 2019 Hi, On 2/27/2019 at 2:39 PM, ntux said: I managed to have docker running on a S812 box (Minix X8-H Plus model same as you), you need to recompile the kernel with all the required flags set for docker to work. I started from Balbes150's latests images with 4.x kernel (but should be good as well using 5.0), downloaded the kernel sources from Kevin Hilman's repo (https://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-amlogic.git), made the .config changes required for docker to work (you can have a look at docker's site, or to the script that validates current kernel flags for docker), build the kernel uImage, headers and modules, installed everything and rebooted. After that the docker service runs fine (even in swarm mode). Expand Many thanks @ntux for your answer and sharing. Exactly the feedback I was looking for! I will try to build the kernel with the required flags. One additional question, your are running Armbian on SDcard, USB or internal? Kind regards,
ntux Posted March 4, 2019 Posted March 4, 2019 On 2/28/2019 at 9:01 AM, lcmg said: Hi, Many thanks @ntux for your answer and sharing. Exactly the feedback I was looking for! I will try to build the kernel with the required flags. One additional question, your are running Armbian on SDcard, USB or internal? Kind regards, Expand You're welcome! Regarding storage, I am using a usb hard drive, but plugged into the otg port (with the box provided otg adapter) to save the other ports' bandwidth for other stuff (otg and 'regular' usb ports are on 2 different usb buses, so I assume not shared bandwidth but I haven't tested). The only drawbacks are that the otg port doesn't provide power (I am using a non-bus-powered 3.5" hd sata usb adapter so I'm fine) and does not boot (so I have to put the /boot partition on a sdcard or usb stick on one of the regular usb ports). I haven't played with internal memory, I'm not sure how the mainline kernels support this... Has anyone tried? Thanks & regards,
lcmg Posted March 7, 2019 Posted March 7, 2019 Hi, Many thanks @ntux! I tried again to boot using Armbian with Kernel 4.x and 5.0 but with no luck, the Minix doesn't boot. I think I have the Minix X8h+ gen1 version, not sure if is because of the hw version. Anyway I decided to give a try using the kernel 3.10. I've sucessfully build the kernel and manage to solve part of dependecies pointed by the docker depencies script, playing with .config. But I was not able to solve all of them, I didn't found some of dependencies to activate on the .config file. I've tried to add them manually with no luck. Meanwhile I runned out of time... Any sugestion are welcome :).
ntux Posted March 7, 2019 Posted March 7, 2019 On 3/7/2019 at 9:49 AM, lcmg said: Hi, Many thanks @ntux! I tried again to boot using Armbian with Kernel 4.x and 5.0 but with no luck, the Minix doesn't boot. I think I have the Minix X8h+ gen1 version, not sure if is because of the hw version. Anyway I decided to give a try using the kernel 3.10. I've sucessfully build the kernel and manage to solve part of dependecies pointed by the docker depencies script, playing with .config. But I was not able to solve all of them, I didn't found some of dependencies to activate on the .config file. I've tried to add them manually with no luck. Meanwhile I runned out of time... Any sugestion are welcome :). Expand Hi, I think I read somewhere (maybe the OpenElec forums but I don't remember exactly) that the 3.10 was just too old/hacked by AmLogic to support docker properly. Also it only exposes 1.6G of ram due to I think memory dedicated to the gpu (that I don't need personally as my box is headless, I prefer have the full 2G of ram for software). I don't know about the gen of my Minix box, I'm not sure if there is a simple way for me to know? I just reinstalled armbian using the 5.0 kernel, and I had some issues booting directly from the usb drive, what is working for me right now is having the boot partition on the sdcard and the rootfs on the usb drive. Also the otg port did work for me using a 2.5 usb hdd with the double power usb ports (data port on the otg adapter, power port on one of the other usb ports), but it doesn't seem to work using a powered 3.5 usb hdd adapter. I don't know if you somehow need to backfeed current to the otg port for it to work, or if it's an issues with the 5 kernel... Anyway, if I were you and wanted to test step by step, I would: - Grab a sdcard and try with flashing the latest balbes' image with 5.0.0-rc4 kernel (not on a usb drive, I had less issues booting from sdcards) - See if it boots. Remember there's no gpu support so no video output, see with your router's dhcp allocations or a network scan (personally I use a network scan app on my android phone) to detect the ethernet IP and try to ssh to it (root/1234) - Grab the 5.0.0 kernel sources, and the config file I attached (there's no dot in the filename I provided, add it) - try to compile it, and install: make -j 4 LOADADDR=0x00208000 uImage dtbs modules sudo make modules_install sudo make headers_install sudo cp arch/arm/boot/uImage /boot - reboot, see if it boots with the compiled 5.0.0 kernel. If it does you should be able to install docker - from there you could play with migrating the rootfs partition to a usb drive. Remember that the boot process will look for a ext4 partition with the "ROOTFS" label. That's how you should be able to switch between the sdcards and usb drive rootfs partitions. What I did is that I flashed balbes' image on a usb drive, and removed the rootfs label from the sdcard partition (sudo e2label /dev/mmcblk0p2 "") Also, the .config file I provided is clearly not optimized. I grabed a default one that includes lots of stuff for many boards and added the docker flags I needed. It clearly needs optimization as it include support for a lot of unnecessary bloat. But it works for me, I'll make some cleanup in the future if I have some time... I hope that helps, 1
ntux Posted March 8, 2019 Posted March 8, 2019 On 3/7/2019 at 6:24 PM, balbes150 said: Update image 5.76 kernel 3.10 Expand Thanks a lot! Also, could you consider making one of your builds with the 5.0 kernel and a btrfs ROOTFS? I tried converting the ext4 partition to btrfs and adjusting the uEnv.ini file to change the rootfstype but it wouldn't boot either... I don't know if there are other things to change?
bausshal Posted March 21, 2019 Posted March 21, 2019 I'm getting an strange error. When I connect to the tv-box (MXIII 4k S812) via ssh it's tell me to change the root password and when I try to set the new password it's close the ssh session immediately. I'm getting the same error both ubunto and debian versions 5.44, 5.64, 5.73 and 5.76 it's giving me the same error. I tryed with other dtb.img files (mxiii plus and others, with the same error or not boot). The log from putty. Incoming raw data at 2019-03-20 00:03:04 00000000 26 04 36 54 33 c0 15 72 ad b3 36 d5 9e 80 0f b9 &.6T3..r..6..... 00000010 69 3a b4 08 33 78 43 71 11 ce 19 b9 02 4b 1a 16 i:..3xCq.....K.. 00000020 12 02 62 e4 e6 8b 55 d9 36 1e 03 f3 3e 37 0e e0 ..b...U.6...>7.. 00000030 2f bd 6c af e7 23 70 f6 67 02 7d 98 c8 7c 41 b4 /.l..#p.g.}..|A. 00000040 93 d6 85 cf 3f 6d 58 16 29 9d 89 dd d9 a5 4d 90 ....?mX.).....M. 00000050 09 2f 71 fa dd e6 47 22 11 16 4d a3 94 07 24 a2 ./q...G"..M...$. 00000060 f1 fd 15 86 96 85 c3 75 04 71 ce b0 78 da b2 5f .......u.q..x.._ 00000070 f5 64 ce c0 f3 9f 80 7c 91 b2 34 f3 5b 5d 20 80 .d.....|..4.[] . Incoming packet #0x1c, type 98 / 0x62 (SSH2_MSG_CHANNEL_REQUEST) 00000000 00 00 01 00 00 00 00 0b 65 78 69 74 2d 73 74 61 ........exit-sta 00000010 74 75 73 00 00 00 00 ff tus..... Event Log: Server sent command exit status 255 Incoming packet #0x1d, type 97 / 0x61 (SSH2_MSG_CHANNEL_CLOSE) 00000000 00 00 01 00 .... Event Log: Disconnected: All channels closed
gmytis Posted March 21, 2019 Posted March 21, 2019 (edited) hi, im trying to boot my m8 square box with s802 2gb ram and 8gb nand. made sd card, activated multiboot (rebooted twice), selected meson8_k200b_2G_emmc_sdhc.dtb in uEnv.ini but after this box doesnt boot to sd card. this my printenv Reveal hidden contents m8_k200_v1#printenv 720poutputheight=691 720poutputwidth=1229 720poutputx=25 720poutputy=14 aml_dt=m8_k200_2gsdhc baudrate=115200 bootargs=init=/init console=ttyS0,115200n8 no_console_suspend storage=4 cvbsdrv=0 vdaccfg=0xa007 logo=osd1,loaded,0x15100000,576cvbs,full hdmimode=720p50hz cvbsmode=576cvbs androidboot.firstboot=0 hdmitx= bootcmd=run storeboot bootdelay=1 bootfile=boot.img bootm_low=0x00000000 bootm_size=0x80000000 bootpath=u-boot.bin bootsize=100000 bootstart=0 bootup_1080_offset=0x13000280 bootup_1080_size=0x5eec7a bootup_720_offset=0x135eef00 bootup_720_size=0x2a3036 bootup_offset=0x135eef00 bootup_size=0x2a3036 chipname=8726m8 console=ttyS0,115200n8 cvbs_drv=0 cvbsmode=576cvbs digitaudiooutput=PCM disp.fromleft=true display_bpp=24 display_color_bg=0 display_color_fg=0xffff display_color_format_index=24 display_height=576 display_layer=osd2 display_width=720 ethact=Meson_Ethernet ethaddr=c4:4e:ac:08:61:75 fb_addr=0x15100000 fb_height=720 fb_width=1280 firstboot=0 gatewayip=10.18.9.1 get_dt=checkhw has.accelerometer=false hdmimode=720p50hz hostname=arm_m8 initargs=init=/init console=ttyS0,115200n8 no_console_suspend storage=4 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 stderr=serial stdin=serial stdout=serial store=4 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=secukey auto;secukey write keyexample 1234567890; echo Booting...; if unifykey get usid; then setenv bootargs ${bootargs} androidboot.serialno=${usid};fi;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_bar_offset=0x13891f40 upgrade_bar_size=0xde upgrade_error_offset=0x13892020 upgrade_error_size=0x41ee6 upgrade_fail_offset=0x138d3f10 upgrade_fail_size=0x41ee6 upgrade_logo_offset=0x13915e00 upgrade_logo_size=0x41ee6 upgrade_step=0 upgrade_success_offset=0x13957cf0 upgrade_success_size=0x41ee6 upgrade_unfocus_offset=0x13999be0 upgrade_unfocus_size=0xde upgrade_upgrading_offset=0x13999cc0 upgrade_upgrading_size=0x41ee6 us_delay_step=1 usb_burning=update 1000 vdac_config=0xa007 video_dev=tvout wipe_data=success Environment size: 4294/65532 bytes and booting Reveal hidden contents EEEE I3000000032940xf100110303B77500EEEE I400000004294_M8_BL1_10221D113B323EEEE I3000000032940xbbbb000026A22525 no sdio debug board detected TE : 102615 BT : 16:03:10 Jul 28 2015 PMU:rn5t618 DC01 v:1100, 0x[36]: 28 -> 28 DC02 v:1150, 0x[37]: 2c -> 2c DC03 v:1500, 0x[38]: 48 -> 48 LDO01 v:2900, 0x[4c]: 50 -> 50 LDO02 v:1800, 0x[4d]: 24 -> 24 LDO03 v:1800, 0x[4e]: 30 -> 30 LDO04 v:2850, 0x[4f]: 4e -> 4e LDO05 v:1800, 0x[50]: 24 -> 24 LDO0a v:2700, 0x[56]: 28 -> 28 LDO0b v:900, 0x[57]: 00 -> 00 CPU clock is 1200MHz CPU type: M8 DDR info: 2GB(auto) @ 528MHz(1T) DDR channel: DDR 0 + DDR 1 DDR init use : 12560 us HHH Boot From SPI ucl decompress...pass 0x12345678 Boot from internal device 1st SPI TE : 473224 System Started U-boot-00000-g2832a16(m8_k200_v1@s82_netxeon) (Jul 28 2015 - 16:03:00) clr h-ram DRAM: 2 GiB relocation Offset is: 6fec0000 show partition table: part: 0, name : logo, size : 2000000 part: 1, name : recovery, size : 2000000 part: 2, name : misc, size : 2000000 part: 3, name : boot, size : 2000000 part: 4, name : system, size : 60000000 part: 5, name : cache, size : 20000000 part: 6, name : data, size : end aml_card_type=0x100 MMC: [mmc_register] add mmc dev_num=0, port=1, if_type=6 [mmc_register] add mmc dev_num=1, port=2, if_type=6 SDIO Port B: 0, SDIO Port C: 1 PMU fault status: reg[0x9A] = 0x0d LSI version:04, OTP version:0c PMU type:RN5T618 register usb cfg[0][1] = 7ff6fccc register usb cfg[2][0] = 7ff731dc NAND: SPI BOOT: boot_device_flag 0 Nand PHY driver Version: 1.01.001.0004 (c) 2013 Amlogic Inc. amlnf_phy_init : amlnf init flag 0 NAND device id: 2c 64 44 4b a9 0 0 0 detect NAND device: B revision NAND 8GiB MT29F64G08CBABA AML_NAND_NEW_OOB : new oob bus_cycle=5, bus_timing=7,system=3.9ns,flash->T_REA =16,flash->T_RHOH=15 NAND CKECK : arg nbbt: arg_valid= 1, valid_blk_addr = 4, valid_page_addr = 0 NAND CKECK : arg ncnf: arg_valid= 1, valid_blk_addr = 5, valid_page_addr = 0 NAND CKECK : arg nkey: arg_valid= 1, valid_blk_addr = 8, valid_page_addr = 130 i=0,register --- nand_key nfcache : offset: 0x000006000000 -0x000024800000 : partitons 1 : single_chip multi_plane nfcode : offset: 0x00002a800000 -0x000073800000 : partitons 5 : single_chip multi_plane nfdata : offset: 0x00009e000000 -0x000162000000 : partitons 1 : single_chip multi_plane bad block count = 0 bad block count = 0 bad block count = 0 amlnf_logic_init: START aml_nftl_start:117,size_in_blk=145,tmp_block=128,part->free_block_num=17 aml_nftl_start:117,size_in_blk=462,tmp_block=416,part->free_block_num=46 amlnf_logic_init: COMPLETE get_boot_device_flag: init_ret 0 get_boot_device_flag SPI BOOT: nand init success, change the device_boot_flag to 4 : spi+nand SPI BOOT,spi_env_relocate_spec : env_relocate_spec 53 SF: Detected W25Q16 with page size 256, total 2 MiB SPI NOR Flash have write protect!!! set_storage_device_flag: store 4 Multi dtb tool version: v2 . Multi dtb detected, support 6 dtbs. aml_dt soc: m8 platform: k200 variant: 2gsdhc dtb 0 soc: m8 plat: k200 vari: 2gsdhc dtb 1 soc: m8 plat: k200 vari: 2gsdio dtb 2 soc: m8 plat: k200 vari: sdhc dtb 3 soc: m8 plat: k200 vari: sdio dtb 4 soc: m8m2 plat: n200 vari: 1G dtb 5 soc: m8m2 plat: n200 vari: 2G Find match dtb: 0 vpu driver detect cpu type: m8 vpu clk_level in dts: 7 set vpu clk: 364300000Hz, readback: 364300000Hz(0x700) Net: Meson_Ethernet init suspend firmware done. (ret:0) cvbs trimming.1.v5: 0xa0, 0x7 cvbs performance type = 0, table = 0 vdac open.1 = 0x1, 0x7 [ImgPck]ver=2 reboot_mode=charging Hit Enter key to stop autoboot -- : 0 exit abortboot: 0 current storer:nand_key key save is auto select storer(nand or emmc) write key code version3_flush:708,prov->write:7fee8470 size:4096 arg_pages:1 extra_page:0 write key ok!! Booting... pos 509 value is 20ERR(v2_common/optimus_download_key.c)L268:failed to query key state, rc 0, keyIsBurned=0 ## ANDROID Format IMAGE ## Booting kernel from Legacy Image at 12000000 ... im using 64gb micro sdxc card, same card boots alexelec no problem. is it something with u-boot? do i need to upgrade it somehow? thanks Edited March 21, 2019 by Tido added spoiler
RaptorSDS Posted March 21, 2019 Posted March 21, 2019 one error i saw is that dtb file not working for you you need another one Quote Multi dtb detected, support 6 dtbs. aml_dt soc: m8 platform: k200 variant: 2gsdhc dtb 0 soc: m8 plat: k200 vari: 2gsdhc dtb 1 soc: m8 plat: k200 vari: 2gsdio dtb 2 soc: m8 plat: k200 vari: sdhc dtb 3 soc: m8 plat: k200 vari: sdio dtb 4 soc: m8m2 plat: n200 vari: 1G dtb 5 soc: m8m2 plat: n200 vari: 2G Find match dtb: 0 Expand
gmytis Posted March 21, 2019 Posted March 21, 2019 On 3/21/2019 at 7:27 PM, RaptorSDS said: one error i saw is that dtb file not working for you you need another one Expand what is proper way of selecting dtb? is it to edit uEnv.ini first line, or rename to dtb.img and copy to root folder?
RaptorSDS Posted March 21, 2019 Posted March 21, 2019 on old image was the way to copy working dtb to boot Fat partiotion and rename to dtb.img on new image edit the uEnv.ini for selecting proper dtb file it is testing only , one after another until one is working
gmytis Posted March 21, 2019 Posted March 21, 2019 i extracted dtb from working rom with this guide: https://www.cnx-software.com/2014/05/12/how-to-extract-a-device-tree-file-from-android-firmware-files/ i will try it tommorow.
gmytis Posted March 21, 2019 Posted March 21, 2019 renamed boot.img-second.gz to meson8.dtb, copied to dtb folder, edited uEnv.ini still exactly same: Reveal hidden contents EEEE I3000000032940xf100110303B77500EEEE I400000004294_M8_BL1_10221D113B323EEEE I3000000032940xbbbb000026A22525 no sdio debug board detected TE : 102615 BT : 16:03:10 Jul 28 2015 PMU:rn5t618 DC01 v:1100, 0x[36]: 18 -> 28 DC02 v:1150, 0x[37]: 18 -> 2c DC03 v:1500, 0x[38]: 38 -> 48 LDO01 v:2900, 0x[4c]: 4e -> 50 LDO02 v:1800, 0x[4d]: 24 -> 24 LDO03 v:1800, 0x[4e]: 30 -> 30 LDO04 v:2850, 0x[4f]: 4e -> 4e LDO05 v:1800, 0x[50]: 24 -> 24 LDO0a v:2700, 0x[56]: 28 -> 28 LDO0b v:900, 0x[57]: 00 -> 00 CPU clock is 1200MHz CPU type: M8 DDR info: 2GB(auto) @ 528MHz(1T) DDR channel: DDR 0 + DDR 1 DDR init use : 12568 us HHH Boot From SPI ucl decompress...pass 0x12345678 Boot from internal device 1st SPI TE : 473110 System Started U-boot-00000-g2832a16(m8_k200_v1@s82_netxeon) (Jul 28 2015 - 16:03:00) clr h-ram DRAM: 2 GiB relocation Offset is: 6fec0000 show partition table: part: 0, name : logo, size : 2000000 part: 1, name : recovery, size : 2000000 part: 2, name : misc, size : 2000000 part: 3, name : boot, size : 2000000 part: 4, name : system, size : 60000000 part: 5, name : cache, size : 20000000 part: 6, name : data, size : end aml_card_type=0x100 MMC: [mmc_register] add mmc dev_num=0, port=1, if_type=6 [mmc_register] add mmc dev_num=1, port=2, if_type=6 SDIO Port B: 0, SDIO Port C: 1 PMU fault status: reg[0x9A] = 0x1d LSI version:04, OTP version:0c PMU type:RN5T618 register usb cfg[0][1] = 7ff6fccc register usb cfg[2][0] = 7ff731dc NAND: SPI BOOT: boot_device_flag 0 Nand PHY driver Version: 1.01.001.0004 (c) 2013 Amlogic Inc. amlnf_phy_init : amlnf init flag 0 NAND device id: 2c 64 44 4b a9 0 0 0 detect NAND device: B revision NAND 8GiB MT29F64G08CBABA AML_NAND_NEW_OOB : new oob bus_cycle=5, bus_timing=7,system=3.9ns,flash->T_REA =16,flash->T_RHOH=15 NAND CKECK : arg nbbt: arg_valid= 1, valid_blk_addr = 4, valid_page_addr = 0 NAND CKECK : arg ncnf: arg_valid= 1, valid_blk_addr = 5, valid_page_addr = 0 NAND CKECK : arg nkey: arg_valid= 1, valid_blk_addr = 8, valid_page_addr = 132 i=0,register --- nand_key nfcache : offset: 0x000006000000 -0x000024800000 : partitons 1 : single_chip multi_plane nfcode : offset: 0x00002a800000 -0x000073800000 : partitons 5 : single_chip multi_plane nfdata : offset: 0x00009e000000 -0x000162000000 : partitons 1 : single_chip multi_plane bad block count = 0 bad block count = 0 bad block count = 0 amlnf_logic_init: START aml_nftl_start:117,size_in_blk=145,tmp_block=128,part->free_block_num=17 aml_nftl_start:117,size_in_blk=462,tmp_block=416,part->free_block_num=46 amlnf_logic_init: COMPLETE get_boot_device_flag: init_ret 0 get_boot_device_flag SPI BOOT: nand init success, change the device_boot_flag to 4 : spi+nand SPI BOOT,spi_env_relocate_spec : env_relocate_spec 53 SF: Detected W25Q16 with page size 256, total 2 MiB SPI NOR Flash have write protect!!! set_storage_device_flag: store 4 Multi dtb tool version: v2 . Multi dtb detected, support 6 dtbs. aml_dt soc: m8 platform: k200 variant: 2gsdhc dtb 0 soc: m8 plat: k200 vari: 2gsdhc dtb 1 soc: m8 plat: k200 vari: 2gsdio dtb 2 soc: m8 plat: k200 vari: sdhc dtb 3 soc: m8 plat: k200 vari: sdio dtb 4 soc: m8m2 plat: n200 vari: 1G dtb 5 soc: m8m2 plat: n200 vari: 2G Find match dtb: 0 vpu driver detect cpu type: m8 vpu clk_level in dts: 7 set vpu clk: 364300000Hz, readback: 364300000Hz(0x700) Net: Meson_Ethernet init suspend firmware done. (ret:0) cvbs trimming.1.v5: 0xa0, 0x7 cvbs performance type = 0, table = 0 vdac open.1 = 0x1, 0x7 [ImgPck]ver=2 reboot_mode=charging Hit Enter key to stop autoboot -- : 0 exit abortboot: 0 current storer:nand_key key save is auto select storer(nand or emmc) write key code version3_flush:708,prov->write:7fee8470 size:4096 arg_pages:1 extra_page:0 write key ok!! Booting... pos 509 value is 20ERR(v2_common/optimus_download_key.c)L268:failed to query key state, rc 0, keyIsBurned=0 ## ANDROID Format IMAGE ## Booting kernel from Legacy Image at 12000000 ... Image Name: Linux-3.10.33 Image Type: ARM Linux Kernel Image (lzo compressed) Data Size: 6522503 Bytes = 6.2 MiB Load Address: 00208000 Entry Point: 00208000 Verifying Checksum ... OK Ramdisk start addr = 0x12639000, len = 0xdb559 Multi dtb tool version: v2 . Multi dtb detected, support 6 dtbs. aml_dt soc: m8 platform: k200 variant: 2gsdhc dtb 0 soc: m8 plat: k200 vari: 2gsdhc dtb 1 soc: m8 plat: k200 vari: 2gsdio dtb 2 soc: m8 plat: k200 vari: sdhc dtb 3 soc: m8 plat: k200 vari: sdio dtb 4 soc: m8m2 plat: n200 vari: 1G dtb 5 soc: m8m2 plat: n200 vari: 2G Find match dtb: 0 Flat device tree start addr = 0x12715000, len = 0x51b4 magic=0xedfe0dd0 Uncompressing Kernel Image ... OK uboot time: 2760337 us. EFUSE machid is not set. Using machid 0xf81 from environment From device tree /memory/ node aml_reserved_end property, for relocate ramdisk and fdt, relocate_addr: 0x50e5001 Loading Ramdisk to 05009000, end 050e4559 ... OK Loading Device Tree to 05000000, end 050081b3 ... OK Starting kernel ... [ 0.000000@0] Booting Linux on physical CPU 0x200 i must be doing something wrong? any help?
RaptorSDS Posted March 22, 2019 Posted March 22, 2019 do you test the other dtb that are inside the dtb folder because older dtb files may not compatible with dtb selector; also do you look inside extracted dbt files did it look the same structure as the dtb that are inside the folder
Recommended Posts