编译au1200的autoboot
来源:互联网 发布:淘宝运营找工作技巧 编辑:程序博客网 时间:2024/05/17 22:38
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
- 编译au1200的autoboot
- AU1200 GPIO的使用
- 基于Au1200的多媒体播放终端设计 PXA270 AU1200
- EFI Autoboot 设定变更的方法
- AU1200 BSP的变量未声明错误
- Au1200 CoreBSP v1.51默认工程编译记录
- [H/W] EFI Autoboot 设定变更的方法
- 美菱项目(AU1200):NorFlash相关的设定
- AU1200 SoC 及 NorFlash 物理地址与虚拟地址的映射机制
- ARM1136JF、ARM1176JZF、MIPS32-Au1200三款CPU的浮点运算测试
- au1200 kdrive cross compile
- AU1200 ISR (HAL Interrupt Install)
- 用AU1200设计便携式媒体播放器
- au1200 linux mae driver 冲突
- 提供S32440/AU1200 Sd 卡驱动源码
- Intel PXA270与AMD Au1200比较分析
- 让uboot按下指定键停止autoboot
- 让uboot按下指定键停止autoboot
- svn在linux下的使用(svn命令)
- 使用OTA来发布J2ME程序
- 优优智能客户关系管理系统UUCRM5.0
- c#中struct和class的区别
- HermesJMS 连接 ActiveMQ
- 编译au1200的autoboot
- bfin-xxx-gcc-4.3.1中config.status的生成及运行(6):子目录获取
- 数据结构小结
- ERP和SAP的详细名词解释~~
- 3D基础:3D坐标变换在OpenGL 中的实践
- 向量第一篇
- GridView 和DataGrid区别
- 内训资料公开:设计师的实战过程(3)
- 利用键盘画线