The establishment of zedboard's Linux cross-compilation environment

The most important thing to develop ZedBoard is the Xilinx ISE toolset, where most of the logic and underlying software development work can be done. If you do streaking development, an IDE is enough, but if you don't want to wear clothes for a lifetime, you need to involve software design under Linux, you have to compile in Linux. Xilinx's IDE seems to integrate the environment for developing Linux software, but rabbits are not very useful, and there are too many things that need to be compiled under Linux. In many places, SDKs can't do anything, so they still take the traditional route - in Linux. Create a Xilinx build environment. First install a virtual machine on the machine, install ubnutu linux1 12.04 stl version on it, if you are a 64-bit machine, you need to install a 32-bit library file. The method is sudo apt-get install ia32-libs, if you have further instructions on the 64-bit system distribution, visit: The next step is to download the cross-compilation environment URL: -source/downloads/detail?name=xilinx-2011.09-50-arm-xilinx-linux-gnueabi.bin&can=2&q=Installing a cross-compilation environment: An article on the Mentor website says that a 32-bit version of xulrunner is also required. I have not installed it here, but it can also be used. If you are not comfortable, you can follow the steps here: and enter it in the terminal: dpkg-reconfigure dash in the pop-up dialog box No, change dash to bash in order to successfully execute the Sourcery CodeBench installer. Download the good installation file: xilinx-2011.09-50-arm-xilinx-linux-gnueabi.bin, enter ./xilinx-2011.09-50-arm-xilinx-linux-gnueabi.bin in the file path to open the installer. Rabbit chooses the default path (Do not modify PATH), the installed executable file path is /root/CodeSourcery/Sourcery_CodeBench_Lite_for_Xilinx_GNU_Linux/bin/, and each time you compile the software, you need to add the path of the compilation environment to the PATH environment variable through the export command. After compiling some content, you will need to modify ARCH. The instructions are as follows: export ARCH=armexport CROSS_COMPILE=arm-xilinx-linux-gnueabi-export PATH=/root/CodeSourcery/Sourcery_CodeBench_Lite_for_Xilinx_GNU_Linux/bin/:$PATH if you don't want to Enter all the time, just open the bash.bashrc file through the gedit /etc/bash.bashrc command, add the above command inside, so the boot will be executed automatically, you can also run the source /etc/bash.bashrc command to make the settings take effect immediately. Through the echo $PATH command, you can see the path we just set. Let's try to compile something, first of all HelloWorld. Find a place to create a new hello.c file, edit it with gedit, the code is as follows: #includeint main(void){ printf("Hello ZedBoard!"); return 0;} Enter the following command in the directory where the C file is located: arm- Xilinx-linux-gnueabi-gcc hello.c generated a.out file on the rabbit computer, probably the reason for the previous settings, not sure what to call you. Figure:


Copy the generated file to the USB flash drive, connect to the USB OTG of ZedBoard, mount the USB flash drive first, and then run the software test: mount /dev/sda1 /mnt//mnt/a.out Now the cross environment is fixed. The effect is as follows: Try to compile U-Boot below, Xilinx also introduced on the wiki: First, choose a directory for development, the rabbit's directory is located in /arm/zed, which is customizable. Download the Xilinx U-Boot code via Git (note that the name has been changed here): git clone git:// .gitcd u-boot-xlnx with our previously installed cross-compiler environment Compile, because we have set the environment variables, here to directly compile, you can first configure: make zynq_zed_config configuration is completed after compilation: after the completion of the make, will generate a u-boot file (no suffix name), this is a Elf file, save it as u-boot.elf. This file is very important, it will be used when we generate the Boot Loader in the future, and then explain it when it is used. Then we will start designing our own custom AXI bus peripherals. Next time we will present a GPIO to read the Switch value and control the LED IP. The ultimate goal is to control this hardware IP through Linux under our own software. Source: Where is the wind flying?

KNB6-63 Miniature Circuit Breaker

KNB6-63 Mini Circuit breakers, also named as the air switch which have a short for arc extinguishing device. It is a switch role, and also is a automatic protection of low-voltage electrical distribution. Its role is equivalent to the combination of switch. Fuse. Thermal Relay and other electrical components. It mainly used for short circuit and overload protection. Generally, According to the poles, mini Circuit breaker can be divided into 1P , 1P+N , 2P, 3P and 4P.

KNB6-63 Miniature Circuit Breaker,Electronics Miniature Circuits Breaker,Automatic Miniature Circuit Breaker,Mini Circuit Breaker

Wenzhou Korlen Electric Appliances Co., Ltd. ,