Home Forum Software discussion Successfully flashed UEFI EDK II – now what? Help!

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #475
    slimsamu
    Participant

    I’ve taken the plunge and flashed the UEFI EDK II onto my Armada board.

    I built the image as per the procedure here: http://wiki.macchiatobin.net/tiki-index.php?page=Build+from+source+-+UEFI+EDK+II
    And installed (flashed) as per here: http://wiki.macchiatobin.net/tiki-index.php?page=Update+the+Bootloader

    The good news is that I did not brick the board. I now have a UEFI shell that comes up.

    BootROM – 2.03
    Starting CP-1 IOROM 1.07
    Booting from SPI NOR flash 1 (0x32)
    Found valid image at boot postion 0x000
    lNOTICE: Starting binary extension
    mv_ddr: mv_ddr-devel-17.08.0-g7ffc0a5 (Sep 27 2017 – 20:43:31)
    ………………………
    mv_ddr: completed successfully
    NOTICE: Cold boot
    NOTICE: Booting Trusted Firmware
    NOTICE: BL1: v1.3(release):devel-17.08.1:627667b
    NOTICE: BL1: Built : 20:43:34, Sep 27 2017
    NOTICE: BL1: Booting BL2
    lNOTICE: BL2: v1.3(release):devel-17.08.1:627667b
    NOTICE: BL2: Built : 20:43:36, Sep 27 2017
    NOTICE: BL1: Booting BL31
    lNOTICE: BL31: v1.3(release):devel-17.08.1:627667b
    NOTICE: BL31: Built : 20:43:41, Sep 27 2017
    lUEFI firmware (version MARVELL_EFI built at 20:31:38 on Sep 27 2017)

    Armada 8040 MachiatoBin Platform Init

    Comphy0-0: PCIE0 5 Gbps
    Comphy0-1: PCIE0 5 Gbps
    Comphy0-2: PCIE0 5 Gbps
    Comphy0-3: PCIE0 5 Gbps
    Comphy0-4: SFI 10.31 Gbps
    Comphy0-5: SATA1 5 Gbps

    Comphy1-0: SGMII1 1.25 Gbps
    Comphy1-1: SATA2 5 Gbps
    Comphy1-2: USB3_HOST0 5 Gbps
    Comphy1-3: SATA3 5 Gbps
    Comphy1-4: SFI 10.31 Gbps
    Comphy1-5: SGMII2 3.125 Gbps

    UTMI PHY 0 initialized to USB Host0
    UTMI PHY 1 initialized to USB Host1
    UTMI PHY 0 initialized to USB Host0
    RTC: Initialize controller 1
    Skip I2c chip 0
    Succesfully installed protocol interfaces
    ramdisk:blckio install. Status=Success

    That’s the good news. The bad news is that I can’t get neither Fedora 26 or Debian 9 network installers to work. But I’ll write more about that later.

    I did have Ubuntu 16 installed on the MMC in the system – but I can’t seem to be able to boot that. I’m stuck and have managed to put my machine into a state where I can’t boot it anymore. Any tips would be greatly appreciated as I’m not fluent in UEFI, etc.

    Best,

    Gabor

    #476
    slimsamu
    Participant

    the Fedora 26 install (from an SD card) boot up and hangs at the following:

    EFI stub: Booting Linux Kernel…
    EFI stub: Using DTB from configuration table
    EFI stub: Exiting boot services and installing virtual address map…
    [ 0.000000] Booting Linux on physical CPU 0x0
    [ 0.000000] Linux version 4.11.8-300.fc26.aarch64 (mockbuild@buildvm-aarch647
    [ 0.000000] Boot CPU: AArch64 Processor [410fd081]
    [ 0.000000] efi: Getting EFI parameters from FDT:
    [ 0.000000] efi: EFI v2.60 by EDK II
    [ 0.000000] efi: SMBIOS 3.0=0xbfda0000 ACPI 2.0=0xb6760000 MEMATTR=0xb8e9
    [ 0.000000] cma: Reserved 64 MiB at 0x00000000bb000000
    [ 0.000000] NUMA: No NUMA configuration found
    ….
    [ OK ] Started udev Kernel Device Manager.
    [ 14.688453] audit: type=1130 audit(1498599887.740:12): pid=1 uid=0 auid=4294′
    Starting dracut pre-trigger hook…
    [ OK ] Started dracut pre-trigger hook.
    [ 14.878456] audit: type=1130 audit(1498599887.930:13): pid=1 uid=0 auid=4294′
    Starting udev Coldplug all Devices…
    Mounting Configuration File System…
    [ OK ] Mounted Configuration File System.
    [ 14.980245] libphy: orion_mdio_bus: probed

    #477
    slimsamu
    Participant

    As recommended by an Arm guru, I’m giving Fedora rawhide a try. Crickets chirping here eh?

    -Gabor

    #478
    blu
    Participant

    It’s been a ‘users helping users’ type of support forum ever since its inception. You apparently happen to be at the forefront of UEFI endeavors among us ; )

    #479
    slimsamu
    Participant

    So it seems that even with Fedora rawhide and CentOS 7 – which according to this post is good on Armada 8040: https://www.spinics.net/lists/centos-arm-devel/msg02518.html

    I was the smart one who went ahead and moved to UEFI but in retrospect this was a mistake as I have a system I can’t use at the moment. I won’t bore you with everything I’ve tried in the meantime, but I’ve spent way too much time on this for now. Will wait until F28 is GA – as that likely should work well.

    But if anybody here finds out how to get this all working after moving to UEFI, please let me know.

    #1530
    mjb67
    Participant

    Are you still having problems? I’ve managed to install Debian testing (while using UEFI EDK2) from a recent daily installer build.

    #7311
    hydro-b
    Participant

    Hi slimsamu / Gabor

    I also want to run EDKII on the MacchiatoBIN. I succesfully build the image (according to the logs / output). Below the process of flashing the new image:

    Marvell>> setenv ipaddr 192.168.0.195
    Marvell>> ping 192.168.0.34
    Using mvpp2-4 device
    host 192.168.0.34 is alive
    Marvell>> setenv serverip 192.168.0.34
    Marvell>> bubt flash-image.bin
    Burning U-BOOT image “flash-image.bin” from “tftp” to “mmc”
    Using mvpp2-4 device
    TFTP from server 192.168.0.34; our IP address is 192.168.0.195
    Filename ‘flash-image.bin’.
    Load address: 0x5000000
    Loading: #################################################################
    #################################################################
    ######################################################
    6 MiB/s
    done
    Bytes transferred = 2692784 (2916b0 hex)
    Image checksum…OK!
    sdhci_send_command: MMC: 1 busy timeout increasing to: 200 ms.
    sdhci_send_command: MMC: 1 busy timeout increasing to: 400 ms.
    sdhci_send_command: MMC: 1 busy timeout increasing to: 800 ms.
    sdhci_send_command: MMC: 1 busy timeout increasing to: 1600 ms.
    sdhci_send_command: MMC: 1 busy timeout increasing to: 3200 ms.
    sdhci_send_command: MMC: 1 busy timeout.
    sdhci_send_command: MMC: 1 busy timeout.
    sdhci_send_command: MMC: 1 busy timeout.
    sdhci_send_command: MMC: 1 busy timeout.
    sdhci_send_command: MMC: 1 busy timeout.
    sdhci_send_command: MMC: 1 busy timeout.
    Error – written 0x0 blocks
    exit not allowed from main input shell.
    Marvell>>

    So apparently it doesn’t have written anything …
    AFAIK the MMC: 1 is the sdcard. According to the “bubt” command it would use the device it got booted with. That should be sdcard as well. What “destination” did you select? What “boot” preference did you have configured (mmc, sata, emmc)?

    To avoid bricking the board I flashed an official u-boot image from the site (http://macchiatobin.net/wp-content/uploads/2018/07/mcbin-uboot-armada-17.10.zip):

    Burning U-BOOT image “flash-image.bin” from “tftp” to “mmc”
    Using mvpp2-4 device
    TFTP from server 192.168.0.34; our IP address is 192.168.0.195
    Filename ‘flash-image.bin’.
    Load address: 0x5000000
    Loading: #################################################################
    ################
    5.7 MiB/s
    done
    10:18 <stefan> Bytes transferred = 1186536 (121ae8 hex)
    10:18 <stefan> Image checksum…OK!
    10:18 <stefan> sdhci_send_command: MMC: 1 busy timeout.
    10:18 <stefan> Error – written 0x0 blocks
    10:18 <stefan> exit not allowed from main input shell.

    After power cycling the board I see this:

    BootROM – 2.03
    Starting CP-0 IOROM 1.07
    Booting from SD 0 (0x29)
    SD – wait_for_sd_interrupt: Error interrupt – 00008000
    SD – wait_for_sd_interrupt: Error interrupt status 00000003
    SD – sd_get_cmd_response: Get command response failed.

    SD – sd_init: Failed – ret = 00000081
    Error: Failed initializing interface
    Found valid image at boot postion 0x000
    lNOTICE: Starting binary extension
    NOTICE: SVC: SW Revision 0x0. SVC is not supported
    mv_ddr: mv_ddr-armada-18.09.2-g99d7725 (Dec 15 2018 – 19:49:49)
    mv_ddr: completed successfully
    NOTICE: Cold boot
    Error: image checksum verification failed
    Error: no valid header till end of media
    Error: Failed boot attempt 02. error = 0x041

    So it apparently loads the new mv_ddr binary … from the sdcard? Because if I insert a sdcard with Arch linux Arm on it, it will use the u-boot / mv_ddr card installed on that card (https://8n1.org/14204/175e

    So, now I’m not sure if the newly build image is actually good or not. Is it possible to first test the new firmware on sdcard before flashing it?
    Is it possible to flash a “u-boot” image once you have flashed a EDKII image on it, i.e.: does EDKII has support for flashing images?

Viewing 7 posts - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.

Technical specification tables can not be displayed on mobile. Please view on desktop