jock
-
Posts
2121 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by jock
-
-
-
@GmP thanks for the contribution, but I want to advice you that the driver changed in kernel 6.17 due to kernel developers requests and suggestion, so that device tree overlay is suitable only up to 6.16
I made a pull request to include the device tree overlays: https://github.com/armbian/build/pull/8848
-
The optimal would be understanding the reason why the watchdog triggers, but could be a difficult task without a hint because of the closed source proprietary trust os.
The easiest thing is to provide armbian images with the opensource trust os rather than the proprietary, which is totally feasible because it just requires to swap a file in the armbian build scripts. That would blow the issue away, but unfortunately the proprietary trust os provided DDR scaling and virtual poweroff. The latter is a seldom used feature, but the DDR scaling provided a dramatic improvement in performance and it is hard to give up on that.
Swapping the things at runtime is not savvy: when u-boot updates, the proprietary trust os will be reinstalled overwriting whatever you put in there.
I would be happy with opensource Trust OS and no runtime DDR scaling, but stil having it at a fixed decent rate (660MHz, instead of the default 330MHz), but some boards do not boot at all when they are instructed to boot at 660MHz.
-
1 hour ago, Igor said:
I had to rebuild server and this was not fixed yet. Temporally location https://stpete-mirror.armbian.com/users.armbian.com/
Thanks!
For @Victor Picinin the temporary working URl is https://stpete-mirror.armbian.com/users.armbian.com/jock/web/rk322x/armbian/beta/Armbian-unofficial_24.11.0-trunk_Rk322x-box_noble_current_6.6.56_xfce_desktop.img.xz
-
@Virgilio Junior you can use multitool, and use the "jump start" installation: you should be able to boot from sdcard and USB as well without doing the process by hand.
Forget about the NAND, it causes troubles you would not deal with
-
4 hours ago, Victor Picinin said:
I've seen this post before but the link is "404 Not Found" thats why i resorted to trying to build my own multitool and armbian hahahahahha
uhm, there is misconfiguration in the server actually; I see users.armbian.com is serving the certificate for stpete-mirror.armbian.com, perhaps @Igor can fix the issue
-
14 hours ago, Victor Picinin said:
If anyone here has a working build that does not trigger this watchdog, please let me know.
Found with google: https://forum.armbian.com/topic/34923-csc-armbian-for-rk322x-tv-box-boards/page/96/#findComment-218361
-
-
2 minutes ago, Victor Picinin said:
Is there a armbian distro that will work, what should i do here?
Mmmh, the easiest thing you can do you can build an armbian image taking rk322x_tee_os.bin from this branch in my repo and overwrite rk322x_tee.bin in the same path of your armbian copy, then build a regular image which will have an opensource TEE and should have no issues anymore.
Actually you could even reinstall u-boot without reinstalling the whole system, but it is just a tiny bit more involved. If you can restart from scratch, rebuilding the image with opensource TEE is easier.
-
6 minutes ago, Victor Picinin said:
The one in your multitool git did not work for me, also it shows the last change was 2 years ago hahahha.
Multitool uses the proprietary miniloader blob for booting and it does not work with opensource OPTEE unfortunately. I guess the issue is related with this patch that allows mainline opensource u-boot to support proprietary Trust OS, but that's just an ineducated guess.
-
Hello @Victor Picinin
yes the problem is exactly a watchdog in the proprietary trust os. Some people have issues after 60 seconds, others after 30 seconds and others after 30 minutes.
Being the proprietary Trust OS closed source, we can't know what is happening. I suspect it is a sort of automatic "suspend" feature of some sort, but can't be sure because digging into practically is diffucult.
What is sure is that if we use OPTEE Trust OS compiled from open sources (OPTEE is the base for the proprietary Trust OS too), there are no issues of sort, but we lose some features like DDR3 memory scaling and "virtual power off" (a suspend mode that can awaken the board via IR-control; there is a driver and a device tree overlay for that to work in armbian)
-
37 minutes ago, GmP said:
I will try to upgrade to tm16xx driver and be back.
38 minutes ago, GmP said:As for the HDMI, do you mean that Multitool shoud work anyway?
Yes, or at least there should be less chances to hit some corner case that reduces the compatibility. LibreELEC is using the mainline kernel only for years though, so it is really strange you have issues with both armbian and multitool. I may wonder there is something odd in the device tree, but it would be odd that a misconfiguration in the device tree causes a kernel fault in the DRM code and in particular in the wait for vblank function 🙄
-
42 minutes ago, GmP said:
Still not clear why HDMI not working, However VFD display based n FD650 is working. Attached the vfd.conf file for openvfd: clock , USB, ETH,WIFI and COLON working.
Very weird HDMI is not functional in both armbian and multitool: they use very different kernels. Multitool uses the 4.19 vendor kernel, which should be supposed to provide "best" compatibility.
The dmesg error is highly related to the missing HDMI, but in a way I can't recognize.
About the VFD driver, I guess you're using OpenVFD driver. Latest kernels (both 6.12 and >= 6.16) come with tm16xx driver which is by far much much better and candidate to be upstreamed in the mainline kernel. Here is the github project reference; the driver is already compiled in the kernel, but you may need to edit a device tree overlay by yourself to let it work with your board.
To try some debugging, the complete dmesg output and the original device tree of the stock android firmware would be very useful.
-
2 hours ago, robertoj said:
I would rather stay with trixie and low fps, because it seems easier to solve my other problem: need 100% wayland and 0% X11 due to a LCD driver problem.
AFAIK bookworm is fine with wayland (weston, kde, ...)
-
13 hours ago, robertoj said:
Can you confirm that you use the patch in mpv PR1460, or something else?
I compiled mpv 0.40.0 and the commits from this PR. Results are mixed and situation is messier than before, so if you need hardware acceleration, it is better to go gstreamer or revert to debian bookworm for now.
-
One suggestion I can give you is to try a fresh image from https://github.com/armbian/community/releases. Make a backup of the eMMC and clean it up (multitool can do both things), then try to boot from sdcard with the new image.
Newer images come with u-boot v2025.10-rc5 and a "fix" to reset the VOP before entering the kernel. Some people on the other thread reported that disabling u-boot HDMI made the HDMI work once in Linux. With kernel 6.17 this issue hit my box and I could arrange a fix, perhaps this fix will address your problem too (for reference: https://github.com/armbian/build/pull/8674/files#diff-70c2c867b6e2024080868c0d5c3230d58be2d2c4b88a24291b0469c7d2229629)
-
39 minutes ago, robertoj said:
Which github project and branch/release are you trying?
mpv official github repo. v4l2request commits are in a pull request.
-
I compiled mpv 0.40.0 on Debian Trixie with the patches for v4l2request, but the outcome is messy at best. There is a new hwdec v4l2request, but also two new gpu-hwdec-interop v4l2request and v4l2request-overlay. It works with acceleration when launched from a terminal, but in wayland/weston v4l2request refuses to work. I don't know what happened, but it looks like a big regression from 0.39. Better use the old mpv version IMHO.
-
You're welcome @Hqnicolas 👍
-
-
@samircobra Did you try multitool? You can find it in the first post; also read carefully the first post, it contains very useful informations, for example the hint about the failing eMMC on these rk3318 boards. Probably your box has a failing eMMC. Also another important thing: we don't talk about "firmwares" here, we talk about Armbian, so if you have questions not related to Armbian, this is the wrong place.
-
On 9/29/2025 at 5:28 AM, JaydenWithaWhy said:
Even with the new version,I am still running into the same error
Don't know what to tell you, it is running fine on my boxes and dmesg is clean.
Also I cannot see what is your build version since the screenshot is missing the top line of the screen. 🤷♂️
-
@JaydenWithaWhy I rebuilt and uploaded again a new copy of the multittol. Please download and try again, I tested successfully on a tvbox of mine and worked fine.
-
7 hours ago, JFL said:
Don't have experience to compile or build packages for Linux. Experience Armbian users and developers might be able to build the mpv-full-git for Debian Trixie.
"Regular" mpv coming in Debian Bookworm works perfectly fine, as Bullseye did also. There should be no need for custom mpv builds, unless some features have been removed.
HONGTOP H50 alias T98-3318-221-V1.1
in Rockchip CPU Boxes
Posted
@GmP oook, so now I understand the differences between the two dtso files provided here and in the other thread.
Do you spot other differences or peculiarities? Things that are useful are:
* the gpio led (do the separate red/blue/green led blinks on both boards?)
* wifi reset gpio (do wifi get detected in both boards with base configuration?)
* is there a separate PMIC like rk805/rk808 on any of the boards?
Things like these go into the dtso for full board support. The PMIC is very important since missing that could cause stability issues.