Generate device tree Vivado/SDK/HSI 2015.2

1) Clone git://github.com/Xilinx/device-tree-xlnx.git to device-tree-xlnx
2) Export Hardware from vivado 2015.2
3) Launch SDK 2015.2
4) Add cloned device-tree-xlnx folder to repositories in SDK 2015.2
5) From SDK, File->New->Board Suppor Package. Select device_tree from Board Support Package OS options. Click Finish
6) The following error is displayed in the SDK log:
****** hsi v2015.2 (64-bit)
 **** SW Build 1266856 on Fri Jun 26 16:35:25 MDT 2015
   ** Copyright 1986-2015 Xilinx, Inc. All Rights Reserved.
INFO: [Hsi 55-1698] elapsed time for repository loading 0 seconds
ERROR: [Common 17-161] Invalid option value '' specified for 'object'.
ERROR: [Hsi 55-1545] Problem running tcl command ::sw_device_tree::generate : ERROR: [Common 17-161] Invalid option value '' specified for 'object
   while executing
"get_property BASE_VALUE $ip_mem_handle"
   (procedure "get_baseaddr" line 4)
   invoked from within
"get_baseaddr ${ip} no_prefix"
   (procedure "gen_peripheral_nodes" line 5)
   invoked from within
"gen_peripheral_nodes $drv_handle "create_node_only""
   ("foreach" body line 3)
   invoked from within
"foreach drv_handle [get_drivers] {
       # generate the default properties
       gen_peripheral_nodes $drv_handle "create_node_only"
       gen_r..."
   (procedure "::sw_device_tree::generate" line 3)
   invoked from within
"::sw_device_tree::generate device_tree"
ERROR: [Hsi 55-1442] Error(s) while running TCL procedure generate()
ERROR: [Common 17-39] 'hsi::generate_target' failed due to earlier errors.
----------------------

Hi,
After lookming at my work in the morning, I am afraid the solution requires alot more work than I am willing to delve into. At the very list I can help you with a work around.
In the IP packager
1) Remove IIC interface or other broken interface.
2) Select all ports that used to be grouped in 1) above, right click and select "Create Interface Definition"
3) If the selected ports are part of an input interface (left side of IP) select Slave Mode, and set location to be where your ip is. NOTE! after clicking ok, at the next prompt to create the Interface select NO unless it is one of kind IE you dont need an inteface opposite of the one being created due to selection of pins.
4) Select each port and hopefully your IP follows some of Xilinx's naming conventions e.g one of my IIC ports is int_sda_i and rename it to sda_i. Basically all other data is entered for you, you just have to fix the names of all the ports. This is import for the Auto Infer ports function.
5) save the interface. Do not close it yet. I don't know how to open it again if you need to adjust anything.
6) Now go back to Ports and Interfaces on the Package IP tab and slect the ports you previously selected. Right click and select "Auto Infer Interface"
7) Now go to the User tree and select your Interface definition. It is named what you set it to be in 3) above. Click OK
8) Give your IP a name and set interface presence as desired. As a side note, the example "$my_num_var > 0" does not make it clear that the variable my_num_var is created in "Customization Parameters"
9) If applicable, select the port for the other interface eg output iface and repeat 6), 7), 8)
10) The bad new is that on the side that interfaces with Xilinx IP block e,g IIC_1 on a processing system block you have to wire it up manually but at least you can gropu that mess into a hierachy. The good news is that the other end can be made "external" on the BD so you don't have wires all over the place.
 

Similar Messages

  • SDIO Wifi device tree

    Hi
    I am trying to bring up TI SDIO Wifi module on Zedboard
    I am using this adaptor
    http://zedboard.org/product/wilink-8-adaptor
    with WL1837MODCOM8I (from TI) on zedboard
    I have built the  hardware platform explained in this tutorial
    http://zedboard.org/sites/default/files/documentations/GSG-AES-PMOD-WILINK8-G-v1_6.pdf
    I use Vivado 2015.2 and Petalinux 2014.4 (kernel 3.17)
    I have added the following lines to the device tree generated by Petalinux
         wlcore {
               compatible = "wlcore";
               interrupt-parent = <&intc>;
               irq = <0x0>;
               platform-quirks = <0x1>;
               board-ref-clock = <0x4>;
         fixedregulator@1 {
               compatible = "regulator-fixed";
               regulator-name = "wlan-en-regulator";
               regulator-min-microvolt = <0x325aa0>;
               regulator-max-microvolt = <0x325aa0>;
               gpio = <0x4 0x9 0x4>;
               startup-delay-us = <0x11170>;
               enable-active-high;
               linux,phandle = <0x6>;
               phandle = <0x6>;
    I have also followed this link to build TI’s firmware and wifi tools
    http://processors.wiki.ti.com/index.php/WL18xx_System_Build_Scripts
    Petalinux comes up fine on Zedboard and the high speed SDIO device is recognized. However when I run the following script on Zedboard to configure the module, I encounter an error
     /usr/sbin/wlconf/configure-device.sh
    “missing wlan platform data&colon; -19”
    I went ahead and loaded the module (wl18xx) but no error/warning was given by linux (no message on dmesg)
    I am wondering what is going wrong in my setting that Wifi platform cannot be configured and set up as an Wifi interface

    Replying to say 'me too' and subscribe to the thread.
    I have encountered this issue and find it annoying.
    My designs use many i2c busses and serial ports, too many to fit on the standard 16 IRQs so I use shared OR'ed interrupts - under a Linux kernel. 
    Under petalinux: I override the interrupt and interrupt-parent in system-top.dts.  The device tree generator omits them from pl.dtsi.
     

  • Impossible to program a Kintex-7 with Vivado Lab Edition 2015.[1,2]

    Hello,
    I'm trying to program a Kintex-7 160T with a Platform USB Cable and Vivado Lab Edition 2015.1 and 2015.2. The JTAG chain is shown on the screenshot below:
    It is possible to program very small bitstream (~600KiB). But when the bitstreams become bigger, the configuration fails.
    Configuring the same FPGA on the same board with Impact 14.2 is working.
    How can I configure the FPGA with Vivado Lab Edition?
    Olivier

    For the following tests, I'm using two bitstream files:
    logic.bit:
    Very basic design which sets pins to some values.The file is compressed and its size is 676,383 bytes
    ISE 14.2 has been used to generate it.
    logic_vivado.bit:
    It's our design.
    Its size is 6,692,674 bytes
    Vivado 2014.4 has been used to generate it.
    I'm using two computers for these tests:
    A Windows7 computer with iMPACT 14.2
    A Windows8 computer with Vivado Lab Edition 2015.1
    The same board and the same Platform USB Cable (DLC9) were used.
    For each tool, I'm configuring the "logic.bit" bitstream and then the "logic_vivado.bit" bistream.
    Here is the log of iMPACT 14.2:
    Welcome to iMPACT
    iMPACT Version: 14.2
    // *** BATCH CMD : setMode -bs
    // *** BATCH CMD : setMode -bs
    // *** BATCH CMD : setMode -bs
    // *** BATCH CMD : setMode -bs
    GUI --- Auto connect to cable...
    // *** BATCH CMD : setCable -port auto
    INFO:iMPACT - Digilent Plugin: Plugin Version: 2.4.4
    INFO:iMPACT - Digilent Plugin: no JTAG device was found.
    AutoDetecting cable. Please wait.
    PROGRESS_START - Starting Operation.
    Connecting to cable (Usb Port - USB21).
    Checking cable driver.
    Driver file xusbdfwu.sys found.
    Driver version: src=1027, dest=1027.
    Driver windrvr6.sys version = 10.2.1.0. WinDriver v10.21 Jungo (c) 1997 - 2010 Build Date: Aug 31 2010 x86_64 64bit SYS 14:14:44, version = 1021.
    Cable PID = 0008.
    Max current requested during enumeration is 280 mA.
    Type = 0x0605.
    Cable Type = 3, Revision = 0.
    Setting cable speed to 6 MHz.
    Cable connection established.
    Firmware version = 1100.
    File version of C:/Programs/Xilinx/14.2/ISE_DS/ISE/data/xusbdfwu.hex = 1100.
    Firmware hex file version = 1100.
    PLD file version = 0012h.
    PLD version = 0012h.
    PROGRESS_END - End Operation.
    Elapsed time = 0 sec.
    Type = 0x0605.
    ESN not available for this cable.
    Attempting to identify devices in the boundary-scan chain configuration...
    INFO:iMPACT - Current time: 7/22/2015 5:50:01 PM
    // *** BATCH CMD : Identify -inferir
    PROGRESS_START - Starting Operation.
    Identifying chain contents...'0': : Manufacturer's ID = Xilinx xc7k160t, Version : 0
    INFO:iMPACT:1777 -
    Reading C:/Programs/Xilinx/14.2/ISE_DS/ISE/kintex7/data/xc7k160t.bsd...
    INFO:iMPACT - Using CseAdapterBSDevice
    INFO:iMPACT:501 - '1': Added Device xc7k160t successfully.
    '1': : Manufacturer's ID = Xilinx xcf32p, Version : 13
    INFO:iMPACT:1777 -
    Reading C:/Programs/Xilinx/14.2/ISE_DS/ISE/xcfp/data/xcf32p.bsd...
    INFO:iMPACT:501 - '1': Added Device xcf32p successfully.
    '2': : Manufacturer's ID = Xilinx xcf32p, Version : 13
    INFO:iMPACT:501 - '1': Added Device xcf32p successfully.
    '3': : Manufacturer's ID = Xilinx xcf32p, Version : 13
    INFO:iMPACT:501 - '1': Added Device xcf32p successfully.
    '4': : Manufacturer's ID = Xilinx xc7k70t, Version : 0
    INFO:iMPACT:1777 -
    Reading C:/Programs/Xilinx/14.2/ISE_DS/ISE/kintex7/data/xc7k70t.bsd...
    INFO:iMPACT - Using CseAdapterBSDevice
    INFO:iMPACT:501 - '1': Added Device xc7k70t successfully.
    done.
    PROGRESS_END - End Operation.
    Elapsed time = 1 sec.
    // *** BATCH CMD : identifyMPM
    // *** BATCH CMD : assignFile -p 5 -file "P:/[...]/logic.bit"
    '5': Loading file 'P:/[...]/logic.bit' ...
    done.
    INFO:iMPACT - Using CseAdapterBSDevice
    INFO:iMPACT:2257 - Startup Clock has been changed to 'JtagClk' in the bitstream stored in memory,
    but the original bitstream file remains unchanged.
    UserID read from the bitstream file = 0xFFFFFFFF.
    Data width read from the bitstream file = 4.
    INFO:iMPACT:501 - '5': Added Device xc7k160t successfully.
    INFO:iMPACT - Current time: 7/22/2015 5:50:52 PM
    // *** BATCH CMD : Program -p 5
    PROGRESS_START - Starting Operation.
    Maximum TCK operating frequency for this device chain: 15000000.
    Validating chain...
    Boundary-scan chain validated successfully.
    1: Device Temperature: Current Reading: 65.14 C, Min. Reading: 41.02 C, Max. Reading: 65.63 C
    1: VCCINT Supply: Current Reading: 0.990 V, Min. Reading: 0.987 V, Max. Reading: 0.993 V
    1: VCCAUX Supply: Current Reading: 1.813 V, Min. Reading: 1.790 V, Max. Reading: 1.816 V
    5: Device Temperature: Current Reading: 58.74 C, Min. Reading: 56.28 C, Max. Reading: 59.23 C
    5: VCCINT Supply: Current Reading: 0.987 V, Min. Reading: 0.987 V, Max. Reading: 0.993 V
    5: VCCAUX Supply: Current Reading: 1.811 V, Min. Reading: 1.811 V, Max. Reading: 1.813 V
    INFO:iMPACT - Creating XC7K160T device.
    PROGRESS_START - Starting Operation.
    '5': Programming device...
    Match_cycle = NoWait.
    Match cycle: NoWait
    LCK_cycle = NoWait.
    LCK cycle: NoWait
    done.
    INFO:Cse - Status register values:
    INFO:Cse - 0011 1111 1001 1110 0000 1000 0000 0010
    INFO:Cse - '5': Completed downloading bit file to device.
    INFO:Cse - '5': Programming completed successfully.
    PROGRESS_END - End Operation.
    Elapsed time = 2 sec.
    Match_cycle = NoWait.
    Match cycle: NoWait
    LCK_cycle = NoWait.
    LCK cycle: NoWait
    INFO:iMPACT - '5': Checking done pin....done.
    '5': Programmed successfully.
    // *** BATCH CMD : assignFile -p 5 -file "P:/[...]/logic_vivado.bit"
    '5': Loading file 'P:/AS/OCt/dvk310/as1662/logic_vivado.bit' ...
    done.
    INFO:iMPACT - Using CseAdapterBSDevice
    INFO:iMPACT:2257 - Startup Clock has been changed to 'JtagClk' in the bitstream stored in memory,
    but the original bitstream file remains unchanged.
    UserID read from the bitstream file = 0XFFFFFFFF.
    Data width read from the bitstream file = .
    INFO:iMPACT:501 - '5': Added Device xc7k160t successfully.
    INFO:iMPACT - Current time: 7/22/2015 5:51:22 PM
    // *** BATCH CMD : Program -p 5
    PROGRESS_START - Starting Operation.
    Maximum TCK operating frequency for this device chain: 15000000.
    Validating chain...
    Boundary-scan chain validated successfully.
    1: Device Temperature: Current Reading: 66.13 C, Min. Reading: 41.02 C, Max. Reading: 66.13 C
    1: VCCINT Supply: Current Reading: 0.990 V, Min. Reading: 0.987 V, Max. Reading: 0.993 V
    1: VCCAUX Supply: Current Reading: 1.813 V, Min. Reading: 1.790 V, Max. Reading: 1.816 V
    5: Device Temperature: Current Reading: 58.74 C, Min. Reading: 58.25 C, Max. Reading: 59.23 C
    5: VCCINT Supply: Current Reading: 0.990 V, Min. Reading: 0.990 V, Max. Reading: 0.990 V
    5: VCCAUX Supply: Current Reading: 1.811 V, Min. Reading: 1.790 V, Max. Reading: 1.813 V
    PROGRESS_START - Starting Operation.
    '5': Programming device...
    Match_cycle = NoWait.
    Match cycle: NoWait
    LCK_cycle = NoWait.
    LCK cycle: NoWait
    done.
    INFO:Cse - Status register values:
    INFO:Cse - 0011 1111 1001 1110 0000 1000 0000 0010
    INFO:Cse - '5': Completed downloading bit file to device.
    INFO:Cse - '5': Programming completed successfully.
    PROGRESS_END - End Operation.
    Elapsed time = 15 sec.
    Match_cycle = NoWait.
    Match cycle: NoWait
    LCK_cycle = NoWait.
    LCK cycle: NoWait
    INFO:iMPACT - '5': Checking done pin....done.
    '5': Programmed successfully.
    Now, the log of Vivado 2015.1:
    start_gui
    open_hw
    connect_hw_server
    INFO: [Labtools 27-2285] Connecting to hw_server url TCP:localhost:3121
    INFO: [Labtools 27-2222] Launching hw_server...
    INFO: [Labtools 27-2221] Launch Output:
    ****** Xilinx hw_server v2015.1
    **** Build date : Apr 27 2015-19:25:29
    ** Copyright 1986-1999, 2001-2015 Xilinx, Inc. All Rights Reserved.
    open_hw_target [lindex [get_hw_targets -of_objects [get_hw_servers localhost]] 0]
    INFO: [Labtoolstcl 44-466] Opening hw_target localhost:3121/xilinx_tcf/Xilinx/Port_#0001.Hub_#0005
    current_hw_device [lindex [get_hw_devices] 0]
    refresh_hw_device -update_hw_probes false [lindex [get_hw_devices] 0]
    INFO: [Labtools 27-1434] Device xc7k70t (JTAG device index = 0) is programmed with a design that has no supported debug core(s) in it.
    WARNING: [Labtools 27-3123] The debug hub core was not detected at User Scan Chain 1 or 3.
    Resolution:
    1. Make sure the clock connected to the debug hub (dbg_hub) core is a free running clock and is active OR
    2. Manually launch hw_server with -e "set xsdb-user-bscan <C_USER_SCAN_CHAIN scan_chain_number>" to detect the debug hub at User Scan Chain of 2 or 4. To determine the user scan chain setting, open the implemented design and use: get_property C_USER_SCAN_CHAIN [get_debug_cores dbg_hub].
    current_hw_device [lindex [get_hw_devices] 4]
    refresh_hw_device -update_hw_probes false [lindex [get_hw_devices] 4]
    INFO: [Labtools 27-1435] Device xc7k160t (JTAG device index = 4) is not programmed (DONE status = 0).
    set_property PROBES.FILE {} [lindex [get_hw_devices] 4]
    set_property PROGRAM.FILE {P:/[...]/logic.bit} [lindex [get_hw_devices] 4]
    program_hw_devices [lindex [get_hw_devices] 4]
    INFO: [Labtools 27-3164] End of startup status: HIGH
    refresh_hw_device [lindex [get_hw_devices] 4]
    INFO: [Labtools 27-1434] Device xc7k160t (JTAG device index = 4) is programmed with a design that has no supported debug core(s) in it.
    WARNING: [Labtools 27-3123] The debug hub core was not detected at User Scan Chain 1 or 3.
    Resolution:
    1. Make sure the clock connected to the debug hub (dbg_hub) core is a free running clock and is active OR
    2. Manually launch hw_server with -e "set xsdb-user-bscan <C_USER_SCAN_CHAIN scan_chain_number>" to detect the debug hub at User Scan Chain of 2 or 4. To determine the user scan chain setting, open the implemented design and use: get_property C_USER_SCAN_CHAIN [get_debug_cores dbg_hub].
    set_property PROBES.FILE {} [lindex [get_hw_devices] 4]
    set_property PROGRAM.FILE {P:/[...].bit} [lindex [get_hw_devices] 4]
    program_hw_devices [lindex [get_hw_devices] 4]
    ERROR: [Labtools 27-3165] End of startup status: LOW
    program_hw_devices: Time (s): cpu = 00:00:15 ; elapsed = 00:00:15 . Memory (MB): peak = 710.723 ; gain = 0.000
    ERROR: [Common 17-39] 'program_hw_devices' failed due to earlier errors.
    With Vivado, the configuration of the second file fails because DONE does not rise.
     

  • There is a missing letter of Path name or file name when vivado SDK linking object files

    I used vivado SDK 2014.3 to complie the third source code and could get *.o files. But when linking them, there was an error to show that No such file or directory. I found that there was lack of letter in path name of object file.  It's a SDK bug or I don't set up correctly? 
    Thank you for an early answer.

    I tried it in vivado SDK 2015.1, but there was still the same problem. And I found that it was successful if only importing a small part of source code. What is the reason for this situation?

  • Zynq Petalinux 2014.4 device tree node for two SD card interfaces?

    I'm using a 3rd party zynq module (Trenz TE0720) for which they provide a .bsp file.  The resulting Petalinux build boots just fine out of the SD card.  But the module also has an on board eMMC memory that should look llike second SD card and it is connected to the zynq's second sdhci controller.  But Linux is unaware of its existence.
    The likely cause is an omission from the device tree script and I would imagine it should be possible to add the missing device tree node.  However all of attempts thus far have failed.  The (very simple) device tree script looks like the below.
    Can anyone point me to a correct SD card device tree node for a Petalinux 2014.4 device tree script?  Also the full present device tree script archive is attached.  Thanks!
    /dts-v1/;
    /include/ "system-conf.dtsi"
    aliases {
    mio = &gpio0;
    /* TE0720-02 uses Spansion Flash */
    &qspi {
    flash0: flash@0 {
    compatible = "spansion,s25fl256s1";
    &usb0 {
    dr_mode = "host";
    &gem0 {
    phy-handle = <&phy0>;
    mdio {
    #address-cells = <1>;
    #size-cells = <0>;
    phy0: phy@0 {
    compatible = "marvell,88e1510";
    device_type = "ethernet-phy";
    reg = <0>;
    /* restore LED settings */
    marvell,reg-init = <0x3 0x10 0x0000 0x0501 0x3 0x11 0x0000 0x4415>;
    &i2c1 {
    /* Real Time Clock RAM is not supported, map as EEPROM */
    eeprom@57 {
    compatible = "at,24c01";
    reg = <0x57>;
    /* Real Time Clock, rtc0 name can used to set time at startup! */
    rtc0: rtc@6F {
    compatible = "isl12022";
    reg = <0x6F>;
    };

    I figured out a solution by myself:
    The Kernel image was not read from the correct position in the QSPI flash. In order to find out which is the correct address to read from, I modified the .bif-file (./build/bootgen.bif)  that was generated by petalinux-package:
    the_ROM_image:
    [bootloader] ./images/linux/zynq_fsbl.elf
    ./images/linux/u-boot.elf
    ./images/linux/image.ub
    Then I executed:
    bootgen -image newbif.bif -o test.bin -debug -w
    The -debug is important here. This gave me:
    *** After Link
    -- Dump of Binary cache ----
    00000000 Len: 000008a0 Res: 00000000 "BootHeader"
    000008c0 Len: 00000014 Res: 00000000 "ImageHeaderTable"
    00000900 Len: 00000024 Res: 00000000 "ImageHeader zynq_fsbl.elf"
    00000940 Len: 00000020 Res: 00000000 "ImageHeader u-boot.elf"
    00000980 Len: 00000020 Res: 00000300 "ImageHeader image.ub"
    00000c80 Len: 00000040 Res: 00000000 "PartitionHeader zynq_fsbl.elf.0"
    00000cc0 Len: 00000040 Res: 00000000 "PartitionHeader u-boot.elf.0"
    00000d00 Len: 00000040 Res: 00000000 "PartitionHeader image.ub.0"
    00000d40 Len: 00000040 Res: 000009c0 "PartitionHeader Null"
    00001700 Len: 0001800c Res: 00000000 "zynq_fsbl.elf.0"
    00019740 Len: 00043054 Res: 00000000 "u-boot.elf.0"
    0005c7c0 Len: 00691ac0 Res: 00000000 "image.ub.0"
    -- End of Dump
    Here we see that the Kernel image is to be found at an offset of 0x0005c7c0 and has a length of 0x00691ac0.
    The image can therefore be booted in u-boot by doing:
    U-Boot-PetaLinux> sf read $netstart 0005c7c0 00691ac0
    SF: 6888128 bytes @ 0x5c7c0 Read: OK
    U-Boot-PetaLinux> bootm $netstart
    This loads and successfully boots the kernel, finally presenting me a login prompt.
    Hope this helps someone in the future. 

  • PetaLinux vs Vivado SDK?

    Can someone explain the difference between PetaLinux and the Vivado SDK for linux development? As far as I can tell, the Vivado SDK contains all of the build tools needed to build linux applications (arm-xilinx-linux-gnueabi-*). What's the difference between manually building linux-xlnx and u-boot-xlnx from the Git repository vs using PetaLinux? What's the prefered method to build and setup a linux development enviornment?
    I've installed Vivado SDK on my Ubuntu Machine; git cloned, configured, and built u-boot-xlnx and linux-xlnx. Everything seems to be working fine on my Microzed board. Are there any advantages to using PetaLinux?

    PetaLinux is our full Linux distribution which includes the Linux OS as well as a complete configuration, build and deploy environment for Xilinx silicon.PetaLinux Tools provide a simple and fast method to build and deploy Linux-based software on Xilinx Zynq-7000 APSoC and MicroBlaze devices.
    Although the PetaLinux kernel is based on a stable and thoroughly tested Linux, also from the Xilinx Git server, PetaLinux offers much more than what can be downloaded from our Git. PetaLinux includes installer, development tools, BSPs, platform management utilities, application and library frameworks and documentation that are not found within our OSL offering.
     With PetaLinux, you can:
    • Build and configure Linux components; Linux kernel, u-boot and file system, for Zynq-7000 APSoC and MicroBlaze based designs
    • Easily synchronize your Linux software platform and hardware platform in a single step
    • Easily target and migrate your Linux user application to Zynq-7000 APSoC or MicroBlaze based Linux platform
    • Quickly get started with building Linux-based software on Xilinx and partner development boards using the pre-built Board Support Packages (BSPs)
    • Test your Zynq-7000 APSoC or MicroBlaze Linux system without any hardware in a virtual machine environment using QEMU
    You can refer to the design flow details in the link http://www.wiki.xilinx.com/PetaLinux+Getting+Started
    For more details refer to the Petalinux Documentation.
    Regards,
    Achutha

  • 3 USB not showing up in device tree

    Hi folks,
    I have a May 2010 17 inch Macbook Pro with 3 USB ports on the left side. I was just checking to see that they were USB 2.0. When clicking on the Apple Logo > About This Mac > More Info > USB, shouldn't I see 3 USB High-Speed Bus in the device tree? I only see 2. When I click on the one that is highlighted in the picture it says up to 480 Mb / sec for the speed. When I click on the "USB High-Speed Bus" 5 columns below it, it also says 480 Mb / sec for speed. I know that these 2 are USB 2.0 because of that. Where is my 3rd USB port represented? Shouldn't there be a 3rd "USB High-Speed Bus" somewhere in there or is it in one of the sub folders?
    I was reading online that some of the USB ports on the MBP aren't as fast as the others. Some people said the one closest to the screen is slowest and others said the opposite. Thats what started me to look at the device tree. I use the ports for live audio so it is very important that I use the most effective one.
    Thanks so much for your time!

    All of the USB 2.0 ports should operate the same - the reason that you're not seeing something is probably because you don't have anything attached to the ports. If you did, the devices would show up in the Hardware>USB tree.
    Clinton

  • When the device tree node(dev_info_t) is built for a pseudo device?

    Hi Expert,
    I am a new driver writer. I am writing a pseudo driver.
    As my understanding, the a device node (dev_info_t) must exist before the attach routine is called.
    int attach(dev_info_t *dip, ddi_attach_cmd_t cmd);
    For the hardware device, the node will be built when the system boots.
    But when the node is built on the device tree for the pseudo device.
    Thanks,
    Eric

    Two options:
    - Use another payment method like redeeming and iTunes gift card.
    - Create a new account that is only good for app by using the instructions here:
    Creating an iTunes Store, App Store, iBookstore, and Mac App Store account without a credit card
    Please follow the instructions. oyu have to do it exactly as it says.

  • Dynamically generate a tree

    is there anyway that i can generate a tree dynamically.If i have a part no(1) then i want a sub assembly so i select a part no(2) and it should be added as a leaf .if i select another partno(3) it should be added to the partno(2) thus populating the tree
    can anybody help me out in this
    Thanks

    Hi,
    I suppose you're using Document so If you have 2 Documents, you can easily get the root Node.
    So have a Doument1 and Document2 :
    1. get the root Node of the Doucument2 : Node root=Document2.getDocumentElement();
    2. import it in Document1 : Node child1=Document1.importNode(root,true); //true -> deep
    3. append the child to Document1 : Document1.appendChild(child);
    Now add Document3 :
    4. get the root Node of the Doucument2 : root=Document2.getDocumentElement();
    5. import it in Document1 : Node child2=Document1.importNode(root,true); //true -> deep
    6. append the child to Document1 after Document2 : child1.appendChild(child2);
    then for others set child1 to child2, set child2 to the new Node to add and append it to child 1 ...
    Hope this helps

  • Generating category tree failed! on secmon reporting

    This morning I wanted to create a new report in the security monitor of our vms 2.2 server.
    I selected reports and the definitions> create > ids alarms report and then proceeded to the try select some specific signatures from the ids signature dropdown menu below. In the part where the signature categories are meant to appear, there is an error message.
    “Generating category tree failed!”
    If I point at the error with the mouse
    “Error while building the SETI category tree”
    I have attached a jpeg file that shows the error message.
    Is this a bug and if so, how can we fix it?

    Once again, I guess I should search the bug database before opening new conversations. Many apologies for that…
    I found the bug in the bug database at Cisco. The bug is entitled
    “SecMon: cannot create report based on signature ID” (CSCsc31745)
    According to the bug:
    The report section tries to grab the latest signatures to include in the "IDS Signature" section, it does this based on the latest signature level then the latest service pack number. If there is say, 4.1(5)S197 AND 5.0(4)S197 installed on the VMS server, the report will try to use 4.1(5)S197 because its SP number is later. This fails and the "Generating Category Tree Failed" error is displayed. (auto signature download is responsible for that!!)
    The Workaround is to replacement a Java file that resolves this issue which can be obtained by opening a TAC case and referencing this bug ID.

  • MIO GPIO interrupt in device tree

    Hi
    I am trying to specify a MIO GPIO as an interrupt source for a linux driver. The driver in question is for the ADS7846 touchscreen controller. I have been able to get the touchscreen working by modifying the PCB to take the interrupt line to the PL, then connecting this to a PL-PS interrupt. I would like to know how to use the MIO GPIO instead.
    My dev tree:
    &spi0 {
        is-decoded-cs = <0>;
        num-cs = <2>;
        status = "okay";
        touchscreen@0 {
                    reg = <0>;
                    compatible = "ti,ads7846";
                   /* I have been able to get it working by using a PL-PS interrupt */
                    /*interrupt-parent = <&intc>;
                    interrupts = <0 29 1>;*/
                   /* I can't find how to specify the MIO GPIO as an interrupt source */
                    interrupt-parent = <&gpio0>;
                    interrupts = <&gpio0 52 0x2>;
                    spi-max-frequency = <1000000>;
                    pendown-gpio = <&gpio0 52 0>;
                    vcc-supply = <&regulator_vccpint>;
    Does anyone have examples of setting up a MIO GPIO as an interrupt source in the device tree? Or links to good documentation?
    Thanks in advance,
    Will

    OK - so it's taken a while, but I think I have now worked it out!
    I changed the gpio entry in the "zynq-7000.dtsi" file to the following:
    gpio0: gpio@e000a000 {
                compatible = "xlnx,zynq-gpio-1.0";
                #gpio-cells = <2>;
                clocks = <&clkc 42>;
                gpio-controller;
                interrupt-parent = <&intc>;
                interrupts = <0 20 4>;
                #interrupt-cells = <2>;
                interrupt-controller;
                reg = <0xe000a000 0x1000>;
    And then specified interrupts for devices as follows:
    &spi0 {
        is-decoded-cs = <0>;
        num-cs = <2>;
        status = "okay";
        touchscreen@0 {
            reg = <0>;                                                         /* CS0 */
            compatible = "ti,ads7846";
            interrupt-parent = <&gpio0>;
            interrupts = <52 2>;                                       /* MIO 52, falling edge */
            spi-max-frequency = <1000000>;
            pendown-gpio = <&gpio0 52 0>;
            vcc-supply = <&regulator_vccpint>;              /* dummy */
        nfc@0 {
            compatible = "ti,trf7970a";
            reg = <1>;
            pinctrl-names = "default";
            spi-max-frequency = <2000000>;
            interrupt-parent = <&gpio0>;
            interrupts = <15 1>;                                            /* GPIO MIO 15, rising edge */
            ti,enable-gpios = <&gpio0 14 0>,
                    <&gpio0 13 0>;                                          /* 13 = dummy- don't need EN2 support */
            vin-supply = <&regulator_vccpint>;              /* dummy */
            autosuspend-delay = <30000>;
            /*irq-status-read-quirk;
            en2-rf-quirk;*/
            status = "okay";
    For info,
    # dmesg | grep ads
    ads7846 spi32766.0: touchscreen, irq 148
    # cat /proc/interrupts
    CPU0 CPU1
    27: 0 0 GIC 27 gt
    29: 891 540 GIC 29 twd
    35: 0 0 GIC 35 f800c000.ocmc
    40: 0 0 GIC 40 f8007000.devcfg
    41: 0 0 GIC 41 f8005000.watchdog
    43: 0 0 GIC 43 ttc_clockevent
    45: 0 0 GIC 45 f8003000.dmac
    46: 0 0 GIC 46 f8003000.dmac
    47: 0 0 GIC 47 f8003000.dmac
    48: 0 0 GIC 48 f8003000.dmac
    49: 0 0 GIC 49 f8003000.dmac
    51: 4513 0 GIC 51 e000d000.spi
    53: 0 0 GIC 53 zynq-udc
    56: 88 0 GIC 56 mmc0
    57: 26 0 GIC 57 cdns-i2c
    58: 724 0 GIC 58 e0006000.spi
    72: 0 0 GIC 72 f8003000.dmac
    73: 0 0 GIC 73 f8003000.dmac
    74: 0 0 GIC 74 f8003000.dmac
    75: 0 0 GIC 75 f8003000.dmac
    79: 52 0 GIC 79 mmc1
    82: 334 0 GIC 82 xuartps
    111: 0 0 zynq-gpio 15 trf7970a
    148: 21 1 zynq-gpio 52 ads7846
    IPI1: 0 0 Timer broadcast interrupts
    IPI2: 2061 2277 Rescheduling interrupts
    IPI3: 0 0 Function call interrupts
    IPI4: 8 45 Single function call interrupts
    IPI5: 0 0 CPU stop interrupts
    IPI6: 1 0 IRQ work interrupts
    IPI7: 0 0 completion interrupts
    Err: 0
    Thanks Milosoftware for your help.
    Will

  • Fatal Error with Java ME Device Manager and SDK Updates

    I recently installed the Java ME 3 EA SDK Platform which looks promising. Everything seem to work fine. In the process of new updates and the desire to remove some older versions of Java, I installed a new Java versions (1.6.0_11) and removed some old ones (1.6_0_04 and 1.6_0_10).
    Following this whenever I startup my machine, following the attempted start of the Java ME Device Manager, I get a "Fatal Error: Cannot start child. Error code: 0" dialog.
    Following this I get an exception indicating:
    java.net.ConnectException: Connection refused: connect
         at java.net.PlainSocketImpl.socketConnect(Native Method)
         at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
         at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
         at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
         at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
         at java.net.Socket.connect(Socket.java:519)
         at java.net.Socket.connect(Socket.java:469)
         at java.net.Socket.<init>(Socket.java:366)
         at java.net.Socket.<init>(Socket.java:180)
         at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
         at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
         at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:595)
    Caused: java.rmi.ConnectException: Connection refused to host: localhost; nested exception is:
         java.net.ConnectException: Connection refused: connect
         at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:601)
         at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:198)
         at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184)
         at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:322)
         at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
         at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:97)
    Caused: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is:
         java.net.ConnectException: Connection refused: connect]
         at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:101)
         at com.sun.jndi.toolkit.url.GenericURLContext.lookup(GenericURLContext.java:185)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.java:1871)
         at javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1841)
         at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:257)
    Caused: java.io.IOException: Failed to retrieve RMIServer stub
         at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:323)
         at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
         at com.sun.jme.toolkit.remoting.client.rmiimpl.ObjectServerConnectionImpl.connect(Unknown Source)
         at com.sun.jme.toolkit.remoting.client.rmiimpl.ObjectServerConnectionImpl.start(Unknown Source)
         at com.sun.jme.toolkit.remoting.client.rmiimpl.ObjectServerConnectionImpl.lookupMBean(Unknown Source)
         at com.sun.jme.toolkit.remoting.client.rmiimpl.ObjectServerConnectionImpl.findObject(Unknown Source)
         at org.netbeans.modules.javame.common.container.devicemanager.DevicemanagerHelper.openConnection(DevicemanagerHelper.java:56)
         at org.netbeans.modules.javame.common.container.devicemanager.DevicemanagerHelper.getDeviceManager(DevicemanagerHelper.java:73)
         at org.netbeans.modules.j2me.cdc.platform.jme_sdk.autoinstaller.AutoInstaller.ensureDMStarted(AutoInstaller.java:228)
         at org.netbeans.modules.j2me.cdc.platform.jme_sdk.autoinstaller.AutoInstaller.restored(AutoInstaller.java:65)
         at org.netbeans.core.startup.NbInstaller.loadCode(NbInstaller.java:419)
         at org.netbeans.core.startup.NbInstaller.load(NbInstaller.java:340)
         at org.netbeans.ModuleManager.enable(ModuleManager.java:888)
         at org.netbeans.core.startup.ModuleList.installNew(ModuleList.java:428)
         at org.netbeans.core.startup.ModuleList.trigger(ModuleList.java:364)
         at org.netbeans.core.startup.ModuleSystem.restore(ModuleSystem.java:276)
         at org.netbeans.core.startup.Main.getModuleSystem(Main.java:163)
         at org.netbeans.core.startup.Main.start(Main.java:315)
         at org.netbeans.core.startup.TopThreadGroup.run(TopThreadGroup.java:110)
    [catch] at java.lang.Thread.run(Thread.java:619)
    When I try to start the SDK itself, I also get "Cannot find java.exe in specified jdkhome. Neither E:\java\jdk1.6.0_10\jre\bin\java.exe or E:\java\jdk11.6.0.0_10\bin\java.exe exists. Do you want to try to use default version?". This also happens with I try starting Netbeans as well.
    When I say No, it appears to not start at all. When I say Yes, it appears to try to start but I continually get errors as listed above for the Java ME Device Manager startup error.
    After reinstalling the _10 version, things started to work again, so I suspect this is due to my removal of the an older version of the JDK.
    How is the proper way to "update" without causing similar errors? Are the environment variable JAVA_HOME, JAVA2_HOME, or some other variable used to specify the JDK/JRE in use? I would rather not be forced to change my startup each time to specify a -jdkhome related parameter.
    Should I install the new version, find install the "Java Platform" in the SDK/Netbeans, set it as
    Also...
    How do you set the default version from within the SDK/Netbeans?
    And is there a way to prevent the Device Manager from starting?
    Eric

    You can try this link to see if it solves your problem.
    [http://java.lillegutt.com/?p=3]
    Cheers,

  • ICA-compatible device + ImageCapture Tiger SDK

    I have a brand new iMac running Leopard 10.5.2. I ran the CameraCheck program from the ImageCaptureTigerSDK, and it reports "number of ICA devices found: 0".
    Question 1: Isn't iMac's built-in camera ICA-compatible?
    Question 2: Is it true any camera/scanner recognized by Mac OS X is available as source through the ImageCapture SDK?
    Question 3: Perhaps this SDK is not compatible with Leopard? (I doubt so)
    Question 4: If I need to write an application to capture live video+audio, is this the correct SDK to use?
    Thank you in advance.

    I have a brand new iMac running Leopard 10.5.2. I ran the CameraCheck program from the ImageCaptureTigerSDK, and it reports "number of ICA devices found: 0".
    Question 1: Isn't iMac's built-in camera ICA-compatible?
    Question 2: Is it true any camera/scanner recognized by Mac OS X is available as source through the ImageCapture SDK?
    Question 3: Perhaps this SDK is not compatible with Leopard? (I doubt so)
    Question 4: If I need to write an application to capture live video+audio, is this the correct SDK to use?
    Thank you in advance.

  • Error in SchemaConstantOptionLookup after generate Artifacts in CCB SDK

    I'm getting this error on a fresh CCB 2.3.1 SP5 FW 2.2.0 SP15 Development installation (windows xp + tomcat).
    After getting SPL SDK configured in Eclipse, run Artifact Generator and some java source code is generated in the gen folder.
    The SchemaConstantOptionLookup.java file show a compilation error:
    Source Code:
    CUSTOMER_CONTACT_CLASS = (SchemaConstantOptionLookup) com.splwg.ccb.api.lookup.SchemaConstantOptionLookup.constants.*CUSTOMER_CONTACT_CLASS*;
    Error:
    com.splwg.ccb.api.lookup.SchemaConstantOptionLookup.constants.CUSTOMER_CONTACT_CLASS cannot be resolved or is not a field     SchemaConstantOptionLookup.java     /CCB231Project/gen/com/splwg/cm/api/lookup     line 106     Java Problem
    Went to the application (online) and verified that the Lookup Value C1CC/CustomerContactClass is defined within the F1CN_OPT_TYP_FLG Lookup Field so I don't know what the problem should be.
    Please Help

    I figured out theres a patch out there included in the CCB 2.3.1 SP6 (don't have the patch number with me right now) but you can search on the SP6 Release Notes PDF.

  • Generating clock with vivado

    Hi,
    I am using Vivado with a ZedBoard  programming in VHDL (PL). The ZedBoard clock source for PL is 100Mhz. I need two clocks: clkgen1= 100kHz and clkgen2= 350Mhz to clock the FMC.
    How can I generate these clocks in Vivado? I know I can use PLL or Mmcm. Which one would be better?
    Is there any tutorial?
    Thank you.

    ---- Where can i read documentation about this?
    You can find documents about zed board in the following board’s link http://www.xilinx.com/support/university/boards-portfolio/xup-boards/XUPZedBoard.html .
    -------How can i do this in Vivado?
    Check whether the below thread applicable to your issue
    http://forums.xilinx.com/xlnx/board/crawl_message?board.id=GenDis&message.id=18987
    ________________________________________________

Maybe you are looking for

  • Convert Chinese signs to UTF-8

    Hi there I am trying to find a tool, or some code, who can help me covert Chinese signs to UTF-8 format. The resen is that I am working on a project who has to develop a web-site containg both english and chinese text. So first of all to test oure se

  • Transparency problem InDesign CS5

    Hi, when I put squares filled with colour and then some percent of transparency, the boxes show as filled after a little while. When I close my document and then re open it, or if I print it, the transparency is back. Has this happend to anyone else,

  • Use of converter-for-class

    Hello, I start to use Jdev11 TP4. I have written my own converter which performs "trims" on character fields. This converter works fine when I apply it to the adf input texts which are present on my jspx pages. But I would like to apply this converte

  • Problems opening Pagemaker 7 document

    Hi, I need some help with a Pagemaker 7 document that a client in America has supplied to us here in the UK. When trying to open it in InDesign, InDesign crashes during the "Converting Regular Spreads" stage of the import. Firstly let me say that we'

  • Playing DVDs with 5.1 sound

    I connected Bose Companion 2 speakers to the stereo jack of MBP. The problem is when I play DVDs that come with 5.1 Dolby Digital Sound, some of the sound effects cannot be heard as they are channels not picked up by the stereo jack. Is there any way