Porting U-Boot-2009.08 to mini2440 Basic Configuration

1. Environment

Target board: mini2440

u-boot version: u-boot-2009.08

Cross compiler: arm-linux-gcc-4.3.2 Download from http://www.linuxidc.com/Linux/2011-04/34049.htm

Operating System: Linux ( Ubuntu -11.10)

U-Boot source code download address http://www.linuxidc.com/Linux/2011-07/38897.htm

2. Purpose

Build the mini2440 target board environment. Before reading this article, it is recommended to read Embedded System Boot Loader Technology Insider See http://www.linuxidc.com/Linux/2011-12/50389.htm

Steps

1. Download source code

1. tar –jxvf u-boot-2009.08.tar.bz2

2. Create mini2440 directory and header file

Before that, you must be familiar with the U-boot directory tree. For example, the board directory is where the root board related files (smdk2410.c, etc.) are stored.

、

Enter the root directory of u-boot

1. cp -r board/samsung/smdk2410/ board/samsung/mini2440

2. mv board/samsung/smdk2410/smdk2410.c board/samsung/mini2440/mini2440.c

3. cp include/configs/smdk2410.h include/configs/mini2440.h

3. Modify the Makefile in the u-boot root directory

U-boot is a good thing, with detailed documentation. Looking at the README [line 227] in the root directory of U-boot, we know that we must configure the target board environment before making.

For all supported boards there areready-to-use default

configurations available; just type"make _config".

Find line 2997 of Makefile, where you can see the configuration for different boards. For example:

1. smdk2410_config :   unconfig

2. @$(MKCONFIG) $(@:_config=) arm arm920t smdk2410 samsung s3c24x0

After this, we add the following:

1. mini2440_config :   unconfig

2. @$(MKCONFIG) $(@:_config=) arm arm920t mini2440 samsung s3c24x0

The above parameters are described as follows.

unconfig: Dependency on unconfig. Executing unconfig actually performs cleanup work.

unconfig:

@rm–f  $(obj)include/config.h$(obj)include/config.mk

$(obj)board/*/config.tmp$(obj)board/*/*/config.tmp

$(obj)include/autoconf.mk$(obj)include/autoconf.mk.dep

ARM CPU architecture (ARCH)

arm920t CPU type, which corresponds to the cpu/arm920t subdirectory

The model of the mini2440 development board (BOARD), which corresponds to the board/samsung/mini2440 directory

Samsung developer/vender. The parent directory of the new development board project directory. If you create a new development board project directory directly under board, this will be NULL.

s3c24x0 System on Chip (S0C)

If the default cross compiler is arm-linux-gcc, you do not need to reset the compilation environment, otherwise you need to add it again.

Find line 161 of the Makefile

1. # set default to nothing for native builds

2. ifeq ($(HOSTARCH),$(ARCH))

3. CROSS_COMPILE ?=

4. endif

Setting up the cross compiler:

1. CROSS_COMPILE = arm-linux-

2. # set default to nothing for native builds

3. ifeq ($(HOSTARCH),$(ARCH))

4. CROSS_COMPILE ?=

5. endif

4. We will start NorFlash first, so there is no need to modify other codes for the time being.

5. Test whether there is any problem with the previous modification. If there is no problem, the u-boot.bin file will be generated after successful compilation.

Return to the u-boot root directory

1. make distclean

2. make mini2440_config

3. make

4. Errors

make -C board/samsung/mini2440/

make[1]: Entering directory `/home/yz019/u-boot/u-boot-2009.08/board/samsung/mini2440'

make[1]: *** No rule to make target '.depend' needed by 'libmini2440.a'. Stop.

make[1]: Leaving directory `/home/yz019/u-boot/u-boot-2009.08/board/samsung/mini2440'

make: ***[board/samsung/mini2440/libmini2440.a] Error 2

Solution:

Check board/Samsung/mini2440/Makefile28

1. COBJS := smdk2410.o flash.o

Modified to

1. COBJS := mini2440.o flash.o

make. I was pleasantly surprised to find the following statement, and it was done~

arm-linux-objcopy -Osrec u-boot u-boot.srec

arm-linux-objcopy--gap-fill=0xff -O binary u-boot u-boot.bin

V. Achievements

Since the clock configuration and other related board-level settings are not made, the serial port cannot output debugging information, so burning the compiled u-boot.bin to NorFlash will not produce any effect.