Jump to content

HR Wang

Validating
  • Posts

    1
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I have a development board, model eaidk-310, with soc rk3228h (which is said to be the same as rk3328). The official website of the board has been closed, so I cannot obtain more related information. However, I found the official firmware and can use rockchip's official tool for burning. The file structure is as follows. 190798 Jun 8 2020 MiniLoaderAll.bin 33554432 Jun 8 2020 boot_linux.img 374 Jun 8 2020 parameter-linux.txt 6815744000 Jun 8 2020 rootfs.img 4194304 Jun 8 2020 trust.img 4194304 Jun 8 2020 uboot.img parameter-linux.txt is: FIRMWARE_VER:8.1 MACHINE_MODEL:RK3328 MACHINE_ID:007 MANUFACTURER:Rockchip MAGIC: 0x5041524B ATAG: 0x00200800 MACHINE: 3328 CHECK_MASK: 0x80 PWR_HLD: 0,0,A,0,1 TYPE: GPT CMDLINE:mtdparts=rk29xxnand:0x00002000@0x00002000(uboot),0x00002000@0x00004000(trust),0x00010000@0x00006000(boot_linux:bootable),-@0x00016000(rootfs:grow) uuid:rootfs=614e0000-0000-4b53-8000-1d28000054a9 I tried to install armbian's image based on rk3328, which is officially supported. Some of them can boot up but neither network nor Bluetooth works properly. Therefore, I want to compile my own version to support these peripherals. My question is whether I can use the pre-compiled .img files in these official images to compile my own armbian? If possible, how should I configure ./compile.sh? Thank you all. Translated from:
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines