From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-wm1-f67.google.com (mail-wm1-f67.google.com [209.85.128.67]) by mx.groups.io with SMTP id smtpd.web12.2122.1589928892806085777 for ; Tue, 19 May 2020 15:54:53 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@akeo-ie.20150623.gappssmtp.com header.s=20150623 header.b=Ikl5T6lC; spf=none, err=permanent DNS error (domain: akeo.ie, ip: 209.85.128.67, mailfrom: pete@akeo.ie) Received: by mail-wm1-f67.google.com with SMTP id z72so959594wmc.2 for ; Tue, 19 May 2020 15:54:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akeo-ie.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=q+P6ODcYLvZsWaFDz1NUMz0k4EIW9WENih9Q4ZQ9Q+c=; b=Ikl5T6lCFurqWShH9oTXDvUSUwTBXSKw5cQQdzCnDNfstF9QSS6ghdC/53AjDfQVEF S7gmzXiHv74aGjTn4Dj0835FiDkiScMKX6Z9p6ajfEFNxH9h6Aqn7z0gGAu2aoipU8v3 zHZ0C/bPsy584R3sqWYNUn1edkDfhIXkAQVUQr0Nqg98/VRcJohbENBO4ahL03sc0vAa VpHMdGAEkSUBUiI6kufuNR2DJK6dTkdpisQNGG/c/YR/EhX30ftMkWjji3A/LDC+7mHw P0kXYFv4QpGLwD/7ch0ZQySjQ46w2ybNuRgXvn6P39uEayZIHPY7quYnV8j2QEiEOndx 8t0A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=q+P6ODcYLvZsWaFDz1NUMz0k4EIW9WENih9Q4ZQ9Q+c=; b=TTei13BvAmi/n821OrhYz8TgOf7d2R+7ax52gIlyuzmV0u4SzeMT1PtRRlNLXecNUm 6TkBOc7oYhw+/zB1Uqb0jxegNBqZtWI4+QxWbivuqvsbyRDpaJKrG8rHN/8QCwOJwClF WYyNzvo6Cb9Z8aMhPIVdwX5czDPtuIGVoLOHqS6kbPE7kovBjO8O18yqRAy2q//gVbZ+ LvgLLWS0WZtivIPL3zkeFxaOySCvdi7cruOXBio39iDVcFhVqmXv9uUhd7rIQwsoY1wZ 0p0lhohbe5qxtUwlfoB+bORlF+Aqe3vtIcBEVCKBdd5IvEoM9HUUdyXmFkUO97MLS87B 4xfQ== X-Gm-Message-State: AOAM5314Y2AkIYKvYhOK6jz8MtG38bhxQBl+XJUq02aK2lkl5eYA9Y6T wXzplbP8vLDRxlHittGaA4PBoA== X-Google-Smtp-Source: ABdhPJxI3Oi3YkxMJXz6adE2jcE6dGuQVeETBIRS0HOusJjRgTdxn8EElFYL1J5YqNdf4WzOeUa3eA== X-Received: by 2002:a7b:c385:: with SMTP id s5mr1690662wmj.189.1589928891213; Tue, 19 May 2020 15:54:51 -0700 (PDT) Return-Path: Received: from [10.0.0.122] ([84.203.59.63]) by smtp.googlemail.com with ESMTPSA id h137sm6446299wme.0.2020.05.19.15.54.49 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 19 May 2020 15:54:50 -0700 (PDT) Subject: Re: [edk2-devel] [HELP] EDK2 on Raspberry Pi 3 B+ To: devel@edk2.groups.io, raingloom@riseup.net References: <20200519235448.1f0fd537@riseup.net> From: "Pete Batard" Message-ID: Date: Tue, 19 May 2020 23:54:49 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0 MIME-Version: 1.0 In-Reply-To: <20200519235448.1f0fd537@riseup.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit Hi, You may be interested with the pre-built Raspberry Pi 3 UEFI images from: https://github.com/pftf/RPi3 At the very least it should tell you if your serial setup works or not, as, if properly configured (115200 bauds), you should get some serial output regardless of whether you are using RELEASE or DEBUG. I would first try to use these pre-built images (make sure to replace all the files, including config.txt and start.elf as it may matter) and check that everything works as expected, before using a custom build. Now to answer some of your points: On 2020.05.19 22:54, raingloom wrote: > Hi! > > I'm trying to get EDK2 working on a Raspberry Pi 3 B+ and am running > into some issues. > > Setup: > First, I created a Guix package for EDK2, to make it nice and > reproducible. It can be found on > https://git.sr.ht/~raingloom/guix-packages in bootloaders.scm. You can see how we build the firmware using AppVeyor/Ubuntu here: https://ci.appveyor.com/project/pbatard/RPi3?fullLog=true > It took a few tries to compile it, after which I copied RPI_EFI.fd to > the USB flash drive / microSD card (tried both), alongside the > necessary blobs and configs, and the miniuart overlay, and finally the > contents of the latest ARM64 Debian netinst image. > > > Problem: > USB boot straight up doesn't work. Known issues: https://github.com/pftf/RPi3/issues/13 & https://github.com/pftf/RPi3/issues/14 We'll be working on enabling boot without SD, but there's no telling when that will happen. > microSD does get me into GRUB, but none of my USB keyboards work, so > it's just stuck there. I can't get into the EFI settings either, > obviously. This used to be an issue when using the latest Raspberry Pi Foundation start.elf before we applied the commits referenced in version 1.24: https://github.com/pftf/RPi3/releases/tag/v1.24 Are you sure your edk2-platforms repository is up to date? > I tried debugging it over UART, so I bought my first ever USB UART > adapter (from a verified RPi reseller in Hungary, who advertised it as > compatible), wired it up according to the docs, launched screen with > the right baud rate, and... nothing. As I mentioned, you should always get some output, regardless of how you build the firmware, as the TF-A blob, will produce some. So if you're not seeing anything, you need to check your serial connection. Regards, /Pete