Freeze

Ok, but now, how i can recovery damage DTB files? I cant start armbian, just console is working

After apt-get update and upgrade DTB files was damaged :(( How its recovery, dont know rkdeveloptool dont working rkdeveloptool reboot-maskrom Reset Device quit, creating comm object failed! It's log from console interface(COM port) Trying fit image at 0x4000 sector ## Verified-boot: 0 ## Checking atf-1 0x40040000 ... sha256(1d13f803de...) + OK ## Checking uboot 0x40200000 ... sha256(ad96202f45...) + OK ## Checking fdt 0x4033dd80 ... sha256(6d0c8a3eca...) + OK ## Checking atf-2 0x400f0000 ... sha256(2f297c059b...) + OK ## Checking atf-3 0x3fe70000 ... sha256(9d9e1b461e...) + OK ## Checking optee 0x48400000 ... sha256(31c3421ab3...) + OK Jumping to U-Boot(0x40200000) via ARM Trusted Firmware(0x40040000) Total: 94.153/238.645 ms INFO: Preloader serial: 0 NOTICE: BL31: v2.3():v2.3-749-g30018b771:derrick.huang, fwver: v1.04 NOTICE: BL31: Built : 09:43:01, Apr 16 2024 INFO: ext 32k is not detected INFO: ARM GICv2 driver initialized INFO: dfs DDR fsp_params[0].freq_mhz= 2112MHz INFO: dfs DDR fsp_params[1].freq_mhz= 528MHz INFO: dfs DDR fsp_params[2].freq_mhz= 1068MHz INFO: dfs DDR fsp_params[3].freq_mhz= 1560MHz INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 1 INFO: BL31: Initializing runtime services INFO: BL31: Initializing BL32 I/TC: I/TC: OP-TEE version: 3.13.0-791-g185dc3c92 #hisping.lin (gcc version 10.2.1 20201103 (GNU Toolchain for the A-profile Architecture 10.2-2020.11 (arm-10.16))) #2 Tue Apr 16 11:05:25 CST 2024 aarch64, fwver: v1.01 I/TC: OP-TEE memory: TEEOS 0x200000 TA 0xc00000 SHM 0x200000 I/TC: Primary CPU initializing I/TC: Primary CPU switching to normal world boot INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x40200000 INFO: SPSR = 0x3c9 U-Boot 2017.09-armbian-2017.09-S57b8-P9d8d-H8c72-V8051-Bda0a-R448a (Sep 13 2024 - 04:56:59 +0000) Model: Rockchip RK3576 Evaluation board MPIDR: 0x0 PreSerial: 0, raw, 0x2ad40000 DRAM: 4 GiB Sysmem: init Relocation Offset: bda21000 Relocation fdt: fb9f9a70 - fb9fecf0 CR: M/C/I Using default environment DM: v2 mmc@2a310000: 1, mmc@2a330000: 0 Bootdev(atags): mmc 0 MMC0: HS400 Enhanced Strobe, 200Mhz PartType: EFI No misc partition boot mode: None FIT: No boot partition Failed to load DTB, ret=-19 No valid DTB, ret=-22 Failed to get kernel dtb, ret=-22 Model: Rockchip RK3576 Evaluation board download key pressed... entering download mode... RKUSB: LUN 0, dev 0, hwpart 0, sector 0x0, count 0x3a3e000 \usb device is high-speed \usb device is high-speed

Hello. Thanks for your work, fine result. i've tested desktop image and.. 1) For begginers, before executing the command "rkdeveloptool db...", make sure that the board is in operation mode => maskrom rkdeveloptool list rkdeveloptool rd 3 #and after that h96 ready to: rkdeveloptool db RK3576_MiniLoaderAll.bin rkdeveloptool wl 0x0 Armbian-unofficial_24.8.0-trunk_H96-m9_noble_vendor_6.1.75_gnome_desktop.img ========================== 2) Disable hibernate, i catched it on SSH session (pic 1) helped me gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type nothing 3) HDMI i use virtual monitor for stable work, without real monitor #in terminal sudo nano /usr/share/X11/xorg.conf.d/10-quirks.conf add it on end of file and save. Switch off hdmi from h96 and restart. Section "Monitor" Identifier "Monitor0" HorizSync 28.0-80.0 VertRefresh 48.0-75.0 # https://arachnoid.com/modelines/ # 1920x1080 @ 60.00 Hz (GTF) hsync: 67.08 kHz; pclk: 172.80 MHz Modeline "1920x1080_60.00" 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -HSync +Vsync EndSection Section "Device" Identifier "Card0" Driver "dummy" VideoRam 256000 EndSection Section "Screen" DefaultDepth 24 Identifier "Screen0" Device "Card0" Monitor "Monitor0" SubSection "Display" Depth 24 Modes "1920x1080_60.00" EndSubSection EndSection On other PCs, only the virtual display works. In this case, both can work. It doesn't have to be that way, but it's useful in this case. ====================================== One question. I soldered sd slot on h96, but cant see disk on terminal, lsblk shows just mmcblk2. is it poorly soldered or do I need to do something else?