1、u-boot编译脚本:mk.sh

#! /bin/sh
export PATH=$PATH:/opt/ti-sdk-am335x-evm-08.00.00.00/linux-devkit/sysroots/i686-arago-linux/usr/bin/
export ARCH=arm
export CROSS_COMPILE=arm-linux-gnueabihf- make clean
make am335x_evm_config
make

make am335x_evm_config:配置所需要的硬件平台和模块。

make:根据make am335x_evm_config得到的配置项(CONFIG_XXX)来决定编译哪些源码。

2、make am335x_evm_config 命令

在Makefile中:


MKCONFIG := $(srctree)/mkconfig

%_config:: outputmakefile # %通配符,相当于xxx_config:: outputmakefile
@$(MKCONFIG) -A $(@:_config=) # :_config=,用=符号后的’’(空字符)替换”_config”
# $@目标集,$(@:_config=) 就是am335x_evm

相当于:

am335x_evm_config:: outputmakefile
@mkconfig -A am335x_evm

3、顶层目录mkconfig:

#!/bin/sh –e     # set –e 判断每条指令的返回值(#?)是否为0,非0自动退出

# Script to create header files and links to configure
# U-Boot for a specific board.
#
# Parameters: Target Architecture CPU Board [VENDOR] [SOC]
#
# (C) 2002-2013 DENX Software Engineering, Wolfgang Denk <wd@denx.de>
#
# SPDX-License-Identifier: GPL-2.0+
# APPEND=no # Default: Create new config file
BOARD_NAME="" # Name to print in make output
TARGETS="" arch=""
cpu=""
board=""
vendor=""
soc=""
options="" if [ \( $# -eq 2 \) -a \( "$1" = "-A" \) ] ; then # 参数个数为2且第一个参数是”-A”
# Automatic mode
# 在顶层boards.cfg中找到匹配“am335x_evm”的行,存在line变量。
line=`awk '($0 !~ /^#/ && $7 ~ /^'"$2"'$/) { print $1, $2, $3, $4, $5, $6, $7, $8 }' $srctree/boards.cfg`
if [ -z "$line" ] ; then
echo "make: *** No rule to make target \`$2_config'. Stop." >&2
exit 1
fi set ${line} # 把line成员设置为参数$1, $2, $3, $4…
# add default board name if needed
[ $# = 3 ] && set ${line} ${1}
fi
# 结果:line= Active arm armv7 am33xx ti am335x am335x_evm am335x_evm:SERIAL1,CONS_INDEX=1,NAND while [ $# -gt 0 ] ; do
case "$1" in
--) shift ; break ;;
-a) shift ; APPEND=yes ;;
-n) shift ; BOARD_NAME="${7%_config}" ; shift ;;
-t) shift ; TARGETS="`echo $1 | sed 's:_: :g'` ${TARGETS}" ; shift ;;
*) break ;;
esac
done # 参数个数为7或8
[ $# -lt 7 ] && exit 1
[ $# -gt 8 ] && exit 1 # Strip all options and/or _config suffixes
CONFIG_NAME="${7%_config}" # 去掉$7的“_config” CONFIG_NAME= am335x_evm [ "${BOARD_NAME}" ] || BOARD_NAME="${7%_config}" # BOARD_NAME= am335x_evm arch="$2" # arch=arm
cpu=`echo $3 | awk 'BEGIN {FS = ":"} ; {print $1}'` # cpu= armv7
spl_cpu=`echo $3 | awk 'BEGIN {FS = ":"} ; {print $2}'` # spl_cpu= if [ "$cpu" = "-" ] ; then
cpu=
fi [ "$6" != "-" ] && board="$6" # board= am335x
[ "$5" != "-" ] && vendor="$5" # vendor=ti
[ "$4" != "-" ] && soc="$4" # soc=am33xx
[ $# -gt 7 ] && [ "$8" != "-" ] && {
# check if we have a board config name in the options field
# the options field mave have a board config name and a list
# of options, both separated by a colon (':'); the options are
# separated by commas (',').
#
# Check for board name
tmp="${8%:*}"
if [ "$tmp" ] ; then
CONFIG_NAME="$tmp" # CONFIG_NAME= am335x_evm
fi
# Check if we only have a colon...
if [ "${tmp}" != "$8" ] ; then
options=${8#*:} # options= SERIAL1,CONS_INDEX=1,NAND
TARGETS="`echo ${options} | sed 's:,: :g'` ${TARGETS}" # TARGETS= SERIAL1 CONS_INDEX=1 NAND
fi
} if [ "${ARCH}" -a "${ARCH}" != "${arch}" ]; then
echo "Failed: \$ARCH=${ARCH}, should be '${arch}' for ${BOARD_NAME}" 1>&2
exit 1
fi #
# Test above needed aarch64, now we need arm
#
if [ "${arch}" = "aarch64" ]; then
arch="arm"
fi if [ "$options" ] ; then
echo "Configuring for ${BOARD_NAME} - Board: ${CONFIG_NAME}, Options: ${options}"
else
echo "Configuring for ${BOARD_NAME} board..."
fi #
# Create link to architecture specific headers
#
if [ -n "$KBUILD_SRC" ] ; then
mkdir -p ${objtree}/include
LNPREFIX=${srctree}/arch/${arch}/include/asm/
cd ${objtree}/include
mkdir -p asm
else
cd arch/${arch}/include # cd arch/arm/include
fi rm -f asm/arch # 删除arch/arm/include下的asm/arch if [ "${soc}" ] ; then
ln -s ${LNPREFIX}arch-${soc} asm/arch # 创建软连接arch -> arch-am33xx
elif [ "${cpu}" ] ; then
ln -s ${LNPREFIX}arch-${cpu} asm/arch
fi if [ -z "$KBUILD_SRC" ] ; then # 判断$KBUILD_SRC是否为空,为空返回真
cd ${srctree}/include # cd include
fi #
# Create include file for Make
#
( echo "ARCH = ${arch}" # ARCH = arm
if [ ! -z "$spl_cpu" ] ; then
echo 'ifeq ($(CONFIG_SPL_BUILD),y)'
echo "CPU = ${spl_cpu}"
echo "else"
echo "CPU = ${cpu}"
echo "endif"
else
echo "CPU = ${cpu}" # CPU = armv7
fi
echo "BOARD = ${board}" # BOARD = am33xx [ "${vendor}" ] && echo "VENDOR = ${vendor}" # VENDOR = ti
[ "${soc}" ] && echo "SOC = ${soc}" # SOC = am33xx
exit 0 ) > config.mk # 创建config.mk # Assign board directory to BOARDIR variable
if [ -z "${vendor}" ] ; then
BOARDDIR=${board}
else
BOARDDIR=${vendor}/${board} # BOARDDIR=ti/am33xx
fi #
# Create board specific header file
#
if [ "$APPEND" = "yes" ] # Append to existing config file
then
echo >> config.h
else
> config.h # Create new config file # 默认创建新文件
Fi # 往include/config.h 文件中写入配置参数等
echo "/* Automatically generated - do not edit */" >>config.h for i in ${TARGETS} ; do
i="`echo ${i} | sed '/=/ {s/=/ /;q; } ; { s/$/ 1/; }'`"
echo "#define CONFIG_${i}" >>config.h ;
done echo "#define CONFIG_SYS_ARCH \"${arch}\"" >> config.h
echo "#define CONFIG_SYS_CPU \"${cpu}\"" >> config.h
echo "#define CONFIG_SYS_BOARD \"${board}\"" >> config.h [ "${vendor}" ] && echo "#define CONFIG_SYS_VENDOR \"${vendor}\"" >> config.h [ "${soc}" ] && echo "#define CONFIG_SYS_SOC \"${soc}\"" >> config.h [ "${board}" ] && echo "#define CONFIG_BOARDDIR board/$BOARDDIR" >> config.h
cat << EOF >> config.h
#include <config_cmd_defaults.h>
#include <config_defaults.h>
#include <configs/${CONFIG_NAME}.h>
#include <asm/config.h>
#include <config_fallbacks.h>
#include <config_uncmd_spl.h>
EOF exit 0

4、总结

mkconfig做了些什么:

1)       从顶层目录boards.cfg文件中根据make am335x_evm_config中的am335x_evm找到对应单板的属性参数;

2)       创建对应CPU架构的头文件软连接arch/arm/include/asm/arch -> arch/arm/include/asm/arch-am33xx;

3)       创建Makefile的包含文件include/config.mk,并将单板属性参数写进去;

4)       创建对应单板的特征的头文件include/config.h,并将单板属性参数宏定义和必须头文件写进去。

u-boot-2015.07 make xxx_config 分析的更多相关文章

  1. Myeclipse 2015 stable 1.0 完美破解方法(转自 http://yangl.net/2015/07/14/myeclipse_2015stable_1/)

    Myeclipse 2015 stable 1.0 完美破解方法 http://yangl.net/2015/07/14/myeclipse_2015stable_1/ 破解包(注册机)下载地址:链接 ...

  2. spring boot 2.0 源码分析(一)

    在学习spring boot 2.0源码之前,我们先利用spring initializr快速地创建一个基本的简单的示例: 1.先从创建示例中的main函数开始读起: package com.exam ...

  3. spring boot 2.0 源码分析(四)

    在上一章的源码分析里,我们知道了spring boot 2.0中的环境是如何区分普通环境和web环境的,以及如何准备运行时环境和应用上下文的,今天我们继续分析一下run函数接下来又做了那些事情.先把r ...

  4. Murano Weekly Meeting 2015.07.21

    会议时间: 2015.07.21 主持人: Kirill Zaitsev, core from Mirantis 会议摘要:  1.murano client和murano dashboard升级到y ...

  5. Murano Weekly Meeting 2015.07.14

    会议时间: 2015.07.14 主持人: Kirill Zaitsev, core from Mirantis 会议摘要:  1.periodic nightly builds,然后通过mailin ...

  6. Spring Boot 自动配置 源码分析

    Spring Boot 最大的特点(亮点)就是自动配置 AutoConfiguration 下面,先说一下 @EnableAutoConfiguration ,然后再看源代码,到底自动配置是怎么配置的 ...

  7. Archlinux 2015.07.01 和 Windows7 双系统 安装教程

    提前在windows7下给Archlinux预留一个分区,大小最好在20G以上(根据自己硬盘情况分配). 第一步,安装前的准备 从arch官网下载最新的ISO文件archlinux-2015.07.0 ...

  8. Spring Boot探究之旅--启动分析

    刚接触SpringBoot,感觉挺方便的,不用配置那么多乱七八糟的配置,很方便!酒饱思淫欲,得陇望蜀一下,看看SpringBoot到底怎么做到这么方便的. 首先呢,先来看个SpringBoot的hel ...

  9. spring boot 2.0 源码分析(五)

    在上一篇文章中我们详细分析了spring boot是如何准备上下文环境的,今天我们来看一下run函数剩余的内容.还是先把run函数贴出来: /** * Run the Spring applicati ...

随机推荐

  1. 利用idea的code inspect功能进行代码静态分析

    利用idea.phpstorm系列的ide的code inspect功能可以开发出适用于各种编程语言的代码静态分析工具.这个功能大家可以自己实现扩展规则,规则也使用了visitor模式,规则里对关心的 ...

  2. sql server动态行列转换

    原文链接:https://www.cnblogs.com/gaizai/p/3753296.html sql server动态行列转换 一.本文所涉及的内容(Contents) 本文所涉及的内容(Co ...

  3. 基于rman的坏块恢复

    转载请注明出处 http://blog.csdn.net/guoyjoe/article/details/30965303   实验过程例如以下: 1.使用rman备份全库 Recovery Mana ...

  4. Telnet命令参考手册

    Dubbo2.0.5以上版本服务提供端口支持telnet命令,使用如: telnet localhost 20880 或者: echo status | nc -i 1 localhost 20880 ...

  5. 详解Spark sql用户自定义函数:UDF与UDAF

    UDAF = USER DEFINED AGGREGATION FUNCTION Spark sql提供了丰富的内置函数供猿友们使用,辣为何还要用户自定义函数呢?实际的业务场景可能很复杂,内置函数ho ...

  6. 关于手机适配中的rem的学习随笔

    githup 下载地址 :https://github.com/comjustforfun/remformobile adaptivejs利用rem解决移动端页面开发的自适应问题 页面模板初始化的时候 ...

  7. C++学习笔记--异常简介

    C++异常是对程序运行过程中发生的异常情况(如被0除)的一种响应.异常提供了将控制权从程序的一个部分传递到另一部分的途径. 1.对异常的处理有3个部分组成: (1)引发异常 (2)捕获有处理程序的异常 ...

  8. Ajax跨域请求 同源策略与Jsonp

    同源策略 同源策略(Same origin policy)是一种约定,它是浏览器最核心也最基本的安全功能,如果缺少了同源策略,则浏览器的正常功能可能都会受到影响.可以说Web是构建在同源策略基础之上的 ...

  9. Outputting Strings in the Console

    Outputting Strings in the Console #include <windows.h> class Console {public:  enum fore_color ...

  10. java 定时器实现

    java工程中,不免遇到需要定时处理任务的需求,有如下两种方法: 1.使用java.util.TimerTask 2.使用Quartz 一.java.util.TimerTask Timer time ...