Jason Duhamell

Essentially I compared the standard EVB (Evaluation Board) DTS against the DTS I extracted from the original android firmware. I used CSC to make a back-up of the original android firmware onto the SD card, from there I just extracted the boot.img from the back-up. Using " extract-dtb" provided by PabloCastellano, I was able to extract a DTB, and subsequently use DTC to convert it into a readable DTS. Using comparison tools like "Meld", I focused in on the hardware differences. I am very inexperienced and only started working on this project as a means to compare the cost to performance ratio of this TV box compared to something such as a Raspberry pi. Both the Wi-Fi and eMMC are wired to the sdmmc_ext bus instead of the normal SDIO bus. That is why, originally, I was not able to run the rk3318 legacy build off of the internal storage, it was not able to detect the "alternate" bus. If I had to guess, it is how the address to hex code conversion was done. From some porting documents I read, the proper address should be like <&gpio3 pin_the_power_tied_to active_high>, compared to 0xcd being the hex address for gpio3, but I don't know what 0x01 or 0x08 are supposed to be in EVB DTS? Any advice on how to map-out the gpio pins would be appreciated.

I am getting closer with my modifications to the DTS file. I am now able to get it to boot from emmc on the rk3318 legacy image you had posted. The only part I am still playing around with to see if I can get it to work is the wifi. From what I can tell, the wifi chip should be activated, but the wifi is still not working. Any advice would be much obliged. rk3328-evb-test.dts

Is this what you mean by the "Alternate bus"? It uses sdmmc_ext instead of sdio. dwmmc@ff5f0000 { compatible = "rockchip,rk3328-dw-mshc\0rockchip,rk3288-dw-mshc"; reg = <0x00 0xff5f0000 0x00 0x4000>; clock-freq-min-max = <0x61a80 0x8f0d180>; clocks = <0x02 0x140 0x02 0x1f 0x02 0x4d 0x02 0x51>; clock-names = "biu\0ciu\0ciu-drv\0ciu-sample"; fifo-depth = <0x100>; interrupts = <0x00 0x04 0x04>; status = "okay"; bus-width = <0x04>; cap-sd-highspeed; cap-sdio-irq; disable-wp; keep-power-in-suspend; max-frequency = <0x23c3460>; mmc-pwrseq = <0x79>; non-removable; num-slots = <0x01>; pinctrl-names = "default"; pinctrl-0 = <0x7a 0x7b 0x7c>; supports-sdio; sd-uhs-sdr104; phandle = <0xcf>;

I am inching my way to a working DTB. Here is a copy of a dmesg log from the Station M1 Legacy build.

I have attached some photos of the MX10 Pro. I also made a backup of the original android firmware if there is any interest in me uploading it.

I read the part number off of the wi-fi chip. I am working on making my own DTB for the board, but I need to reinstall Ubuntu to compile my own Armbian. I will upload some photos of the board in a bit, but the board does not have a UART port from what I can see so far, taking a proper log of the bootup will be difficult, but I will try and take a screenshot with my phone.

I have a MX10 Pro TV box I have been trying to get working with the dreaded SV6051 wifi. The board silkscreen is labeled as MXQ-RK3328-D4_A VER: 1.2. The board itself is 4GB ram and 64GB eMMC and everything is working other than the wifi. So far I am only having luck with RK3318 mainline and the rk3328 legacy Station M1 builds. The board will not boot with the legacy rk3318 build. The other issue I have noticed is when I use rk3318-config to enable the alternate SDIO bus, it will hang on reboot. I have decompiled the DTS from the Android backup I made using the Multitool (Multitool is a lifesaver, thank you.).