jock
-
Posts
2077 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by jock
-
-
-
21 hours ago, Fr id said:
My goal is to get the firmware, then edit it - translate to another language, add some games, etc, then flash it back to the TV box.
Sorry but this is the wrong place to ask about that; no Android or custom setups here, just armbian.
-
You'd better ask directly to Radxa for that, they probably know better the specs of their boards.
I would take the power for disks from the PSU anyway if possible to avoid unnecessary stress to the board: I guess the SATA power pins on the board are there for those who wants to feed the board with 12V barrell connector, but if you got a fully-fledged ATX PSU, go with the classic power connection.
-
No hardware issue, the problem is rather finding the material time to do the task!
-
Mmmh 82°C seems rather low threshold to me. If you repeat the compilation and it hangs at the same temperature?
Lowering the threshold to 82°C means that it should start throttling big cores around 75°C, throttle the rest at 78°C and reboot at 80/81°C
-
There is no grub in armbian.
Try multitool or reinstall armbian.
-
I really don't understand where is the problem.
You claim you cannot login, but root and 1234 are the default username and password, and those have always been for ages.
You claim you cannot enter maskrom, but you should be perfectly able to boot from sdcard/USB either another armbian image or multitool to do maintenance or erase the eMMC and get back maskrom mode
-
It could also be some broken welding among the small SMD components. You may try with a hot air gun.
-
-
I'm not used to rkdevtool for windows, but indeed if the board does not get past the ddrbin, any tool won't work. The first thing the utilities do is upload a small binary (which contains the ddrbin as well) to initialize the board. The binary/executable then has the service functions that are invoked by the GUI utility when you click the button.
You should be able to read the serial log while rkdevtool uploads the binary and tries to initialize the board, but this will probably give you the same errors you already know.
The problem is that if you don't have the original firmware and nothing changes switching from 2T to 1T, there is nothing more you can do other than randomly trying firmwares, with the doubt your eMCP chip is even broken.
-
-
-
@hfrts hello!
First of all: no documentation from the manufacturs of any kind. Cheap tv boxes come without any kind of documentation: they are dirty cheap hardware with barely working software.
The board footprint/silkscreen is indeed the first thing to look for to find the matching led-config: all known boards are listed within the rk322x-config script.
If your board is not listed, then the stock firmware (or its device tree) and photos of the board most of the time are enough to properly match an existing led-config with the board or create a new led-config for a new board.
-
-
@wilsonh hmmm, that commit I think it was an attempt to bring the libreelec patches into rockchip64 family. Those attempts generated a lot of discussions, where many were happy and some concerned. Concerns won the battle, and the branch was never merge into mainline, despite it was tested a lot by libreelec folks and gave an all-around improvement in the video/display front.
The patch in the main armbian branch instead is a knitwork I did around the libreelec patches to figure out what could fix the HDMI issues on rockchip64 in the latest kernels without including the whole libreelec patchset. Unfortunately (or fortunately) I have no issues with any monitor/TV I have here around, so I could not test directly the outcome of the knitwork. I got some positive feedback from the community, so the smaller patch went in main armbian, but some useful things that fixed issues may have been left out in the process.
Anyway I read that, with kernel 6.12, a number of patches that are in the kernel mailing lists (that also are in the libreelec patchset) will be finally mainlined. Hopefully, that would be a step forware the right direction (or wreck everything...)
-
@wilsonh hello! There are no particular compilation steps, once you put the patch in the right place (patch/kernel/archive/rockchip64-6.6), the armbian build system should automatically apply it.
Anyway, the patch is already in the main branch of armbian for quite a lot of time; perhaps the patch does not solve the issue with your monitor - for example, I have been unable to run my AOC 3440x1440 monitor on any SBC I have here around, Opi4 included 😕
-
13 hours ago, Ben N Voutour said:
This DTB enables all the ram speeds and the Mali 450 MP2 GPU is set so it can boost to 750 MHz well within safe operating voltages and the CPU is set to be able to scale to 1.5 GHz (also well-within safe operating voltages.
Which ram speeds? are you aware that ddr scaling does not work on these tv boxes?
-
On 7/23/2024 at 6:35 PM, alejor said:
Hi, I tried this with armbian bookworm and orange pi zero 3 worked flawlessly with h264 hwdec. Now... Armbian image are Ubuntu Noble 24.04, can you please create or recompile packages for that 24.04 distro? or give some instructions to create those packages? thank you!
That will take some time to set the whole setup; unfortunately it is not easy task to bring up a system which could be used easily to rebuild the packages, but will do in the future. Can't say when though.
-
-
2 hours ago, Mikee Mike said:
Thank you for the response @jock. Is it possible to use that old TrustOS in an Armbian? Or maybe is there an existing Armbian that uses that old TrustOS? Thanks again!
No, because it is old and buggy. It would perhaps let some boards work but it will break many others.
The best option is to use the opensource trust os, but it lacks some features (DDR frequency scaling, virtual poweroff most of all).
-
First fact:
the problem is in a mainline upstream kernel driver; there is no device tree magic sauce that will fix until the driver is fixed.
The patch to fix the issue is already around in the kernel mailing lists (https://patchwork.kernel.org/project/linux-rockchip/patch/20240709105428.1176375-1-i@eh5.me/), if it will take more than another week to be merge, I will import into armbian patches set.
Second fact:
the big fat disclaimer when you run community armbian images tells you that they are not stated to run in production. If you do so, you have no guarantees of any kind. Community supported boards (CSC, as all tvboxes are), can only have community images. Supported boards (proper SBCs) have supported images.
-
@Mikee Mike the difference is that the "old tee" is a very old TrustOS proprietary and closed source binary from rockchip that does not put the board in standby after one minute. On the other side it has several compatibility issues among various boards.
The "regular" multitool has a newer TrustOS that works fine for the majority of the boards around, but on some very rare boards will put them in standby after one minute.
As long as they are closed source binaries, we don't know why that happens.
-
11 hours ago, MarcelTunholi said:
The H96 Max with the RK3318 chip does indeed have analog audio input capabilities, which are typically accessed through a 3.5mm stereo audio jack.If you want to upgrade your TV box, you can look at H96 MAX RK3576 TV box, android 14.0 system, it also has a number of interfaces, meet your requirements, such as Audio, DC, SPDIF, 1000 m Ethernet, HD2.1, start, usb, etc., If you're interested, take a look.https://www.h96tvbox.com/product/h96-max-rk3576-android-14-tv-box/
Suggesting a tv box is the best way to waste money in something probably unsupported.
-
On 7/14/2024 at 4:37 PM, Alex ThreeD said:
I can confirm DWC2 usb2 does not see keyboard/flash-drive in u-boot 2024.07. (usb3 port doesn't work either on my board, but the same was in uboot 2024.01 and 2022.07).
This definitely requires more attention. Each uboot revision seem to change something and every time is a lucky shot.
CSC Armbian for RK3318/RK3328 TV box boards
in Rockchip CPU Boxes
Posted
Hello, I am working on an alternative fd6551 and clones led driver for our tv boxes front displays.
It is getting up in very good shape, but requires some tuning up; I would like to ask anyone who owns a box with a front led panel and is interested to report the board name, the display chip (common chips are fd6551, fd650, tm1650, etc...) and the original stock dts if possibile.
It would make things easier to support already existing boards.
Thank you!
edit: for source code and reference: https://github.com/paolosabatino/leds-fd6551