fabiobassa

@Alessandro if your wifi chip is ssv6051 you will have it working as well that driver is really crap so be ready for some instable acting

for all interested please visit https://forum.armbian.com/topic/12656-wip-armbian-for-rk322x-devices/ some ready to test images there thanks to @jock

@Alessandro as you can see ALL started exactly from your board https://forum.armbian.com/topic/12401-long-story-linux-on-rk3229-rockchip/

@hexdump yes , I also suspect something related to trust os since libreelec uses a modded trut os for booting on 3228b Alessandro you should take everything of libreeelec just changing kernel and root from jock's compilation hexdump alredy did this can follow you in right steps

so Alessandro this board is well supported by armbian since me and @jock have worked exactly on one of those Actually Jock has this and should be a 3228b with ddr3 but le't s wait what jock can confirm But if goes off after 30 seconds i suspect more power failure than software problems since trust os will die in few seconds and kernel panic will occur in 10/15 seconds is working with original Android rom ? sorry just realized with libreelec is working let' wait jock's suggenstions

@Alessandro I truly would explain that even if we have great knowledge of those board, is terribly hard to do a diagnostic without even a uart log or dmesg log. Is like to say the car doesn't go !!! Yes but : 1) battery ? 2) gasoline ? 3) tyres ? 4) the driver is sleeping ? if you haven't a uart at least give more details : photos of board, any marks on board , anything that could help in tracing the problem

if you are able to boot in linux starting by sd you can easily erase then the first sector of the internal emmc/nand and in this way FOR SURE you will be in maskrom mode ( a simple dd of a certain amount of zeroes on the first 8 mega will do the job ) A bit risky but it should work . In the same manner you could restore the original boot loader on internal storage your decison thought

about the memory, yes my board has 2 giga and I see all 2 giga without problems but maybe @jock will answer better to this question about mali &co if you use the linaro rootfs ALL is already included, otherwise the mali.ko is already compiled in kernel, the userspace *.so you can download from here https://github.com/rockchip-linux/libmali/tree/29mirror/lib/arm-linux-gnueabihf of course choose the one fro your use ( utgard mali 400 and then choose fb or gbm or what you need)

no this board isn't familiar to me (this lovely chinese producters ) and yes I told you that if booting then the board will work smoothless Looks interesting the 3 pads on the right of white led and, if you manage to program the internal emmc/nand, then you will have uart even on one of the pads of SD reader ( of course you soul'dnt insert sd )

@hexdump In my case study ( and I own many different boards)I always found a uart somewhere, maybe little copper pads but always I found a uart for debugging if you post a photo of your board up/down maybe we can identify them I can confirm that the buildings from @jock are working fine and never happened that boots and hangs: if boot it works, otherwise no boot occurs, because of 1) wrong ddr settings 2) wrong trust OS but this is easily debugged by uart we can summarise 3 BIG categories of boards: 3228 ddr 2 ( NO dinamic frequency scaling of ddr speed DMC) 3228 ddr 3 ( DMC is working fine) 3229 ( well exactly even here ddr2 and ddr3 but.... let's assume newer 3229 have only ddr3) 3229images will not boot on 3228 because different trst OS (thanks @knaerzche for all those USEFULL infos) and yes if on the original emmc/nand is present the loader and some other little stuffs then the board looks for uboot on sd , without touching the internal process and the boot occurs from external SD Just to be complete, give a try to this rootfs : https://drive.google.com/open?id=1jmtwGs88iXfCs7UtaEv1d5h7C9-9KGFg EDIT : if we find the UART put the command line to both ttyS2

Well I know nand is obsolete but you know how technician people are , now I want I understand and go deeper in this knowledge trying to relive the board just I should search for already compiled image without going trhought the whole process. Hope armian had also a " legacy" approach Ty anyway

@martinayotte ty for replaying Yes I guessed something like that, also on rockchip ( on those boards I have much much experience than allwinner, this is my first approach here ) there is no support for nand on mainline would you be so kind to point me , if you know , to any armbian version with legacy kernel of course that could support internal nand of those Q6 h+ (h6 processor) ? and if you know, is there a way to reboot in recovery to try a deep wipe of /data ( i know for sure nand isn't completely corrupted since it boots to some point) The canonical method of pushing the button while powering on leads to nowhere

good morning @balbes150 ty for kind answer nothing regarding NAND, only mmcblk0 that is SD , neither lsblk does show any nand simply internal nand not being recognized may be is lacking support for nand and should I use a older kernel ?

the purpose of that button is set the board in " loader mode" so be prepared to receive new firmwares

Good morning all, maybe someone could enlight me I own this box who internal board is a Q+ h6 version 3.0 . Despite of what is claimed ( 4 giga ram ) really the board is 2 giga ram. But the biggest problem is that the board is stick on Q logo and doesn't go further I have access to uart and when I try to flash new firmware, DOESN'T MATTER if I use phoenixsuite or the sd I have got this message: [18.838]nand not support! channel 0 chip 0: 2c 84 64 3c a9 04 00 00 [18.843]nand not support! channel 0 chip 1: 00 00 00 00 00 00 00 00 [18.849]nand not support! channel 0 chip 2: 00 00 00 00 00 00 00 00 [18.855]nand not support! channel 0 chip 3: 00 00 00 00 00 00 00 00 [18.861] no nand found ! [18.863]nand_physic_init nand_build_nsi error [18.867]nand_physic_init error -1 [18.870]NB1 : nand phy init fail [18.873]NB1 : enter phy Exit [18.876]nand_physic_exit [18.878]NAND_UbootProbe end: 0xffffffff [18.881]try nand fail [18.883]try spinor fail [18.885]flash init end initcall sequence 5ee50300 failed at call 4a00f9dc ### ERROR ### Please RESET the board ### well is clear that programming doesn't occur due failure on nand . But i would try to understand if I own the wrong firmware or effectively the internal nand is damaged So I flashed a SD with latest armbian Armbian_20.02.0-rc1.035_Aw-h6-tv_bionic_current_5.5.0-rc6_desktop_20200204.img and the board boots and run PERFECTLY. But I don't see the internal nand yet may be this armbian version doesn't support nand Please could you point me to right armbian version, if exist that can support internal NAND ? At least id I recognize the internal storage could have some e2fsck or doing other analysis ty in advance

for a better understanding and also other studies on kodi please https://forum.libreelec.tv/thread/21117-unoffical-le-9-2-images-for-rk3229-rk3228/?pageNo=1

@jock Well, simply speachless . Great details and great work. Personally will support this adventure as soon as I will own more and more different boards. Hope someone will join the study and add ideas, suggestions, solutions Thank you Jock

@hexdump you and all friends from forum are absolutely welcome hope this could be usefull for someone I could have been even more detailed but hope people on this forum has just little knowledge of what they are doing and also the risk ( very remote thought) to definetly destroy the board. and then ... If I did, ( me dumb on programming) quite everyone can do it actually I use the board as voip pbx( asterisk) , and to drive a relay following this project https://github.com/darrylb123/usbrelay

A real application case after the theory i want describe a real application case: the board is R329Q _ V3.0 , it is equipped with 1 GIGA RAM and 8 GIGA internal NAND storage. In photo you can see the uart connected and also a little wire on pin 7 of NAND to force the board to go in maskrom if something goes wrong . I assume who is reading this post knows the difference between MASKROM and LOADER modes . If you don't , better you take your time to study ROCKCHIP flow boot Original firmware has a little file called " parameters.txt" that contains informations about internal nand partition. Original one COULD , but also COULD NOT look like this: FIRMWARE_VER:7.0.0 MACHINE_MODEL: Leelbox MACHINE_ID:007 MANUFACTURER:RK30SDK MAGIC: 0x5041524B ATAG: 0x60000800 MACHINE: 3228 CHECK_MASK: 0x80 KERNEL_IMG: 0x60408000 #RECOVER_KEY: 1,1,0,20,0 CMDLINE:console=ttyFIQ0 androidboot.selinux=disabled androidboot.hardware=rk30board androidboot.console=ttyFIQ0 init=/init mtdparts=rk29xxnand:0x00002000@0x00002000(uboot),0x00004000@0x00004000(trust),0x00002000@0x00008000(misc),0x00000800@0x0000A000(baseparamer),0x00007800@0x0000A800(resource),0x00006000@0x00012000(kernel),0x00006000@0x00018000(boot),0x00010000@0x0001E000(recovery),0x00020000@0x0002E000(backup),0x00040000@0x0004E000(cache),0x00008000@0x0008E000(metadata),0x00002000@0x00096000(kpanic),0x00400000@0x00098000(system),-@0x00498000(userdata) well we need to change this parameters since we will boot from a different init and also PERSONALLY I get rid of all partitions I don't need anymore , such as recovery, misc, userdata, data etc etc MY PERSONAL parameters look like this: FIRMWARE_VER:7.0.0 MACHINE_MODEL: Leelbox MACHINE_ID:007 MANUFACTURER:RK30SDK MAGIC: 0x5041524B ATAG: 0x60000800 MACHINE: 3228 CHECK_MASK: 0x80 KERNEL_IMG: 0x60408000 #RECOVER_KEY: 1,1,0,20,0 CMDLINE:console=earlycon=uart8250,mmio32,0x11030000 console=uart8250,mmio32,0x11030000,1500000n8 rw root=/dev/rknand_system rootwait rootfstype=ext4 init=/sbin/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x00002000@0x00002000(uboot),0x00006800@0x00004000(trust),0x00007800@0x0000A800(resource),0x00006000@0x00012000(kernel),0x00010000@0x00018000(boot),-@0x00028000(system) different earlycon, root has became /dev/rknand_system, init is now /sbin/init and a big big system to enjoy the widest possible space on nand We open now RKDevelopTool v 2.67 and we put the board in LOADER MODE by pushing the little switch inside A/V hole and connecting a male-male USB cable. Of course you must have drivers for rockchip but I won't discuss here of this. when you first open rkdeveloptool you will have such situation: No start/end partitons, nothing just empty rows. So click on parameters and pick up the path where your parameters.txt are. For me are under D: disk etc etc etc clck on run and the board will load new partition table. To check it , alsays in loader mode you can push Dev Partition big button and result is: Well is now time to fill the boxes with right pieces of puzzle that I hope you already have in one folder uboot is the original one, don't touch trust is trust_with_ta_ga4fd2d1.img as previously described kernel we obtained by compiling resources are resources-linux from previous post boot !!! what is this boot ???? boot is like initrd in normal linux booting but again is made in a way rockchip can understand: I toke some hints on official RAXDA site: https://github.com/radxa/initrd so you can follow the same approach. ORIGINAL boot from ANDROID doesn't work You must convert in a format readable by rockchip and this is done again with Justin Swartz scripts: https://github.com/jhswartz/rk3229/blob/master/PARTITION-REPLACEMENT.md and last piece is rootfs from linaro Once we have all pieces push RUN and if every thing is in the right place you will see on the right the programming going on. When finished unplug usb and plug normal power this is my boot log: EDITED AS QUOTE FOR BETTER READING and this is screen: linaro uses LXDE as DE but you can use what you want since apt is working smoothly well this is all; mostly infos are taken from radxa official page , even if is for another board the proof of concept can be adapted to rk3229 and also you can take hints. I believe that is public contents , if not I will remove the referece to them https://wiki.radxa.com/Rock/flash_the_image ETHERNET is working out of box, wifi not even if I found firmware and drivers, must be something wrong with gpios enabling the wifi chip. ssh is working as normal use linaro/linaro you must set a root password: and also edit /etc/ssh/sshd_config to allow root ssh if you want, but this is nornal linux approach so again won't discuss of this Hoping this can be usefull for someone and also hoping to get the hardware gpu graphical working better TODO: understanding gpios understanding wifi better support for leds ( hard disk heartbeat)

I own a couple of tvboxes bought in a private exchange market by a seller claiming they were not working(stuck on ANDROID logo = for sure bad firmware inside) Since the price was really low i bougth some and discovered that mainly the inner processor is rk 3229 from rockchip. A quick search about the possibility to install linux on those tvboxes lead me to the very first approach on theme: https://respeaker.io/rk3229_core Well, I thought If already someone did it , I can do it too; that was the beginning of one of worst nightmares of my life Those boards are totally different even when they look similar: some have nand storage, some have emmc, some have ddr2 ram, some ddr3, some have ddr 330 mhz , some other 300, some have GPT partitioning some other have a system called rk_parameter , some control led in a manner some others in other manner. The first approach was a complete disaster, not even booting or, when booting , missing pieces of hardware or/and nand storage drivers. Then luckly I met two persons that helped me a lot: first thanks go to the man that owns this github: Mr. Justin Swartz https://github.com/jhswartz/rk3229.git and then thanks also Mr. Willerson from another forum that discovered where was the neck bottle that prevent booting the boards and let them work smoothless ( before boards stopped to work after 29.59 minutes as you can read on Justin Swartz github) I am not a coder , I am a good technician in soldering and I had many boards to experiment on , the joint venture coders/tester was successfull , so finally I/We can say there is a good method to boot the mayority of those bords and have a complete linux system aboard. DISCLAIMER this method still has a problem : NO HARDWARE acceleration from GPU by missing/lacking libraries that "couple" kernel drivers ( MALI 400 ) with userspace libraries : the decoding of video is made by CPU so AT THE ACTUAL STATE no 4k and even youtube on chromium isn't working at the top performances So if someone is looking to replace android for better video performances, well go back on android !!!!! SECOND DISCLAIMER I will not release any binary or/and pre compiled stuff: not because I want to hold and hide the discoveries for my self, but because I DON'T want any responsability on bricking, destroying, hidden malwares, security holes in firmware. You have to do by yourself following those instruction or use the original things shipped with original firmware adapted to your needings WHAT is necessary: 1) AndroidTool_Release_v2.67.zip 2) a pc running UBUNTU/Debian distro for cross compiling 3) rockchip official toolchain, kernel version is 4.4.189 https://github.com/rockchip-linux/kernel 4) gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf.tar.xz 6) original/official firmware of you actual tvbox ( there are pleeeentyyyy.. kingbox, leelbox, stock android) before doing ANYTHING be sure you can go back (Fortunately those boards are very UNBRICKABLE since they have a inner,but inner, but inner bootrom not accessible by user so, unless you do a PHISYCAL DAMAGE you will alway able to re-life the board) 5) having a serial connection ttl/usb could save many hours blaming and avoid headaches I strongly reccomend having a serial debug We will use the method described here : https://github.com/jhswartz/rk3229/blob/master/COMPILE.md and here https://github.com/jhswartz/rk3229/blob/master/PARTITION-REPLACEMENT.md all credits go to the OWNER of that github JUstin Swartz START 1) git clone https://github.com/rockchip-linux/kernel As previously said we will obtain kernel 4.4.189 2) search on the net for gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf.tar.xz ( assuming your pc is 64bit)and put somewhere. Untar it 3) go into directory kernel-develop-4.4-189 and do : make ARCH=arm linux_defconfig you will obtain a basic .config for the compilation here is it one config modded to enable rknand support, you can open and edit as per you needing YOU MUST RENAME from .config-linux to .config (there is a dot) .config-linux 4) then ready to compile: make ARCH=arm CROSS_COMPILE=/path/where_is_compiler/bin/arm-linux-gnueabihf- zImage you will obtain a zImage under /your_path/kernel-develop-4.4-189/arch/arm/boot 5) well this is our first step, we must convert this kernel into a readable image for rockchip. We will use scripts once more thanks to Justin Swartz SCRIPTS https://github.com/jhswartz/rk3229/tree/master/scripts /pack-kernel /bla-bla-bla/yourpath/linux/arch/arm/boot/zImage kernel.img $((0x6000 * 512)) this is one of the most important part of the process because we have our kernel, the real engine of linux we will use original uboot.img from android stock firmware !!!! but we still need trust.img .resources.img, boot.img and a rootfs.img trust.img is taken from android 8.1 stock version : trust_with_ta_ga4fd2d1.img trust_with_ta_ga4fd2d1.img resources too are obtained from android 8.1. original stock firmware with slight modifications resources-linux.img Root fs is original linaro release so we assume is public domain rootfs-debian-20170504(xserver 1.18) from here https://drive.google.com/drive/folders/0BwAJtUrQohwXdGRVYTAwdlJDOUU We are " quite " ready to put all things together to have the board booting In second part of this post I will put some photos and images of procedure

@jock first of all ty for your kind replay well you are the 1st to go deep in specific problem. I googled a lot about this , what i am experiencing when I launch chromium by the command line is: as I said many many times I am not a coder, but a good technician with good soldering skills and optimum hardware modding, but of couse can even read a bit of " diagnostic" so it is clear there is a mismatch between kernel driver and userspace libraries anyway here it goes the new 3ad on rk3229 devices https://forum.armbian.com/topic/12401-long-story-linux-on-rk3229-rockchip/ I have no problems to go on mainline 5.x.x, but here is lacking of rk_nand drivers so compilations will only work on devices with emmc post scriptum : maybe you forgot the link to your work ??? where ??

@hexdump yes you right never opened a different 3ad but I went in bad mood when I read this on official respeaker site: it seems no interest in developing a decent support to video acceleration BTW i can publish at least a method to get a working kernel if this interests someone

@amirul but you are speaking of a Rk3399 , here we talking of rk3229. Maybe I misunderstood ? @hexdump sure this is a nice idea: maybe opening a whole new thread would be the best in the meanwhile I would like to share how difficult is working on those boards !! Look here: two board apparentely ugual but one is emmc the other is nand! On one the whole stuf is booting out of box, on other wont boot because uboot don't recognizes nand By the way actually have a stable 4.4 kernel with a decent rootfs from linaro debian stretch 9 with decent usabe desktop what is missing is the propietary acceleration , I am trying to adapt some scripts I found on this forum for other boards but need collaboration Ok let me know what is the best to do,if continue here or open a new thread

hello amirul , doesnt exist yet a github with final work since the video acceleration is actually insufficient Also many variables since a lot of different harware combinations even on same shape box anyway if you would have a test ( not good for playing videos in youtube or vlc thought, perfect to have a server, a pihole , a samba share , a print server at the moment) i can give you useful infos to compile all stuff by youself ( only kernel because root file system is public gpl from respeaker) which board have you?

Good morning forum, this is my first post here , didn't find a presentation section, so here I am thanks to the work of some people finally there is a kernel 4.4. stable and well running on RK 3229 tv boxes The original ROOTFS from linaro is starting fine and all is working out of the box, except the wifi chip ssv6051 that never has been compiled. The desktop is debian with lxde environment and is showing up in all parts But has been personalized for another purpose that is respeaker echo system What is missing is the hardwate accelleration so I was wondering if the armbian method and scripts could be usefull to bring up support for better performances on video or those scripts are specific only to rk 33xx platform and not to rk32xx platform The sources are public avaible from rockchip Anyone interested in testing on rk 3329 tv boxes?