jock

@Truong Thinh Chau I see that you are using an armbian image from a third-party source (ophub), I'm sorry but you have to ask them about issues; I'm not aware of their customizations and modifications. If you want help from this forum, please use an image from an official source.

@Truong Thinh Chau perfect, thanks fot the device tree, I had the chance to give a quick look into and I can't see anything very different about your board, so it should work out of the box. As long as dmesg looks ok to me, it could be an issue with HDMI. Did you try to access the box via SSH? Here are the instructions: https://forum.armbian.com/topic/34923-csc-armbian-for-rk322x-tv-box-boards/page/45/#comment-135407 In case HDMI is not accessible or is not working, the multitool can be operated via regular SSH access, just give a dozen seconds or more to boot. The board led should be blinking when ready and the device should be pingable.

@Truong Thinh Chau hello, happy to lend a hand, but you should be more specific on what is your problem... dmesg looks ok to me; your board is a new entry too, and it looks to me it has an unknown (to me) PMIC that could be a source of issues. I will try to have a look into the dtb from your firmware (thanks for that), but lately I've been quite busy and can't promise anything

@Vladimir Trondin I see no issues about eMMC in that dmesg

@haven could not check right now, but nothing should have changed from the audio side. Perhaps the order of the devices changed and what was once the default, now it is not anymore? Recently I enjoyed some Quake running on an rk3318 box and analog audio was the default. Those errors also are not relevant, the audio devices will still work with no issues.

Hello @Vladimir Trondin, as @fabiobassa already pointed out, there is no driver for ssv6158. Doing some research, it seems that it may use the ssv6x5x driver, but it would require adaptation, plenty of time, plenty of patience and you would not be sure if it will finally work. About the eMMC of your board, it would be handy to get the output of dmesg command, but in the meantime you could do some experimentation with the emmc parameters in rk322x-config withing this page: In particular, try to enable emmc-pins and emmc-ddr-ph45 or emmc-ddr-ph180 or emmc-hs200 (these last three are alternative, only one should be enabled) and see if your emmc gets detected after a reboot. Also your board r3229q is not listed within the led-conf options, but I see some similarities with r329q board (led-conf2) MXQPRO_V72 (led-conf6), so you may start trying with those ones, or stick with generic since your wifi is already detected despite being useless.

Exacty, mpv in debian bookworm already has full support for drm-prime, so there is no need for a patched version of that the instructions that work are there, in the meantime it can be that mpv changed some default, actually I didn't check recently

There is a post on the rk3318 tvboxes forum with a kernel dump and something that did not went good with work queues: https://forum.armbian.com/topic/26978-csc-armbian-for-rk3318rk3328-tv-box-boards/?do=findComment&comment=203586 I did take a little look into the code, but could not spot anything wrong. By the way @Jean-Francois Lessard wasn't it simpler to use .led_set_brightness_blocking in place of .led_set_brightness and let the led core do the job with the work queues?

@Parth the soc is slow, it is one of the slowest socs around with a modest amount of memory on board , so don't expect stellar performance. The image with debian bookworm is a minimal image: small and good for servers. For all the other questions, you can consult the official armbian documentation https://docs.armbian.com/ and related forums

@Vidhome I'm glad it worked, but you didn't really need to compile the driver yourself, it should have worked out of the box after choosing led-conf5 and rebooted

I uploaded also a bookworm with kernel 6.11 image here

you should get the regular log on the uart and then kernel and systemd messages. You shoul also get proper HDMI output (except for R29/R2B/H10 boards, which require to be first configured with rk322x-config). edit: ah, uboot is fully functional both via uart and via usb keyboard

You can burn it on an sdcard and test directly from sdcard if you blank your emmc with rkdeveloptool or a similar tool. When emmc is empty (as well as when it is "masked", hence maskrom), the board will boot from sdcard and it is the suggested way to verify the board boots with armbian or has issues.

@Parth here it is, you may try to run this image and see if it boots

@Parth Yatin Temkar hello; I'm a bit confused about your journey. First of all, as @RaptorSDS said, the specs of the rk3228a board are fake because the chip cannot support more than 2gb of DRAM. You have 1gb of DRAM and the proof is the ddrbin that is reporting the DRAM size. A backup of the original firmware would have been really useful, I suspect you have some issue with the trust os. This: makes me think there is some artificial in the proprietary trust os that is freezing the board. You have to try with a bootloader with opensource optee but at the moment I don't have it at hand, but can give a chance to build an image with the older opensource trust os and see if it works for you. As long as you have the serial working, could you please post the output of the multitool boot?

@SuperMaximus I just double checked on a pristine armbian installation on my tinkerboard and enabling pwm1, pwm2 and pwm3 does not incur in any inconvenience. All the 4 pwms are available in my case: root@tinkerboard:/sys/class/pwm# ls -lah total 0 drwxr-xr-x 2 root root 0 Oct 14 12:26 . drwxr-xr-x 66 root root 0 Oct 14 12:26 .. lrwxrwxrwx 1 root root 0 Oct 14 12:26 pwmchip0 -> ../../devices/platform/ff680000.pwm/pwm/pwmchip0 lrwxrwxrwx 1 root root 0 Oct 14 12:26 pwmchip1 -> ../../devices/platform/ff680010.pwm/pwm/pwmchip1 lrwxrwxrwx 1 root root 0 Oct 14 12:26 pwmchip2 -> ../../devices/platform/ff680020.pwm/pwm/pwmchip2 lrwxrwxrwx 1 root root 0 Oct 14 12:26 pwmchip3 -> ../../devices/platform/ff680030.pwm/pwm/pwmchip3

@SuperMaximus oh, that's weird, sorry for the inconvenience! You should be able to attach an usb cable to the USB micro OTG port and then to a computer: the tinkerboard will appear as a mass storage device and you should be able to revert the changes. By the way, always enable only the overlay you need. I double checked and to use pwm2 or pwm3 ,you need to disable uart2 because some pins are muxed. Anyway I see something wrong in the device tree for the tinkerboard: all 4 uarts are enabled in the base device tree, thus having the overlays to enable is not useful and, moreover, uart2 should be the debug uart which is not a good idea to disable. I need to investigate a bit in this, but I hope you will be able at least to restore functionality of the board.

Here you get the pwm1, 2 and 3 overlays. Put them in /boot/dtb/rockchip/overlay directory and enable those you need in /boot/armbianEnv.txt or via armbian-config and you should get the pwm devices. rockchip-pwm1.dtbo rockchip-pwm2.dtbo rockchip-pwm3.dtbo

Unfortunately I don't have a Tinkerboard S R2.0 but a Tinkerboard S R1.0. I took a look into the device trees and in fact I have the confirmation: for the Tinkerboard (all versions) only the pwm0 is enabled. pwm1, 2 and 3 are disabled. If you're still interested, I can provide the necessary device tree overlays to enable them selectively.

It seems that your board is freezing after DDR initialization and before miniloader boot. It could be an issue with the DRAM or an issue with flash memory, but since you said you swapped the sdcard and moved to eMMC, probably the problem may somewhere in the DRAM. I'm more prone to suspect some power issue or interference issues though. I see from your dmesg that you have a faulty USB device attached: USB device could easily cause the board to misbehave, either by direct effect (faulty or shortcircuited USB device) or indirectly (interference coming from external equipment attached to the USB device). I have seen once a faulty USB stick that was preventing a Raspberry Pi to boot at all; removing the stick allowed the board to boot fine.

Well, the X88 Pro board is supported, so you may just want to try it

@Alex ThreeD yes, the proprietary SPL (the "miniloader") bahaves that way: I'm going by memory so I may be faulty about numbers, but in general it starts from an address (sector 0x2000) and tries to find the LOADER signature; if it does not find the signature, retries adding 0x800 sectors and so it goes on... Then does the same for the trust os (looks for TOS), starting from sector 0x4000. As said, numbers may not be exact. What is not really widely known is that you can put a GPT partition table on the flash and name the partitions uboot (or u-boot, can't remember exactly) and trustos and the miniloader will start looking directly there. About the bootrom and miniload order, you're right: bootrom first tries from emmc, then from sdcard. miniloader first checks the sdcard, then emmc. This is a great source of pain when dealing with booting on rockchip; allwinner, for example, has the bootrom that boots first from sdcard and then emmc and everything is much simpler there.

@Vidhome drop the openvfd driver, recent armbian kernel have the tm16xx driver from @Jean-Francois Lessard already compiled in for rockchip64. You have to enable the beta repository, upgrade and everything should be already set up for X88 Pro 10: https://forum.armbian.com/topic/26978-csc-armbian-for-rk3318rk3328-tv-box-boards/?do=findComment&comment=203491 Don't forget to take a backup of your installation before enabling beta repository. Otherwise, you could compile the tm16xx driver it by yourself: https://forum.armbian.com/topic/43667-help-wanted-to-test-a-new-openvfd-alternative/?do=findComment&comment=202875

Actually the main trigger for bootloading is the miniloader, which leads to boot from sdcard or emmc depending on what it finds in sdcard. If there is a proper signature in some expected addresses, it will load u-boot and trust OS from sdcard, otherwise goes with emmc. Also it will check for GPT partition table searching for the address hints where to find uboot and trust os. Actually you should not need to supply a trust os: uboot (called the "loader) should suffice for the rockchip miniloader. Anyway, the main idea is to wipe all the proprietary blobs and keep the bare minimum to do the job. Currently, despite u-boot is capable of initializing DDRs on rk3328, the rockchip ddrbin is kept proprietary for broader DDR compatibility among the boards, the rest is fully open source. The proprietary trust OS would also allow DDR frequency scaling, but it is doing nasty things and crashes the SoC when you run it faster than 1.1GHz. Dual boot may be interesting, but at the moment I won't merge that unless there are very important advantages.

About the service and driver issues, you could post in the post of the author about the kernel module: I'm glad you tested also the indivual leds and they work; I will integrate those into the RK3318_V1.4 device tree overlay