Ben Voutour

then what is 1596000000 ?
that is what it returned for me as root #
"cat /sys/kernel/debug/clk/dpll/clk_rate"
should i try 1333? or 1600?
i'm gonna try 1066 first.
unless i'm missing something , some of these boxes can sort of handle the higher ddrbin, we might have to play a bit with it.
these boxes are a dime a dozen from most online stores....
 

I confirm this 👍

The ddrbin is "packaged" by the u-boot command mkimage, then some other code (uboot SPL) is appended to the resultant binary.
 
In theory the ddr frequency is set in just a bunch of bytes in the ddrbin, so substituting the ddrbin (or altering the target bytes) on the sdcard/emmc with a bare "dd" command would work. But that requires some math and a hex editor to find the exact position where to put it with dd command AND I don't know if there are some CRC checks that would break the whole thing.
 
I need to investigate a bit about, surely it is a job for a script because manual intervention would be a bit risky.

You're welcome
 
This is actually not possible with the openvfd driver because it is not wired to the kernel led framework but is a totally custom module that just exposes the hardware to userspace.

RK3318 board (x88 pro 10)
Kernel: 6.6.2-edge-rockchip64
Ubuntu Jammy 22.04.3 LTS
 
Vidoe hardware acceleration working.
 
Clock and leds working using the OpenVFD service
 

 
See details here if interested:
 
 

here is the English Translation for the Rk3318 TRM
Rockchip+RK3318+Datasheet+V1.0-20190806.en.ru en.pdf

@Jock
Here Are Some DTB Dumps From 2022 to 2023 (Android 9/10/11/12)
The File Names Are "CRC32".dtb
DTB Dumps (2022~2023) (CRC32.DTB)

My TV box freezes on the frequency 667. Until they make a u-boot with stable operation at 667MHz, it will not work well. If you need a frequency of 800MHz, you need to take a u-boot from android

With a DDR memory frequency of 533 MHz, I have no problems with LAN
 
I am using a script to create idbloader.img
../mkimage -n rk3328 -T rksd -d "rk3318_ddr_333Mhz_v1.16.bin" idbloader.img
cat "rk3328_miniloader_v2.50.bin" >> idbloader.img
 
My idbloader.img does not work with Armbian images (kernel update 5.19.15 and libreelec). But, with your other images, my idbloader.img works.
So I'm trying to ask you, maybe you used DDR_v1.19.bin?
 
My RAM = D9PQL 
Operating frequencies and memory timings:
800 MHZ (11-11-11-28) / 39-208-5-12-6-6-24
761 MHZ (10-10-10-27) / 37-199-5-12-6-6-23
685 MHZ (9-9-9-24) / 33-179-5-11-6-6-21
609 MHZ (8-8-8-22) / 30-159-4-10-5-5-19
533 MHZ (7-7-7-19) / 26-139-4-8-4-4-16 - At this frequency 533 MHZ, my TV box is now working flawlessly
457 MHZ (6-6-6-16) / 22-119-3-7-4-4-14
380 MHZ (5-5-5-14) / 19-100-3-6-3-3-12
 
 

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

No. Only linux or android

Which are known to "steal" the work of others without giving credits and support.
That's the best way to kill armbian project 😒

Hello!
 
If you mean overclock the cpu, it depends on your sample. rk3318 are rated for 1.1ghz, for so far it looks like a software limitation rather than a hardware one. Some people pushed them up to 1.5ghz, but the increased horsepower is not worth the heat at all IMHO.
About overlocking the ddr, actually they are underclocked at 333mhz: dynamic reclocking requires a proprietary Trust OS blob, but this won't allow CPU to go beyond 1.1ghz. On the other side, booting the device at 667mhz caused many boards to not boot at all (notably X88 Pro 10 market models)
 
About the LED Clock, if you mean the frontal led panel, there is a kernel driver + userland application which work together; they do the job, but are rather suboptimal for technical reasons and not included into regular images.

@Ineptitude unfortunately the driver is not yet included into armbian. I tried to take a quick look to it and there is the usual mess of preprocessor directives to compile and run on the various manufacturer platforms, plus some low general quality code. I gave it some hours for inspection, then I gave up. Perhaps I will give some more love to it sooner or later, but I don't promise anything.