Well that was fun. Termux wouldn't load so I found an older version from 2022 thinking that version is older than the box so has a higher chance of working. That also wouldn't open until I went a bit silly and attempted to open it multiple times. Just like Mustafa in Austin Powers, once I attempted to load it 3 times in a row it would show up. Bizarre but I now have a dump of Device.DTB How do I view it properly? I opened it in notepad++ and most of it is gibberish but I can make out a few details that are a bit surprising. Namely - allwinner,h616 arm,sun50iw9p1 The label on this thing says H618 but it appears to be a H616. Where do I go to from here? Thanks.

Nice, congratulations! I wonder why cursor does not show when video is playing by the way: there has always been a patch in the armbian code to support hardware cursor, in fact in X11/Wayland the cursor is handled in hardware and it is perfectly visible and usable when a hardware accelerated video is playing. Also I wonder why you need CMA=256M; normally rk322x VPU has its own MMU that is capable to handle direct to memory access without the need of CMA.

@robertoj the problem is not ffmpeg, which already is works totally fine on debian Trixie (and backwards), the problem is within mpv that changed in v0.4.0 carried by debian Trixie, and at the moment I don't have enough motivation to carry on a custom mpv package for Debian Trixie. You may try with debian forky by the way, but it is a moving target as long as it is still in development.

I didn't mention earlier but after I ran the update/upgrade commands I also manually updated the locale file. During the original setup I accidentally selected the wrong locale, I went into armbian config, deselected the wrong one and selected the correct one but the incorrect locale was still being referenced constantly. So I manually removed it from etc/default/locale. I thought this may have been a reason for it no longer booting and not the update/upgrade commands. I'm just explaining that so you understand why I also tried update/upgrade with the x98h image. Turns out it wasn't me messing with the locale that stopped it booting as this image also will not boot now after apt-get update, apt-get upgrade. This image originally booted ok and it seems the ethernet works better. Downloading from the commands listed above took about 20 seconds vs 30 minutes on the vontar image. But wifi/bluetooth still will not work. One other difference is when I select the bluetooth manager app it actually loaded whereas the vontar image would state something about a service not running. The app loaded but had no devices listed. I'll see how I go with termux. The play store doesn't work on it but I was able to sideload a couple of apps.

@jock Thank you for your reply. Unfortunately, I can't do it I tried to short it, but it doesn't load from the SD card. I shorted it with a piece of wire. When I do it with USB connected, I see the device is in Maskrom. Here the console output from rkdeveloptool using: root@lensky-lp:~# lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 10c4:8105 Silicon Labs USB OPTICAL MOUSE Bus 001 Device 005: ID 04ca:707f Lite-On Technology Corp. HP Wide Vision HD Camera Bus 001 Device 006: ID 0bda:b00b Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 001 Device 008: ID 1ea7:0066 SHARKOON Technologies GmbH [Mediatrack Edge Mini Keyboard] Bus 001 Device 009: ID 2207:320c Fuzhou Rockchip Electronics Company RK3328 in Mask ROM mode Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub root@lensky-lp:~# rkdeveloptool ld DevNo=1 Vid=0x2207,Pid=0x320c,LocationID=104 Maskrom root@lensky-lp:~# rkdeveloptool td Test Device failed! root@lensky-lp:~# rkdeveloptool ---------------------Tool Usage --------------------- Help: -h or --help Version: -v or --version ListDevice: ld DownloadBoot: db <Loader> UpgradeLoader: ul <Loader> ReadLBA: rl <BeginSec> <SectorLen> <File> WriteLBA: wl <BeginSec> <File> WriteLBA: wlx <PartitionName> <File> WriteGPT: gpt <gpt partition table> WriteParameter: prm <parameter> PrintPartition: ppt EraseFlash: ef TestDevice: td ResetDevice: rd [subcode] ChangeStorage: cs [storage: 1=EMMC, 2=SD, 9=SPINOR] ReadFlashID: rid ReadFlashInfo: rfi ReadChipInfo: rci ReadCapability: rcb PackBootLoader: pack UnpackBootLoader: unpack <boot loader> TagSPL: tagspl <tag> <U-Boot SPL> ------------------------------------------------------- root@lensky-lp:~# rkdeveloptool rid Reading flash ID failed! root@lensky-lp:~# rkdeveloptool cs 2 AMO: ERR_DEVICE_WRITE_FAILED Change Storage failed! root@lensky-lp:~# rkdeveloptool ppt Read GPT failed! Read parameter failed! Not found any partition table! root@lensky-lp:~# rkdeveloptool db /home/lensky/Downloads/For\ RK3328\ devices/RK3328MiniLoaderAll_V2.50.bin Downloading bootloader succeeded. root@lensky-lp:~# rkdeveloptool ppt **********Partition Info(parameter)********** NO LBA Name 00 00002000 uboot 01 00004000 trust 02 00008000 misc 03 0000A000 baseparamer 04 0000A800 resource 05 00012000 kernel 06 00022000 boot 07 00032000 recovery 08 00042000 backup 09 00062000 cache 10 000A2000 metadata 11 000AA000 kpanic 12 000AC000 system 13 003AC000 userdata As you see after boot it looks like the flash is empty. I can't ready any info and there no partitions. But after download bootloader command I see partiosions and can read flash info and chip info. After reboot all is disappear again. This is my board: This is my eMMC chip: I have found YouTube video how to short the clock pin for my board. On the opposite side, I need to short these pins: When I insert the SD card and boot the device, it just lights the red led and nothing more. Is something I do wrong?