fabiobassa

@NiTr0 armbian has uart Speed at 115200
Original ddrbin at 1500000
I think you already switched to 115200
Other than this It hangs After trust loadingvthatbis quite strange 
 
Let see also  @jock opinion

It seems like trouble was with ddr init code, I replaced it in multiboot image (2-87 sectors) - and it's booted OK.

Here's log of original fw booting:
DDR Version V1.11 20200910_dbg In ID:0xFFF 300MHz LPDDR3 Bus Width=32 Col=10 Bank=8 Row=15 CS=2 Die Bus-Width=32 Size=1536MB mach:14 OUT Boot1 Release Time: Sep 29 2018 16:04:10, version: 2.53 ChipType = 0xc, 370 mmc2:cmd19,100 SdmmcInit=2 0 BootCapSize=2000 UserCapSize=7456MB FwPartOffset=2000 , 2000 SdmmcInit=0 NOT PRESENT StorageInit ok = 18165 SecureMode = 0 SecureInit ret = 0, SecureMode = 0 GPT 0x632d7e08 signature is wrong LOADER Check OK! 0x60000000, 82244 TOS Check OK! 0x68400000, 92952 Enter Trust OS INF TEE-CORE:init_primary_helper:319: Initializing (1.0.1-72-gf230aa2 #2 Fri Sep 29 10:22:10 UTC 2017 arm) INF TEE-CORE:init_primary_helper:320: Release version: 2.0 INF TEE-CORE:init_teecore:79: teecore inits done U-Boot 2014.10-RK322X-06 (Oct 18 2022 - 16:37:01) CPU: rk322x cpu version = 3 CPU's clock information: arm pll = 600000000HZ periph pll = 1200000000HZ ddr pll = 600000000HZ codec pll = 500000000HZ Board: Rockchip platform Board Uboot as second level loader DRAM: Found dram banks: 1 Adding bank:0000000060000000(0000000060000000) Reserve memory for trust os. dram reserve bank: base = 0x68400000, size = 0x00100000 128 MiB GIC CPU mask = 0x00000001 rk dma pl330 version: 1.4 remotectl v0.1 pwm freq=0x47868 pwm_freq_nstime=0xd55 SdmmcInit = 0 20 SdmmcInit = 2 0 storage init OK! Using default environment GetParam Load FDT from resource image. can't find dts node for fixed No pmic detect. set pwm voltage ok,pwm_id =1 vol=1100000,pwm_value=66 set pwm voltage ok,pwm_id =2 vol=1200000,pwm_value=33 DRAM: dram freq:600MHz SecureBootEn = 0, SecureBootLock = 0 #Boot ver: 0000-00-00#0.00 empty serial no. normal boot. checkKey vbus = 1 Normal boot, detecting usb... Auto detect usb timeout:978/1479/1479, return! otg not connected! board_fbt_key_pressed: ir_keycode = 0x0, frt = 0 no fuel gauge found no fuel gauge found can't find power_ctr node for lcdc0 HDMI: no pull up gpio can't find dts node for deviceinfo rk_hdmi_register:fail to read deviceinfo hdmi baseparamer 0x0@0-0 left = 0, right = 0, top = 0, bottom = 0, overscan = 0 panel->left = 100 , panel->right = 100 ,panel->top = 100, panel->bottom = 100, panel->overscan = 100 tve baseparamer 0x0@0-0 Hdmi Devices Not Exist. can't find dts node for rk312x-tve SCREEN_TVOUT rk3036_tve_init:use default config g_tve_pos = 1 read logo on state from dts [1] no fuel gauge found checkKey vbus = 1 board_fbt_key_pressed: ir_keycode = 0x0, frt = 0 Hit any key to stop autoboot: 0 load fdt from resouce. ERROR: [get_entry_ram]: Cannot find logo_kernel.bmp! vendor read error! Set oem_unlocked=0Secure Boot state: 0 kernel @ 0x62000000 (0x0066db38) ramdisk @ 0x65bf0000 (0x001693f0) bootrk: do_bootm_linux... Loading Device Tree to 65600000, end 656155bd ... OK Add bank:0000000060000000, 0000000008400000 Add bank:0000000068500000, 0000000057b00000 WARNING: could not set reg FDT_ERR_BADOFFSET. Starting kernel ... <hit enter to activate fiq debugger> [ 0.000000] Booting Linux on physical CPU 0xf00 [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 3.10.104 (hxws@gxt) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #76 SMP PREEMPT Mon Aug 7 10:45:16 CST 2023 [ 0.000000] CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c5387d [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] Machine: Rockchip RK3229, model: rockchip,rk3229 [ 0.000000] rockchip_uboot_logo_setup: mem: 0x02000000@0xbdc00000, offset:0x00000000 [ 0.000000] hdmi init vic is 65536 [ 0.000000] cvbs init tve.format is 1 [ 0.000000] cvbs init tve.format is 1 [ 0.000000] cvbs init tve.format is 1 [ 0.000000] rockchip_uboot_mem_reserve: reserve 0x02000000@0xbdc00000 for uboot logo [ 0.000000] rockchip_ion_reserve [ 0.000000] ion heap(cma): base(0) size(0) align(0) [ 0.000000] ion heap(drm): base(0) size(0) align(0) [ 0.000000] ion heap(vmalloc): base(0) size(0) align(0) [ 0.000000] cma: CMA: reserved 16 MiB at 7f000000 [ 0.000000] Memory policy: ECC disabled, Data cache writealloc [ 0.000000] system serial: c0cd2128 [ 0.000000] 52 57 30 31 00 00 0b 1d [ 0.000000] 55 4b 35 30 32 00 00 21 [ 0.000000] psci: probing function IDs from device-tree [ 0.000000] PERCPU: Embedded 9 pages/cpu @c1a15000 s13440 r8192 d15232 u36864 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 391936 [ 0.000000] Kernel command line: vmalloc=496M psci=enable rockchip_jtag console=ttyFIQ0 androidboot.selinux=permissive androidboot.hardware=rk30board androidboot.console=ttyFIQ0 init=/init mtdparts=rk29xxnand:0x00002000@0x00002000(ub0 [ 0.000000] rockchip jtag enabled [ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes) [ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) [ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) [ 0.000000] allocated 3145728 bytes of page_cgroup [ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups [ 0.000000] Memory: 132MB 1403MB = 1535MB total .....  

Thanks. My board has KMQN10006B-B318 eMCP chip.
 
Also, I experimented with different usbplug loader parts - board boots with v2.53 (which is in this loader) and hangs with v2.56.

@chrisrer My box is running so well that I managed to write a procedure to install HA on it.
@Scmel  I find a fix for the error you reported, check bellow
 
Hope this helps
!3runo
from Brazil

Thank you @jock for this hint! I was trying Armbian_23.8.1_Rk322x-box_jammy_current_6.1.50_minimal.img directly from the SD without installing to check if it would work before burning the unit (just getting blue and red LEDs shine very tiny at each attempt) and was wondering why multitool would run from the SD and the image, won't.
 
My unit is the cheap MXQ Pro 4k 5g with R329Q_V8 board. It has 4 H5TC2G43BFR-H9A DDR3L DRAM, 512MX4 memory chips (1GB RAM total), a KLM8G1GETF-B041 eMMC 5.1 (8GB) and the SV6256P wireless. After installing it successfully booted, I plug a spare USB WIFI dongle I had and enabled internet access using nmtui to apt update && apt upgrade
 
I select on rk322x-config rk3228 no pins and overlays=emmc led-conf2, are these the right settings for this board?
 
My goal was to setup a cheap print server for an old non-wifi printer I have and thanks to you guys awesome work I succeed
 
While preparing I managed to get some info from the board using the shell from multitool
 
# hexdump -C /sys/bus/nvmem/devices/rockchip-efuse0/nvmem 00000000 52 4b 23 82 81 d4 70 55 52 4b 4e 30 39 30 32 35 |RK#...pURKN09025| 00000010 00 00 00 00 01 2c 15 03 00 03 81 00 00 80 00 00 |.....,..........| --> 3228 chip  
(I was not able to remove the heatsink to check if the RK3228 is a or b, it is very well glued)
 
# cat /sys/class/devfreq/dmc/trans_stat cat: /sys/class/devfreq/dmc/trans_stat: No such file or directory --> shows that unit is not using frequency scaling  
# cat "/sys/bus/mmc/devices/mmc1:0001/mmc1:0001:1/modalias" sdio:c07v3030d3030  
Some pictures of the board and from the android that came with it attached (system's and Aida64). There are R T and GND points on the board but I didn't try a serial there
 
I made a backup of the android that came installed, if anyone wants just tell and I'll post a link
 
Thank you @jock @fabiobassa @hexdump @knaerzche Igor Pecovnik, Justin Swartz and all others that contributed so much for Ambiam project and to this port.
 
Cheers
!3runo
from Brazil
 
(As a side note, I was able to get rid of the annoying adware that popups every time android booted - the video at /system/media/bootanimation.ts - by adding to /system/build.prop the following single line using adb or an file manager app capable of editing files. The box came factory rooted and with adb network enabled - beware of that if you use its android!)
 
debug.sf.nobootanimation=1  

Yeah, we live in the clouds and sometimes we land to go to the grocery store ...

Hi @n3o
 
please don't say things I've never said. I won't do what you wrote. You are still free to use my (hard) work because I believe in healthy sharing, which is already the basis of my work on libreelec. Without @jock and @fabiobassa these boxes would not have this level of support.
 
Cheers
Michele

@jock
with updated uboot
 
I can add that no armbian with kernel higher than 4.4 ever run on this board, all did crash. Wrong CPU/DDR freq ?
updateduboot.txt
 
Edit:
Oh, it just runned after few power unplugs ...
HDMI ok, strange xD
 
works!.txt
 
lan 100Mbit also ok
[   34.223396] rk_gmac-dwmac 30200000.ethernet end0: Register MEM_TYPE_PAGE_POOL RxQ-0
[   34.288631] rk_gmac-dwmac 30200000.ethernet end0: PHY [stmmac-0:00] driver [Rockchip integrated EPHY] (irq=POLL)
[   34.297804] rk_gmac-dwmac 30200000.ethernet end0: No Safety Features support found
[   34.297885] rk_gmac-dwmac 30200000.ethernet end0: PTP not supported by HW
[   34.299134] rk_gmac-dwmac 30200000.ethernet end0: configuring for phy/rmii link mode
[  290.306195] rk_gmac-dwmac 30200000.ethernet end0: Link is Up - 100Mbps/Full - flow control rx/tx
 
Thanks !

@Benedito Portela Here it is a debian buster minimal image with latest 6.5 kernel. I did not had time to test it though, so try it with an sdcard first!
 
edit: tested the image, it works plenty well!

The Debian version has nothing to do with the underneath hardware. It's just that if you use an older image simply you miss some corrections and compatibility fixes here and there that allowed the eMCP boards work in a stable way.

@Benedito Portela I checked your firwmare and actually R29_MXQ and R2B_MXQ share the same identical original device tree, so you can go testing the image, just follow the instruction and try with a pristine system on sdcard/usb stick, not juggling with dtbs on existing systems

@MattWestB @Benedito Portela guys I appreciate your feedback, but please use the armbian image I gave from an sdcard and post the dmesg log if you can.
Doing cut&paste over custom setups just makes me really confused. If you already have regular Armbian installed on eMMC/eMCP, just burn the new image on sdcard, plug the sdcard and boot the board.
Your installed system won't be touched because sdcard boot has priority over internal flash. When Armbian is installed, boot priority is always sdcard, then USB stick, then internal flash.

Was doing one fast test with Multitool on my device that have updated eMMC with new bootloader and putting it on one USB-Stick and its booting with HDM is working and can navigating with keyboard so looks great. The video is not looking great then its one full HD TV and we is knowing all video modes is not supported but its more then OK.
Shall testing the DEB but i only running Ubuntu on my Linux machines so im not installing it.
 
Thanks for great work !!!

UPDATE FOR R29-MXQ USERS!
 
Hello, this is an update for those people who has R29 board and have suffered issues regarding stability problems and no HDMI output.
I had the chance to have a board in my lab thanks to @Hudson FAS and something is moving!
 
What's wrong with this board:
Differently from any other known board, it has a specific GPIO pin to turn the HDMI on and off: discovering such GPIO required extensive trial and error, it was disguised in the original dtb as "power-hold" 😅
But the main problem with this board is that it has no power regulation for CPU, so it cannot run faster than 1Ghz.
The default dtb shipped with Armbian and Multitool are set to run the CPU up to 1.2Ghz. For this reason, some (most?) unlucky R29 samples were totally unable to boot with the default configuration.
 
I still need some help from community though: my sampl is able to boot and works stable but:
emmc does not work ethernet does not work unless I downgrade the link to 10 Mbit/s I suspect my sample is damaged, but I need a feedback from other users to understand if there's something more in the dtb to discover or it is just my sample.
 
Multitool
you can download a fixed version from here. It should work flawlessy and HDMI should turn on with no problems.  
Armbian
you still need to do some manual passages:
Burn the multitool on a sdcard, run it on the board, make a backup of the original firmware then erase the internal flash to force sdcard boot. Store the backup on a safe place; if you wish, it would be appreciated if a copy can be shared here for further studies! Burn this Debian Bookworm minimal Armbian image on the sdcard, the try to boot the board. If you're able to boot, access via ssh, run rk322x-config, select your configuration options and select led-conf7 as GPIO configuration in the last passage, then reboot; you're done! if your board does not boot, mount the sdcard partition and manually add  overlays=led-conf7 in /boot/armbianEnv.txt, then you should be able to boot  
Thanks!

@Daraz Season I upload it for you! 
 
https://drive.google.com/file/d/1chrBXzLiuquS1zeviy4ctN4yM7eJfHpF/view?usp=sharing

but this isnt the kernel , that is the armbian base system update .
 
my knowladge that kernel never get update at non offizial Armbain device with apt-upgrade , ever only the base system in some range
 
also than we have the package with header linux-header-rk322x_23.x.x.....
 
the new kernel only with new compile complete image files
 
last year or maybe begin of 2023 i update header without base system this also break one box
 

@Felipe Muniz I don't think it was a good idea to change the NAND. AFAIK, eMMC can be switched with no real software issues, but NAND chips in my opinion are way thougher because they require a software layer (the FTL) to work correctly. The proprietary NAND driver contains the FTL routines for a bunch of vendors and specific parts, so IMHO you can't put any bigger/better part and expect to work out of the box.
 
You may boot in maskrom mode, upload a recent loader and see if rfdeveloptool/rkflashtool detect the nand parameters correctly (size, vendor, page size, ecc bits, etc...),otherwise I would not expect it to work in any way.
 
 

@Jumperbillijumper from that link It seems t'ha t you already adked the same quesion in that thread and jock ( the same jock that is the author of all this stuff ) aleady answered there.
 
Please do not cross posting , thanks so much
 

@Felipe Triana

Felipe armbian uses gpt , android uses a organization of partitions called rkparameters . rk parameters are written into sector 0X02000 of the nand, just after the loader address space
is a bit as you modified the master boot record to use mbr or uefi. This just to explain the difference between android and armbian and also this is an annoing alert repeating from the beginning of this post, saying  mxq-4k means NOTHING !!!!!!!
Neither is possible ask a backup from a mxq-4k from other users for the reasons explained  later in this post

Please open the bow ( 4 little screws under rubber pads) and give more info ( mx4v ? mz4vr? r329q ??) or better attach photos of the box

If you really want go back to android ( but .. why ???   🙂  )  and if you are also a windows user or you can use windows in some way , you can use the attached windows tool and,  instead of using the backup obtained by multitool,  look for an android suitable for you board ( that despite of being called mxq-4k could be a 3228. 3228a, 3229, ddr2, ddr3 and all the hell the china market does ) !!!
😄 🤣

For the future, backup before any experiment !

AndroidTool_Release_v2.69.zip

 

@Jumperbillijumper hello

h20 is commercial name of this box

it means nothing ! Can you give more infos, maybe open the box e grab some photos ?

Anyway are you sure it is a rockchip platform ?

@n3o  As a moderator of these forums, I have been watching your postings.  You are abusing these forums and the people that contribute to them.  (Everyone, especially @RaptorSDS and @jock have been very willing to invest a lot of time to help you)   However, repeatedly you have been given specific information that you ignore, been given advise that you ignore and then you come back with more and more questions.  There are very limited people resources working on Armbian (and even less with TV boxes).  You alone are consuming way more developer time than any one individual has the right to receive.  This is open source, and therefore users are needed to contribute as much as they consume in resources from the community in order for this to work.  This is not a school where you can come to be taught how everything works, demanding the attention of everyone else to teach you. 
 
Your latest questions are now venturing into very deep and difficult areas of code (none of which is expected to work on these TV boxes as has been mentioned to you).  If you want to continue down the path you are going, you first need to become an expert at these topics on known working platforms, then you can try to apply that expertise on TV boxes.  You may not realize it, but the questions you are asking, are essentially asking for weeks if not months of developer help to get working, if it is at all possible.
 

there are some tools for linux and IR on this box it can be became complicate because GPIO and DTB and tools, relearn remote   , so on .............  
when you are lucky the right setting are already in dtb and the tool recognise the IR comannd than you need to relearn the remote inside the tool
 
thats not topic of this board and dont relatet to rk322x , maybe smbv2 vs smbv1 , anyonmus account etc ..... please ask in the right place

I will never stress out that THESE issues reported by you are the exact reasons to chose a properly supported Single Board Computer from the officially supported list and not buy crap like supercheap tvboxes. If you don't have the time, will and skills to solve troubles, tvboxes may end up being a large source of frustration. The very same problems are the main reason tvboxes are NOT OFFICIALLY SUPPORTED and NOT ENDORSED by Armbian project; tvboxes are just a community effort to have fun with them and avoid some waste, but the mileage can vary greatly. Here are the FAQs

@Benedito Portela
 
In this same whole 3ad the boot process of RK 322x Is explained plenty of times, with links to the original pages of rockchip too.
Now... I understand that is a huge duty read all posts but... Did you ready It ?