Comments

ARM64 – Dragonboard 410c – Now with U-Boot.. — 7 Comments

  1. Could you point to the version of mkbootimg you are using? None of the ones I’ve found seem to support the –dt option.

  2. I tried to boot my kernel and rootfs from USB hard drive. However, I went into trouble. Thus, I want to debug it.

    I’m not sure tty0/ttyMSM0 maps to UART0 in dragonboard. In any case, I connect USBtoSerial board to UART0. But I saw nothing.

    Could you recommend how to debug it?

  3. Thanks! I can see u-boot message from PC now

    However, I got stuck when loading kernel from USB hard drive. Both my kernel and rootfs in an external ext4 partition USB hard drive. The UUID points to that partition.

    Here is boot command:

    #define CONFIG_BOOTCOMMAND “usb start; usb storage; ext4load usb 0:1 0x90000000 /boot/uImage; ext4load usb 0:1 0x89000000 /boot/apq8016-sbc.dtb; bootm 0x90000000 – 0x89000000”
    #define CONFIG_BOOTARGS “root=UUID=ae5fa761-95be-469b-b7dc-a355d080ed23 rw rootwait console=tty0 console=ttyMSM0,115200n8 rootfs=ext4 noinitrd selinux=0”

    ———–
    Output from serial console

    DRAM: 986 MiB
    MMC: msm_sdhci: 0, msm_sdhci: 1
    Using default environment

    In: serial
    Out: serial
    Err: serial
    Net: Net Initialization Skipped
    No ethernet found.
    Hit any key to stop autoboot: 0 Escape CONFIG_ZERO_BOOTDELAY_CHECK: abort(0)

    starting USB…
    USB0: USB EHCI 1.00
    scanning bus 0 for devices… 3 USB Device(s) found
    scanning usb for storage devices… 1 Storage Device(s) found
    scanning usb for ethernet devices… 0 Ethernet Device(s) found
    Device 0: Vendor: StoreJet Rev: 0 Prod: Transcend
    Type: Hard Disk
    Capacity: 1907729.0 MB = 1863.0 GB (3907029168 x 512)
    13886016 bytes read in 927 ms (14.3 MiB/s)
    59281 bytes read in 137 ms (421.9 KiB/s)
    ## Booting kernel from Legacy Image at 90000000 …
    Image Name: Dragonboard
    Image Type: AArch64 Linux Kernel Image (uncompressed)
    Data Size: 13885952 Bytes = 13.2 MiB
    Load Address: 80080000
    Entry Point: 80080000
    Verifying Checksum … OK
    ## Flattened Device Tree blob at 89000000
    Booting using the fdt blob at 0x89000000
    Loading Kernel Image … OK

  4. I think there might be a typo in uImage creation:
    mkimage -A arm64 -O linux -C none -T kernel -a 0x80080000 -e 0x80080000 -n Dragonboard -d Image uImage
    Address and entry point according to context should be 0x90000000

    I saw more output line after fixing it:
    Image Name: Dragonboard
    Image Type: AArch64 Linux Kernel Image (uncompressed)
    Data Size: 13885952 Bytes = 13.2 MiB
    Load Address: 90000000
    Entry Point: 90000000
    Verifying Checksum … OK
    ## Flattened Device Tree blob at 89000000
    Booting using the fdt blob at 0x89000000
    Loading Kernel Image … OK
    Using Device Tree in place at 0000000089000000, end 0000000089011790

    Starting kernel …

    However, I don’t see the kernel get boot.

Leave a Reply to Rich Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.