Blackenz Posted March 5 Posted March 5 @Nick A using the @rafman image that he previously posted (Armbian-unofficial_24.11.0-trunk_X96q-v5-1_bookworm_current_6.6.44_mate_desktop.img.xz), on the same card, the tv box boots from the sdcard just fine. I am assuming that the image that is being generated by the compile.sh script from the oficial repo, has some kind of problem. Anyway, i will try pushing the button on the AV port, with my image, just to eliminate that possibility. Thanks 0 Quote
Nick A Posted March 6 Posted March 6 (edited) Try building an image using sicXnull's branch. git clone https://github.com/sicXnull/armbian-build.git --branch X96Q-5.1-DDR3 --single-branch Patch directory is. patch/u-boot/u-boot-sunxi/board_x96q-v5-1 He also has a branch called "X96Q-TVBOX-LPDDR3" Edited March 6 by Nick A 0 Quote
Blackenz Posted March 6 Posted March 6 Hi @Nick A, So i just happened to do exactly that. I used sicXnull's branch and tvbox is finally booting from the sdcard, running my custom image. Didn't have to apply your patch. Any thoughts on merging @sicxnull branch into armbian official codebase? Thanks for your help 0 Quote
Nick A Posted March 6 Posted March 6 (edited) I'm busy with another build but If anyone wants to send a PR? I don't think sicxnull would mind. A lot of the source comes from Warpme's Minimyth2 patches. https://github.com/warpme/minimyth2/blob/master/script/bootloaders/u-boot-h616/files/150-add-x96-q-lpddr3-defconfig.patch https://github.com/warpme/minimyth2/blob/master/script/bootloaders/u-boot-h616/files/151-add-x96-q-ddr3-defconfig.patch https://github.com/warpme/minimyth2/blob/master/script/bootloaders/u-boot-h616/files/159-add-x96-q-lpddr3-v1.3-defconfig.patch https://github.com/warpme/minimyth2/blob/master/script/bootloaders/u-boot-h616/files/163-add-x96-q-ddr3-v5.1-defconfig.patch Sicxnull already sent a PR for "X96Q-TVBOX-LPDDR3" branch back in august. https://github.com/armbian/build/pull/7101 Clone the Official Armbian build then add Sicxnull/Warpme changes. Send a PR. Edited March 6 by Nick A 0 Quote
Nick A Posted March 6 Posted March 6 (edited) If anyone wants to test my Armbian unofficial build using the latest Armbian 25.05.0 build, Kernel 6.12.11 and miniarch patches. I compiled all 4 versions of X96Q. If you need secure boot or desktop build let know. This is a work in progress so I might be updating the build often. Images: https://github.com/NickAlilovic/build/releases/tag/20250306 Sources: git clone https://github.com/NickAlilovic/build.git --branch v20250306 Edited March 7 by Nick A 0 Quote
Blackenz Posted March 6 Posted March 6 (edited) Hi @Nick A! I will test it for sure. On another subject, i found my dmesg filled with these messages: These happen on sub second as you may notice. I am worried that this issue will eventually kill my EMMC... Anyone else seeing this behavior? Edited March 7 by Blackenz 0 Quote
lynya5 Posted March 10 Posted March 10 Цитата Nick A Hi, I would be grateful for assembling armbian desktop ubuntu xfce. Thanks 0 Quote
Nick A Posted March 10 Posted March 10 (edited) Hi @lynya5 Can you test the server images and let me know which version works for you. Edit: Never mind.. I had time so I compiled ubuntu xfce for all 4 x96q versions. Remember you have a custom kernel. You need to block kernel updates with the armbian config tool. Edited March 10 by Nick A 0 Quote
lynya5 Posted March 11 Posted March 11 Цитата Never mind.. I had time so I compiled ubuntu xfce for all 4 x96q versions. Hi Nick A. Thank you very much for building xfce. I will test it and write back later. Thanks 0 Quote
Wan Lan Posted March 16 Posted March 16 @Nick A hello sir, would it be possible to provide a secure boot version for x96q h313 or h616? thank you so much 0 Quote
Nick A Posted March 16 Posted March 16 Not sure which version you have.. I'll make a secure boot image for all 4 versions of x96q. 0 Quote
Wan Lan Posted March 16 Posted March 16 I have both an H616 and an H313 (the latter is not pictured). I've tested nearly every X96Q Armbian build as well as Miniarch, but they have all resulted in issues such as a black screen, no HDMI output, or booting directly into Android. 0 Quote
Nick A Posted March 17 Posted March 17 @Wan Lan you should install a serial console. You can see GND,TX and RX on your board. https://linux-sunxi.org/UART Also, the last Miniarch release had a bug where it would freeze trying to detect the dram size. https://github.com/NickAlilovic/build/releases/tag/20250306 my images has the dram bug fixed. 0 Quote
Wan Lan Posted March 18 Posted March 18 Just tried that image, it boots straight to Android unfortunately. Can you please recommend me a brand to purchase? 0 Quote
Wan Lan Posted March 20 Posted March 20 @Nick A Hello, I've extracted the DTS for my device 01_dtbdump.dtb.dts 0 Quote
Nick A Posted March 20 Posted March 20 (edited) @Wan Lan Try this image.. if it doesn't work. I'll make a SECURE BOOT version. If they both don't work then you need a serial console. https://github.com/NickAlilovic/build/releases/download/20250306/Armbian-unofficial_25.05.0-trunk_X96q-lpddr3-v1-3_noble_edge_6.12.11_xfce_desktop.img.xz Your power controller is axp1530 aka axp313a pmu { compatible = "x-powers,axp1530"; reg = <0x36>; wakeup-source; linux,phandle = <0x128>; phandle = <0x128>; standby_param { vcc-dram = <0x4>; linux,phandle = <0x129>; phandle = <0x129>; }; regulators { dcdc1 { regulator-name = "axp1530-dcdc1"; I think these are your Dram Settings dram_select_para { device_type = "dram_select_para"; select_mode = <0x1>; select_gpio0 = <0x53 0x8 0xe 0x0 0x1 0xffffffff 0xffffffff>; select_gpio1 = <0x53 0x8 0xf 0x0 0x1 0xffffffff 0xffffffff>; select_gpio2 = <0x53 0x8 0x10 0x0 0x1 0xffffffff 0xffffffff>; select_gpio3; }; dram_para1 { device_type = "dram_para1"; dram_clk = <0x288>; dram_type = <0x7>; dram_dx_odt = <0x6060606>; dram_dx_dri = <0xd0d0d0d>; dram_ca_dri = <0xd0d>; dram_odt_en = <0x1>; dram_para1 = <0x30fa>; dram_para2 = <0x0>; dram_mr0 = <0x0>; dram_mr1 = <0xc3>; dram_mr2 = <0x6>; dram_mr3 = <0x1>; dram_mr4 = <0x0>; dram_mr5 = <0x0>; dram_mr6 = <0x0>; dram_mr11 = <0x0>; dram_mr12 = <0x0>; dram_mr13 = <0x0>; dram_mr14 = <0x0>; dram_mr16 = <0x0>; dram_mr17 = <0x0>; dram_mr22 = <0x0>; dram_tpr0 = <0x0>; dram_tpr1 = <0x0>; dram_tpr2 = <0x0>; dram_tpr3 = <0x0>; dram_tpr6 = <0x2fa88080>; dram_tpr10 = <0x2f3359>; dram_tpr11 = <0xaa889967>; dram_tpr12 = <0xeeee8979>; dram_tpr13 = <0x60>; }; or it could be this one. The dram_type = <0x3>; in this one and dram_type = <0x7>; above. [329]DRAM Type =? (3:DDR3,4:DDR4,7:LPDDR3,8:LPDDR4) dram { compatible = "allwinner,dram"; clocks = <0xd9>; clock-names = "pll_ddr"; dram_clk = <0x288>; dram_type = <0x3>; dram_zq = <0x3f3fdd>; dram_odt_en = <0x1>; dram_para1 = <0x30fb>; dram_para2 = <0x0>; dram_mr0 = <0x840>; dram_mr1 = <0x4>; dram_mr2 = <0x8>; dram_mr3 = <0x0>; dram_tpr0 = <0xc0000007>; dram_tpr1 = <0x0>; dram_tpr2 = <0x100>; dram_tpr3 = <0x0>; dram_tpr4 = <0x0>; dram_tpr5 = <0x0>; dram_tpr6 = <0x33808080>; dram_tpr7 = <0x0>; dram_tpr8 = <0x0>; dram_tpr9 = <0x0>; dram_tpr10 = <0x2f6606>; dram_tpr11 = <0xffffdddd>; dram_tpr12 = <0xfedf7657>; dram_tpr13 = <0x40>; linux,phandle = <0x17c>; phandle = <0x17c>; device_type = "dram"; dram_dx_odt = <0x3030303>; dram_dx_dri = <0xe0e0e0e>; dram_ca_dri = <0x1c16>; dram_mr4 = <0x0>; dram_mr5 = <0x0>; dram_mr6 = <0x0>; dram_mr11 = <0x0>; dram_mr12 = <0x0>; dram_mr13 = <0x0>; dram_mr14 = <0x0>; dram_mr16 = <0x0>; dram_mr17 = <0x0>; dram_mr22 = <0x0>; }; Edited March 20 by Nick A 0 Quote
Nick A Posted March 20 Posted March 20 If you had a serial console we can get an android and armbian boot log. Not easy to debug errors without it. 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.