NiTr0

about leds - blue (system led) works OK; red LED - just ligths constantly (not too bright, but much brighter than before dtb applying), doesn't react on aux led change.

here's stable options for dtb overlays: overlays=emmc emmc-pins emmc-hs200 ddr3-528 led-conf7 maybe ddr3 will work even on higher frequency (660 or 800mhz) but in stock it works at 600mhz, so I decided to set it at nearest lower value (I don't need much CPU/GPU power in this box, but factory 330MHz seems to be too low)

I saw in rk322x-config DDR frequency options - they are applied by kernel like emmc settings, right? I mentioned factory DTS only as a source of frequency information (KMQN10006B-B318 has no datasheet/specs available in public internet).

hm, h20 board in rk322x-config works OK. how LED behavior can be changed? are they blinking by some script/binary, or? also, question about DDR/eMMC settings - when they're applied, and how device can be crash-recovered if settings are wrong (boot button should work, or only resistors shorting will help)? and what is default DDR freq - 300MHz, or 600MHz? I looked up into factory dts and there was 600MHz frequency; but in rk322x-config there's no 600MHs option - there are 528 and 660 MHz...

I've placed compiled u-boot-rk322x-with-spl.bin at 0x8000 in image and image boots OK. small question: how to check (and change) GPIO pin assignment? currently I have only dark red light; it seems like it's looks like GPIOs mismatched. I've extracted and decompiled DTS from original firmware, but at first quick look I can't see pin assignments here - maybe I'm hav no enough experience...

try this image: https://drive.google.com/file/d/1bcOfc-df_84-qa0-SQjrQnKpzfEGrdsd/view?usp=sharing I've updateed ddrbin (I manually placed u-boot-rk322x-with-spl.bin with ddrbin 1.11 at 0x8000 in image) and it boots OK on my board

and quite strange that ddrbin code twice appears in image (second time at 7D93800)...

quite strange: --- a/config/sources/families/rk322x.conf +++ b/config/sources/families/rk322x.conf @@ -123,7 +123,7 @@ uboot_custom_postprocess() { # tools/mkimage -n rk322x -T rksd -d tpl/u-boot-tpl.bin u-boot-rk322x-with-spl.bin # - tools/mkimage -n rk322x -T rksd -d $SRC/packages/blobs/rockchip/rk322x_ddr_330MHz_v1.10_2t.bin u-boot-rk322x-with-spl.bin + tools/mkimage -n rk322x -T rksd -d $SRC/packages/blobs/rockchip/rk322x_ddr_300MHz_v1.11.bin u-boot-rk322x-with-spl.bin cat spl/u-boot-spl.bin >> u-boot-rk322x-with-spl.bin dd if=u-boot.itb of=u-boot-rk322x-with-spl.bin seek=$((0x200 - 0x40)) conv=notrunc user@laptop:/mnt/hdd/other/LinDevelopment/armbian$ but grep -a "Version V1.1[01] 20" output/images/Armbian_23.11.0-trunk_Rk322x-box_bookworm_legacy_4.4.194.img (���<���t� ����������������>�$��'� F����ޠDDR Version V1.10 20190926 (���<���t� ����������������>�$��'� F����ޠDDR Version V1.10 20190926 ^C

your board enters to maskrom, or boots from EMMC (ddrbin is on eMMC)?

unfortunately they're built with ddrbin 1.10... I tried to built images with ddrbin 1.11 (I placed it into blob and changed config/sources/families/rk322x.conf) but got image with ddrbin 1.10 for some reason - maybe there's cached intermediate results?

try to short ROM data lanes that are passed via 51R resistors (8 pcs or 2x 4-resistors assembles hear eMMC). I just shorted any 2 lines between different assembles by tweezer.

@jock multiboot from your post boots OK on my board from SD card till shell. also, maybe it'll be good to use baudrate 1500000 for uboot/kernel too if bootloader reports to console at 1500000bps?

any ideas how can I boot armbian on my H20 board? maybe I can create GPT partitions by rkdeveloptool, and write stock uboot, legacy kernel and rootfs image on flash?

I've updated multiboot image at this link https://drive.google.com/file/d/13X2-9DVrrnDyDg1zd_mkGOs3SCZV84Wl/view?usp=sharing , now it boots OK.

yes I switched speed to 115200. it seems like rockchip miniloader starts from eMMC and then boots from microSD. I wrote first 128KB of eMMC content to SD card with multiboot image (except 1st sector with partition table) - and it boots OK with empty eMMC.