![]() ![]() DCONFIG_4xx -ffixed-r2 -mstring -msoft-float -Wa,-m405 -mcpu=405 -Wall -Wstrict. Gcc/powerpc-montavista-linux-gnu/4.2.0/include -pipe -DCONFIG_PPC -D_powerpc_ DTEXT_BASE=0xFFFC0000 -I/home/chris/sandbox/u-boot/include -fno-builtin -ffree. Ppc_440ep-gcc -g -Os -mrelocatable -fPIC -ffixed-r14 -meabi -D_KERNEL_ Make: Entering directory '/home/chris/sandbox/u-boot/board/ep/ep405' After copying the files to your new board directory, edit the filenames appropriately for your board name: $ cd board We don't know yet if we need all of them. include/configs/EP405.hĪfter you have copied the configuration header file, you must create the board-specific directory and make a copy of the AR405 board files. These commands are issued from the top-level U-Boot source tree: $ cp. Copy the board configuration file to a new file with a name appropriate for your board. We need a custom board configuration header file for our EP405 board. The goal is to minimize any development work by borrowing from similar architectures in the spirit of open source. It supports the LXT971 Ethernet transceiver, which is also on the EP405. After examining a few, we choose the AR405.h configuration as a baseline. In a recent U-Boot snapshot, 28 board configuration files are configured for the 405GP. A quick grep of the board-configuration header files narrows the choices to those that support the 405GP processor: $ cd. Many boards in the U-Boot source tree support the 405GP processor. The first step is to see how close we can come to an existing board. ![]() Numerous other devices complete the design. The particular board used for this example was provided courtesy of Embedded Planet and came with 64MB of SDRAM and 16MB of on-board Flash. We will use the Embedded Planet EP405 board, which contains the AMCC Power Architecture 405GP processor. The same logic used in porting to a different CPU applies to porting U-Boot to a new board. Finally, modify the resulting sources to add the specific support for your new CPU's requirements. Determine what CPU is closest to yours, and clone the functionality found in that CPU-specific directory. Whether you are porting to a new CPU or a new board based on an existing CPU, study the existing source code for specific guidance. The good news is that someone before you has probably done the bulk of the work. If you must add a new CPU, plan on substantially more effort. If your board contains one of the supported CPUs, porting U-Boot is straightforward. U-Boot supports a large variety of popular CPUs and CPU families in use today, and a much larger collection of reference boards based on these processors. Note that, in some cases, the CPU configuration covers a family of chips, such as ppc4xx, that supports several processors in the Power Architecture 4 xx family. In this same U-Boot version, 49 different CPU configurations are supported (counted in the same manner). board/vendor/boardname subdirectory under the U-Boot top-level source directory, where boardname specifies a particular board.Īs of a recent U-Boot snapshot, more than 460 different board configuration files are named config.mk under the. These files are all given the name config.mk. ![]() Each board port must supply a subordinate makefile that supplies board-specific definitions to the build process. One of the reasons U-Boot has become so popular is the ease with which new platforms can be supported. Embedded Linux Primer: A Practical Real-World Approach, 2nd Edition ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |