Jump to content

qiheng

Members
  • Posts

    5
  • Joined

  • Last visited

  1. good news! so happy!My box is working Yes, there are three LEDs on the board,After power on, the middle LED will light up, After the kernel starts, the LED on the right will start to flashing I did not use USB otg to boot armbian,Use Androidtool_ Release_ v2.67 to directly burn the modified image into eMMC. This is feasible I used Armbian_ 21.02.0-trunk_ Rk322x-box_ buster_ dev_ 5.10.2_ minimal.img , only modified verbosity=7 What puzzles me is that the CPU temperature can be displayed when the system is first started, reboot the system CPU temperature is unavailable, but it doesn't affect anything So far it’s working well, It seems that Wi-Fi is also working The complete boot log is here Armbian_21.02.0_5.10.2_boot log.txt Thanks again for your help! I also hope my experience will be helpful to future friends (Use translation tools to translate,Please forgive me for causing confusion in reading)
  2. Sorry, it’s my negligence. The box is a simple personal file server with Wi-Fi and Bluetooth. The service has been stopped due to the closure of the service company, so I want to use it I can't find the entrance to upload files to the forum. The files are on Googl Drive (Use translation tools to translate,Please forgive me for causing confusion in reading) backup.img yhmh.dtb yhmh.dts Android boot log.txt Thank you very much and for causing you trouble
  3. I cannot follow the instructions, there is no SD card slot and HDMI on the board, and I cannot boot from the USB otg port after testing.
  4. Thank you for your reply Product name and model: chainedbox m1-aa-bk The image used is Armbian_ 20.11.6_ Rk322x-box_ buster_ legacy_ 4.4.194.img The burning tool is Android tool_ Release_ v2.6 yhmh.dtbyhmh.dtsbackup.img I back up and try to extract the DTB If using armbian_ 21.02.0-trunk_ Rk322x-box_ buster_ dev_ 5.10.2_ minimal.img The result is a restart in 10 seconds Device 0: unknown device switch to partitions #0, OK mmc0(part 0) is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 2909 bytes read in 4 ms (710 KiB/s) ## Executing script at 60000000 Boot script loaded from mmc 0 214 bytes read in 3 ms (69.3 KiB/s) 6038582 bytes read in 144 ms (40 MiB/s) 9821608 bytes read in 230 ms (40.7 MiB/s) 41189 bytes read in 11 ms (3.6 MiB/s) 232 bytes read in 6 ms (37.1 KiB/s) Applying kernel provided DT fixup script (rk322x-fixup.scr) ## Executing script at 600f0000 ## Loading init Ramdisk from Legacy Image at 64000000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 6038518 Bytes = 5.8 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 61f00000 Booting using the fdt blob at 0x61f00000 Loading Ramdisk to 67e3d000, end 683ff3f6 ... OK Loading Device Tree to 67dca000, end 67e3cfff ... OK Starting kernel ... I/TC: Secondary CPU 1 initializing I/TC: Secondary CPU 1 switching to normal world boot I/TC: Secondary CPU 2 initializing I/TC: Secondary CPU 2 switching to normal world boot I/TC: Secondary CPU 3 initializing I/TC: Secondary CPU 3 switching to normal world boot
  5. My English is very poor, this is translated using a translation tool; it may cause you some reading confusion, I am very sorry. I have a box, rk3228a 512m ram 8G emmc, no sd card slot, vacant mini HDMI, I used AndroidTool to burn the image to emmc, uboot can start, but it seems that the kernel cannot be started. I tried to replace all the dtbs of rk3228 and rk3229 in the image, and the result was the same. I don't know how to solve it, Finally, use rkdeveloptool to back up the original firmware from a new box and try to extract dtb. The original firmware is Android, I am not sure whether the extracted dtb is correct, I need some help DDR Version V1.10 20190926 In ID:0xFFF 600MHz DDR3 Bus Width=32 Col=10 Bank=8 Row=14 CS=1 Die Bus-Width=16 Size=512MB mach:1 OUT U-Boot SPL 2020.10-armbian (Jan 05 2021 - 03:46:43 +0100) Trying to boot from MMC2 I/TC: I/TC: Non-secure external DT found I/TC: Switching console to device: /serial@11030000 I/TC: OP-TEE version: 3.10.0-40-ga1d5c81f (gcc version 9.2.1 20191025 (GNU Toolc hain for the A-profile Architecture 9.2-2019.12 (arm-9.10))) #6 Wed Sep 16 21:36 :15 UTC 2020 arm I/TC: Primary CPU initializing M/TC: Not protecting region 1: 0x68400000-0x68600000 I/TC: Primary CPU switching to normal world boot U-Boot 2020.10-armbian (Jan 05 2021 - 03:46:43 +0100) Model: Generic Rockchip rk322x TV Box board DRAM: 480 MiB MMC: dwmmc@30000000: 1, dwmmc@30020000: 0 Loading Environment from EXT4... ** File not found /boot/boot.env ** ** Unable to read "/boot/boot.env" from mmc0:1 ** In: serial@11030000 Out: serial@11030000 Err: serial@11030000 Model: Generic Rockchip rk322x TV Box board Net: eth0: ethernet@30200000 starting USB... Bus usb@30040000: USB DWC2 scanning bus usb@30040000 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found stopping USB.. starting USB... Bus usb@30040000: USB DWC2 scanning bus usb@30040000 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 Card did not respond to voltage select! Device 0: unknown device switch to partitions #0, OK mmc0(part 0) is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 2909 bytes read in 3 ms (946.3 KiB/s) ## Executing script at 60000000 Boot script loaded from mmc 0 165 bytes read in 2 ms (80.1 KiB/s) 5694522 bytes read in 137 ms (39.6 MiB/s) 8771432 bytes read in 206 ms (40.6 MiB/s) 49812 bytes read in 6 ms (7.9 MiB/s) 232 bytes read in 5 ms (44.9 KiB/s) Applying kernel provided DT fixup script (rk322x-fixup.scr) ## Executing script at 600f0000 ## Loading init Ramdisk from Legacy Image at 64000000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 5694458 Bytes = 5.4 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 61f00000 Booting using the fdt blob at 0x61f00000 Loading Ramdisk to 67e91000, end 683ff3fa ... OK Loading Device Tree to 67e1c000, end 67e90fff ... OK Starting kernel ...
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines