PowerPC is a CPU chip jointly developed by Motorola and IBM for Apple's MAC machine. The trademark rights belong to both IBM and Motorola, and become their leading products. IBM's main PowerPC products include PowerPC604s (deep blue internal CPU), PowerPC750, PowerPCG3 ( 1.1GHz).Motorola mainly has MC and MPC series. Although their products are different, they all use PowerPC's kernel. Most of these products are used in embedded systems. We will introduce them here mainly for IBM on xilinx platform. PowerPC embedded kernel. The content written in this article is basically used for the XUP University program development board, but many of the steps are common. You can refer to these steps on the Xilinx ML-403 development board or other corresponding boards. The biggest difference is that the command line when creating SystemACE is different, and will be explained in the corresponding section. It should be said that no matter what platform, the whole process is followed by: Kernel preparaTIon —†isntall BSP —†Build hardware platform —†Memory test —†Build kernel image —》 Download This article assumes that the reader has already operated the ISE, EDK and other tools in the Linux environment. Familiarity and familiarity with customizing basic hardware systems on the XUP development board, so this is not covered in detail. The author directly uses linux as the development environment, so the article will not involve the creation of a cross-compilation environment. If you are a Windows user, please refer to the online cygwin article; if the operating system you are using is linux, but for development The environment is not familiar with the establishment, you can refer to the eda tool I wrote earlier to install this article; if you are not familiar with the hardware system customization, please target the problem to a module, and then leave a message. The whole article is relatively long. From the content that has been written so far, it may be released in three parts. Here is the first part. Basic system information software: ISE and EDK are 9.1, no sp, the operating system is ubuntu 7.04; hardware: XUP development board, usb download line; basic system components: 300MHz PPCopb_sysaceopb_ethernet (no DMA) DDR memory controlleropb_uart_16550plb_bram_if_cntrl (bram selects the maximum capacity) All components must have interrupt support. According to the above basic requirements, the system is built. The OS first selects standalone and runs a basic program to take a look. Only after confirming that the basic system is normal can you know if the problem encountered in the future migration of the system is hardware. Creating a BSP in EDK First, open the options for the software platform settings, follow the steps below: 1. Set the OS of PPC_405_0 to linux_mvl31, my version here is 1.01.c2. Enter the Library/OS option, where MEM_SIZE is set to you. The memory capacity of the platform used, for example, 256MB is set to 0 or TImes; 10000000, and so on. PLB_CLOCK_FREQ_HZ is the frequency of your PLB bus. XUP is 100MHz, which is 100000000. Other types of development boards modify themselves. TARGET_DIR is the path you use to store the BSP. Note that the path must not have spaces. 3. Add hardware, inside connected_periphs, but after you usually go in, you have already added it automatically. 4. Execute libgen. If all goes well, you can generate the corresponding bsp. If there is any problem in this process, you can go to the sw/ThirdParty/bsp/linux_mvl31_v1_00_a/data/ directory in the EDK installation directory to see the corresponding tcl files, which are the commands used to actually perform BSP operations. At this point, you already have working bitstream files and BSP files for Linux. But what's interesting is that I found that the role of BSP is very small. All the files generated by edk9.1, you only need xparameters.h and xparameters_ml403.h are really useful, other files work very little, if you download the Linux source The code is something of montavista, not even the two files. Of course, if the board used is custom, like xparameters_ml403.h there will be different macro definitions, so these two must be overwritten with the same name in the default kernel directory. For insurance, the last time you use this BSP. Creating a cross-compilation environment for ppc Typically, programs are compiled on one computer and then distributed to other computers that will be used. When the host system (the system running the compiler) and the target system (the system on which the generated program will run) are incompatible, the process is called cross-compilation. Building a cross-compilation toolchain is a fairly complicated process. If you don't want to go through the complicated compilation process yourself, there are some compiled cross-compilation toolchains available for download on the web. Here, we directly create a cross-compilation environment for ppc through off-the-shelf scripts. If you are interested in compiling and building this environment, you can refer to the article on how to build a cross-compilation environment for embedded development. Considering that most people use x86 computers, it is necessary to establish a cross-compilation environment suitable for ppc. First, come here to download the crosstoll installation package. After downloading, unzip and go into the folder, you can see a lot of scripts similar to the form demo-arch.sh. Each type of arch, the corresponding nature is a hardware platform, and what we want to use here is demo-powerpc-405.sh. If you are interested in this tool, you can refer to its instructions for use. Here, the author only explains according to his own development environment. Before using it, you need to edit the script first. Open demo-powerpc-405.sh, TARBALLS_DIR is the storage location of the relevant download resources, because you need to download the source code package of glibc, gcc, etc. from the Internet before installing the cross-compilation environment. The value of RESULT_TOP is the directory after installation and is modified as needed. Also find this sentence: eval `cat powerpc-405.dat gcc-4.1.0-glibc-2.3.6.dat` sh all.sh –notestls will be gcc-4.1.0-glibc-2.3.6.dat Change to a dat file for your platform. You can first look at the dat files in the folder, gcc-4.1.0 indicates the version of gcc, glibc-2.3.6 indicates the version of glibc, these version numbers must correspond to the version number on your actual machine. If you are not ready to modify the directory, create a crosstool directory in the /opt directory and change its permissions to writable. Finally, execute the script: sudo mkdir /opt/crosstoolsudo chown $USER /opt/crosstoolsh demo-powerpc-405. After sh, the script will go online to find the corresponding version of gcc, gdb, glibc, kernel, etc. according to the options you have modified, download and compile and install. The specific time spent is closely related to your network speed. If your network is very slow, I suggest you not try it. Try another network and test it. Or you can look at the value of the TARBALLS_DIR directory in the script, and then download the various tools and kernel source packages you need, and put them in this directory, then execute sh demo-powerpc-405.sh. The only thing to note is that the version of the source tool source package you downloaded yourself needs to be the same as the version specified in demo-powerpc-405.sh. After all the required resources have been downloaded, it is not directly executed demo-powerpc-405.sh, because there may be some problems when directly executed, so I have to do some preparatory steps before: 1. Unset LD_LIBRARY_PATH, why, The author guesses that the LD_LIBRARY_PATH environment variable is usually modified by the installer to include the directory where the relevant library is located. It is estimated that the compiler environment cannot be affected by the existing library. To temporarily give LD_LIBRARY_PATH a value during the compilation process, after compiling Change it back. 2. Install the parser generator bison/flex and execute apt-get install bison flex. 3. Change the /bin/sh connection object from dash to bash, which is due to a bug in my selection of glibc-2.3.6 and dash. Even if you are not using glibc-2.3.6, it is recommended to modify it. First use ls -la /bin/sh to see what your sh link is. If it is dash, it should be changed by sudo ln -sf /bin/bash /bin/sh. After performing the above steps, execute demo-powerpc-405.sh again, and the compilation process should be smoother. Of course, this time is also relatively long, the specific time depends on the machine configuration, it is strongly recommended to eat a meal, play the ball, and then come back to see ~. After the environment is built, the list of tools in the environment is as follows: Don't forget to add the path to the PATH variable, which is ${prefix}/bin, so you can use these tools directly. Reprinted from: Baixi space of fcni_cn
Thin Film Transistor,Tft Ad Lcd Screen,Tft Lcd Screen Colour,3.5 Inch Tft Lcd Screen,TFT
ESEN Optoelectronics Technology Co., Ltd, , https://www.esenlcd.com