10/02/2015 PetaLinux Linux Image Network Connection

Size: px

Start display at page:

Download "10/02/2015 PetaLinux Linux Image Network Connection"

Brent Warner
5 years ago
Views:

1 Contents 1 History Introduction Vivado Project Open Vivado New Project Project Settings Create Processor System New Block Diagram Generate Output Products HDL Wrapper Implement Design Export Hardware Launch SDK SDK Project New Application Project Hello Bootloader Bootloader debug flags PetaLinux Hardware Platform Petalinux project Import Hardware Description Linux System Configuration Device Tree Configuration pcw.dtsi pl.dtsi skeleton.dtsi system-conf.dtsi zynq-7000.dtsi system-top.dts ethernet Create Application Linux/Rootfs Configuration Build system image Build Application Software Testing Linux Kernel Image Page 1 of 71

2 5.11 Generate Boot Image for Zynq Configure Host Network Adaptor Enable Telnet in Windows 7 Host Booting from Micro SD card Micro SD card preparation Set Avnet MicroZed Development Board Boot Mode Configure HyperTerminal Reset Avnet MicroZed Development Network connection Ping Configure Avnet MicroZed IP address Cmd tool Telnet Web Server Page 2 of 71

3 1 History Revision Date Author Description A 5/2/2015 info@syfer.com.au Initial Revision Table 1 : History 2 Introduction This document describes how to create, test and configure a Linux image with network support using PetaLinux on Ubuntu LTS (64-bit). Ubunto LTS (64-bit) Guest is running Oracle VM VirtualBox on a Windows 7 Professional Service pack 1 (64-bit) Host. Vivado (Avnet MicroZed) Create Block Diagram Implement design Export hardware to SDK Launch SDK Create application Create bootloader PetaLinux Create project Import hardware Configure Linux system Device Tree configuration Create application Test Linux image in software Create boot image Test boot and Linux images Boot FPGA from Micro SD card (Avnet MicroZed) Test network connection Ping Telnet PetaLinux Webserver Page 3 of 71

4 3 Vivado Project 3.1 Open Vivado Open terminal ctrl+alt+t. $ source /opt/xilinx/vivado/2014.4/settings64.sh $ vivado & Figure 1: Open Vivado Figure 2: Vivado Page 4 of 71

5 3.2 New Project Create a new Vivado project. File -> New Project. Click on the Next button. Figure 3: Vivado Figure 4: New Project - Create a New Vivado Project Page 5 of 71

6 Select Project Name and Location. Project name: -> basic_test Project location: -> /home/syfer/projects/basic_test Click on the Create project subdirectory check box to un-check. Click on the Next button. Note: If you have permission problems then use sudo chmod R 777 /home/syfer/projects Figure 5: New Project - Project Name Page 6 of 71

7 Select the Project Type. Click on the RTL Project radio button to select. Click on the Next button. Figure 6: New Project - Project Type Page 7 of 71

8 Add HDL Source Files. No HDL sources are required to be added at this stage. Click on the Next button. Figure 7: New Project - Add Sources Page 8 of 71

9 Add Existing IP. No Existing IP are required to be added at this stage. Click on the Next button. Figure 8: New Project - Add Existing IP (Optional) Page 9 of 71

10 Add Constraints. No constraints are required to be added at this stage. Click on the Next button. Figure 9: New Project - Add Constraints (Optional) Page 10 of 71

11 Select Development Board. Select MicroZed Board. Note: Ensure that Revision F is selected. Click on the Next button. Figure 10: New Project - Default Part Page 11 of 71

12 Project Summary. Click on the Finish button. Figure 11: New Project - New Project Summary Figure 12: Vivado (New Project) Page 12 of 71

13 3.3 Project Settings Tools -> Project Settings. Select General. Select Target language: -> VHDL Click on the OK button. Figure 13: Project Settings - General Page 13 of 71

3.4 Create Processor System 3.4.1 New Block Diagram Flow -> Create Block Diagram.

Click on the Add IP hyperlink. Click on the ZYNQ7 Processing System IP.

14 3.4 Create Processor System New Block Diagram Flow -> Create Block Diagram. Type Design name -> system. Click on the OK button. Click on the Add IP hyperlink. Click on the ZYNQ7 Processing System IP. Press Enter to add IP. Figure 14: Create Block Diagram Figure 15: ZYNQ7 Processing System IP Page 14 of 71

15 ZYNQ7 Processing System block diagram without connections. Figure 16: Vivado Add ZYNQ7 Processing System IP (Complete) Page 15 of 71

16 Make external connections. Click on the Run Block Automation hyperlink. Click on the OK button. Figure 17: Run Block Automation Page 16 of 71

17 Validate Design. Tools -> Validate Design Figure 18: Vivado ZYNQ7 Processing System IP (Run Block Automation Complete) Click on the OK button. Figure 19: Validate Design Page 17 of 71

Right click and select Generate Output Products.

18 3.5 Generate Output Products Click on the Sources tab in the Sources window and select system block diagram. Right click and select Generate Output Products. Click on the Generate button. Click on the OK button. Figure 20: Generate Output Products Figure 21: Generate Output Products (Complete) Page 18 of 71

19 3.6 HDL Wrapper Click on the Sources tab in the Sources window and select system block diagram. Right click and select Generate Output Products. Click on the Copy generated wrapper to allow user edits radio button to select. Click on the OK button. Click on the OK button. Figure 22: Create HDL Wrapper Figure 23: Create HDL Wrapper (Complete) Page 19 of 71

20 HDL Wrapper. Figure 24: Vivado - HDL Wrapper Page 20 of 71

Figure 25: Vivado Missing Synthesis Results Click on the Generate Bitstream radio button to select.

21 3.7 Implement Design Flow -> Run Implementation Vivado lets the user know if any dependent sources are missing or out of date. Click on the OK button. Figure 25: Vivado Missing Synthesis Results Click on the Generate Bitstream radio button to select. Figure 26: Implementation Completed Click on the Open Implemented Design radio button to select. Click on the OK button. Figure 27: Bitstream Generation Completed Page 21 of 71

22 Take a few moment to explore the implemented design in the Device window. Figure 28: Vivado - Implemented Design Page 22 of 71

23 3.8 Export Hardware Export hardware to SDK. File -> Export Hardware Click on the Include bitstream check box to select. Click on the OK button. Figure 29: Export Hardware Page 23 of 71

24 3.9 Launch SDK File -> Launch SDK Click on the OK button. Figure 30: Launch SDK Figure 31: SDK Project Page 24 of 71

25 4 SDK Project 4.1 New Application Project Hello File -> Application Project Type Project name -> hello. Click on the Next button. Figure 32: Hello Application Project Page 25 of 71

26 Select Hello World template. Click on the Finish button. Figure 33: Templates - Hello World Page 26 of 71

27 4.1.2 Bootloader File -> Application Project Type Project name -> zynq_fsbl. Click on the Next button. Figure 34: Bootloader Application Project Page 27 of 71

28 Select Zynq FSBL template. Click on the Finish button. Figure 35: Templates - Zynq FSBL Page 28 of 71

4.1.3 Bootloader debug flags Set Debug flags for zynq_fsbl. Select the zynq_fsbl application in the Project Explorer window, right click and select Properties.

29 4.1.3 Bootloader debug flags Set Debug flags for zynq_fsbl. Select the zynq_fsbl application in the Project Explorer window, right click and select Properties. Select C/C++ Build -> Settings Select Tool Settings tab. Select ARM gcc compiler -> Debugging Type -DFSBL_DEBUG_INFO=1 for Other debugging flags. Figure 36: "zynq_fsbl" properties Page 29 of 71

5 PetaLinux 5.1 Hardware Platform The PetaLinux hardware platform requires the following: TTC External memory controller with atleast 32MB of memory eg.

30 5 PetaLinux 5.1 Hardware Platform The PetaLinux hardware platform requires the following: TTC External memory controller with atleast 32MB of memory eg. DDR3 UART (Optional) Non-volatile memory Ethernet (Optional). The hardware platform created in Vivado Project exceeds all requirements. Figure 37: Zynq Block Diagram Page 30 of 71

5.2 Petalinux project The Vivado project was created in the basic_test directory. In the basic_test directory create a sub-directory called petalinux.

31 5.2 Petalinux project The Vivado project was created in the basic_test directory. In the basic_test directory create a sub-directory called petalinux. $ mkdir petalinux Figure 38: Create petalinux sub-directory Create a new PetaLinux project from a default template. $ petalinux-create --type project --template zynq --name MicroZed_PetaLinux Note: MicroZed_PetaLinux is the PetaLinux project directory <plnx-proj-root>. Figure 39: Create PetaLinux project directory MicroZed_PetaLinux Page 31 of 71

32 5.3 Import Hardware Description Change directory to the PetaLinux project directory <plnx-proj-root>. /home/syfer/projects/basic_test/petaliux/microzed_petalinux $ petalinux-config --get-hwdescription=/home/syfer/projects/basic_test/basic_test.sdk/system_wrapper_hw_platform_0 The linux System Configuration windows will open the first time that petalinux-config --get-hwdescription=/home/syfer/projects/basic_test/basic_test.sdk/system_wrapper_hw_platform_0 is run. To open the linux System Configuration window again use petalinux-config. The linux System Configuration will be examined in a later section. Use the right arrow key to select <Exit>. Press the Enter key. Select <Yes>. Press the Enter key. Figure 40: Linux System Configuration Figure 41: Linux System Configuration (Complete) Page 32 of 71

33 Figure 42: Import hardware configuration Page 33 of 71

34 5.4 Linux System Configuration $ petalinux-config Figure 43: PetaLinux Linux System Configuration Use the down arrow key to select Subsystem AUTO Hardware Settings. Press the Enter key. Figure 44: Linux System Configuration Linux System Configuration Page 34 of 71

35 Use the down arrow key to select Advanced bootable image storage Settings. Press the Enter key. Figure 45: Linux System Configuration Subsystem AUTO Hardware Settings Page 35 of 71

36 Use the down arrow key to select boot image settings. Press the Enter key. Figure 46: Linux System Configuration Advanced bootable images storage Settings Page 36 of 71

37 Micro SD is selected as the primary storage media for BOOT.BIN. This can be changed to FLASH eg. QSPI. Leave setting unchanged. Use the right arrow key to select <Exit> then press the Enter key. Figure 47: Linux System Configuration boot image settings Page 37 of 71

38 Use the down arrow key to select kernel image settings. Press the Enter key. Figure 48: Linux System Configuration Advanced bootable images storage Settings Page 38 of 71

39 Micro SD is selected as the primary storage media for image.ub. This can be changed to FLASH eg. QSPI. Leave setting unchanged. Use the right arrow key to select <Exit> then press the Enter key. Figure 49: Linux System Configuration Kernel image settings Exit Linux System Configuration. Use the right arrow key to select <Exit> then press the Enter key. Use the right arrow key to select <Exit> then press the Enter key. Use the right arrow key to select <Exit> then press the Enter key Page 39 of 71

40 Figure 50: Linux System Configuration (Complete) Page 40 of 71

5.5 Device Tree Configuration The device tree is a simple tree structure of nodes and properties. Device tree configuration files are located in <plnx-proj-root>/subsystems/linux/configs/device-tree.

41 5.5 Device Tree Configuration The device tree is a simple tree structure of nodes and properties. Device tree configuration files are located in <plnx-proj-root>/subsystems/linux/configs/device-tree. pcw.dtsi, pl.dtsi, skeleton.dtsi, system-conf.dtsi and zynq-7000.dtsi are automatically generated and should not be modified. Changes should only be made to system-top.dts. / is a single root node Every node has a compatible property. The & is used to reference an existing node. This section details gem0 nodes only pcw.dtsi No include files. Contains gem0 node name reference for the ethernet node. Figure 51: Device Tree pcw.dtsi Page 41 of 71

5.5.2 pl.dtsi No include files. 5.5.3 skeleton.dtsi No include files. 5.5.4 system-conf.dtsi Includes "skeleton.dtsi", "zynq-7000.

42 5.5.2 pl.dtsi No include files skeleton.dtsi No include files system-conf.dtsi Includes "skeleton.dtsi", "zynq-7000.dtsi", "pcw.dtsi" and "pl.dtsi". Contains gem0 node name reference for the ethernet node. Figure 52: Device Tree system-conf.dtsi Page 42 of 71

43 5.5.5 zynq-7000.dtsi Include "skeleton.dtsi". Contains gem0 node name reference for the ethernet node. Figure 53: Device Tree zynq-7000.dtsi Page 43 of 71

44 5.5.6 system-top.dts Includes "system-conf.dtsi". gem0 node name reference for the ethernet node with child node phy. Figure 54: Device Tree system-top.dts Page 44 of 71

45 5.5.7 ethernet The Avnet MicroZed uses the Marvell 88E1512.The most significant 4 bits of the address are internally set to The least significant bit is configured by a pin during hardware reset. For Avnet MicroZed the least significant bit is 0. Therefore, the PHY address for Avnet MicroZed is 0. Note: LED behaviour can be changed by using reg-init. Refer to Marvell 88E1512 Datasheet for further details. The default LED behaviour is: Function YELLOW GREEN No Link Off Off 10Mbps Solid - On Blink - Activity 100Mbps Solid - On Blink - Activity 1000Mbps Solid - On Blink - Activity Table 2: LED Behaviour The example given on page 94 of UG1144 (v2014.4) November 25, 2014 can be used as a starting point for system-top.dts. Figure 55: Example system-top.dts Page 45 of 71

46 system-conf.dtsi includes zynq-7000.dtsi and pcw.dtsi. system-top.dts includes system-conf.dtsi. This means that property names and values from the four files are combined based on node name labels. Where Black = zynq-7000.dtsi, Red = systemtop.dts and Green = system-conf.dtsi. Blue = pcw.dtsi. gem0: ethernet@e000b000 { compatible = "xlnx,ps7-ethernet-1.00.a"; reg = <0xe000b000 0x1000>; status = "disabled"; interrupts = <0 22 4>; clocks = <&clkc 13>, <&clkc 30>; clock-names = "ref_clk", "aper_clk"; local-mac-address = [00 0a ]; xlnx,has-mdio = <0x1>; #address-cells = <1>; #size-cells = <0>; }; + &gem0 { phy-mode = "rgmii-id"; status = "okay"; xlnx,ptp-enet-clock = <0x69f6bcb>; ps7_ethernet_0_mdio: mdio { #address-cells = <1>; #size-cells = <0>; }; + &gem0 { local-mac-address = [00 0a c 46]; }; + &gem0 { phy-handle = <&phy0>; phy-mode = "rgmii-id"; ps7_ethernet_0_mdio: mdio { phy0: phy@0 { compatible = "marvell,88e1510"; device_type = "ethernet-phy"; reg = <0>; } ; } ; }; Figure 56: Device Tree files (ethernet) Page 46 of 71

47 = gem0: { compatible = "xlnx,ps7-ethernet-1.00.a"; reg = <0xe000b000 0x1000>; status = "okay"; interrupts = <0 22 4>; clocks = <&clkc 13>, <&clkc 30>; clock-names = "ref_clk", "aper_clk"; local-mac-address = [00 0a c 46]; xlnx,has-mdio = <0x1>; #address-cells = <1>; #size-cells = <0>; phy-mode = "rgmii-id"; status = "okay"; xlnx,ptp-enet-clock = <0x69f6bcb>; phy-handle = <&phy0>; ps7_ethernet_0_mdio: mdio { #address-cells = <1>; #size-cells = <0>; phy0: phy@0 { compatible = "marvell,88e1510"; device_type = "ethernet-phy"; reg = <0>; } ; }; }; Figure 57: Device Tree (ethernet combined) Page 47 of 71

template hello.c in /home/syfer/projects/basic_test/petalinux/microzed_petalinux/components/apps/ Change directory to hello.

48 5.6 Create Application Create user application hello. $ petalinux-create --t apps --template c --name hello --enable Figure 58: Custom Application hello Note: PetaLinux creates a template hello.c in /home/syfer/projects/basic_test/petalinux/microzed_petalinux/components/apps/ Change directory to hello.c template. $ cd components/apps/hello Open hello.c with gedit. Figure 59: Custom Application Change directory to hello.c template Figure 60: Custom Application Open hello.c with gedit Page 48 of 71

49 PetaLinux c template. Modify hello.c. Save file and exit. Figure 61: Custom Application hello.c template Figure 62: Custom Application hello.c modified Page 49 of 71

50 5.7 Linux/Rootfs Configuration $ petalinux-config -c rootfs Figure 63: Linux/Rootfs Configuration Use the down arrow key to select Apps then press the Enter key. Figure 64: Linux/Rootfs Configuration - Linux/Rootfs Configuration Page 50 of 71

51 Ensure that hello is marked with *. Use the down arrow key to select hello then press the Enter key. Figure 65: Linux/Rootfs Configuration Apps Page 51 of 71

Figure 66: Linux/Rootfs Configuration hello Figure 67: Linux/Rootfs Configuration

52 Exit Linux/Rootfs Configuration. Use the right arrow key to select <Exit> then press the Enter key. Use the right arrow key to select <Exit> then press the Enter key. Use the right arrow key to select <Exit> then press the Enter key. Figure 66: Linux/Rootfs Configuration hello Figure 67: Linux/Rootfs Configuration (Complete) Page 52 of 71

53 5.8 Build system image Generate system image image.ub. petalinux-build will build the system image including the application hello. Change directory to the PetaLinux project directory <plnx-proj-root>. /home/syfer/projects/basic_test/petaliux/microzed_petalinux $ petalinux-build Note: If the build fails check /home/syfer/projects/basic_test/petalinux/microzed_petalinux/build/build.log. Figure 68: petalinux-build Page 53 of 71

54 Figure 69: petalinux-build (Complete) Page 54 of 71

quicker using: $ petalinux-build -c rootfs/hello Note: If the build fails check

55 5.9 Build Application petalinux-build will build the system image including the application hello. If the application hello is changed after running petalinux-build then it can be built into the system image considerably quicker using: $ petalinux-build -c rootfs/hello Note: If the build fails check /home/syfer/projects/basic_test/petalinux/microzed_petalinux/build/build.log. $ petalinux-build -x package Figure 70: petalinux-build c rootfs/hello Figure 71: petalinux-build -x package Page 55 of 71

56 5.10 Software Testing Linux Kernel Image Boot the most recent Linux image in the QEMU. Change directory to the PetaLinux project directory <plnx-proj-root>. /home/syfer/projects/basic_test/petaliux/microzed_petalinux $ petalinux-boot --qemu --kernel Figure 72: petalinux-boot Page 56 of 71

57 Type root for login. Type root for Password. Type hello to run the hello application. Press ctrl+a, then x to exit. Figure 73: petalinux-boot (complete) Page 57 of 71

58 5.11 Generate Boot Image for Zynq Generate BOOT.BIN. Change directory to the PetaLinux project directory <plnx-proj-root>. /home/syfer/projects/basic_test/petaliux/microzed_petalinux $ petalinux-package --force --boot --fsbl /home/syfer/projets/basic_test/basic_test.sdk/zynq_fsbl/debug/zynq_fsbl.elf -- fpga /home/syfer/projects/basic_test/basic_test.sdk/system_wrapper_hw_platform_0/system_wra pper.bit --u-boot Figure 74: petalinux-package generate BOOT.BIN Page 58 of 71

59 6 Configure Host Network Adaptor An additional Gigabit Network Adapter is required. The network adapter will be configured with a fixed IP address. Start -> Control Panel Click on the View network status and tasks hyperlink. Figure 75: Windows 7 - Control Panel Page 59 of 71

60 Click on the Local Area Connection 2 hyperlink. Click on the Properties button Figure 76: Windows 7 Network an Sharing Center Figure 77: Windows 7 Local Area Connection 2 Status Page 60 of 71

Click on the OK button. Click on the Close button.

61 Select Internet Protocol Version 4 (TCP/IPv4) Click on the properties button. Set IP address: -> Set Subnet mask: -> Click on the OK button. Click on the OK button. Click on the Close button. Figure 78: Windows 7 Local Area Connection 2 Properties Figure 79: Windows 7 Internet Protocol Version 4 (TCP/IPv4) Properties Page 61 of 71

62 7 Enable Telnet in Windows 7 Host Start -> Control Panel Click on the Programs hyperlink. Figure 80: Windows 7 Control Panel Click on the Turn Windows features on or off hyperlink. Figure 81: Windows 7 Programs Page 62 of 71

63 Click on the Telnet Client check box to select. Figure 82: Windows 7 Turn Windows features on or off Figure 83: Windows 7 System change Page 63 of 71

$bin /media/sf_vbox Figure 84: Copy BOOT.BIN and image.ub Copy I:\syfer\Vbox\BOOT.BIN and image.ub to the Micro SD card. 8.2 Set Avnet MicroZed Development Board Boot Mode Disconnect power from the Avnet MicroZed Development Board.$

64 8 Booting from Micro SD card 8.1 Micro SD card preparation The Micro SD card must be formatted as FAT32. Copy BOOT.bin from $HOME/projects/basic_test/petalinux/MicroZed_PetaLinux/images/linux to /media/sf_vbox. Copy image.ub from $HOME/projects/basic_test/petalinux/MicroZed_PetaLinux/images/linux to /media/sf_vbox. $ cp /home/syfer/project/basic_test/basic_test.sdk/hello/bootimage/boot.bin /media/sf_vbox Figure 84: Copy BOOT.BIN and image.ub Copy I:\syfer\Vbox\BOOT.BIN and image.ub to the Micro SD card. 8.2 Set Avnet MicroZed Development Board Boot Mode Disconnect power from the Avnet MicroZed Development Board. Insert Micro SD card into Avnet MicroZed Development Board Micro SD card connector J6. Set the Avnet MicroZed Development Board Boot Mode to Micro SD. JP3=2,3 JP2=2,3 Jp1=1,2 Figure 85: Boot Mode Page 64 of 71

Configure HyperTerminal with settings 115200/8/n/1/n. Figure 86: HyperTerminal 8.

65 8.3 Configure HyperTerminal Connect USB cable to PC and Avnet MicroZed Development Board J2. On the Windows 7 Host open HyperTerminal. Configure HyperTerminal with settings /8/n/1/n. Figure 86: HyperTerminal 8.4 Reset Avnet MicroZed Development Press SW2 on the Avnet MicroZed Development Board to reset the PS. Figure 87: HyperTerminal - FSBL Page 65 of 71

66 Type root for login. Type root for Password. Figure 88: HyperTerminal FSBL to U-Boot Handoff Figure 89: HyperTerminal PetaLinux login Page 66 of 71

67 9 Network connection Test that there is a network connection between Windows 7 host and Avnet MicroZed. 9.1 Ping Configure Avnet MicroZed IP address ~# ifconfig eth ~# ifconfig Figure 90: HyperTerminal ifconfig Figure 91: HyperTerminal ifconfig (updated) Page 67 of 71

$Start - > (type cmd) C:\ ping 10$ .10.1.10 Figure 92: Cmd Ping (Success) Un-plug Ethernet

68 9.1.2 Cmd tool Windows 7 Host. Start - > (type cmd) C:\ ping Figure 92: Cmd Ping (Success) Un-plug Ethernet cable and observe xemacps e000b000.ethernet: link down message. Figure 93: HyperTerminal Link Down Page 68 of 71

69 Observe that ping fails. C:\ ping Figure 94: Cmd Ping (Fail) Page 69 of 71

$9.2 Telnet Windows 7 Host. C:\ telnet 10.10.1.10 Type root for Login. Type root for Password. Write telnet test to log.$

70 9.2 Telnet Windows 7 Host. C:\ telnet Type root for Login. Type root for Password. Write telnet test to log.txt ~# echo telnet test > log.txt View contents of log.txt ~# more log.txt Type exit to quit Telnet connection. Figure 95: Cmd Telnet Figure 96: HyperTerminal Page 70 of 71

9.3 Web Server Windows 7 Host. Open Internet Explorer. http://10.

71 9.3 Web Server Windows 7 Host. Open Internet Explorer. Figure 97: Internet Explorer Page 71 of 71

10/02/2015 PetaLinux Image with Custom Application

10/02/2015 PetaLinux Image with Custom Application Contents 1 History... 3 2 Introduction... 3 3 Vivado Project... 4 3.1 Open Vivado... 4 3.2 New Project... 5 3.3 Project Settings... 13 3.4 Create Processor System... 14 3.4.1 New Block Diagram... 14 3.5