Ben N Voutour

Update!
 
Images on first page have been updated to kernel 5.14.13
 

Thank you for your response.
 
Dont know what y did ,  I was unable to create DTB.
 
dtc -I dts -O dtb -f rk3318-box_1.5Ghz_SDCARD_v1a_ST_sdhr104.dts -o rk3318-box_1.5Ghz_SDCARD_v1a_ST_sdhr104.dtb Error: rk3318-box_1.5Ghz_SDCARD_v1a_ST_sdhr104.dts:2894.3-2895.1 syntax error FATAL ERROR: Unable to parse input tree  
I download my rk3318-box_1.3Ghz_SDCARD_v2_ST_sdhr104.dts file , looks like the same error. Will fix dts file.
 
rk3318-box_1.3Ghz_SDCARD_v2_ST_sdhr104.dts  fixed.
Is it possible to delete post , can't find a way to do it.
 
 

Look at the post edit I made a little after, clarifies why the thing can't work on our tv boxes.
 
I learned things are and there on the internet, could not find a proper guide.
Anyway google reports this forum thread, which is a good starting point:
 
Yeah, undervolting is cool, but results vary a lot depending on the cpu sample.
GPU can be tweaked too. RAM can't be tweaked for three reasons:
the dmc (dram memory controller) node in the dtb is disabled the dmc driver in the kernel is a bit broken the piece of code that does the dram frequency scaling is not present The dram frequency is fixed by a thing which is called ddrbin, and it is the very first thing that boots (even before u-boot).
It is fixed to 330 Mhz currently, but probably I will push it to a higher yet safe value.
 
You need to put together an idbloader, which is composed of ddrbin + u-boot SPL.
You can inspect armbian sources for that, but if you're not an expert in compiling u-boot, I would rather suggest you to stay away from that to avoid lose mental sanity.
 

DTB SDCARD mode up to 104 MB/s
 
Have tried to squeeze some more performance out of my H96 max + RK3328.
 
SDCARD speed runs at sd high-speed mode / max 24MB/s R∕W on rk3318-box.dtb
Its possible to get higher speed from sd-card
 

 
# Org DTB sudo cat /sys/kernel/debug/mmc0/ios clock: 50000000 Hz actual clock: 50000000 Hz vdd: 21 (3.3 ~ 3.4 V) bus mode: 2 (push-pull) chip select: 0 (dont care) power mode: 2 (on) bus width: 2 (4 bits) timing spec: 2 (sd high-speed) signal voltage: 0 (3.30 V) driver type: 0 (driver type B)  
Have modified the dtb to support up to hr104 (104 MB/s)
rk3318 image will not boot , but Armbian_21.11.0-trunk_Station-m1_hirsute_edge_5.14.11_xfce_desktop.img are booting using this modified DTB  DTS

 
# Mod DTB Station m1 image sudo cat /sys/kernel/debug/mmc0/ios clock: 150000000 Hz actual clock: 150000000 Hz vdd: 21 (3.3 ~ 3.4 V) bus mode: 2 (push-pull) chip select: 0 (dont care) power mode: 2 (on) bus width: 2 (4 bits) timing spec: 6 (sd uhs SDR104) signal voltage: 1 (1.80 V) driver type: 0 (driver type B)  
Using gnome-disks performance tool , i get 70+ read 40+ write speed.  about 2-3X performance boost on sdcard.
 
If y like to test this DTB disable all overlays in /boot/extlinux/extlinux.conf
 
Have tried to enable modules  in rk3318 image to boot.
APPEND root= xxx yyy ....   ADD to end    mmc_block sdhci tifm_sd
 
Dont know if kernel need a patch to boot from sdacrd when sd-uhs-XX modes enabled.
 
SOME links about sdcard mode i DTB
https://android.googlesource.com/kernel/msm/+/android-wear-5.1.1_r0.6/Documentation/devicetree/bindings/mmc/mmc.txt
https://patchwork.kernel.org/project/linux-arm-kernel/patch/87imkryz5t.fsf@vany.ca/
https://tinkerboarding.co.uk/forum/archive/index.php/thread-310.html
 
Changed i  rk3318-box.dtb

 
mmc@ff500000 { compatible = "rockchip,rk3328-dw-mshc\0rockchip,rk3288-dw-mshc"; reg = <0x00 0xff500000 0x00 0x4000>; interrupts = <0x00 0x0c 0x04>; clocks = <0x02 0x13d 0x02 0x21 0x02 0x4a 0x02 0x4e>; clock-names = "biu\0ciu\0ciu-drive\0ciu-sample"; fifo-depth = <0x100>; max-frequency = <0x8f0d180>; resets = <0x02 0x6d>; reset-names = "reset"; status = "okay"; bus-width = <0x04>; cap-mmc-highspeed; cap-sd-highspeed; disable-wp; pinctrl-names = "default"; pinctrl-0 = <0x49 0x4a 0x4b 0x4c>; sd-uhs-sdr12; <-------------------------- sd-uhs-sdr25; <-------------------------- sd-uhs-sdr50; <-------------------------- sd-uhs-sdr104; <-------------------------- vmmc-supply = <0x4d>; vqmmc-supply = <0xd4>; <-------------------------- DISABLED phandle = d4 spdif-2 could not find l free phandle to use card-detect-delay = <0x320>; // Diff / Disabled // phandle = <0x9a>; // card-detect-delay = <0x320>; // cd-gpios = <0x48 0x05 0x01>; // no-sdio; // supports-sd; }; sdmmc-regulator { compatible = "regulator-fixed"; gpio = <0x6b 0x1e 0x01>; pinctrl-names = "default"; pinctrl-0 = <0x6c>; regulator-name = "vcc_sd"; regulator-always-on; regulator-boot-on; regulator-min-microvolt = <0x325aa0>; regulator-max-microvolt = <0x325aa0>; vin-supply = <0x1e>; phandle = <0x4d>; }; // ADD high speed sdcard 1,8v mode sdmmcio-regulator { compatible = "regulator-gpio"; gpios = <0x68 0x00 0x00>; states = <0x1b7740 0x01 0x325aa0 0x00>; regulator-name = "vcc_sdio"; regulator-type = "voltage"; regulator-min-microvolt = <0x1b7740>; regulator-max-microvolt = <0x325aa0>; regulator-always-on; // vin-supply = <0x2b>; vin-supply = <0x6e>; phandle = <0xd4>; }; // spdif-2 { // // spdifm2-tx { // rockchip,pins = <0x00 0x02 0x02 0x5f>; // phandle = <0xd4>; // }; // };  

Uhm, I see that you have and old full-hd monitor. It should not be an issue, but apparently it is.
From the hints about your experiences (working on Android, working on multitool, not working with armbian), I guess you installed armbian with mainline kernel: there are some tweaks in the mainline kernel that alter the HDMI timings, thus they may be better with some monitors and worse with others. In your case it may be that your monitor does not like those timings.
You may give a chance to the legacy kernel image, you can just put in on sdcard, plug the sdcard and boot: the box should automatically boot from sdcard, so you can easily test if HDMI is properly working with legacy kernel at least.

Great, thank you very much!

Read the instructions!! rk3318-config to configure it for 1.3 ghz !!

OK no worries I have already read the 15 pages of this thread ...
Now the problem is that when I run rk3318-config at the end it requires a reboot and there starts the bug, my box bug during the boot process .. only solution I found, delete all the overlays line which a was added in the armbianEnv.txt (luckily I can connect my SD card to my computer) ..

The cpu-hs overlay is responsible for the 1.3ghz clock. If it is causing you issues, then the cpu is not really happy running with that frequency

It's strange I never had any problem using the 1.3GHz processor with the other armbian images. The Station-M1 system installed on Emmc works at 1.3GHz without any particular problem.
When I had put rk3328-evb.dtb in armbianEnv.txt I had found the max value at 1.3 GHz and the system started up without worries (but no hdmi signal).
In any case for the moment the system is stable, I left it running all night without any problems (but at 1GHz) .. I will continue ..
Something a little off topic:
Any idea why lightdm crashes startup when lxdm is running fine ..?
Thank you again for the job, great ..!
 

Need to check out the station m1 dtb though. Maybe your board has a dedicated PMIC to control the CPU voltage and not the common cheap PWM voltage regulation.
It would be the first case for rk3318, but it could definitely could be.
Or the other dtbs are just giving more voltage to the CPU, that could be also...
I'm not having problems with lightdm right now; in the recent past lightdm-gtk-greeter caused some issues with hangs and crashes, but on arm64 it should be fine right now. Try to upgrade the package with apt (take care not to upgrade the kernel and dtbs though!)
 

Here is the .dtb file that I use with the Station-M1 image, I just modify rk3328-box.dtb  a little to have a correct use of the leds on my MX10 box (a red led "off" and a led blue "on")
rk3328-mx10.dtb rk3328-mx10.dts

You should also provide some detailed photos of the board, in particular report if you see a small chip with the rk805 printing on it.
Also the device tree of the original firmware (or the original firmware itself) would be useful.

Yes there is a small chip marked RK805-1 CAADA9018
When I bought it it was running on android 7.1.2 here is the link to the firmware I was using (because rooted)
http://geekbuying.mediafire.com/file/brngum8r862f8h2/MX10_RKMC18.0_20171212_r1.img
 

Hi everybody,
someone has got this box?
I have installed Armbian_21.11.0-trunk_Rk3318-box_hirsute_current_5.10.68_xfce_desktop following the guide, then run rk3318-config. 
I can connect to it with SSH and RDP but HDMI shows nothing.
Ideas?
Thanks.

@MX10.AC2N Okay, so that's the reason your board works fine with Station M1 device tree.
Your board seems to be better constructed than regular rk3318 boards, maybe is it rk3328? (rk3318-config will tell you)
Another non-common thing is the GL850G USB2 hub chip, but that should not be a problem.
 
I need a bit of time to study and prepare an appropriate overlay specific for your board, so you have to be patient...

I replaced the existing /lib/firmware/brcm/brcmfmac4334-sdio.rockchip,rk3318-box.txt with this file. Then it worked in nmcli
#nmcli device wifi list shows available wifi networks then #nmcli --ask device wifi connect vodafone5CC8 and it asked for the password for my wifi named vodafone5CC8, and now it connected, before it didn't. My overlays are: overlays=rk3318-box-cpu-hs rk3318-box-emmc-ddr rk3318-box-led-conf1 rk3318-box-wlan-ap6334

Thanks for the quick reply.
 
Did not work , used nmcli.
Even tried to disable password on WiFi.
Error: Connection activation failed: (11) 802.1X supplicant took too long to authenticate.
 
1. Copied and renamed brcmfmac4334-sdio.rockchip,rk3318-box.txt to brcmfmac4334-sdio.txt
Rebooted:  no wifi
2. Replaced the existing text in /lib/firmware/brcm/brcmfmac4334-sdio.rockchip,rk3318-box.txt and brcmfmac4334-sdio.txt with this file
Rebooted:  no wifi
 
Think I have a different WiFi chip.
Any idea what chip SP2743C is ?
 
Curse have you opened your box and seen what name is on your wifi chip ?

No, I'm quite bad at screwing and such because of an injury. Sorry. Oh... I have the H96Max+ RK3328 4GB/64GB Voice Remote version (not that I have tried using voice commands on it). Who knows, the Voice Remote version and the normal remote version might differ.

Jock I have a problem, when I pass the command rk3318-config it opens normal I select all of the chip on my tvbox which is a MX10 RK3328 4GB-RAM/32GB-ROM
Then I reboot, the tvbox doesn't turn on anymore what do I do? already tested all the config settings..
 

The most offending things are:
1. emmc settings
2. cpu frequency
 
eMMC settings are the most dangerous. Leave all the options unchecked in the eMMC panel.
CPU frequency safe setting is 1.1Ghz (which is the default). Not all chips can reach 1.3Ghz.
 

@Gausus
Your chip is definitely an AP6334/BCM4334, it declares that way to the system.
Printings on the chip cages are fantasious chinese characters which does not relate to anything known.
 
Can't say anything more about, the nvram.txt you took from github is the one which I know is working pretty fine on my box, which is an Ap6334 too, but it can be your board configuration is different and not handled well with that nvram, but fixing this is beyond my possibility.
 
 

Good Morning. Just a quick question.
Is it possible that the temperature is shown wrong at login? 
____ _ ____________ _ ___ ____ | _ \| |/ /___ /___ // |( _ ) | __ ) _____ __ | |_) | ' / |_ \ |_ \| |/ _ \ | _ \ / _ \ \/ / | _ <| . \ ___) |__) | | (_) | | |_) | (_) > < |_| \_\_|\_\____/____/|_|\___/ |____/ \___/_/\_\ Welcome to Armbian 21.11.0-trunk Bullseye with Linux 5.10.68-rockchip64 No end-user support: built from trunk System load: 3% Up time: 2 days 21:03 Memory usage: 4% of 3.88G IP: 192.168.0.35 CPU temp: 68°C Usage of /: 8% of 57G It seems to idle at 68 C and when doing stuff goes to 90+. At the same time, "top" sees the CPU going at 270%. While the box feels warm, it doesn't feel hot, which I assume it would be, if it were 90+C a centimeter from my finger.

@curse
Yes, it is possible. Temperatures are quite varying with these chips and reportings are not very reliable IMHO. The problem is very similar with rk322x too.
Cpu usage in top is the sum of all cores/processors, so it can go beyond 100% if your process is doing multithreaded work.

BTW, today I downloaded and installed the latest "minimal" 
"Armbian 21.11 - Debian Bullseye minimal - mainline kernel 5.10.68 - Download from here - Build date: 2021-09-24"
I don't seem to find "armbian-config". In /usr/local/bin/ there is only rk3318-config. Has it been forgotten or is it just me who are looking at the wrong place?
 
Edit/
I just remembered reading somewhere that armbian-config isn't in the minimal images because it needs a lot of dependencies...