Bootable image for Macchatobin Double Shot?

[Mark Millard]

On 2020-Apr-25, at 09:12, greg at unrelenting.technology wrote:

> April 25, 2020 6:46 PM, "Mark Murray" <markm at freebsd.org> wrote:
> 
>>> On 25 Apr 2020, at 16:22, greg at unrelenting.technology wrote:
>>> 
>>> April 25, 2020 5:51 PM, "Mark Murray" <markm at freebsd.org> wrote:
>>> 
>>> https://unrelentingtech.s3.dualstack.eu-west-1.amazonaws.com/flash-image.bin
>>> https://unrelentingtech.s3.dualstack.eu-west-1.amazonaws.com/flash-image2.bin
>>>> The second has the same binary bits as the one I downloaded from the link in my original post.
>>> 
>>> It should work then..
>>> 
>>> Unless I really screwed something up and *somehow* this is not a good image -
>>> you can check by running (as root):
>>> 
>>> /usr/sbin/acpidump -t -d -o /dev/null | grep -a -C10 PNP0C02
>> 
>> # /usr/sbin/acpidump -t -d -o /dev/null | grep -a -C10 PNP0C02
>> acpidump: FACS is corrupt
>> 
>>> that should find the PCIe controller in the DSDT table, its Memory32Fixed resource should
>>> contain the address 0xE0000000, NOT 0xE0008000.
>> 
>> Not quite there yet :-)
>> 
>>> What does the pci command in the EFI Shell say? Run `pci 00 00 00 -i` to get info about a
>>> particular device,
>>> e.g. https://gist.github.com/myfreeweb/8b09f1c93ee9572aef01513ba9bf756f
>> 
>> Shell> pci
>> Seg Bus Dev Func
>> --- --- --- ----
>> 00 00 00 00 ==> Network Controller - Ethernet controller
>> Vendor 8086 Device 1521 Prog Interface 0
>> 00 00 00 01 ==> Network Controller - Ethernet controller
>> Vendor 8086 Device 1521 Prog Interface 0
>> ASSERT [PciHostBridgeDxe]
>> /home/mw/git/uefi-27/edk2-platforms/Silicon/Marvell/Armada7k8k/Library/Armada7k8kPciExpressLib/PciEx
>> ressLib.c(78): Address < (0x0 + 1) * 0x00100000
>> 
>> Looks like something went badly wrong there :-(
> 
> Woah, "/home/mw/git/uefi-27" doesn't look like something that should appear in one of my builds..!
> 
> I guess flash-image2 is a reupload of an old build from the github wiki, and flash-image was my build,
> but I might have overwritten it with a bad one. *facepalm*

Back in 2019-Dec my success was based on getting and using:

https://unrelentingtech.s3.dualstack.eu-west-1.amazonaws.com/flash-image2.bin

as it was at the time. flash-image.bin did not work back then.
(I've not checked if there have since been replacements of the
file.)

I still have a copy of the flash-image2.bin file sitting on
the macOS machine where I downloaded it and:

% strings /Users/markmi/Downloads/flash-image2.bin | grep uefi-27
/home/mw/git/uefi-27/MdePkg/Library/BaseLib/String.c
/home/mw/git/uefi-27/MdePkg/Library/BasePrintLib/PrintLibInternal.c
. . .
/home/mw/git/uefi-27/Build/Armada80x0McBin-AARCH64/RELEASE_GCC5/AARCH64/MdeModulePkg/Core/DxeIplPeim/DxeIpl/DEBUG/AutoGen.c
/home/mw/git/uefi-27/Build/Armada80x0McBin-AARCH64/RELEASE_GCC5/AARCH64/MdeModulePkg/Core/DxeIplPeim/DxeIpl/DEBUG/DxeIpl.dll

So it appears that, no matter if the 2019-Dec flash-image2.bin
was your build or not, it worked on the DoubleShot (and is
still working on the DoubleShot).

For identification:

% openssl dgst -sha512 /Users/markmi/Downloads/flash-image2.bin
SHA512(/Users/markmi/Downloads/flash-image2.bin)= 48c6a9bbd0d5bac7ae107bb5fc3a2413c46bde8d3ec63af6b38ad08189a8917d784fb08eb284b907eb18df1116a2caa7c15d26bfab71a42e62c1b5f2d829fcd4

===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)