After this time, by the US Lun DIY competition, the ZEDBOARD is slightly income, has a certain understanding of this new platform. Here, it is called a note, and it is almost written. Since still study, there will be some fallacy or insufficient, but also look at the children's shoes.
To develop zedboard is the most important thing about the Xilinx ISE toolset, which can complete most of the logical and underlying software development work in this IDE. If you have a naked development, an IDE is enough, but if you don't want to wear clothes for a lifetime, you need to build a software design under Linux, you have to compile in Linux. Xilinx's IDE is also integrated into the environment of developing Linux software, but the rabbit is not used, and there is too much thing to compile under Linux, and many local SDK can also be powerful, so take the traditional route - in Linux Establish a Xilinx compilation environment.
The rabbit's operating system is Win7 Ultimate, and the multi-system is used up, so the VMware virtual machine is installed, and Ubuntu is installed under the virtual machine. The version is 11.10 64-bit. Establishing a compilation environment is the topic of the old life, there are a lot of online, but in order to keep your integrity, please feel patient here again.
Download Source CodeBench in the Xilinx Wiki website (http://wiki.xilinx.com/zynq-tools), because this environment is designed for 32-bit system, users of the 64-bit system need to install some 32-bit libraries first. Enter root privileges in the Ubuntu terminal (rabbit likes the terminal on Sudo SU, save later), enter the following command:
APT-GET Install IA32-LIBS IA32-LIBS-GTK
An article on the Mentor website said that there is also a 32-bit version of Xulrunner. I haven't installed it here, but I can use it. I can use it here. Step is installed here: https: //sourcery. man.com/gnutoolchain / KBENTRY62
Then enter in the terminal:
DPKG-RECONFIGURE DASH
Overhead in the pop-up dialog box, change the DASH to Bash so that the Sourcery CodeBench installer can be successfully executed. Download a good installation file is: Xilinx-2011.09-50-Arm-xilinx-linux-gnueabi.bin, enter ./xilinx-2011.09-50-arm-xilinx-linux-gnueabi.bin Open the installer, Rabbit Select the default path (Do Not Modify Path), after the execution file path is / root / code, / source_codebench_lite_for_xilinx_gnu_linux / bin /, you need to add a path to the compilation environment via the Export instruction every time you compile the software. After compiling some contents, you will use the need to modify the Arch, and the instructions are as follows:
Export Arch = ARM
Be
Export cross_compile = arm-xilinx-linux-gnueabi-
Be
Export Path = / Root / CodeSourcery / Sourcery_codebench_lite_for_xilinx_gnu_linux / bin /: $ PATH
If you don't want to enter each time, open the bash.bashrc file through the gedit /etc/bash.bashrc instruction, add the above instructions, so that the boot will be executed, and you can also run the source /etc/bash.bashrc instruction Set immediately, you can see the path we just set up with the Echo $ PATH instruction.
Let's compile things, try, first is HelloWorld. Find a place to create a new hello.c file, editing with gedit, the code is as follows:
#include
Int main (void)
{
Printf ("Hello Zedboard! \ n");
Return 0;
}
Enter the following instructions in the directory where the C file is located:
ARM-XILINX-Linux-gnueabi-gcc hello.c
Generate a.out file on the rabbit computer, which may be the reason for the previous settings, uncertain, what will be called there huh. Figure:
Copy the generated file to the USB flash drive, connect to the USB OTG of ZEDBOARD, first mount the USB flash drive, then run the software to test:
Mount / DEV / SDA1 / MNT /
Be
/mnt/a.out
The cross environment is done, the effect is as follows:
Let's compile a U-BOOT, Xilinx has also introduced on Wiki: http://wiki.xilinx.com/zynq-uboot
First choose a directory for development, the bunny directory is located in / arm / zed, this is good for it. Download the Xilinx U-Boot Code via git (note, here is already changed):
git clone git: //git.xilinx.com/
Be
U-boot-xlnx
.git
Be
CD U-boot-xlnx
Compile with the cross-compilation environment we have previously installed, because we have set an environment variable, here is directly compiled, first configured:
Make zynq_zed_config
Compiled after the configuration is completed:
Make
After completing the completion, a U-boot file (no suffix name) is generated, which is an ELF file that saves it as u-boot.elf. This file is very important, it will be used when we generate boot loader in the future, and then explain it again.
After we will start designing your own custom AXI bus peripheral, the next time you will present a Switch value through GPIO and control the IP of the LED, the ultimate goal is to control this hardware IP through its own software under Linux.
Ok, come here today. Good night ~~~
Our other product:
