MattWestB

@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!

@donluca

yes this board is NOW supported and you will have great satisfaction in using it for your purposes.

And yes ethernet will work out of the box ( and if I am not wrong, wifi too but about this let's wait @jock suggestion )

Description
This commit forces cgroup v1 usage as a workaround for docker / runc BPF issues until a proper fix is submitted
Context
Docker 20.10+ cannot run on our Asus Tinkerboard, it throws BPF related errors (Like opencontainers/runc#2959 , especially this comment). I tried a lot of armbian flavors (focal, jammy, bullseye + current, edge and legacy kernels), and even building an image with CONFIG_BPF_SYSCALL=y as suggested by this comment but it didn't fix the issue. The only thing that fixed docker was to add extraargs=systemd.unified_cgroup_hierarchy=0 to /boot/armbianEnv.txt.
Until someone else does a proper fix to make cgroup v2 working, I suggest downgrading to cgroup v1 with this extraarg.
How Has This Been Tested?
[x] Tested on Asus Tinkerboard with latest 5.15 stable kernel from apt repository. [ ] :x: NOT tested with edge and legacy kernels (Sorry I had to quickly put the machine into production and didn't have time to test other kernels) Checklist:
[x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation => Does it need a documentation change ? [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

@jock I think i figured what the problem was .....  I have a S905L not a RK3228A processor 😂, good lord! I'm feel so stupid that i didn't open it from the beginning! 🤣