fabiobassa

There is such 2734C chip, a google search would have confirmed that to you easily.
The chipset under the hood is an ampak AP6334 which is in turn made of a couple of broadcom chips. The wireless part is a bcm4334.
 
Probably your issue is not the dtb but the wifi chip firmware or, more in particular, the nvram /lib/firmware/brcm/brcmfmac4334-sdio.rockchip,rk3318-box.txt which is not suitable for your board setup. The wifi depends on how the board is build for important things like reference frequency, antenna setup, sideband gpio, etc... If the nvram does not specify these params correctly, it will not perform well or will not work at all.
 
The best thing you could do is mount the vendor partition of your Android firmware and search for a suitable firmware for your board or extract from the live Android system.
Tthat could be easy but could also require various steps  to get access to the partition, it depends and how the firmware is built.
 
Otherwise you could look around in google, download new nvrams for bcm4334/ap6334 and try and see if they work for you.
 
edit: BTW the wifi chip is fully supported by linux kernel and works wonderfully well on my board; when I say don't buy tv boxes if you want supported hardware I mean exactly this.
 

All right.. We got our own topic for Docker talking 😁

Done.  I went back to the end of April and tried to pull out all the docker related posts into this new thread.  If you think I should go back farther, or if some of these posts should be moved back to the original thread let me know.

UPDATE!!
 
Hello, I'm pleased to announce that rk3318 CSC configuration has been accepted into mainline kernel!.
This means that next Armbian release (probably August) will provide regular kernel upgrades offered by Armbian ecosystem via normal apt upgrade command.
Until then, please stay stick to the usual manual upgrade!
 
But there is something more: new update for the rk3318/rk3328 images!
Most important changes:
Kernel upgraded to version v5.18.6 Memory clock set to 667 MHz (was 333 MHz), providing a nice boost in general, desktop and GPU performance; despite this works fine on my board I always warn you to test images first via sdcard Introduces MGLRU patches from @yuzhaogoogle (you can read about here and search google for more details), which should provide much snappier experience especially on low-memory devices You can find the images and deb packages for upgrades browsing the directory pointed on first page as usual.
 
You can visit the Armbian MGLRU topic, if you have questions about the features or kernel issues (like crash dumps which involve kswapd, for example)
 
 

Dear friends, lately many many questions on this 3ad are about docker and it's problems.

I really would suggest to open a different discussion and leave here only kernel and hardware relate problems, because if we continue here with user space implementantions the 3ad becames abnormous and difficult to read.

Maybe @MattWestB and @primoitt could start soewhere else an apposit 3ad and guide other friends into solutions.

Lately if solution needs an intervent on kernel all of you will be welcome to ask here

Thanks a lot !!! 🤗

 

Dear friends, lately many many questions on this 3ad are about docker and it's problems.

I really would suggest to open a different discussion and leave here only kernel and hardware relate problems, because if we continue here with user space implementantions the 3ad becames abnormous and difficult to read.

Maybe @MattWestB and @primoitt could start soewhere else an apposit 3ad and guide other friends into solutions.

Lately if solution needs an intervent on kernel all of you will be welcome to ask here

Thanks a lot !!! 🤗

 

Dear friends, lately many many questions on this 3ad are about docker and it's problems.

I really would suggest to open a different discussion and leave here only kernel and hardware relate problems, because if we continue here with user space implementantions the 3ad becames abnormous and difficult to read.

Maybe @MattWestB and @primoitt could start soewhere else an apposit 3ad and guide other friends into solutions.

Lately if solution needs an intervent on kernel all of you will be welcome to ask here

Thanks a lot !!! 🤗

 

Ah-ha, nope... or to be precise: I guess you would need the android kernel sources/headers to compile a working driver for it.

@Revsearcher
Try to remove heatsink the uart could be there

@Felipe Triana DDR memory detection is made by a rockchip proprietary code that is called ddrbin as the very first binary code.
It's a closed source binary, so whatever it does and how it does is not known. It produces some debug messages that may be useful to you (memory arrangement, density, bus width) when the serial adapter is connected to the board.
 
There is a tool, ddrbin_tool, that can be used to alter ddr speed, ddr command rate timing and uart debug speed, but nothing more.
 
If you totally erased the NAND, then the ddrbin in use is the one from the sdcard, if you installed "jump start" with multitool, then the ddrbin in use is from NAND.
 
Multitool can't completely erase the NAND because the kernel driver has some limitations and cannot access the first sectors of the NAND, thus multitool can't neither write or read the installed ddrbin  in NAND.

@fabiobassa
 
Hi, I'm only replying now, because the forum limts one post per day for me, for now a least. Ok. Back to the topic.

Yesterday, I was trying to go back to the android because I was thinking in use the TV BOX as a temporary replacemant to my father's notebook, that stopped working and I already resoldered almost everything changed the SIO, SB etc.. Anyway, today I just boght another box, with android and installed for him, and worked fine... but would be nice to have a full backup of the nand anyway, if one day I wish to go back to original firmware, I should have done the backup. 

The box is a MXQ-4K, as i said, but now I will give details:

It features a RK3228A, with 2GB of Micron DDR3 (2 chips on top, 2 on the back of board), a 8GB BGA NAND, and a SV6051 wireless chip and R329Q_V3.0 board revision. I took some photos for more details, right below here:


Here a close up of the rockchip on this board, before I changed the heatsink
 

Here is 2 of the 4 DDR3 ram chips, its HTTC4G83BGR (4 gigabites, or 512MB per module)
 

The wireless chip, SV6051P, nothing special..


An overview of the back of the board, showing the nand and pcb shape


And finely a overview of the board powered on, running main build from SD Card...

Ok, things that I noticed, that can ou cannot be bugs:
 
So far is what I noticed... 

I would be already happy if a least I could recognize the full 2GB of ram on board and wireless worked on inbound connections, a least I could use the box as a home server, for files, websites, etc.

I found other issues that I think is maybe the hardware itself that cant cope with todays demands: main or legacy, even with multimedia tools installed, Youtube can't even play at 144p without dropping 20 to 40% of the frames, tested windowd, and fullscreen, same. Youtube keep rendering on CPU mode, with firefox or chromium, even if I run the browser with glrun command.

So far thats it, I'm afraid that I will be able only to reply after 24 hours, because of forum limitation, so in this case, until tomorrow! Thank you for the attention, 

Until are kernel related problems Is ok discuss here.
Or you can discuss elsewhere, test and then make requests here about missing features in kernel

Until are kernel related problems Is ok discuss here.
Or you can discuss elsewhere, test and then make requests here about missing features in kernel

@fedex My test script is showing the same and i can installing portainer and / or docker agent and its working OK.
What is HA complaining then you is trying installing it ?
Also the CPU is 32 bits so need using installing the "armv7l" version by selecting "raspberrypi2" or its failing.
 
@jock I think we shall not hijacking the thread with no Armbian things and you must saying if we shall stop spamming it with HA problems.

I may remember not so well because rk3318 received little attention lately, but it should be enable and provided via opensource Lima driver.
You can check if AccelMethod is set to "glamor" (enabled) or "none" (disabled) in /etc/X11/xorg.conf.d/40-serverflags.conf
As usual, it is wise to disable compositing for a bit better performance in a typical desktop usage.

@Vittorio Mori

Ciao Vittorio, buongiorno e benvenuto
I will answer in a straight manner don't consider it rude 😄 but just the answer of someone that loosed sleep trying to achieve the same as you.

 

Yes ! You have to go trought the whole compile method and then build your buildroot stripping down what is un-needed.
Now the problem is that used to exist a rockchip buildroot method described on github and i don t find anymore it

 

NO !! Unfortunately you still have to go trought the compilation method enabling compile fmpeg with some tweaking as described

here 

with this 3 " magic" flags 
 
--enable-rkmpp \ --enable-version3 \ --enable-libdrm \

or even on this same post at the beginning where @jock says as to enable to HW acceleration with some script
 
 
I did it but was a PITA !!!
hope you get your goal


 

@fabiobassa Yes. I'm thinking about the defective emmc issue because I have several 3318 boxes and 1 box get this kernel panic issue, an other box get crashed after several hours running, other ones work well over time. 

@chinhhut
home assistant is a great project but at the same time is very hard disk intensive and resource eating. In special mode if you even have motion plug-in or other pugins that extensively use the hard disk and/or internal emmc
And it also coul be a defective emmc since many chinese tvboxes are badly assembled with faulty components

@chinhhut
 
What services/app have installed?
Did kernel crashed before new installation or crashes even with unloaded system ?
As @jockexplained me, no user space applications should ever freeze/panic the kernel , unless drivers are involved.
And if kernel crashes I am afraid you Will not have any log either

@chinhhut

Try these steps:
1) push the little switch inside the hole while inserting a male-male cable into the otg
2) on another linux machine you should have now a new device (lsusb will help you) and you can run rkdeveloptool
3) rkdeveloptool ld should List Device
4) rkdeveloptool rd 3 should Reset Device into mode 3  ( maskrom )
5) rkdeveloptool db MiniLoaderAll.bin ( of course from your path) should upload a temporary loader to recognize the internal emmc
6) if all is successfull until now you can rkdeveloptool wl 0X0 yourimage.img . This should flash the internal emmc .

DISCLAIMER: very " dangerous" approach , be ready to have the opportunity to short the emmc clock pin to ground to go back into mask rom
 
MiniLoaderAll.zip

@Antoxic
it say this because you didn't specify where is miniloader.bin i suppose

the exact syntax is :
 
rkdeveloptool db /home/Antoxic/miniloader.bin
assuming that your home is called Antoxic. If not adapt the right names
if you don't specify the path where is miniloader it will say creating comm object failed

Another info : yours is a REAL 3328, this post is mainly on 3318 that is the " poor brother" of 3328
It should work all, but maybe ddr frequencies or other oddities can still appear

What do you mean by adding support ? To what ?
To libreelec recognizing the wifi chip, but then should ask in libreelec forum, or add support to armbian to run kodi, then you missed a lot of previous posts.. ?

 

@chinhhut

Try these steps:
1) push the little switch inside the hole while inserting a male-male cable into the otg
2) on another linux machine you should have now a new device (lsusb will help you) and you can run rkdeveloptool
3) rkdeveloptool ld should List Device
4) rkdeveloptool rd 3 should Reset Device into mode 3  ( maskrom )
5) rkdeveloptool db MiniLoaderAll.bin ( of course from your path) should upload a temporary loader to recognize the internal emmc
6) if all is successfull until now you can rkdeveloptool wl 0X0 yourimage.img . This should flash the internal emmc .

DISCLAIMER: very " dangerous" approach , be ready to have the opportunity to short the emmc clock pin to ground to go back into mask rom
 
MiniLoaderAll.zip

@chinhhut
Will try to explain you what loader is with an analogy: in normal pc you have bios and master boot record. Well, maskrom is bios and is contained in the soc itself, loader is a sort of master boot record and it enables the emmc and ddr.
You can have a look here
http://opensource.rock-chips.com/wiki_Boot_option

 

I did extract it by a working firmware using a tool that unpacked the whole firmware. Try to google for RK3xxx_firmware_tools_5.23.1_by_SergioPoverony.zip and leave alone that github since it is just one piece of the puzzle. The detailed infos how to get a working loader are in the rockchip instructions

 

Of course and the command would be rkdeveloptoo rl 0x0 etc etc etc ( try rkdeveloptool -h to get the help)
But if you are lucky that works multitool, well that is the easiest way to clone and clone back

@chinhhut
Glad you got success .
Don't forget to put a like that helps @jock and myself in community reputation