Gausus

So I build a minimal image from sources with Armbian 22.08.0-trunk Bullseye with Linux 5.15.58-rockchip64 and burned it with multitool without erasing emmc this time.
Connected sigrok-pico to uart tx line and pulseview at 3mhz and 100M samples uart protocol decoder. It was a bit of a pain using a logic analyzer first time but I found a login prompt and so replaced sigrok-pico with ch340g usb uart and was able to login and create account without any issue this time. No wifi so I just stuck ethernet cable to my router and dhcp gave ip address to it. I connected hdmi and now that works as well. It seems that only 2gb of 4gb ram is detected but I can see that this kind of issues has been discussed before on this thread.

So to sum it up, it seems 5.18 kernel has no hdmi but if you stick ethernet cable to a dhcp capable router one can get the ip and ssh into it - you probably want to use 5.15 kernel for the time being though. Perhaps something along the lines of git-bisect to get to the bottom of the hdmi issue. I do find it a bit strange that hdmi did not seem to work immediately after flashing. Perhaps one needs to replug the hdmi cable after it has booted.
 
Feel like a winner already, thanks to everyone working on this!
 

Found info from this post:
 
Some general info her on u-boot for RK. https://u-boot.readthedocs.io/en/latest/board/rockchip/rockchip.html
 
1. Can you boot from Multitool.img ? , IF no then its will not be possible to boot Armbian from sdcard.
2. If you can , burn Armbian 22.08 - Debian image found inn first post  to sdcard.
3. Burn Multitool.img to another sdcard or mount image on Linuxpc
 
Manuel mount multitool.img
From terminal.
 
cd $HOME/Downloads/  
# find first unused device  , /dev/loop(24)
losetup -f  
# Mount img on /dev/loop24
 
sudo losetup -P /dev/loop24 multitool.img  
# Open file-browser  MULTITOOL/bsp/
# copy uboot.img and trustos.img to $HOME/Download Linuxpc
# Insert sdcard to linuxpc and find dev of sdcard / often last sdX
 
lsblk -f  
# My sdcard is assigned /dev/sdf
 
# DD uboot and trust IMG to sdcard armbian
# Replace /dev/SDCARD  to your dev for sdcard like sdf

 
sudo dd if=uboot.img of=/dev/SDCARD seek=16384 conv=fsync sudo dd if=trustos.img of=/dev/SDCARD seek=24576 conv=fsync  
If this not work you can copy the generic DTB rk3318-box.dtb form multitool.img to sdcard.
You find generic DTB on root /  multitool.
Copy this to /boot/dtb/rockchip SDCARD to overwrite DTB on Armbian image.
 
Or burn older Armbian img to test if they boots form sdcard when Android on internal storage.
 
Happy booting!!
 
 

Thank you for the tips @jock
 
 
I have 2 H96max+ RK3328 ∕ 4GB  tvboxes.
 
Armbian 22.08 - Debian Bullseye minimal - mainline kernel 5.18.10
 
BOX1 :  On internal eMMC
BOX2:   Boot Armbian from SDCARD  , Android on internal eMMC
 
Benchmark from terminal:
mbw 1000  
Box1 : RAM 667Mhz CPU @ 1,3GHz
AVG    Method: MEMCPY    Elapsed: 0.82118    MiB: 1000.00000    Copy: 1217.764 MiB/s
AVG    Method: DUMB    Elapsed: 0.88632    MiB: 1000.00000    Copy: 1128.263 MiB/s
AVG    Method: MCBLOCK    Elapsed: 0.27756    MiB: 1000.00000    Copy: 3602.800 MiB/s
 
Box2 : RAM 333Mhz (Android uboot) CPU @ 1,3GHz
AVG    Method: MEMCPY    Elapsed: 1.51033    MiB: 1000.00000    Copy: 662.107 MiB/s
AVG    Method: DUMB    Elapsed: 1.62614    MiB: 1000.00000    Copy: 614.955 MiB/s
AVG    Method: MCBLOCK    Elapsed: 0.54709    MiB: 1000.00000    Copy: 1827.854 MiB/s
 
To boot from sdcard when Android on internal storage.
1. Flash Armbian on sdcard
2. Download Multitool.img 
3. Mount multitool.img on linuxpc or flash to another sdcard.
4. Copy  trustos.img and uboot.img from bsp folder to a folder on linuxpc,
5 . DD trustos.img and uboot.img to sdcard Armbian from linuxpc
 
sudo dd if=uboot.img of=/dev/SDCARD seek=16384 conv=fsync sudo dd if=trustos.img of=/dev/SDCARD seek=24576 conv=fsync  
 
 

Thank you for the tips @jock
 
 
I have 2 H96max+ RK3328 ∕ 4GB  tvboxes.
 
Armbian 22.08 - Debian Bullseye minimal - mainline kernel 5.18.10
 
BOX1 :  On internal eMMC
BOX2:   Boot Armbian from SDCARD  , Android on internal eMMC
 
Benchmark from terminal:
mbw 1000  
Box1 : RAM 667Mhz CPU @ 1,3GHz
AVG    Method: MEMCPY    Elapsed: 0.82118    MiB: 1000.00000    Copy: 1217.764 MiB/s
AVG    Method: DUMB    Elapsed: 0.88632    MiB: 1000.00000    Copy: 1128.263 MiB/s
AVG    Method: MCBLOCK    Elapsed: 0.27756    MiB: 1000.00000    Copy: 3602.800 MiB/s
 
Box2 : RAM 333Mhz (Android uboot) CPU @ 1,3GHz
AVG    Method: MEMCPY    Elapsed: 1.51033    MiB: 1000.00000    Copy: 662.107 MiB/s
AVG    Method: DUMB    Elapsed: 1.62614    MiB: 1000.00000    Copy: 614.955 MiB/s
AVG    Method: MCBLOCK    Elapsed: 0.54709    MiB: 1000.00000    Copy: 1827.854 MiB/s
 
To boot from sdcard when Android on internal storage.
1. Flash Armbian on sdcard
2. Download Multitool.img 
3. Mount multitool.img on linuxpc or flash to another sdcard.
4. Copy  trustos.img and uboot.img from bsp folder to a folder on linuxpc,
5 . DD trustos.img and uboot.img to sdcard Armbian from linuxpc
 
sudo dd if=uboot.img of=/dev/SDCARD seek=16384 conv=fsync sudo dd if=trustos.img of=/dev/SDCARD seek=24576 conv=fsync  
 
 

Thank you for the tips @jock
 
 
I have 2 H96max+ RK3328 ∕ 4GB  tvboxes.
 
Armbian 22.08 - Debian Bullseye minimal - mainline kernel 5.18.10
 
BOX1 :  On internal eMMC
BOX2:   Boot Armbian from SDCARD  , Android on internal eMMC
 
Benchmark from terminal:
mbw 1000  
Box1 : RAM 667Mhz CPU @ 1,3GHz
AVG    Method: MEMCPY    Elapsed: 0.82118    MiB: 1000.00000    Copy: 1217.764 MiB/s
AVG    Method: DUMB    Elapsed: 0.88632    MiB: 1000.00000    Copy: 1128.263 MiB/s
AVG    Method: MCBLOCK    Elapsed: 0.27756    MiB: 1000.00000    Copy: 3602.800 MiB/s
 
Box2 : RAM 333Mhz (Android uboot) CPU @ 1,3GHz
AVG    Method: MEMCPY    Elapsed: 1.51033    MiB: 1000.00000    Copy: 662.107 MiB/s
AVG    Method: DUMB    Elapsed: 1.62614    MiB: 1000.00000    Copy: 614.955 MiB/s
AVG    Method: MCBLOCK    Elapsed: 0.54709    MiB: 1000.00000    Copy: 1827.854 MiB/s
 
To boot from sdcard when Android on internal storage.
1. Flash Armbian on sdcard
2. Download Multitool.img 
3. Mount multitool.img on linuxpc or flash to another sdcard.
4. Copy  trustos.img and uboot.img from bsp folder to a folder on linuxpc,
5 . DD trustos.img and uboot.img to sdcard Armbian from linuxpc
 
sudo dd if=uboot.img of=/dev/SDCARD seek=16384 conv=fsync sudo dd if=trustos.img of=/dev/SDCARD seek=24576 conv=fsync  
 
 

EDIT:
 
Try forcing mode on HDMI
Add new line inn armbianEnv.txt
 
sudo nano /boot/armbianEnv.txt
extraargs=video=HDMI-A-1:D drm.edid_firmware=edid/1920x1080.bin
 
# OR you can test this setting
extraargs=video=HDMI-A-1:D drm.edid_firmware=HDMI-A-1:edid/1920x1080.bin video=HDMI-A-1:1920x1080
 
# IF not working test lower res like 1024x768 
 
# Y can set different refresh rate to :  1024x768@30
extraargs=video=HDMI-A-1:D drm.edid_firmware=HDMI-A-1:edid/1024x768.bin video=HDMI-A-1:1024x768@30
 
If working change res after login from Settings > Display ( Xfce)
 
More info her LINK1 : LINK2
 
 
 
 

I have used sudo apt-mark hold <linux-package-name>  , on kernel .
 
sudo apt-mark hold linux-image-current-rockchip64
sudo apt-mark hold linux-dtb-current-rockchip64
sudo apt-mark hold linux-u-boot-current-rk3318-box
 
I then can run apt update and apt upgrade not updating kernel.
 
To remove mark hold use : sudo apt-mark unhold <linux-package-name>
Can y make a list of packages not to upgrade / overwrite ?
 

I have used sudo apt-mark hold <linux-package-name>  , on kernel .
 
sudo apt-mark hold linux-image-current-rockchip64
sudo apt-mark hold linux-dtb-current-rockchip64
sudo apt-mark hold linux-u-boot-current-rk3318-box
 
I then can run apt update and apt upgrade not updating kernel.
 
To remove mark hold use : sudo apt-mark unhold <linux-package-name>
Can y make a list of packages not to upgrade / overwrite ?
 

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.
 
 

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>; // }; // };  

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 ?

Technically Balbes never supported the s905x3. But it is true that he is now ending support of all amlogic cpus.  I already make my own kernel builds, and since I own a few different amlogic based boxes, I have an interest in seeing support continue in some form.  I have asked balbes in another thread if he would tag his public github repositories with a tag that corresponds to his last build supporting amlogic, which then can be a starting point for continued support by the community if there is enough interest.

@balbes150 If I could ask a favor of you.  Would it be possible to add a tag to your public github repositories that corresponds to your last build supporting AML?  With a tagged version of source code that corresponds to your final released build others can pick up where you have left off if they are capable and motivated.  I appreciate your dedication to armbian and respect your decision to end your support of Amlogic cpus.

X96 Max Plus s905x3 4G  DTB fix for network and sound.
 
https://drive.google.com/file/d/1jWnRu-GdOL72__X-ea8oI2VRW_x1ENTM/view?usp=sharing
 
Tested on Armbian 20.05.01 20200408.