blust0ne

It's been a while so I don't remember exactly, but I think I made this change.

I recently got two rk3528 tvbox. Lemfo T1 2G/16G only. transpeed mx10 (Mx box S) They work with hinlink ht2 image, hdmi always out. ( LAN should be changed , gmac1 - > gmac0 ) DQ08 has missed something on hdmi or rk3528 becomes a revision up ??

try to this image, it may work for you.

You have to check write by Address. In loader mode , MiniLoaderAll.bin is not checked. In maskrom mode , MiniLoaderAll.bin is checked. When the error is occurred, the device seems to be in loader mode.

After the red error message , uncheck the loader item and press "run" again"

Try disconnecting and reconnecting the hdmi cable after the tvbox has done boot. Maybe CEC or HDMI hotplug make the difference.

Please tell me the process of making bootfs.img in more detail.

The rk3528's u-boot with correct android boot image can enable the HDMI. And then the kernel show this message inno-hdmi-phy ffe00000.hdmiphy: phy had been powered up , hdmi working.. /* * reg0xe9 default value is 0xe4, reg0xea is 0x50. * if phy had been set in uboot, one of them will be different. */ if ((inno_read(inno, 0xe9) != 0xe4 || inno_read(inno, 0xea) != 0x50)) { dev_info(inno->dev, "phy had been powered up\n"); inno->phy->power_count = 1; In my guess, rk3528 u-boot can enable the hdmi, but rk3528's kernel code does not enable the hdmi yet.

could you share the usb boot enabled u-boot image for my test?

I have DQ08 with pcb FX-RX3528-D4. The original u-boot for android (when android boot image correct) enable the HDMI for logo display. ANDROID: fdt overlay OK vdd_logic init 900000 uV vdd_cpu init 953000 uV Warn: can't find phy driver Warn: can't find phy driver Model: Rockchip RK3528 DEMO1 LP4 V10 Board Rockchip UBOOT DRM driver version: v1.0.1 VOP have 2 active VP vp0 have layer nr:3[0 2 3 ], primary plane: 2 vp1 have layer nr:2[8 9 ], primary plane: 9 disp info 0, type:11, id:0 use default hdmi phy table *** pause with ctrl+c and insert microsd (h28k armbian image installed) and mmc rescan and then run bootcmd_mmc0 the hdmi working.. mainline kernel does not work with this method ( miniarch 6.4 / 6.5 kernels) So, I make android boot image with armbian kernel, initrd and android recovery image by https://github.com/cfig/Android_boot_image_editor. I can boot on eMMC with HDMI enabled. the partition looks Number Start (sector) End (sector) Size Code Name 1 8192 16383 4.0 MiB FFFF security 2 16384 24575 4.0 MiB FFFF uboot 3 24576 32767 4.0 MiB FFFF trust 4 32768 40959 4.0 MiB FFFF misc 5 40960 49151 4.0 MiB FFFF dtbo 6 49152 51199 1024.0 KiB FFFF vbmeta 7 51200 255999 100.0 MiB 8300 boot 8 256000 460799 100.0 MiB 8300 recovery 9 460800 122142686 58.0 GiB 8300 I manually copied the kernel , initrd and rootfs to eMMC.

https://4pda.to/forum/index.php?showtopic=1072221&st=200#entry125174444 What is your board revision, I have the last one. vontar R3 the original - pcb FX-RK3528-D4 DQ08 with pcb FX-RK3528-D4 - low cost wifi version DQ08 with pcb FX-RX3528-D4 - low cost wifi and remove PMIC

Could you share the changes for HDMI working. My DQ08 can be booted , but HDMI console does not work.