Closed stefan2225 closed 5 years ago
The current prebuilts already have the 3B+ compatible bootcode/start/fixup. Did that not work for you?
Thanks for the Fedora report.
A
On Jun 23, 2018, at 6:33 AM, stefan2225 notifications@github.com wrote:
The UEFI is fully compatible with the RPi 3B+ and I managed to install Fedora 28 Minimal with a custom DTB on an external USB Stick. I just needed to download the latest bootcode.bin, start.elf, fixup.dat. Additionally I needed to add the files fixup_cd.dat, fixup_db.dat, fixup_x.dat and start_cd.elf, start_db.elf, start_x.elf to get the RPi booting.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
I just get the green LED blinking 4-5 on the RPi if I just use the already provided bootcode/start/fixup without the cd/db/x files. I also got no HDMI output, not even an rainbow screen. BTW I'm using the latest release build.
interesting, ok I’ll refresh those bits...
Can you provide the md5 sums for the known good VC firmware files (boot code, fixup and the rest)
A
On Jun 23, 2018, at 3:02 PM, stefan2225 notifications@github.com wrote:
I just get the green LED blinking 4-5 on the RPi if I just use the already provided bootcode/start/fixup without the cd/db/x files. I also got no HDMI output, not even an rainbow screen. BTW I'm using the latest release build.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
Here they are: (pretty much latest VC firmware files right now)
bootcode.bin: 410DE1021E20F1051A5518BC9E863AE9 fixup.dat: 7F160E8B2A7B7D664D9F7930F1D3350B fixup_cd.dat: DC619911230B4D131E67CA36C6A74415 fixup_db.dat: A9FEDCE9810A06935A3CEA0ABECA165A fixup_x.dat: DCF3058140F6C877E2B4CE2C067CA34D start.elf: F17A9D31ADD2B653FACE3DBD25A96D58 start_cd.elf: 2E281DD504E9C34C05539437E3DEBAB7 start_db.elf: 18EC0E15014EA9A9D631FA83C434C1AA start_x.elf: DBDB64DF645DF33334416626844A8EB2
Is it normal that Fedora detects when I remove the SD Card and when i reinsert it? I thought I have seen in a issue that that doesn't work.
Maybe that issue is talking about detecting card removal in UEFI?
yes, I was talking about UEFI
A
On Jun 24, 2018, at 10:01 AM, thchi12 notifications@github.com wrote:
Maybe that issue is talking about detecting card removal in UEFI?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
@stefan2225 Which dtb did you use for the rpi 3b+?
@satmandu I extracted the DTB from a Fedora 28 image with U-Boot.
There is a config.txt option that switches between the normal, cd, db or x versions. If you set that to the x version, it won't even look for the normal one.
Yeah don't do that.
On Thu, Jul 5, 2018 at 10:13 AM Googulator notifications@github.com wrote:
There is a config.txt option that switches between the normal, cd, db or x versions. If you set that to the x version, it won't even look for the normal one.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/andreiw/RaspberryPiPkg/issues/41#issuecomment-402735847, or mute the thread https://github.com/notifications/unsubscribe-auth/AAsta17dIvEsWMHbJXYV38gKFfOim967ks5uDh7-gaJpZM4U0vQK .
-- A
I found by my Pi3B+. I don't confirm the boot issue. If you copy a build directory verbatim it works just fine. You shouldn't need the cd, db or x versions of anything (because the config file doesn't refer to them).
The UEFI is fully compatible with the RPi 3B+ and I managed to install Fedora 28 Minimal with a custom DTB on an external USB Stick. I just needed to download the latest bootcode.bin, start.elf, fixup.dat. Additionally I needed to add the files fixup_cd.dat, fixup_db.dat, fixup_x.dat and start_cd.elf, start_db.elf, start_x.elf to get the RPi booting. Why are the _cd, _db and _x files needed?