Ben N Voutour

@curse
Sorry for the late answer, but I just spot the post edit right now.
 
wlan and bluetooth, despite being on the same chip, are connected to the SoC in different ways: wlan is connected via high-speed sdio bus, bluetooth via common UART; also they are physically different chip parts that just share some things (the radio part), so it may happen that one work and the other does not.
 
Since rk3318-config correctly reports the right chip, it is attached to the right sdio bus.
Now there there may be some board peculiarities that does not make it work.
 
In the first post of this thread there are some good things that help in debugging, in particular if you can provide photos of the board and the original firmware or the original dtb I can inspect it and try solve the issue.
If you can spot some marking/signatures on the board, you can see if there is a match in rk3318-conf when it asks for "led/gpio configuration".
 
At the moment there are just two supported boards: YK_RK3328 (found on my HK1 Max) and X88_PRO_B ( @lucky62's box); maybe yours is a different one that require some minor adjustment to make wifi work.

Sweet. I'll do some testing and get back to you. 
 
Edit
Testing done. 
Most things seem to work. 
Ethernet OK
HDMI Video out OK
HDMI Audio Ok
Bluetooth Audio OK
 
However, I don't seem to be able to connect to WiFi. Odd since Bluetooth and WiFi is the same chip. Armbian-Config and nmcli see it, it also shows the available networks but when trying to connect. No luck. 
rk3318-config says that I have a Broadcom BCM4335/AmPac AP6334 chip. 
Somehow the WiFi times out after 90 seconds and after it has asked me twice for the password, which I know is correct. 
Also, no network settings icon is visible near the clock where the sound and Bluetooth icons are. 
No Web Browser seems to be installed, though the menu item for Web Browser is there. No problem since I had ethernet and could install a Web Browser (and without ethernet or wifi, there is no need for a browser) 
So... H96 Max plus (written with a '+'). RK3328. 4GB RAM and 64GB eMMC. Confirmed mostly working. 
 
Next edit
The version I tried was: Armbian 21.08 - Ubuntu Focal desktop [xfce] - mainline kernel 5.10.41 - Build date: 2021-05-30

Yeah, you're right: the thread title is a bit misleading, because rk3318 and rk3328 are fundamentally the same chip.
It is so because I have no rk3328 to work on, so can't guarantee and test anything on that. People reported that the images works as well on rk3328 boards, so you're invited to try and report if it works for you.
There are good chances that the images works fine, and ap6330 is well supported in mainline kernel, including bluetooth!

I had missed this thread thinking it was only about RK3318 devices, but do I understand it correctly if I say it's for RK3328 devices as well? 
I have a H96 Max Plus RK3328 4/64 box that I've been fighting with for a while. I mostly have had problems with the WiFi.
Reading through this thread seems to show that the ap6330 WiFi I have isn't impossible after all. I've mostly had problems finding a good dtb, that includes it. 
Would there be a chance that this would work on my box? 

AFAIK there is no such tool for rk3188

In the previous post you stated your box is an rk3188 box, this is the thread for rk3318.
If your box is an rk3318, please provide as many as possible of the things described in the first post (logs, photos, original dtb), otherwise it is impossible to help.
HDMI issues are common if cable is cheap, or the monitor less non usual resolution (like 1920x1200, for example)
 

I have now tried a new Class 10 SD card and the same problem still persists. I am using the original power supply as well and there are no power issues.
Any suggestions?

Hi,
 
Newbie here. I have an old CloudGate TV Box. It's an RK3188 based unit that I want to try an repurpose for Home Automation.
 
I downloaded the multitool image, used BalenaEtcher to burn it to an SD Card. Popped the SD Card into the TV Box and turned it on.
 
Unfortunately it just booted into the standard Android OS not the multitool. If I use the file explorer on the box it can see the SD Card and the files on it.
 
Am I missing a step? Or is there something I need to do to boot from SD?
 
thanks.

Hello. At the bottom of the first post there are some useful things you can share to help you.
In particular, serial logs and photos of the board are important, because H96 Max is just the market name, but the board hardware often differs.

For my H96 Max 4GB 64GB box, the Debian Buster minimal - legacy kernel (Built date 2021-04-16) boots up fine after burning it to the emmc using the multitool image. Wired connection works fine, but the wifi does not work (the interface shows up, but nmtui is unable to connect to access point).
 
But other images (Debian Buster minimal - mainline kernel, and Ubuntu Focal desktop [xfce], built date 2021-05-30) does not boot (I think). Specifically, after burning to emmc with multitool image, when I plug the box in, HDMI output remains dark.
 
I saw on the forum that some people managed to get the exact same box to boot.
 
I'll appreciate any help with trouble shooting to figure out what I am doing wrong.

here is a useful repo
https://github.com/kthejoker20
it has the same tool i just uploaded to my G-Drive. and some more...
i'll keep looking for other tools and newer versions as well when available.

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>;  

@RetroFan90

here it comes, but you can also do by yourself looking for the firmware I suggested you
 
3318-OCVR.nPI.dts.zip

@RetroFan90
They are all HK1, the circle one , many but really many have exploded regulators on ddr V+ since the ddr are poorly soldered and/or defective and they have short circuits on the bga balls

Here for you a dts from one of the firmware you send (1.4.1_atv_rk_10.img)

The tool for extracting dtb's is called RK3xxx_firmware_tools_5.23.1_by_SergioPoverony.zip
 
3318dts.zip

how do get the dts file for my box?
do i need to use multitool to dump it first?
i want my clock to work in armbian along with working graphics and a decent overclock
i know that dmssru on 4pda ru forums made a semi decent attempt to overclock android 9 for h96 max but my wifi and bt would not work properly.
and how do i get the metal can off my wifi module? it seems to be soldered on.
here is the firmware for the h96 max modded by dmssru on 4pda
https://drive.google.com/drive/folders/1W7BkOj1Q16O_wvlLlFh06v_D5Yol9KvE
and here is the tools and Firmware , Software & Drivers
https://drive.google.com/drive/folders/1vevBj3JySrkcurvnLPqU6aY-5APtXHYI
and here some random builds as well
https://drive.google.com/file/d/1w1KgbetDIIIU08-jmN3ll_0IF9cR5Lic/view
also this...
https://drive.google.com/file/d/1l_WECaMMWS0BI0rIY7uiWcw6X_BPu-yZ/view?usp=sharing
 
Hope These help

@RetroFan90

I do agree totally with @jock : overclock 3318 is a terrible idea.

We suspect that 3318 is the " poor brother " of 3328 , or in other words , 3318 is a badly assembled/builded 3328 that has some electric electronic characteristic that made impossible to call it 3328 so was downgraded to 3318
I have more than 30 defective 3318 with broken emmc, ddr that go higher than 100 celsius and I wouldn't even try to overclock the few 3318 that are working

In the previous pages I posted some instructions on how to let it work.
The driver for various led drivers is available on github and needs to be manually compiled. I did not include it yet because it has some limitations I would like to fix before integrating into.
Overclock: bad idea on rk3318, but your mileage may vary
 
Why do you want to remove the metal can? It is a very bad idea, it shields the wifi from interferences and if you remove it, probably your wifi/bt will have troubles.
 
There are various instructions over the internet, but what are you expecting from the dts?

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. 

From the dts you posted, the wifi chip is attached to the "alternate" sdio bus.
From the dts also there is no evidence that your wifi chip is sv6051p, that is anyway not supported in mainline kernel. To understand why your box is hanging on reboot if you select the alternate sdio bus there is the need for a detailed log from the serial.
 
edit: photos of the board and chips are welcome and interesting

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

Well, installing the wrong firmware on the wrong box is usually the best recipe to brick the box, as you experienced by yourself.
Just in case someone else reads and wants to do that, it is something that I absolutely DO NOT recommend to do unless you exactly know what are you doing. It's not your case, I see you're fine because you got the eMMC clk pin to put the board in maskrom mode, but not all rk3318/rk3328 have accessible eMMC clock pin.
 
Anyway thanks for the large list of rk3318 firmwares, it will be interesting to scavenge for firmwares and blobs

i don't have an h96 max , only HK1 Max but some versions of h96 max firmware work fairly normal
some versions have wifi 2.4 + 5 GHz with BT 4 but some versions of h96 max firmware have issues with bluetooth in the sense that when you try to pair anything to it , it connects for a split second and then turns off bt and is reproducible on my HK1 Max but might be different...
like for example the m96 and x88 and some other clones seem to have issues getting the 7 segment 4 digit LED Display to show up after booting on HK1MAX.
some 3328 native firmwares seem to cause the 3318 some trouble by softbricking the loader (which is unbrickable at the hardware level (why i picked RockChip as my main box in the first place.) if all else fails you short the two copper dots with a pair of angled tweezers and plug the usb into the 2.0 port as the 3.0 port won't work afaik in my testing so far...
i'll send links to the android 11 firmware along with 9 & 10 soon...

here are some of the same dtb + kernel dumps of firmwares that seemed to work on my hk1 max rk3318 3328 fake?
https://drive.google.com/file/d/1q2x9a9gO5lHe54a6Y8SLlfidCSD7Ycga/view?usp=sharing

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.).