zybo的linux开发教程,嵌入式Linux教程 - Zybo （下）

接上文

Step 20: U-Boot Source Code

*Note: Use the Master-Next Branches until further notice

Get the source code for U-Boot from the Digilent git repository. There are two ways to retrieve the source code:

Using git command:

If you have git installed in your distribution, you can clone the repository to your computer by command git clone https://github.com/Digilent/u-boot-Digilent-Dev.g...The whole Git Repository is around 55MB, as shown in image 1. If you want to get a separate branch, for example the next branch follow image 2. The next contains the u-boot that is not yet released. The clone url referenced above can be found on the Digilent git-hub page as seen in image 3.

Download a compressed package:

If you only want to use u-boot once and do not want to track the updates, you can also download a compressed package from github.com:https://github.com/Digilent/u-boot-digilent.Go to the drop down box that shows the branch and select tags. The most recent tag is zynq-beta-v2.2. (image 4).

If you downloaded the tar.gz, you can decompress it using command

tar zxvf u-boot-digilent-2012.04-digilent-13.01.tar.gz

If you downloaded the zip file, you can decompress it using command

unzip u-boot-digilent-2012.04-digilent-13.01.zip

Step 21: Compile U-Boot

To compile U-Boot, we need cross-compile tools which are provided by Vivado 2014.1. Those tools have a prefix arm-xilinx-linux-gnueabi- to the standard names for the GCC tool chain. The prefix references the platforms that are used. The Zybo board has two arm cores so we reference arm. In order to use the cross-platform compilers, please make sure Vivado 2014.1 settings have been sourced. If not, please refer to step 2. To configure and build U-Boot for Zybo, follow the image attached to this step.

Step 22: U-boot.elf

After the compilation,

the ELF (Executable and Linkable File) generated is named u-boot. We need to add a .elf extension to the file name so that Xilinx SDK can read the file layout and generate BOOT.BIN. In this tutorial, we are going to move the u-boot.elf to sd_image folder and substitute the u-boot.elf that comes along with Zybo Base System Design Package.

Step 23: Export Hardware for SDK

Export the hardware design (after step I-16) to Xilinx SDK by clicking on File -> Export -> Export Hardware for SDK…, as shown in the first image.

Leave the workspace as . Make sure that Launch SDK is checked and click OK, as shown in the second image.

Note: You may have to export twice.

Step 24: New Project

After SDK launches, the hardware platform project is already present in Project Explorer on the left of the SDK main window, as shown in image 1. We now need to create a First Stage Bootloader (FSBL). Click File->New->Project…, as shown in image 2.

Step 25: Application Project

In the New Project window, select Xilinx->Application Project, and then Click Next.

Step 26: Name the Project FSBL

We will name the project FSBL. Select hw_platform_0 for Target Hardware because it is the hardware project we just exported. Select standalone for OS Platform. Click Next.

Step 27: Create Zynq FSBL Template

Select Zynq FSBL as template, and click Finish.

Step 28: FSBL Hook

For the Zybo, we need set the mac address for the Ethernet in the fsbl hook. We want the mac address for the Ethernet to remain constant when we turn off and on the Zybo Board. You can swap the fsbl_hooks.c file in the FSBL project with the fsbl_hooks.c under source/vivado/SDK/fsbl in the Zybo Base System Design.

After you have saved the changes to fsbl_hooks.c,

the project will rebuild itself automatically. If it does not rebuild, Click Project->Clean to clean the project files, and Project->Build All to rebuild all the projects. The compiled ELF file is located in zybo_base_system/source/vivado/hw/zybo_bsd.sdk/SDK/SDK_Export/FSBL/Debug

Step 29: Create Boot Image

Now, we have all the files ready to create BOOT.BIN. Click Xilinx Tools -> Create Zynq Boot Image.

Step 30: Add FSBL, system.bit and u-boot.elf

In the Create Zynq Boot Image window, Click Browse to set the path for FSBL elf. Click Add to add the system.bit file found at /zybo_base_system/source/vivado/hw/zybo_bsd/zybo_bsd.sdk/SDK/SDK_Export/hw_platform_0/.Click Add to add the u-boot.elf file found at zybo_base_system/sd_image/. It is very important that the 3 files are added in this order, or else the FSBL will not work properly. It is also very important that you set FSBL.elf as the bootloader and system.bit and u-boot.elf as data files. In this tutorial, the sd_image folder is set as output folder for the BIN file. Click Create Image.

Step 31: Linux Kernel Source Code

*Note: Use the Master-Next Branches until further notice

Get the Linux kernel source code from Digilent git repository. There are two ways to retrieve the source code:

Using git command: If you have git installed in your distribution, you can clone the repository to your computer by command git clonehttps://github.com/DigilentInc/Linux-Digilent-Dev... The whole Git Repository is around 850MB, as shown in image 1.

Download a compressed package: If you only want to use u-boot once and do not want to track the updates, you can also download a compressed package from github.com: https://github.com/DigilentInc/Linux-Digilent-Dev. Click Tags on the top right corner of the page.The most recent tag is zynq-dt-for-3.14 (image 2).

If you downloaded the tar.gz, you can decompress it using command

tar zxvf linux-digilent-v3.6-digilent-13.01.tar.gz

If you downloaded the zip file, you can decompress it using command

unzip linux-digilent-v3.6-digilent-13.01.zip

Step 32: Configure the Kernel

We will start to configure the kernel with the default configuration for Zybo. The configuration is located at arch/arm/configs/xylinx_zynq_defconfig. To use the default configuration follow the image attached to this step.

Step 33: Compile the Linux Kernel

Follow the example in the image.

Step 34: Make Uimage

After the compilation, the kernel image is located at arch/arm/boot/zImage. However in this case the kernel image has to be a uimage (unzipped) rather than a zimage. To make the uimage follow the image in this step.

Step 35: Optional Path change

Note: Depending on your distribution of linux you may get an error regarding the path of the mkimage. If this is the case you can change the path following the image in this step.

Step 36: Make Uramdisk

To boot the Linux Operating System on the Zybo, you need BOOT.BIN, a Linux kernel image (uImage), a device tree blob (DTB file), and a file system. BOOT.BIN has been created in Section III and uImage has been compiled in Section IV. We will now compile the DTB file. The default device tree source file is located in the Linux Kernel source at arch/arm/boot/dts/zynq-zybo.dts.

RAMDISK: For zynq only the ramdisk image has to be wrapped in a u-boot header in order for u-boot to boot with it. This is shown in the image in this step.

Step 37: Generate DTB file

Follow the example provided in the image.

Step 38: Copy File Image to SD Card

RAMDISK) Copy BOOT.BIN, devicetree.dtb, uImage and uramdisk.image.gz to the first partition of an SD card, as shown in the first image – RamDisk.

NOTE: The first partition of the SD card is mounted to /media/ZYBO_BOOT

Step 39: Boot from SD Card

Plug the SD Card into the Zybo. To boot from SD card, jumper 7 needs to be configured for USB as shown on the Zybo Board and Jumper 5 must be connected to SD. Connect UART port to PC with micro USB cable and set the UART terminal on PC to 115200 baud rate, 8 data bits, 1 stop bit, no parity, and no flow control. After powering on the board, the console should be seen at the UART terminal if you use RamDisk. More information about this file system can be found in Getting Started with Embedded Linux ZedBoard.

Step 40: Create a Drivers Directory

Create a directory named drivers in the Tutorial folder, as shown the image in this step. Inside the drivers directory, we will compose the driver for the myLed controller.

Step 41: Create the Makefile

We need a Makefile so that we can compile the driver. The Makefile is created in image 1.

After creating the file, hit I to change to insert mode and insert the following text in image 2. Make sure you use tab characters where appropriate.

Step 42: Create myled.c

We will start with a simple driver that creates a file named myled under the Linux /proc file system. The status of the on-board LEDs can be changed by writing a number to the file. The driver is coded in the last four images and is attached

Step 43: Compile Driver

Compile and generate the driver module using make. Don’t forget to source Vivado settings.

Step 44: Add myled to the Device Tree

We need to add the myLed device node into the device tree.

Make a copy of the default device tree source in the drivers folder, and modify it according to the second image. The compatibility string of the node is the same as we define in the driver source code (myled.c: line 182). The reg property defines the physical address and size of the node. The address here should match with the address of the myLed IP core in the address editor tab of the Vivado design, as shown in the last image.

Step 45: Recompile Device Tree Blob

Recompile the device tree blob as shown in the attached image.

Step 46: Copy Driver and Modified Device Tree to SD card

Copy these two files to the first partition of the SD card, as shown in the image in this step. We are ready to test our driver on-board now.

Step 47: Boot From SD Card

Plug the SD card into the Zybo, and we can start testing our driver. Use the insmod command to install the driver module into the kernel. After the driver is installed, an entry named myled will be created under the /proc file system. Writing 0x0F to /proc/myled will light up LED 0~3. You can either remove the driver with command rmmod or power off the system by command poweroff. In both case, all the LEDs will be turned off, as shown in Figure 69 and 70. For instructions on using the terminal with the Zybo. please refer to Step V-4 or Section Boot from SD in Getting Started with Embedded Linux – ZedBoard.

Step 48: User Application: led_blink

In this section, we will write a user application that makes the LEDs

blink by writing to /proc/myled. Create a directory named user_app in the Tutorial folder, as shown in the first image. Inside the user_app directory, we will compose the led_blink.c, as shown in the second and third image.

Step 49: Create Makefile and Compile led_blink

Compose a Makefile and compile led_blink.c into led_blink.o, as shown in the three images in this step.

Step 50:

Insert the SD card into the computer, and copy the binary file led_blink onto the first partition of SD card.

Step 51: Run led_blink

Plug the SD card into the ZYBO. Use the insmod command to install the driver module into the kernel. Run led_blink and the LED will start blinking.

Step 52: Feedback!

Just a reminder, this is a draft. There will be an official copy that will be released onDigilentinc.com.

I appreciate any feedback to make the official copy stronger.