-
Posts
394 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Community Map
Everything posted by amirul
-
Single Armbian image for RK + AML + AW (aarch64 ARMv8)
amirul replied to balbes150's topic in General Chat
X88 King meson-g12b-gtking boots to login...no usb -
Android firmware update X88King_20200113-1030 changelog: 1. optimize system 2. fix bugs
-
Armbian_19.11.4_Odroidn2_bionic_legacy_4.9.205_desktop, no boot The Arm-64 images seem to boot fine to desktop, now if I could just get some form of keyboard input going...
-
Tried ubuntu-18.04.3-4.9-minimal-odroid-n2-20190806.img on sdcard, does not boot Guess I wait for balbes image to fix the usb, or android on the box to update to kernel 5
-
thanks
-
Pardon the ignorance, but where do I get a native odroid image?
-
I've tried Armbian_5.87_Odroid-n2_Ubuntu_bionic_default_4.9.177_desktop_20190529, does not boot there is no uEnv.ini to fiddle with I guess what would work is an Armbian_19.11.4_Arm-64 spin with a 4.9 kernel
-
Manufacturer? https://www.tvbox-manufacturer.com/product/b2go-x88-king-s922x/
-
Single Armbian image for RK + AML + AW (aarch64 ARMv8)
amirul replied to balbes150's topic in General Chat
Armbian_19.11.5_Aml-g12_bionic_dev_5.5.0-rc5-next-20200110_desktop on T95Z Plus s912 Boots to login, no usb keyboard ... the same with X88 King -
https://androidpctv.com/magicsee-n6-plus-s922x-opinion/ Magicsee coming in with 128GB eMMc
-
T95Z Plus (ethernet working for kernel 5.3.0)
amirul replied to mumpitzstuff's topic in General Chat
My T95Z Plus works with meson-gxm-q200.dtb. I guess they come with different ethernet chips -
Not even headless because I believe ethernet is not working either on the X88
-
Ok understood. Perhaps I'll give it a go then.
-
It seems that running coreelec will alter the tv box and would require full firmware recovery in order to run armbian afterwards.
-
wanted to try Armbian_5.87_Odroid-n2_Ubuntu_bionic_default_4.9.177_desktop_20190529.img.xz from https://yadi.sk/d/pHxaRAs-tZiei/OLD/5.87/Odroid_N2 but it seems that I've exceeded my download limit
-
Could be the difference in kernel version, android is kernel 4.9 while armbian is kernel 5.5?
-
I have a feeling it's a bit more complicated because in the armbian odroid n2 dtb are the following references to usb: bank@40 { reg = <0x0 0x40 0x0 0x4c 0x0 0xe8 0x0 0x18 0x0 0x120 0x0 0x18 0x0 0x2c0 0x0 0x40 0x0 0x340 0x0 0x1c>; reg-names = "gpio", "pull", "pull-enable", "mux", "ds"; gpio-controller; #gpio-cells = <0x2>; gpio-ranges = <0xe 0x0 0x0 0x56>; phandle = <0x14>; usb-hub { gpio-hog; gpios = <0x14 0x0>; output-high; line-name = "usb-hub-reset"; }; }; .... phy@36000 { compatible = "amlogic,g12a-usb2-phy"; reg = <0x0 0x36000 0x0 0x2000>; clocks = <0x10>; clock-names = "xtal"; resets = <0x8 0x30>; reset-names = "phy"; #phy-cells = <0x0>; phy-supply = <0xb>; phandle = <0x31>; }; --- phy@3a000 { compatible = "amlogic,g12a-usb2-phy"; reg = <0x0 0x3a000 0x0 0x2000>; clocks = <0x10>; clock-names = "xtal"; resets = <0x8 0x31>; reset-names = "phy"; #phy-cells = <0x0>; phy-supply = <0x11>; phandle = <0x32>; }; ... phy@46000 { compatible = "amlogic,g12a-usb3-pcie-phy"; reg = <0x0 0x46000 0x0 0x2000>; clocks = <0x3 0xc9>; clock-names = "ref_clk"; resets = <0x8 0xe>; reset-names = "phy"; assigned-clocks = <0x3 0xc9>; assigned-clock-rates = <0x5f5e100>; #phy-cells = <0x1>; phandle = <0x33>; }; --- usb@ffe09000 { status = "okay"; compatible = "amlogic,meson-g12a-usb-ctrl"; reg = <0x0 0xffe09000 0x0 0xa0>; interrupts = <0x0 0x10 0x4>; #address-cells = <0x2>; #size-cells = <0x2>; ranges; clocks = <0x3 0x2f>; resets = <0x8 0x22>; dr_mode = "otg"; phys = <0x31 0x32 0x33 0x4>; phy-names = "usb2-phy0", "usb2-phy1", "usb3-phy0"; vbus-supply = <0x34>; usb@ff400000 { compatible = "amlogic,meson-g12a-usb", "snps,dwc2"; reg = <0x0 0xff400000 0x0 0x40000>; interrupts = <0x0 0x1f 0x4>; clocks = <0x3 0x37>; clock-names = "ddr"; phys = <0x32>; phy-names = "usb2-phy"; dr_mode = "peripheral"; g-rx-fifo-size = <0xc0>; g-np-tx-fifo-size = <0x80>; g-tx-fifo-size = <0x80 0x80 0x10 0x10 0x10>; }; usb@ff500000 { compatible = "snps,dwc3"; reg = <0x0 0xff500000 0x0 0x100000>; interrupts = <0x0 0x1e 0x4>; dr_mode = "host"; snps,dis_u2_susphy_quirk; snps,quirk-frame-length-adjustment; }; }; ... regulator-usb_pwr_en { compatible = "regulator-fixed"; regulator-name = "USB_PWR_EN"; regulator-min-microvolt = <0x4c4b40>; regulator-max-microvolt = <0x4c4b40>; vin-supply = <0xb>; gpio = <0x14 0x16 0x0>; enable-active-high; phandle = <0x34>; };
-
Look forward to your results. I already have Armbian running on TX9 Pro s912 3gb but probably TX9S is wildly different Waiting for reviews to come in for the Orange Pi 4 rk3399 before putting in the order. Looks great on paper, performance and price
-
Awesome. I look forward to the results of your investigations
-
As far as I can tell from the android dts, these are the bits that look like they have reference to usb dwc3@ff500000 { compatible = "synopsys, dwc3"; status = "okay"; reg = <0xff500000 0x100000>; interrupts = <0x0 0x1e 0x4>; usb-phy = <0x2a 0x2b>; cpu-type = "gxl"; clock-src = "usb3.0"; clocks = <0x13 0x41>; clock-names = "dwc_general"; phandle = <0xdd>; }; usb2phy@ffe09000 { compatible = "amlogic, amlogic-new-usb2-v2"; status = "okay"; reg = <0xffe09000 0x80 0xffd01008 0x100 0xff636000 0x2000 0xff63a000 0x2000>; pll-setting-1 = <0x9400414>; pll-setting-2 = <0x927e0000>; pll-setting-3 = <0xac5f69e5>; pll-setting-4 = <0xfe18>; pll-setting-5 = <0x8000fff>; pll-setting-6 = <0x78000>; pll-setting-7 = <0xe0004>; pll-setting-8 = <0xe000c>; portnum = <0x2>; phandle = <0x2a>; }; usb3phy@ffe09080 { compatible = "amlogic, amlogic-new-usb3-v2"; status = "okay"; reg = <0xffe09080 0x20>; phy-reg = <0xff646000>; phy-reg-size = <0x2000>; usb2-phy-reg = <0xffe09000>; usb2-phy-reg-size = <0x80>; interrupts = <0x0 0x10 0x4>; clocks = <0x13 0x18>; clock-names = "pcie_refpll"; portnum = <0x0>; otg = <0x1>; phandle = <0x2b>; }; dwc2_a@ff400000 { compatible = "amlogic, dwc2"; status = "okay"; device_name = "dwc2_a"; reg = <0xff400000 0x40000>; interrupts = <0x0 0x1f 0x4>; pl-periph-id = <0x0>; clock-src = "usb0"; port-id = <0x0>; port-type = <0x2>; port-speed = <0x0>; port-config = <0x0>; port-dma = <0x0>; port-id-mode = <0x0>; usb-fifo = <0x2d8>; cpu-type = "v2"; phy-reg = <0xffe09000>; phy-reg-size = <0xa0>; phy-interface = <0x0>; clocks = <0x13 0x41 0x13 0x49>; clock-names = "usb_general", "usb1"; controller-type = <0x3>; phandle = <0xde>; }; How to translate to armbian dts is beyond me at the moment
-
Thanks for the suggestion but that might just be beyond my capabilities
-
I have gone dtb -> dts -> changed a few things -> dtb with some success, cpuspeed for eg, but in this case the usb subsystem doesn't fire up at all. With meson-g12b-ugoos-am6.dtb I can get to the desktop, but without usb no keyboard and mouse. 1'll try looking for clues in the extracted dtb/dts. There is reference to g12b_w400_a in the dtb, for odroid N2 perhaps?
-
Thanks for making them for me Unfortunately none of them works I'll root around in the dts to see what's going on. Thanks again
-
How about this file I got from the box android /dev ? dtb
-
This is where I got the img from https://1drv.ms/u/s!ArKioz4lbRJGknWuscSuulC6gUdy?e=0TNnOw Maybe someone else could have better luck extracting the dtb