Re: Problems about installing Debian on Arm64

[YOYO]

Thank you for your instructions.
But I still have some questions to ask.
1. Are following two urls right?
    Tutorial:
    https://lists.centos.org/pipermail/arm-dev/      
      \
    2016-March/001743.html
    Required UEFI image:
    https://dl.dropboxusercontent.com/u/20403943/    \
    mp30ar0_tianocore_binaries.tar.xz


2. Is the UEFI image burnt into the on-borad SPI flash(or perhaps EEPROM) 
    or I need to re-load it every time I startup the machine.


3. If the image is burnt into the on-board storage, 
    then what should I do if I want to return to u-Boot mode?


4. Is there any way to rescue the motherboard if something unexpected 
happens 
    during flashing and the board is not bootable? Do I need a BIOS 
programmer 
    to rescue? If so, which chip is the BIOS program on?



Thank you again for your patient guidance and generous help.


Best Regards,
Richard



BTW: the UEFI image urs seems not working and I can't get access to it. 
    Would you please help me test if it's still working so that I 
could know 
    whether my network is to be blamed. 

------------------ Origin ------------------
From:                                                                           
                                             "Michael Howard"                   
                                                                 
<m...@dewberryfields.co.uk&gt;;
Date:&nbsp;2024-09-19(Thu) 1:57am
To:&nbsp;"debian-arm"<debian-arm@lists.debian.org&gt;;

Subject:&nbsp;Re: Problems about installing Debian on Arm64



On 18/09/2024 18:29, Steve McIntyre wrote:
&gt; On Wed, Sep 18, 2024 at 05:30:35PM +0100, Michael Howard wrote:
&gt;&gt; On 18/09/2024 16:38, YOYO wrote:
&gt;&gt;
&gt;&gt; &nbsp; &nbsp; It seems it a ideal idea to switch from u-Boot to UEFI 
on AR0.
&gt;&gt; &nbsp; &nbsp; Would you please share about how you install UEFI and 
how to revert to
&gt;&gt; &nbsp; &nbsp; u-Boot when needed? I've found some tutorials, but the 
urls of the UEFI
&gt;&gt; &nbsp; &nbsp; firmware seemed to be invalid.
&gt;&gt;
&gt;&gt; I can't be of much help I'm afraid as it was a long time ago and I 
just used
&gt;&gt; the information and files available on the net at the time. I'm not at 
home at
&gt;&gt; the moment but when I am I will see if I still have the relevant 
files, if
&gt;&gt; nobody else chirps up before then. It will be a long shot though.
&gt; I've got the files needed for switching the APM Mustang here at
&gt;
&gt;&nbsp; &nbsp; https://www.einval.com/mustang/easy-uefi/
&gt;
&gt; The instructions are for APM's own Mustang dev board - the Gigabyte
&gt; AR0 might be compatible here or it might be different, be careful!
&gt;
So, the uefi image needed at the time was 'mp30ar0_tianocore_media.img' 
which was provided by Phong Vo,&nbsp; in the archive 
mp30ar0_tianocore_binaries.tar.xz. I do still have the file.

The basic process was;

a) Place mp30ar0_tianocore_media.img on a TFTP server as 
`mp30ar0/mp30ar0_tianocore_media.img'.
b) Within u-boot run thr following;

&nbsp;&nbsp; setenv ipaddr xx.xx.xx.xx&nbsp; &nbsp; # server's own IP address
&nbsp;&nbsp; setenv serverip yy.yy.yy.yy&nbsp; # IP address of TFTP server
&nbsp;&nbsp; setenv media_img mp30ar0_tianocore_media.img
&nbsp;&nbsp; run 
spi_load&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 &nbsp; &nbsp; # check this command succeeds
&nbsp;&nbsp; run spi_update
&nbsp;&nbsp; reset

I think that the above instructions rely upon 'user_dir' being set to 
'mp30ar0'.

Obviously, as Steve says, be careful.

-- 
Michael Howard.