ML507 Embedded Development Platform

Transcription

1 Application Note: Embedded Processing XAPP1114 (v1.2) January 16, 2009 Application Note: VxWorks 6.x on the ML507 Embedded Development Platform Author: Brian Hill Abstract This application note discusses the use of Wind iver VxWorks eal-time Operating System (TOS) on a Xilinx ML507 board. Included Systems Included with this application note is one reference system: xapp1114.zip Introduction The use of the Wind iver VxWorks eal-time Operating System (TOS) on the Virtex -5 FPGA with the embedded PowerPC processor is a good choice for high performance FPGA designs. The introduction of the Wind iver Workbench design environment has provided designers with a new and easier way to control the configuration of the VxWorks kernel. This guide outlines the steps required to build and configure a ML507 Embedded Development Platform to boot and run the VxWorks TOS. A VxWorks bootloader is created, programmed into Flash, and used to boot the design. The concepts presented here can be scaled to any PowerPC processor-enabled development platform. Hardware and Software equirements eference System Specifics The hardware and software requirements are: Xilinx ML507 Development Board Xilinx Platform USB Cable or Parallel IV Cable S232 Cable Ethernet Cable Serial Communications Utility Program (such as, HyperTerminal) Xilinx Platform Studio Xilinx ISE Wind iver Workbench Wind iver Probe / ICE Adaptor from Wind iver Dual Header to the Xilinx Parallel IV cable ribbon connector. This adaptor must be purchased separately. A license for Wind iver multi-core debugging for the Probe/ICE The included ML507 system was created with Base System Builder. The system includes a PowerPC 440 processor, PowerPC 440 Memory Controller (PPC 440MC), XPS GPIO connected to on-board LEDs and push button switches, XPS Interrupt Controller, XPS LL TEMAC Ethernet controller, XPS UAT 16550, XPS Multi-Channel External Memory controller (MCH EMC) connected to on-board flash. The system address map is shown in Table Xilinx, Inc. All rights reserved. XILINX, the Xilinx logo, and other designated brands included herein are trademarks of Xilinx, Inc. All other trademarks are the property of their respective owners. XAPP1114 (v1.2) January 16,

2 Executing the eference System Address Map Table 1: eference System Address Map Instance Peripheral Base Address High Address DD2_SDAM ppc440mc_ddr2 0x x0FFFFFFF LEDs_8Bit xps_gpio 0x x8140FFFF Push_Buttons_5Bit xps_gpio 0x x8142FFFF IIC_EEPOM xps_iic 0x x8160FFFF xps_intc_0 xps_ints 0x x8180FFFF Hard_Ethernet_MAC xps_ll_temac 0x81C x81C0FFFF S232_Uart_1 xps_uart_ x83E x83E0FFFF FLASH xps_mch_emc 0xFE xFFFFFFFF Executing the eference System The bitstreams for the system are available in the ready_for_download/ directory under the project root directory. Executing the eference System using the Pre-Built Bitstream and the Compiled Software Applications To execute the system using files in the ready_for_download/ directory in the project root directory, follow these steps: 1. Change directories to the ready_for_download directory. 2. Connect the Xilinx download cable to the board. 3. Use impact to download the bitstream by using the following command: impact -batch xapp1114.cmd 4. Invoke XMD and connect to the processor by using the following command: xmd -opt xapp1114.opt 5. Download the executables by using the following command: dow <executable> Executing the eference System from XPS To execute the system using EDK, follow these steps: 1. Open system.xmp in EDK. 2. Select Hardware Generate Bitstream to generate a bitstream for the system. 3. Select Device Configuration Download Bitstream to download the bitstream to the board. 4. Select Debug Launch XMD.. to launch XMD. 5. Download the executables by the using following command: dow <executable> Console Connection Connect a serial cable to the S232 port on the ML507 board. Configure the terminal application, such as HyperTerminal to: 9600 BPS, 8 Data Bits, No Parity, 1 Stop Bit, and No Flow Control. XAPP1114 (v1.2) January 16,

3 Create and Modify the BSP Create and Modify the BSP Use XPS to create a VxWorks Board Support Package (BSP) that is specific to the design provided with this application note by following the subsequent steps: 1. In XPS, choose Software Software Platform Settings: a. OS selection of ppc440_0 is changed in Software Platform to vxworks6_5 version 1.01a. b. Change the STDIN and STDOUT settings in OS and Libraries to S232_UAT_1. c. Add the S232_UAT_1 and Hard_Ethernet_MAC to the connected peripherals list in the VxWorks settings. 2. The VxWorks Board Support Package (BSP) is generated using Software Generate Libraries and BSPs. 3. Create a directory in the EDK project called modified_vxworks_bsp. 4. Copy the contents of the <edk_project_dir>\ppc440_0\bsp_ppc440_0 directory to the modified_vxworks_bsp directory. 5. Edit the modified_vxworks_bsp\config.h file to reflect the addresses applicable to a given system. The changes shown in bold below reflect the system supplied with this application note: Note: The value of OM_BASE_ADS matches the base address of the xps_mch_emc peripheral chosen by Base System Builder for the system included with this application note. Enter the value appropriate to the particular system. Note: The value of OM_TEXT_ADS is where the bootrom image is programmed within the flash. This address is chosen so that the end of this image will be exactly at the end of the processor address space, where the boot vector is located (0xFFFFFFFC). /* memory configuration */ #define LOCAL_MEM_LOCAL_ADS 0 #undef LOCAL_MEM_AUTOSIZE /* no run-time memory sizing */ #define LOCAL_MEM_SIZE 0x /* TODO: fixed memory size */ #define USE_ESEVED_MEM 0 /* see sysmemtop() */ #define OM_BASE_ADS 0xFE /* base address of OM */ #define OM_SIZE 0x /* 1MB OM image */ #define OM_TEXT_ADS ((0xFFFFFFFF - OM_SIZE) + 1) /* with PC & SP */ #define OM_WAM_ADS (OM_TEXT_ADS+4) /* warm reboot entry */ #define AM_HIGH_ADS 0x00C00000 /* AM address for bootrom */ #define AM_LOW_ADS 0x /* AM address for vxworks */... #define CONSOLE_BAUD_ATE 9600 /* console baud rate */ 6. Edit the modified_vxworks_bsp\makefile file to reflect the changes highlighted in bold red type below: OM_TEXT_ADS= FFF00000 # OM cold entry address OM_WAM_ADS= FFF00004 # OM warm entry address OM_SIZE= # number of bytes of OM space AM_LOW_ADS= # AM text/data address for vxworks AM_HIGH_ADS= 00C00000 # AM text/data address for bootrom XAPP1114 (v1.2) January 16,

4 Configure and Build a VxWorks Kernel Image Figure 1 shows how OM_BASE_ADS, AM_HIGH_ADS, AM_LOW_ADS, etc., are used in VxWorks bootloading process. X-ef Target - Figure 1 AM OM_BASE_ADS OM AM_LOW_ADS VXWOKS IMAGE NETWOK OM_TEXT_ADS eset Vector OM IMAGE AM_HIGH_ADS OM IMAGE COPY X1114_01_ Figure 1: Bootloading Process 7. Edit the modified_vxworks_bsp\hwconf.c file to reflect the MAC address of the target board. The Ethernet MAC address on the ML507 is printed on a sticker under the board. An example for the Ethernet MAC address 00-0A is shown: static char MacAddrDft0[6] = { 0x00, 0x0A, 0x35, 0x01, 0x23, 0x45 }; 8. Edit the modified_vxworks_bsp\ppc440_0.h to reflect the desired TLB configuration for this system. Caching is enabled for 0xF (FLASH). This will make the bootloader start much faster. The modifications are highlighted in red: #define BOOT_TLB_W 0x0000 /* 1-write through cache, 0-copy back */ #define BOOT_TLB_I 0xFFFE /* 1-cache inhibited, 0-cache enabled */ #define BOOT_TLB_G 0xFFFF /* 1-guarded, 0-not guarded */ #define BOOT_TLB_E 0x0000 /* 1-little endian, 0-big endian */ Configure and Build a VxWorks Kernel Image The modified VxWorks BSP is used with Wind iver Workbench to create a VxWorks kernel image using the following instructions: 1. The Wind iver Workbench tool is run. If prompted, choose Start, then Workbench at the main screen. Create a location for the workspace in the <edk_project>\windriver_workspace directory. 2. In the Project Explorer pane on the left of the screen, right-click and choose New VxWorks Image Project. Assign the project name ml507_vxworks_image, and choose to create the project within the workspace. Choose to base the project upon a board support package and then browse to the modified_vxworks_bsp directory. Set the tool chain to either sfgnu or sfdiab. Note: The user may select gnu or diab for designs which utilize an FPU. Click Finish. A project appears in the left hand Project Explorer pane, and the BSP will be analyzed by the tool. 3. Expand the project tree in the Project Explorer pane and double-click the Kernel Configuration submenu item. A hierarchical tree appears in the center window. The items in bold signify that they are included in the kernel, and the ones in standard text can be added by the user. To add and remove items from the kernel, right-click the item in question XAPP1114 (v1.2) January 16,

5 Configure and Build a VxWorks Kernel Image and select the Include (quick include) or Exclude (quick exclude) options. Configure the kernel as follows: Include development tool components kernel shell components Include development tool components WDB agent components Include development tool components WDB agent components select WDB mode WDB system debugging 4. Close the component configuration window and save the changes. 5. In the Project Explorer pane, right-click on the ml507_vxworks_image project and select Build Project. The kernel is built and Build Finished appears at the bottom of the screen in the Build Console pane. 6. Ensure that the board is powered, then configure the board using the Device Configuration Download Bitstream menu option in XPS. Check that the DONE LED on the target is illuminated. 7. Unplug the Xilinx Download cable from the target board, then connect the Wind iver Probe/ICE to the same socket using the 14-pin adapter. 8. From the Wind iver Workbench tool, configure a target server to connect to the board via the Wind iver Probe / ICE debug cable. The ML507 board has a combined JTAG chain, therefore a BD file must be specified to enable the Wind iver tools to correctly connect to the board. Select the Board File radio button, then browse to the BD file representing the ML507 board. A board file ml507.brd is provided in the <edk_project_dir>\workbench_ml507 directory. The user may wish to copy this to the Wind iver installation in the <windriver_installation>\workbench- 3.0\ocd\0127m\BoarFiles\PowerPC\4xx\Xilinx directory. X-ef Target - Figure 2 ight-click in the emote Systems window and select New Connection or click on the New Connection icon as shown in Figure 2. X1114_02_ Figure 2: New OCD Connection XAPP1114 (v1.2) January 16,

6 Configure and Build a VxWorks Kernel Image As shown in Figure 3, choose the type of cable that is available, then click Next. X-ef Target - Figure 3 X1114_03_ Figure 3: OCD Probe Selection As shown in Figure 4, select the Board File radio button, then browse to the BD file representing the ML507 board. This file, ml507.brd, is in the <edk_project_dir>\workbench_ml507\ directory. X-ef Target - Figure 4 X1114_04_ Figure 4: New Connection Configuration XAPP1114 (v1.2) January 16,

7 Configure and Build a VxWorks Kernel Image Click Next or Finish. The tools connect to the board. The status of Connected is shown next to the target connection in the emote Systems pane. If the connection is not automatically invoked, right-click the connection, then select Connect. 9. Download the VxWorks kernel image to the board. In the hierarchical tree next to the target connection, a processor instance is shown. ight-click on this line, choose eset and Download, then make the selections shown in Figure 5. X-ef Target - Figure 5 Ensure that the eset option checked in the reset section of the eset and Download tab. Select Playback file in the Script section of the eset and Download tab. The file ml507_ppc440.reg is selected from the <edk_project_dir>\workbench_ml507\ directory. This file contains text commands for the OCD Command Shell. It will correctly set up the PPC440 TLB so that the debugger can access the system memories for downloading vxworks images and programming the parallel flash. Note: This file applies only to the address map of the provided system and must be modified for any other address map. X1114_05_ Figure 5: eset Actions Click Add Files in the Download section of the eset and Download tab, then browse to the <edk_project>\windriver_workspace\ml507_vxworks_image\default\v xworks file within the project. This is the kernel image that was previously created. See Figure 6. X-ef Target - Figure 6 X1114_06_ Figure 6: Download File Selection XAPP1114 (v1.2) January 16,

8 Create a VxWorks Boot Loader Select the un to End of Program in the un Options tab shown in Figure 7, then click Apply. X-ef Target - Figure 7 X1114_07_ Figure 7: un to End of Program Selection Click the Debug button. The VxWorks image is downloaded to the target, then run on the processor. The VxWorks banner appears on the UAT terminal. A working VxWorks image that is suitable for use on the ML507 board has been created. 10. ight click on the connection entry in the emote Systems pane, then click Disconnect to terminate the Wind iver debug connection. Create a VxWorks Boot Loader Program the Boot Loader into the Flash with the Wind iver Probe A VxWorks bootloader is a special build of VxWorks used to load the general VxWorks kernel at boot time over the network. Use the sequence below to generate a bootloader image. 1. In the Wind iver Workbench Project Explorer pane on the left of the screen, right click on New VxWorks Boot loader Project. Assign the project name, for example, ml507_vxworks_bootloader, then click Next. Choose the modified_vxworks_bsp Board Support Package which was created earlier. Choose the image style of Uncompressed from the drop-down list. Choose the format of Bin from the drop-down list. Click Finish. 2. ight-click the newly created project, then choose Build Project from the menu options. The boot loader is built and a Build Finished is displayed the bottom of the screen in the Build Console pane. The bootloader is most useful when programmed into flash. Use the following sequence to place the bootloader into the on board flash: 1. Wind iver Workbench includes utilities for programming flash devices. To access this functionality, reconnect to the target board using the Wind iver debug cable. 2. ight-click on the processor instance and choose the Attach to Core option. If this option can not be selected Workbench is already attached to the CPU core. 3. From the Workbench menus, click Window Open Perspective On-Chip Debug. 4. The bootrom an VxWorks images provided with this application note will enable the processor cache for the flash memory address space. This allows the bootloader to operate much more quickly. The Workbench flash programming procedure requires that the flash address space be uncached to operate properly. The user will play back the XAPP1114 (v1.2) January 16,

9 Program the Boot Loader into the Flash with the Wind iver Probe provided register file <edk_project_dir>\workbench_ml507\ml507_ppc440.reg to ensure that the TLB has been configured properly for flash programming: X1114_08_ X-ef Target - Figure 8 Figure 8: egister File Playback 5. From the Workbench menus, click Window Show View Flash Programmer. 6. At the bottom of the screen, the Flash Programmer pane is visible. Click the Configuration View tab as shown in Figure 9, and choose the Intel 28F256P30T 2048 x 16 1 Device option. This represents the part number, quantity, and configuration of the flash devices on the ML507 board. X-ef Target - Figure 9 X1114_09_ Figure 9: Flash Configuration 7. Enter the base address of 0xFE in the Flash Bank Address box as shown in Figure 9. The high address should be automatically completed by the tool. 8. In the AM Workspace box, ensure that the value is set to the base address of the DD2 SDAM (0x ) as shown in Figure Select the Programming tab. On the right of the window, click the Add File button, then browse to the ml507_vxworks_bootloader\bootrom_uncmp.bin file within the XAPP1114 (v1.2) January 16,

10 Program the Boot Loader into the Flash with the Wind iver Probe windriver_workspace area. After choosing this file, check the box for This is a raw binary file as shown in Figure 10, then Click OK. X-ef Target - Figure 10 X1114_10_ Figure 10: File Conversion Utility 10. Select the Programming tab, then make the selections shown in Figure 11. Check that the sectors of the flash in the Erase Sector Selection window appear, then click the Select All button. 11. Click on the start address field for the file that has just been added to the list. The start address value should be set so that the image will reside at the very end of the flash address space. 0xFFFFFFFC is where the processor boot vector is located, and the last word of this image must fall on this flash location. Because a 1MB image is used in this example, the value is 0xFFF X-ef Target - Figure 11 Figure 11: Location in the Flash to Program the POM File X1114_11_ Note: The Start Address matches OM_TEXT_ADS. XAPP1114 (v1.2) January 16,

11 Program the Boot Loader into the Flash with the Xilinx Flashwriter 12. Note the End address generated by the tool; this indicates the size of the file to be programmed into the flash. 13. Check the Send IN before each operation box in the Flash Programming section of this tab. 14. Select the Programming tab, then select Erase/Program. The flash is now programmed with the bootrom_uncmp.bin image. 15. ight click on the active debug connection in the emote Systems pane, then select Disconnect to terminate the connection to the board. 16. Switch off the power to the ML507 board, then disconnect the Wind iver debug cable. Program the Boot Loader into the Flash with the Xilinx Flashwriter If the user does not have a Wind iver Probe, the Xilinx flashwriter can be used to program the bootloader into the flash. 1. Select Device Configuration Program Flash Memory within EDK. 2. Select the generated bootrom_uncmp.bin as the File To Program. 3. Enter 0x01F in the Program at Offset field. 4. Click OK to program the device. X1114_12_ X-ef Target - Figure 12 Figure 12: Xilinx Flashwriter Note: It is necessary that the standalone BSP be selected in order to utilize the Xilinx Flashwriter utility. XAPP1114 (v1.2) January 16,

12 Test the Boot Loader Test the Boot Loader Configure the Boot Loader To test the boot loader, follow the steps below. 1. e-connect the Xilinx cable and power on the board. 2. Download the bitstream to the ML507 by using Device Configuration Download Bitstream from the Xilinx Platform Studio tool. 3. A status line is printed in the UAT terminal window to indicate that the VxWorks_Start project is running, followed by a pause of a few seconds. The Wind iver boot loader application then runs and begins an automated countdown. 4. Press any key in the UAT terminal window to abort the countdown. The [VxWorks Boot]: prompt is seen. Note: If the auto-boot is not terminated, the system will display the error message, Error loading file:. The boot loader is designed to fetch the main VxWorks kernel image across the network from an FTP server. As part of the BSP, the target board is configured with the IP address of The host is configured with an appropriate IP address, such as An FTP server is configured on the host, and the boot loader application is directed to access the desired VxWorks image. 1. Configure the IP address of the host PC as On the host PC, choose Start All Programs Wind iver VxWorks 6.5 and General Purpose Technologies FTP Server from the Start menu. 3. In the FTP Server application, select Security Users/ights from the menu. 4. Click New User and enter the name, my_ftp_user. 5. Enter pass in both of the password boxes. 6. In the Home Directory box, enter the path to the VxWorks kernel image which will be at <edk_project_dir>\windriver_workspace\ml507_vxworks_image\default, then click Done. 7. In the FTP Server application, select Logging Log options from the menu. Check all of the boxes except Windsock calls, then click OK. 8. In the UAT terminal, type p and press the Enter key to display the current boot loader settings. The settings are similar to those shown below. [VxWorks Boot]: p boot device : lltemac NAME OF ETHENET MAC unit number : 0 ID OF ETHENET MAC processor number : 0 host name : host NOT USED file name : VxWorks NAME OF VXWOKS IMAGE inet on ethernet (e) : IP ADDESS OF TAGET BOAD host inet (h) : IP ADDESS OF HOST PC user (u) : xemhost FTP USE NAME flags (f) : 0x0 NOT USED [VxWorks Boot]: XAPP1114 (v1.2) January 16,

13 Boot Load the Design Some of these parameters must be adjusted. Type c and press Enter in the UAT terminal window; each option is presented individually. To leave the setting at the default value, press Enter in the UAT terminal window. To change the setting, type in the new value. Note: These defaults are defined within DEFAULT_BOOT_LINE in xapp1114/modified_vxworks_bsp/config.h 9. Change the settings to match the ones shown in italics in the text below (only the user name and password must be changed. boot device : lltemac0 processor number : 0 host name : host file name : vxworks inet on ethernet (e) : inet on backplane (b) : host inet (h) : gateway inet (g) : user (u) : my_ftp_user ftp password (pw) : pass flags (f) : 0x0 target name (tn) : startup script (s) : other (o) : Note: These settings will not be saved. VxWorks does not supply a software driver for the flash devices on the ML507 board. Boot Load the Design 1. at the [VxWorks Boot] prompt to boot the design. 2. The boot loader connects to the board, downloads the image via FTP, then runs the VxWorks kernel. Monitor the UAT terminal window and the FTP server log during this time. The bootload process can be observed at each stage. 3. Check that the VxWorks kernel is alive by typing i at the prompt. The currently running tasks are listed. Type version at the prompt to display the version information. [VxWorks boot device : lltemac unit number : 0 processor number : 0 host name : host file name : vxworks inet on ethernet (e) : host inet (h) : user (u) : my_ftp_user ftp password (pw) : pass flags (f) : 0x0 Loading Starting at 0x Target Name: vxtarget lltemac: warning - MII clock is defaulted to 1000 Mbps lltemac: Buffer information: 0x bytes allocated for all buffers 1564 byte cluster size 60 x buffers, 1st buffer located at 0x Tx buffers, 1st buffer located at 0x006A9FA0 0x bytes allocated for all BDs 32 xbds, BD space begins at 0x006AD TxBDs, BD space begins at 0x006AD800 Adding 4838 symbols for standalone. XAPP1114 (v1.2) January 16,

14 Make the Board Standalone Bootable ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] ]]]]]]]]]]] ]]]] ]]]]]]]]]] ]] ]]]] () ] ]]]]]]]]] ]]]]]] ]]]]]]]] ]] ]]]] ]] ]]]]]]] ]]]]]]]] ]]]]]] ] ]] ]]]] ]]] ]]]]] ] ]]] ] ]]]] ]]] ]]]]]]]]] ]]]] ]] ]]]] ]] ]]]]] ]]]] ]]] ]] ] ]]] ]] ]]]]] ]]]]]] ]] ]]]]]]] ]]]] ]] ]]]] ]]]]] ] ]]]] ]]]]] ]]]]]]]] ]]]] ]] ]]]] ]]]]]]] ]]]] ]]]]]] ]]]]] ]]]]]] ] ]]]]] ]]]] ]] ]]]] ]]]]]]]] ]]]] ]]]]]]] ]]]]] ] ]]]]]] ] ]]] ]]]] ]] ]]]] ]]]] ]]]] ]]]] ]]]]]]]] ]]]]] ]]] ]]]]]]] ] ]]]]]]] ]]]] ]]]] ]]]] ]]]]] ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] ]]]]]]]]]]]]]]]]]]]]]]]]]]]]] Development System ]]]]]]]]]]]]]]]]]]]]]]]]]]]] ]]]]]]]]]]]]]]]]]]]]]]]]]]] VxWorks 6.5 ]]]]]]]]]]]]]]]]]]]]]]]]]] KENEL: WIND version 2.10 ]]]]]]]]]]]]]]]]]]]]]]]]] Copyright Wind iver Systems, Inc., CPU: Xilinx Virtex5 PPC440x5. Processor #0. Memory Size: 0x BSP version 2.0/0. Created: Jun , 14:15:17 ED& Policy Mode: Deployed WDB Comm Type: WDB_COMM_END WDB: eady. -> i NAME ENTY TID PI STATUS PC SP ENO DELAY tjobtask 776f4 685b28 0 PEND db3dc 6859f0 0 0 texctask 767b8 17f9a8 0 PEND db3dc 181d tlogtask logtask 688ba8 0 PEND d8e60 688a tnbiolog 78da4 68c420 0 PEND db3dc 68c tshell0 shelltask 71a370 1 EADY e320c 71a twdbtask wdbtask 7090b0 3 PEND db3dc 708fb0 0 0 tnettask nettask 690ac0 50 PEND db3dc 6909f0 0 0 ipcom_sysl> b PEND dbb74 6b3e ipnetd f632c 7040f0 50 PEND db3dc value = 0 = 0x0 -> Make the Board Standalone Bootable Throughout this application note, the FPGA has been configured manually. For standalone functionality, the Xilinx Flash POM on the board is programmed with the bitstream, which contains the hardware configuration. To do this, the Xilinx impact tool is used to program the POM. 1. un the Xilinx impact tool. 2. Choose to prepare a POM file by double clicking POM File Formatter. XAPP1114 (v1.2) January 16,

15 Make the Board Standalone Bootable 3. As shown in Figure 13, the location for the POM files to be generated and a file name are chosen. <edk_project_dir>\vxworks_start.mcs is used. Click Next. Note: A previously generated file <edk_project_dir>\ready_for_download\vxworks_start.mcs is provided. X-ef Target - Figure 13 X1114_13_ Figure 13: Prepare the POM Files 4. Select I am using a Xilinx POM in Serial Mode, as shown in Figure 14, then click Next. X-ef Target - Figure 14 X1114_14_ Figure 14: Select the POM Flash Mode XAPP1114 (v1.2) January 16,

16 Make the Board Standalone Bootable 5. Choose the XCF32p POM from the list, then click Add. The POM will appear in the list as shown in Figure 15. Click Next. X-ef Target - Figure 15 X1114_15_ Figure 15: Specify the Xilinx POM Device 6. Impact will prompt for the file to use. If the user has generated a download.bit file as previously instructed, <edk_project_dir>\implementation\download.bit is used. A previously generated bitstream file, <edk_project_dir>\ready_for_download\download.bit is provided as an alternative. 7. Choose No to specify that no other design files are to be added to the POM. 8. Double-click Generate File as shown in Figure 16 to generate the POM file. X-ef Target - Figure 16 X1114_16_ Figure 16: Generate the.mcs POM File XAPP1114 (v1.2) January 16,

17 Make the Board Standalone Bootable 9. Double-click the Boundary Scan icon. ight-click on Initialize Chain as shown in Figure 17. The chain of JTAG devices is automatically detected. X-ef Target - Figure 17 X1114_17_ Figure 17: Initialize JTAG Chain 10. The Add New Configuration File dialog is now displayed for each device on the JTAG chain. The present device icon will appear green. Select BYPASS for all devices except the XCF32P. 11. The file previously prepared by the user <edk_project_dir>\vxworks_start.mcs is chosen for the XCF32P POM. Note: A previously generated file <edk_project_dir>\ready_for_download\vxworks_start.mcs is also available for use. XAPP1114 (v1.2) January 16,

18 Make the Board Standalone Bootable 12. The Device Programming Properties dialog is displayed. Select Verify, Erase Before Programming, and Load FPGA for the XCF32P device as shown in Figure 18. X-ef Target - Figure 18 X1114_18_ Figure 18: Device Programming Properties 13. The XCF32P POM icon is selected. ight click on the device and choose Program As shown in Figure 19. X-ef Target - Figure 19 X1114_19_ Figure 19: Program the XCF32P POM 14. Close impact. 15. emove power from the ML507 board. 16. Disconnect the JTAG cable from the board. 17. Power up the board, and verify that it auto-boots to the Wind iver boot loader screen. XAPP1114 (v1.2) January 16,

19 Configure a Target Server Configure a Target Server The board has been configured to provide Ethernet connectivity. This presents the opportunity to debug the kernel, and any applications running on it, via the network. This functionality is especially useful for use in the software development team, because it removes the necessity for a Wind iver probe to be attached to the host development machine. All software applications that need to be run and debugged on the target can be transferred via Ethernet, meaning that the target board need not be geographically local to the software developers. 1. From the Wind iver Workbench emote Systems, right-click in the pane, then select New Connection. 2. Select Wind iver VxWorks 6.x Target Server Connection from the list, click Next, then make the selection shown in Figure Check that the setting in the Backend field is configured for wdbrpc. 4. Enter the IP address of the board in the Target name / IP Address field. In the provided example, this is Note: This IP address is defined within DEFAULT_BOOT_LINE in xapp1114/modified_vxworks_bsp/config.h 5. Select File in the Kernel Image section, then browse to the <edk_project>\windriver_workspace\ml507_vxworks_image\default\vxwo rks file. Click Next. X-ef Target - Figure 20 X1114_20_ Figure 20: New Target Server Connection 6. Ensure that the Load module symbols.. box is checked, then click Next. XAPP1114 (v1.2) January 16,

20 eferences 7. Click Finish to accept the settings. The connection is automatically started via Ethernet and a VxWorks6x_ entry appears in the emote Systems window. 8. In the emote Systems window, expand the Kernel Tasks tree to view the tasks that are currently running on the kernel as shown in Figure 21. X-ef Target - Figure 21 X1114_21_ Figure 21: Kernel Tasks eferences 1. UG347 ML505/506/507 Evaluation Platform User Guide 2. XAPP548 Getting Started With EDK and Wind iver VxWorks 3. XAPP947 VxWorks 6.x on the ML403 Embedded Development Platform evision History The following table shows the revision history for this document: Date Version Description of evisions 11/5/ Initial Xilinx release. 12/3/ Corrected Test the Boot Loader section error. 1/16/ Modify booloader TLB configuration Notice of Disclaimer Xilinx is disclosing this Application Note to you AS-IS with no warranty of any kind. This Application Note is one possible implementation of this feature, application, or standard, and is subject to change without further notice from Xilinx. You are responsible for obtaining any rights you may require in connection with your use or implementation of this Application Note. XILINX MAKES NO EPESENTATIONS O WAANTIES, WHETHE EXPESS O IMPLIED, STATUTOY O OTHEWISE, INCLUDING, WITHOUT LIMITATION, IMPLIED WAANTIES OF MECHANTABILITY, NONINFINGEMENT, O FITNESS FO A PATICULA PUPOSE. IN NO EVENT WILL XILINX BE LIABLE FO ANY LOSS OF DATA, LOST POFITS, O FO ANY SPECIAL, INCIDENTAL, CONSEQUENTIAL, O INDIECT DAMAGES AISING FOM YOU USE OF THIS APPLICATION NOTE XAPP1114 (v1.2) January 16,