/work/git/tianocore# script -c “edk2-platforms/Platform/Ampere/buildfw.sh -m ASRockRack -p Altra1L2T -b RELEASE” buildoutput.txt
Script started, output log file is ‘buildoutput.txt’.
/work/git/tianocore /work/git/tianocore
‘edk2-platforms/Platform/ASRockRack/Altra1L2TPkg/Altra1L2TBoardSetting.cfg’ → ‘/work/git/tianocore/Build/Altra1L2T/Altra1L2TBoardSetting.cfg.txt’
python3: can’t open file ‘/work/git/tianocore/edk2-ampere-tools/nvparam.py’: [Errno 2] No such file or directory
Script done.
Oh! Sorry the documentation probably doesn’t mention this. You need to clone GitHub - AmpereComputing/edk2-ampere-tools: Ampere's unofficial tools for EDK2 development .
1 Like
Thanks!
Wrote a script to simplify it:
#!/bin/bash
if [ ! -f $1 ]; then
print "No edk2 build file"
exit
fi
NEW_FW_NAME="Build/Altra1L2T/bios.bin"
cp ampere/ALTRAD8UD-1L2T_3.06.ROM ${NEW_FW_NAME}
cp ampere/MANIFEST Build/Altra1L2T/
dd if=$1 of=${NEW_FW_NAME} bs=1MB seek=6 conv=notrunc
cd Build/Altra1L2T/
tar cf fw-`basename $1`.tar bios.bin MANIFEST
Uses manifest file from 3.06 BIOS archive.
1 Like
Have to check what I did wrong as boot process ended at memory initialization.
Flashed 3.06 back.
I built EDK2 with Networking and TPM2 disabled. Also would recommend you try flashing with the ampere_flash_bios.sh script on the BMC, with the main CPU powered off, if you haven’t already. Finally, building a DEBUG version instead of RELEASE will also give you much more serial console logging if necessary to track down boot failures.