3.1 Building AutoBoot
First, obtain the AutoBoot source code package from the AMD Embedded Developer Support site (Alchemy Product page).
Extract the contents of this archive into your working directory (these examples use the user’s home directory as the working
directory):
% cd ~
% tar –xzf au1xxx-booter-src-1.0-r000007.tar.gz
Edit the file, “make.rules”, in the newly created directory to correspond to the host PC’s cross-compiler. The make.rules file
contains several TOOLCHAIN entries that provide example configurations for several common Alchemy build environments.
Choose and edit the entry that corresponds most closely to the host PC’s build environment, or create a new custom
entry. For example, to configure Booter to work with the MontaVista Linux® Pro compiler, uncomment the following line
in the make.rules file:
TOOLCHAIN = mvlp
All other lines that begin with “TOOLCHAIN =” must be commented out. Ensure all the paths and arguments in the selected
TOOLCHAIN entry match the host PC’s build environment before continuing.
Once the make.rules file has been modified, configure AutoBoot using the provided configuration scripts. These scripts are
invoked by issuing the command “make menuconfig.” The desired platform must be chosen, as well as the type of Auto-
Boot application to be built (stand-alone or YAMON-invoked). Additionally, AutoBoot may be configured to boot only signed
images.
After running the configuration scripts, build AutoBoot by issuing the “make” command.
The following example configures and builds a YAMON-invoked AutoBoot application for the RMI Alchemy™ DBAu1200™
development board that boots unsigned images:
% cd ~/Booter_Common_Au1xxx_00.00.07
% make menuconfig
Platform --->
(DB1200) Platform
Applications --->
Au1xxx AutoBoot (Select one) --->
[*] AutoBoot (YAMON assist)
% make
After the build process completes successfully, the AutoBoot S-Record is placed in a directory according to the target platform.
The example above generates the following S-Record:
~/Booter_Common_Au1xxx_00.00.07/applications/booter/obj/DB1200/EL/booter/DB1200_booter.rec
Builds for stand-alone AutoBoot applications append “_standalone” to the filename, while builds creating AutoBoot applications
for signed images append “_sb” to the filename.
实际上,我采用cygwin的编译环境时,执行上面的命令并不能成功,而是执行如下命令:
make oldconfig
make
First, obtain the AutoBoot source code package from the AMD Embedded Developer Support site (Alchemy Product page).
Extract the contents of this archive into your working directory (these examples use the user’s home directory as the working
directory):
% cd ~
% tar –xzf au1xxx-booter-src-1.0-r000007.tar.gz
Edit the file, “make.rules”, in the newly created directory to correspond to the host PC’s cross-compiler. The make.rules file
contains several TOOLCHAIN entries that provide example configurations for several common Alchemy build environments.
Choose and edit the entry that corresponds most closely to the host PC’s build environment, or create a new custom
entry. For example, to configure Booter to work with the MontaVista Linux® Pro compiler, uncomment the following line
in the make.rules file:
TOOLCHAIN = mvlp
All other lines that begin with “TOOLCHAIN =” must be commented out. Ensure all the paths and arguments in the selected
TOOLCHAIN entry match the host PC’s build environment before continuing.
Once the make.rules file has been modified, configure AutoBoot using the provided configuration scripts. These scripts are
invoked by issuing the command “make menuconfig.” The desired platform must be chosen, as well as the type of Auto-
Boot application to be built (stand-alone or YAMON-invoked). Additionally, AutoBoot may be configured to boot only signed
images.
After running the configuration scripts, build AutoBoot by issuing the “make” command.
The following example configures and builds a YAMON-invoked AutoBoot application for the RMI Alchemy™ DBAu1200™
development board that boots unsigned images:
% cd ~/Booter_Common_Au1xxx_00.00.07
% make menuconfig
Platform --->
(DB1200) Platform
Applications --->
Au1xxx AutoBoot (Select one) --->
[*] AutoBoot (YAMON assist)
% make
After the build process completes successfully, the AutoBoot S-Record is placed in a directory according to the target platform.
The example above generates the following S-Record:
~/Booter_Common_Au1xxx_00.00.07/applications/booter/obj/DB1200/EL/booter/DB1200_booter.rec
Builds for stand-alone AutoBoot applications append “_standalone” to the filename, while builds creating AutoBoot applications
for signed images append “_sb” to the filename.
实际上,我采用cygwin的编译环境时,执行上面的命令并不能成功,而是执行如下命令:
make oldconfig
make