Jump to content


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

390 profile views
  1. Can you explain what you mean by connector? or post the instructions to make the connections between serial adapter and Micro SD Card Breakout?
  2. Is there any way I could help with making it work ? it seems a dtb might be all that its needed since it is working already on other s922x devices.
  3. I know that, which is why I wanted to turn it into a headless server using Armbian, right now I have it running Emby server with Android, works really well but I would rather not use android at all
  4. Thank you for the reply, is there any particular reason?
  5. Will this work on a GT-King ? if so, which DTB is needed? I tried all the G12x DTBs and none of them seem to work. Edit: this is the UART log reading /dtb/meson-g12b-odroid-n2.dtb 43263 bytes read in 11 ms (3.8 MiB/s) [rsvmem] get fdtaddr NULL! rsvmem - reserve memory Usage: rsvmem check - check reserved memory rsvmem dump - dump reserved memory rsvmem check failed ## Loading init Ramdisk from Legacy Image at 13000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 7990726 Bytes = 7.6 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Start read misc partition datas! info->magic = info->version_major = 1 info->version_minor = 0 info->slots[0].priority = 15 info->slots[0].tries_remaining = 7 info->slots[0].successful_boot = 0 info->slots[1].priority = 14 info->slots[1].tries_remaining = 7 info->slots[1].successful_boot = 0 info->crc32 = -1075449479 active slot = 0 active_slot is normal load dtb from 0x1000000 ...... Amlogic multi-dtb tool Single dtb detected ## Flattened Device Tree blob at 01000000 Booting using the fdt blob at 0x1000000 find 1 dtbos No androidboot.dtbo_idx configured And no dtbos will be applied libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND [rsvmem] fdt get prop fail. Loading Ramdisk to 7f061000, end 7f7ffdc6 ... OK Loading Device Tree to 000000001fff2000, end 000000001ffff9b4 ... OK Starting kernel ... uboot time: 6934369 us
  • Create New...