MattWestB

Ok guys, Hi.
 
So I have managed to connect box Q96MAX 4k Ultra HD, board MXQ_R2B_LP3_V2.62_220225 via maskrom mode, made EMMC backup, erased it.
 
 
btw thanks @MattWestB for your photos of  pins https://github.com/MattWestb/R29-MXQ-LP3-V2.3-00908
 
Anyway,
 
Box boots armbian legacy from SD card, I have managed to connect to it via SSH, device specs.
 
Detected board features:                                                             │   
                                                           │ Chip type: RK3228A/B - Serial: URKW46025 00000000032b0c                              │   
                                                           │ CPU Leakage: 0x04 - Logic Leakage: 0x04                                              │   
                                                           │ Internal flash: eMMC                                                                 │   
                                                           │ Wifi device: unknown - Device ID: 02d0:4334  
 
EDIT2:
installed RDP client, can connect to device via RDP...HDMI NO Output
 
ok so thanks to this post https://github.com/MattWestb/R29-MXQ-LP3-V2.3-00908/blob/main/README.md  armbian parameters set to emmc-hs200, ddr3-660 and led-config2, led started to work.
 
@MattWestB can you please comment how you fixed your box HDMI and wifi?:)
 
EDIT:
 
ok so ARMBIAN non legacy boots too, but same problems with WIFI and HDMI no video.
 

 
dmesg gives a lot of errors
 
... [ 0.003538] CPU: Testing write buffer coherency: ok [ 0.004292] /cpus/cpu@f00 missing clock-frequency property [ 0.004358] /cpus/cpu@f01 missing clock-frequency property [ 0.004391] /cpus/cpu@f02 missing clock-frequency property [ 0.004424] /cpus/cpu@f03 missing clock-frequency property [ 0.004446] CPU0: thread -1, cpu 0, socket 15, mpidr 80000f00 ... [ 2.029717] inno-hdmi-phy 12030000.hdmi-phy: error -ENXIO: IRQ index 0 not found [ 2.030102] inno-hdmi-phy 12030000.hdmi-phy: phy_flag is: 0 [ 2.033084] rockchip-drm display-subsystem: bound 20050000.vop (ops 0xb127c87c) [ 2.033274] dwhdmi-rockchip 200a0000.hdmi: supply avdd-0v9 not found, using dummy regulator [ 2.033657] mmc_host mmc2: Bus speed (slot 0) = 50000000Hz (slot req 52000000Hz, actual 50000000HZ div = 0) [ 2.033677] dwhdmi-rockchip 200a0000.hdmi: supply avdd-1v8 not found, using dummy regulator [ 2.034239] dwhdmi-rockchip 200a0000.hdmi: Detected HDMI TX controller v2.01a with HDCP (inno_dw_hdmi_phy2) [ 2.035607] mmc2: new high speed MMC card at address 0001 [ 2.035736] dwhdmi-rockchip 200a0000.hdmi: registered DesignWare HDMI I2C bus driver [ 2.037470] mmcblk2: mmc2:0001 Q2J95T 7.28 GiB [ 2.039082] rockchip-drm display-subsystem: bound 200a0000.hdmi (ops 0xb1280568) ... [ 3.603319] rockchip-pinctrl pinctrl: unable to find group for node reset-key ... [ 15.966192] brcmfmac: brcmf_fw_alloc_request: Unknown chip BCM43342/0 ... [ 16.859644] systemd[1]: Starting Armbian memory supported logging... [ 17.040253] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50 [ 17.091210] systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch. [ 17.099828] brcmfmac: brcmf_ops_sdio_probe: F2 error, probe failed -19... [ 17.144754] systemd[1]: Finished Raise network interfaces. ... [ 45.622143] hdmi-audio-codec hdmi-audio-codec.2.auto: Only one simultaneous stream supported! [ 45.652339] hdmi-audio-codec hdmi-audio-codec.2.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22 [ 45.676365] 100c0000.i2s0-i2s-hifi: ASoC: error at __soc_pcm_open on 100c0000.i2s0-i2s-hifi: -22 ...  
 i attach log here pls help with wifi/hdmi
dmesg.log
 
 
 

I haven't read the whole thread. Sorry for any information you had to repeat! I'll take some due time to read it when I enter school break.
 
I meant it in a more of a "create custom images for our client" kind of way. (more on the client at the end)
It's not in the scope of this thread, so don't worry about it!
 
For the first question: not all devices. But I am sure they all have one thing in common: they are based on rk322x chips.
I said they don't boot, but I should clarify. I mean they don't boot without further intervention.
After flashing armbian, the board is "soft-bricked". Multitool doesn't boot from SD again.
If I force them into maskrom and upload a bootloader you posted in this thread, they can boot armbian.
For all that I tested, I could recover them.
I don't have access to a serial adapter yet, sadly.
As for why I'm sure they are all rk322x (at least the vast majority): this week we flashed some hundreds of the same model of device, and about 12 didn't boot completely, for reasons we have yet to investigate, and maybe 2 of those gave no video signal again. All other devices reached a desktop session.
 
On these devices, building multitool from your repo (./create_image rk322x) or using a premade image, replacing the kernel with a newer one doesn't work for us. The devices never boot. Kernel seems to panic before starting the HDMI driver, or whatever makes the console output appear on the screen.
I don't yet have access to a serial adapter, but I'll report if I have any output when I try.
 
However, the mysterious part is that armbian images (with any kernel version) boot! (if installed into the eMMC)
 
For some reason, booting from the SD card with a kernel version other than 4.4 doesn't work, but from armbian installed on the eMMC works.
 
just armbian. I said eMMC image because I thought it was only meant to work there.
Is armbian supposed to boot from the SD card? That never worked here.
And I assumed it wouldn't because it doesn't contain the special images at the special offsets described here https://opensource.rock-chips.com/wiki_Boot_option
But I read the first post again and you said it's supposed to work. Now I'm kind of confused as to why it doesn't work here.
 
The Brazilian government confiscated (big) irregular shipments of TV boxes. They plan on repurposing some of them (the ones that are actually usable) as mini PCs for schools and other social causes. So our university got a portion of TX9-brand boxes to explore the feasibility of using these devices as PCs. They are very sluggish, and I don't expect them to be usable for this purpose.

I created idbloader666.img , but my TV box RK3188 freezes literally a couple of minutes after loading with a frequency of 666MHz idbloader666.img
At a frequency of DDR 333MHZ, it works for months.
 
Using the HEX editor, I created rk3318_ddr_400Mhz_v1.16.bin and collected idbloader400.img with a DDR frequency of 400MHZ.idbloader400.img
The CPU operates at a frequency of 1.3 MHZ - it has been working stably for an hour.
Now I have launched memtester 512M
 
After a successful memory test, I continued experimenting with the HEX editor and increased the DDR frequency to 533MHZ and my TV Box started
Now I'm restarting the memory test
 
idbloader533.img

@ojogoperdi

I am SURE you read the whole 3ad ( did you, isn't it ??? ) and I am SURE you and your team realized that multitool is based upon LEGACY kernel that is the MOST COMPATIBLE ever kernel tha t boots quite every box

This said , I am also sure you and your team realized that saying TX9 box is a little bit as saying "water"..
Sparkling ? Flat ? Cold? Warm ? Salty? With sugar ?
TX9 means NOTHING is just a commercial brand !!!!

 It seems it is emmc from what you wrote and emmc are the easiest to boot since they don't mess with nand and FTL  . To be sure it always boots from external sd is enough to erase the flash and it will boot form the stuff on the sd. I believe you already read this:

https://opensource.rock-chips.com/wiki_Boot_option

DDR2 ? DDR3? the ram is 1T or 2T ??

The only way to anser to a failing boot is attach a UART to the box

I don't personally know this box so I cannot point you where rxd txd are on it, if present or just hiddend pads but I guess in your university you own an oscilloscope to further investigate where serial signals are

About new kernels they should boot quite smoothly even from SD since the early stages of booting (  idbloader and trust or optee in his opensource version should be already in the right places) but missing uart log it is difficult to give you an answer

As last resource we wait for a @jock 's answer regarding this behaviour but without serial log is a bit a nightmare

Regards

found it !
in case someone has the same board, this is the short pin 

@remlei OS agent for ARM 32 and supervised select Pi 3 (not 64 bit version) and also need patching the boot parameters for getting the install working OK by faking GRUB settings.

I successfully installed supervised install of HA using the images here https://users.armbian.com/jock/rk322x/armbian/stable/
 
what I did usually after armbian is installed is perform apt update and upgrade. after that I follow the most generic instruction how to install supervised install of HA, the only thing you need to watch out is install the right architecture for the os_agent.
 
after that its just a matter of how to fix that unsupported install to supported.
 
also a fair warning, do not install esphome on this box, the ram alone will make this box slow to crawl or worst crash the entire thing.

it looks like you already open your box , please send also the Wifi chip code .
Maybe your wifi chip is not support by linux

I have that same tv box, the pins to enter maskrom mode are those indicated by the red arrows, attached image.
 

 
Sorry for my bad english.
 
 

Hey @Vittorio Mori
 
If you need only H265 decoding, try this:
 
Focal Legacy 4.4.194
https://users.armbian.com/jock/rk322x/armbian/stable/

@jock 's media framework
 
ffmpeg -decoders |grep mpp V..... h264_rkmpp h264 (rkmpp) (codec h264) V..... hevc_rkmpp hevc (rkmpp) (codec hevc) V..... vp8_rkmpp vp8 (rkmpp) (codec vp8) V..... vp9_rkmpp vp9 (rkmpp) (codec vp9)  
For testing:
 
wget https://test-videos.co.uk/vids/bigbuckbunny/mp4/h265/1080/Big_Buck_Bunny_1080_10s_30MB.mp4 mv Big_Buck_Bunny_1080_10s_30MB.mp4 Big_Buck_Bunny_1080_10s_30MB_h265.mp4 ffmpeg -benchmark -loglevel debug -hwaccel drm -hwaccel_device /dev/dri/renderD128 -c:v hevc_rkmpp -i Big_Buck_Bunny_1080_10s_30MB_h265.mp4 -f null -  
VP8, VP9 and H265 works
 
H264 not working..
 
Encoding is not working...
 
ffmpeg -encoders |grep mpp  
 
 
 
 
 

@primoitt: @ilmich solved it for me by compiling a libreleec 11 build with mpv binary included- Everything works, h264/hevc/mpeg2 ..... brilliant.

inside linux
goto /boot
open with nano or other editor  armbianEnv.txt
add the new line cpu-stability
save and reboot

Hi @ochentay4
 
I shared with @jock the solution I adopted on libreelec. All that remains is to wait and help him with tests if needed. Thanks for the support you gave me with libreelec.

Great thanks for the archive of current version of armbian for rk3318  boxes !!
Now its possible installing one good working version that is not braking more time in the mouths and is getting current updates :-)))

https://imola.armbian.com/dl/rk3318-box/archive/

Great thanks for the archive of current version of armbian for rk3318  boxes !!
Now its possible installing one good working version that is not braking more time in the mouths and is getting current updates :-)))

https://imola.armbian.com/dl/rk3318-box/archive/

@MattWestB beware that rk3318-config does not let choose DDR frequency, that's for rk322x.
rk3318 requires proprietary trust os to enable the ddr scaling, but the proprietary os does not allow frequencies above 1.1ghz artificially crashing the system.
For this reason, on rk3318 I'm using the mainline opensource trust os, which allows to run the cpu above 1.1ghz without issues, but does not support ddr scaling.
 
That's it, closed source code 🙄

I finally got pictures of the PCB from my cousin
 

@Dario Murgia Don't worry, it is not essential, it was just good to know. However the fix has been mainlined in armbian

@jock @Igor I have been thinking along the same lines for the aml-s9xx-box builds.  While having the weekly builds is great, they are very unstable, being built on current master with edge kernel and the unstable debian and ubuntu userlands.  While that is all good for testing purposes, it is far from desirable for running anything in a production environment (yes there are crazy people like me that use TV boxes for production servers).  Now that current has moved to 6.1 for meson64 and I suspect rockchip current will try to get to 6.1 soon, it would be nice to have stable builds based on a stable master, current kernel and supported userspace (i.e. jammy currently for ubuntu) for the TV Box targets, IMHO.

I am open for this idea - one of you needs to take responsibility to make it happen - I'll just run the build once is in the system. Can be discussed on regular developers meetings.

hi,
i want to stop led blinking red and blue . Is it possible ?
 
thanks

I'm rathe late to the party, but this is what I found:
# armbian-config --help Armbian config options: Examples: Install headers:                    /usr/sbin/armbian-config main=Sytem selection=Headers Update, upgrade and reboot:            /usr/sbin/armbian-config main=System selection=Firmware Switch to nightly builds:                /usr/sbin/armbian-config main=System selection=Nightly Switch to stable builds:                 /usr/sbin/armbian-config main=System selection=Stable Install default desktop:                          /usr/sbin/armbian-config main=System selection=Default Change to ZSH:                    /usr/sbin/armbian-config main=System selection=ZSH Change to BASH:                     /usr/sbin/armbian-config main=System selection=BASH Change to stable repository [branch=dev]:        /usr/sbin/armbian-config main=System selection=Stable Change to nightly repository [branch=dev]:    /usr/sbin/armbian-config main=System selection=Nightly Install headers:                    /usr/sbin/armbian-config main=Software selection=Headers_install Remove headers:                    /usr/sbin/armbian-config main=Software selection=Headers_remove Install kernel source:                /usr/sbin/armbian-config main=Software selection=Source_install Remove kernel source:                /usr/sbin/armbian-config main=Software selection=Source_remove Install Avahi mDNS/DNS-SD daemon:            /usr/sbin/armbian-config main=Software selection=Avahi
And then, according to the help:
# armbian-config main=System selection=Stable  
Then, wait a long time and watch the show. I hope this helps...

@MattWestB AFAIK rockchip devices don't look for USB boot as Amlogic instead do. I don't know if newer SOCs like rk356x or rk3588 do that, but for older SOCs USB boot it is not mentioned anywhere.
 
@r00tl3ss you have to select a piece of text and a quote popup will appear.
You may indeed try the cp210x USB serial, maybe it can reach the 1.5mbps speed even if it is not officially rated for.
 
 

Hi @jock and @fabiobassa, it's great that you guys support the TV boxes that Armbian won't, amazing!
I have a HDMI stick with a RK3229 SOC, and this pathetic stick/board is a clone of a product with the brand "Any-cast", which at the same time is a clone of the Google Chromecast.
 
I thought I had bricked it, but I wonder if there's anything to do with it? 
I didn't expect to run Armbian on it, but if I can ssh into it and run something like lighttpd, it will be already great
 
I think the two soldered spot near the USB port is the UART serial, but I'm not sure
I also managed to do
rkdeveloptool db rk322x_loader_vxxx.bin , seems that the image is flashed successfully, but it still show "Maskrom" mode after I do
rkdeveloptool ld But I'm afraid to say that I'm not too clear about what I am doing 😅
(Oh there is an external WiFi chip that is soldered to a USB cable, you can look at the last three photos)
 

A terrible suspicion came to me right as I was writing the previous post, so I did a quick cat /proc/cpuinfo... and it has an H3 CPU.

Everything that was written on the box and on the eBay auction was completely off.
 
It looks like this one: 
 
 
Apologies for wasting your time, I'll go and try out another image for the correct CPU!