Tiago Sampaio

Members
  • Content count

    4
  • Joined

  • Last visited

  1. I figured out the device is: Hynix+H27UBG8T2CTB I cant find any driver to this device, but I have a running version of OpenWRT running. Is it possible to get the driver (?!?!?) from the OpenWRT source to the Armbian source?
  2. After Fixing some minor errors, I can boot now. But I can't find the root device: Loading, please wait... Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. done. Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/disk/by-uuid/97a9b7ff-f44a-4313-911d-80497c83b965 does not exist. Dropping to a shell! Rebooting automatically due to panic= boot argument My question is: Do you have any Idea what driver is missing? I'm trying enabling all block and sd devices in kernel, but no luck at all..
  3. Building the "Desktop" image, I got: HELLO! BOOT0 is starting! boot0 version : 3.0.0 reg_addr 0x01f00100 =0x00007347 reg_addr 0x01f00104 =0x0000703b reg_addr 0x01f00108 =0x5aa5a55a reg_addr 0x01f0010c =0x000000ff reg_addr 0x01f00110 =0x000000ff reg_addr 0x01f00114 =0x000000ff eraly jump fel U-Boot SPL 2017.03-armbian (Apr 25 2017 - 15:56:39) DRAM: 1024 MiB Trying to boot from MMC1 U-Boot 2017.03-armbian (Apr 25 2017 - 15:56:39 -0300) Allwinner Technology CPU: Allwinner A31? (SUN6I, id: 7) Model: Merrii A31 Hummingbird DRAM: 1 GiB MMC: SUNXI SD/MMC: 0 *** Warning - bad CRC, using default environment Setting up a 1024x768 vga console (overscan 0x0) Error: no valid bmp image at 66000000 In: serial Out: vga Err: vga Net: eth0: ethernet@01c30000 Hit any key to stop autoboot: 0 38518 bytes read in 147 ms (255.9 KiB/s) switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3550 bytes read in 204 ms (16.6 KiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 128 bytes read in 175 ms (0 Bytes/s) 4256917 bytes read in 484 ms (8.4 MiB/s) 6189880 bytes read in 593 ms (10 MiB/s) Found mainline kernel configuration 40041 bytes read in 580 ms (67.4 KiB/s) ** File not found /boot/dtb/overlay/-fixup.scr ** ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 4256853 Bytes = 4.1 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 Loading Ramdisk to 49bf0000, end 49fff455 ... OK reserving fdt memory region: addr=43000000 size=a000 Loading Device Tree to 49be3000, end 49beffff ... OK Starting kernel ... Uncompressing Linux... done, booting the kernel. And it Stucks at that point.
  4. Hello. I just got the board to play with, but I can't find any specific documentation on how to build a specific image to such board. After researching on google, foruns, etc. I've found some *mentions* on using the bananapim2 config and build (since they use the same core), but it's not working. Building an image using bananapim2 profile, after power on the device start booting from SD, but shows me: unknow image format and start asking for TFP to find flash. Can you please point me toward some useful information on how to build an Armbian image on such card? Thank you in advance