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.
 

Similar Messages

  • DIFFICULTY PROGRAMMING CUSTOM BOARD WITH VIVADO

    Hey Xilinx gurus,
    I’ve been having difficulty programming a custom board with Vivado. I am using the XC7A50T-FGG484 Artix device in my design. I am also using the S25FL128SAGMFI003 Spansion flash memory chip. I first tried to program the Artix FPGA directly, then tried to program the FPGA using the flash memory. Neither of these have been successful and I need some help. I have scoured the user guides and forums with little success.
    Here are some warnings/errors that I run into when programming (I included the entire TCL console script below):
    WARNING: [Labtools 27-3123] The debug hub core was not detected at User Scan Chain 1 or 3.
    Byte 15370 does not match (FF != 00)
    ERROR: [Labtools 27-3161] Flash Programming Unsuccessful
    ERROR: [Common 17-39] 'program_hw_cfgmem' failed due to earlier errors.
    Thank you in advance for your time and direction, it is much appreciated!
    Best,
    Ralph
    ENTIRE TCL CONSOLE SCRIPT:
    start_gui
    open_project C:/Vivado/imu3artix/imu3frequency/imu3frequency.xpr
    Scanning sources...
    Finished scanning sources
    INFO: [IP_Flow 19-234] Refreshing IP repositories
    INFO: [IP_Flow 19-1704] No user IP repositories specified
    INFO: [IP_Flow 19-2313] Loaded Vivado IP repository 'C:/Xilinx/Vivado/2015.1/data/ip'.
    open_project: Time (s): cpu = 00:00:21 ; elapsed = 00:00:20 . Memory (MB): peak = 704.227 ; gain = 92.195
    open_hw
    ****** Webtalk v2015.1 (64-bit)
    **** SW Build 1215546 on Mon Apr 27 19:22:08 MDT 2015
    **** IP Build 1209967 on Tue Apr 21 11:39:20 MDT 2015
       ** Copyright 1986-2015 Xilinx, Inc. All Rights Reserved.
    source C:/Vivado/imu3artix/imu3frequency/imu3frequency.hw/webtalk/labtool_webtalk.tcl -notrace
    webtalk_transmit: Time (s): cpu = 00:00:00 ; elapsed = 00:00:15 . Memory (MB): peak = 66.770 ; gain = 0.023
       while executing
    "webtalk_transmit -clientid 3767299429 -regid "210956146_0_0_059" -xml C:/Vivado/imu3artix/imu3frequency/imu3frequency.hw/webtalk/usage_statistics_ext_..."
       (file "C:/Vivado/imu3artix/imu3frequency/imu3frequency.hw/webtalk/labtool_webtalk.tcl" line 28)
    INFO: [Common 17-206] Exiting Webtalk at Thu Aug 06 11:42:27 2015...
    connect_hw_server -url localhost:3121
    INFO: [Labtools 27-2285] Connecting to hw_server url TCP:localhost:3121
    current_hw_target [get_hw_targets */xilinx_tcf/Xilinx/0000177f243b01]
    set_property PARAM.FREQUENCY 1500000 [get_hw_targets */xilinx_tcf/Xilinx/0000177f243b01]
    open_hw_target
    INFO: [Labtoolstcl 44-466] Opening hw_target localhost:3121/xilinx_tcf/Xilinx/0000177f243b01
    set_property PROGRAM.FILE {C:/Vivado/imu3artix/imu3frequency/imu3frequency.runs/impl_1/IMU3.bit} [lindex [get_hw_devices] 0]
    current_hw_device [lindex [get_hw_devices] 0]
    refresh_hw_device -update_hw_probes false [lindex [get_hw_devices] 0]
    INFO: [Labtools 27-1435] Device xc7a50t (JTAG device index = 0) is not programmed (DONE status = 0).
    set_property PROBES.FILE {} [lindex [get_hw_devices] 0]
    set_property PROGRAM.FILE {C:/Vivado/imu3artix/imu3frequency/imu3frequency.runs/impl_1/IMU3.bit} [lindex [get_hw_devices] 0]
    program_hw_devices [lindex [get_hw_devices] 0]
    INFO: [Labtools 27-3164] End of startup status: HIGH
    program_hw_devices: Time (s): cpu = 00:00:24 ; elapsed = 00:00:24 . Memory (MB): peak = 741.168 ; gain = 0.000
    refresh_hw_device [lindex [get_hw_devices] 0]
    INFO: [Labtools 27-1434] Device xc7a50t (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:
    Make sure the clock connected to the debug hub (dbg_hub) core is a free running clock and is active OR
    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].
    create_hw_cfgmem -hw_device [lindex [get_hw_devices] 0] -mem_dev [lindex [get_cfgmem_parts {s25fl128sxxxxxx0-spi-x1_x2_x4}] 0]
    set_property PROGRAM.BLANK_CHECK 0 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
    set_property PROGRAM.ERASE 1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
    set_property PROGRAM.CFG_PROGRAM 1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
    set_property PROGRAM.VERIFY 1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
    refresh_hw_device [lindex [get_hw_devices] 0]
    INFO: [Labtools 27-1434] Device xc7a50t (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:
    Make sure the clock connected to the debug hub (dbg_hub) core is a free running clock and is active OR
    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 PROGRAM.ADDRESS_RANGE {use_file} [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
    set_property PROGRAM.FILES [list "C:/Vivado/imu3artix/imu3frequency/imu3frequency.runs/impl_1/IMU3.bin" ] [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0]]
    set_property PROGRAM.UNUSED_PIN_TERMINATION {pull-none} [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
    set_property PROGRAM.BLANK_CHECK 0 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
    set_property PROGRAM.ERASE 1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
    set_property PROGRAM.CFG_PROGRAM 1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
    set_property PROGRAM.VERIFY 1 [ get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
    startgroup
    if {![string equal [get_property PROGRAM.HW_CFGMEM_TYPE [lindex [get_hw_devices] 0]] [get_property MEM_TYPE [get_property CFGMEM_PART [get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]]]] } { create_hw_bitstream -hw_device [lindex [get_hw_devices] 0] [get_property PROGRAM.HW_CFGMEM_BITFILE [ lindex [get_hw_devices] 0]]; program_hw_devices [lindex [get_hw_devices] 0]; };
    INFO: [Labtools 27-3164] End of startup status: HIGH
    program_hw_devices: Time (s): cpu = 00:00:05 ; elapsed = 00:00:05 . Memory (MB): peak = 784.484 ; gain = 0.000
    program_hw_cfgmem -hw_cfgmem [get_property PROGRAM.HW_CFGMEM [lindex [get_hw_devices] 0 ]]
    Mfg ID : 1   Memory Type : 20   Memory Capacity : 18   Device ID 1 : 0   Device ID 2 : 0
    Performing Erase Operation...
    Erase Operation successful.
    Performing Program and Verify Operations...
    Program/Verify Operation failed.
    Byte 15370 does not match (FF != 00)
    ERROR: [Labtools 27-3161] Flash Programming Unsuccessful
    program_hw_cfgmem: Time (s): cpu = 00:00:00 ; elapsed = 00:00:21 . Memory (MB): peak = 784.484 ; gain = 0.000
    ERROR: [Common 17-39] 'program_hw_cfgmem' failed due to earlier errors.

     This indicates your device got programed. those warnings can be safely ignored.
    INFO: [Labtools 27-1434] Device xc7a50t (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:
    Make sure the clock connected to the debug hub (dbg_hub) core is a free running clock and is active OR
    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].
    FPGA is getting programmed but flash got problems while programming. Let me see if I could get anything from log

  • How to use spirit:componentGenerators with Vivado?

    Hi,
    I'm trying to use <spirit:componentGenerators> with Vivado, but aren't very successful at it. Unfortunately I don't have any other IP-XACT DE nor any existing core that uses it as reference. This makes it rather hard to get started..
    As a simple test I've added the following to the component.xml of a very simple core that I already had:
    <spirit:componentGenerators>
    <spirit:componentGenerator>
    <spirit:name>testGenerator</spirit:name>
    <spirit:parameters>
    <spirit:parameter>
    <spirit:name>language</spirit:name>
    <spirit:value spirit:id="checker" spirit:resolve="user">strict</spirit:value>
    </spirit:parameter>
    </spirit:parameters>
    <spirit:apiType>TGI</spirit:apiType>
    <spirit:generatorExe>/tmp/testGenerator</spirit:generatorExe>
    </spirit:componentGenerator>
    </spirit:componentGenerators>
    (Which basically is the example code from the IEEE IP-XACT standard.) This broke the core, but /tmp/testGenerator is never called (checked using strace and by adding code to /tmp/testGenerator that would create another file in /tmp if it where executed).
    I get the following error in response to "create_ip":
    WARNING: [Vivado 12-1783] Unsupported target specified: 'instantiation_template'. Supported targets for this IP are: 'all' 'synthesis' 'simulation'. File: 'generator_0.xci'.
    ERROR: [Vivado 12-1773] No legal targets specified. Supported targets for this IP are: all synthesis simulation. File: 'generator_0.xci'.
    ERROR: [Common 17-39] 'generate_target' failed due to earlier errors.
    But "update_ip_catalog -rebuild" runs fine, so the XML is valid and if I remove the <spirit:componentGenerators> element then create_ip works just fine.
    So I guess my questions are:
    Is <spirit:componentGenerators> supported by Vivado?
    Is there any example core that demonstrates how to use it?
    None of the Xilinx IPs that come with Vivado are using componentGenerators. Instead it seems they are using TCL scripts that are directly executed by Vivado as part of "create_ip" (and/or "generate_target"). Is there a documentation somewhere on how to do that?
    Thanks in advance for your help!
    PS: I'm still on Vivado 2014.1.
     

    Hi luaraneda,
    unfortunately I have never recieved any response from Xilinx regarding this issue. My experience so far with this forum: Unless you ask super dumb questions you cannot expect any support from here. Often the "answers" are totally unrelated to the question and in general it is impossible to get any support regarding questions that are not also well covered by the documentation... I guess that helps when you don't know where in the documentation to look, but I would expect a bit more...
    Sorry, Xilinx: I really love your products, but your support sucks big time!

  • ILA issues with Vivado 2014.3

    I have been trying to run the Avnet Zedboard lab regarding the 802.11 Beacon frame receiver.
    http://zedboard.org/course/integrated-software-defined-radio-zynq%C2%AE-7000-all-programmable-soc
    I have gotten through all the lab work and am ready now to debug my bit stream using the ILA tool.
    dbg_hub and ila are clearly visible in the synthesized and implemented design, but when I load the bitstream I get the following warning messages:
    refresh_hw_device [lindex [get_hw_devices] 1]
    WARNING: [Xicom 50-38] xicom: No CseXsdb register file specified for CseXsdb slave type: 0, cse driver version: 0. Slave initialization skipped.
    WARNING: [Xicom 50-38] xicom: No CseXsdb register file specified for CseXsdb slave type: 0, cse driver version: 0. Slave initialization skipped.
    INFO: [Labtools 27-1434] Device xc7z020 (JTAG device index = 1) 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. You must 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].
    WARNING: [Labtools 27-1974] Mismatch between the design programmed into the device xc7z020_1 and the probes file D:/Avnet/Zynq_SDR_2014/vivado/fmcomms2_zed_802_11_RX/fmcomms2_zed_802_11_RX.runs/impl_1/debug_nets.ltx.
    The device design has 0 ILA core(s) and 0 VIO core(s). The probes file has 2 ILA core(s) and 0 VIO core(s).
    Resolution:
    1. Reprogram device with the correct programming file and associated probes file OR
    2. Goto device properties and associate the correct probes file with the programming file already programmed in the device.
    So I ran :
    get_property C_USER_SCAN_CHAIN [get_debug_cores dbg_hub]
    1
    As recommended, I reduced my JTAG clock speed to 3MHz and it did not do anything either.
    I also went back to Vivado 2014.3 - same problem.
    So far no luck, and I have been at this for three days now - very frustrating.
    You cannot use an IDE without proper debugginh tool.
    Am I the only one having these issues? I see there were similar problems with Vivado 2013.3 about a year ago.
    But yet not fixed???
    Arne
     

    Hi
    In 2014.3 you will get these warnings if
    the clock connecetd to the debug hub is not free running clock or active
    the debug hub User Scan Chain setting is 2 or 4 (It is a 1 by default)
    We did realize that the resolution to this warning needs to be more explicit and have fixed it in 2014.4 as follows:
    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].
    Thanks
    Smitha

  • SAP on V6R1 - ABAP Import:Program 'Migration Monitor' exits with error code

    Hello,
    We are doing an installation of SAP NW 7.01 SR1 on V6R1.
    <br>
    We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
    <br>
    We are again getting error in following steps:
    <br>
    sapinst.log
    <br>
    <br>WARNING 2009-09-30 23:25:28.477
    Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
    java version "1.4.2"
    Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
    IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
    J9VM - 20090309_31291_BHdSMr
    JIT  - 20090210_1447ifx1_r8
    GC   - 200902_24)
    I<br>mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
    <br>Loading of 'SAPNTAB' import package: OK
    <br>Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
    Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28.<br>
    Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28.<br>
    Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28.<br>
    Loading of 'DOKCLU' import package: OK
    Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28.<br>
    Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28.<br>
    Loading of 'SAPAPPL1' import package: OK
    Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28.<br>
    Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28.<br>
    Loading of 'SAPAPPL2' import package: ERROR
    Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28.<br>
    Loading of 'DD03L' import package: OK
    Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28.<br>
    Loading of 'SCPRSVALS' import package: OK
    Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28.<br>
    Loading of 'SAPSDIC' import package: OK
    Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28.<br>
    Loading of 'SCPRVALS' import package: OK
    Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28.<br>
    Loading of 'SAPSSRC' import package: OK
    Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28.<br>
    Loading of 'FUPARAREF' import package: OK
    Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28.<br>
    Loading of 'TODIR' import package: OK
    Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28.<br>
    Loading of 'SEOSUBCODF' import package: OK
    Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28.<br>
    Loading of 'E071K' import package: OK
    Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28.<br>
    Loading of 'SAPPOOL' import package: OK
    Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28.<br>
    Loading of 'SAPSPROT' import package: OK
    Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28.<br>
    Loading of 'SAPSDOCU' import package: OK
    Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28.<br>
    Loading of 'SAPCLUST' import package: OK
    Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28.<br>
    Loading of 'SAPSLOAD' import package: OK
    Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28.<br>
    Loading of 'SAPSLEXC' import package: OK
    Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28.<br>
    Loading of 'SAPUSER' import package: OK
    Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28.<br>
    Loading of 'SAPDDIM' import package: OK
    Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28.<br>
    Loading of 'SAPDFACT' import package: OK
    Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28.<br>
    Loading of 'SAPDODS' import package: OK
    Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28.<br>
    Loading of 'SAPUSER1' import package: OK
    Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28.<br>
    Loading of 'SAP0000' import package: OK
    Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28.<br>
    Loading of 'SAPAPPL0' import package: OK
    Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28.<br>
    Loading of 'SAPSSEXC' import package: OK
    Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28.<br>
    <br>
    WARNING[E] 2009-09-30 23:25:28.524
    CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
    <br>
    ERROR 2009-09-30 23:25:28.914
    FCO-00011  The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
    <br>
    <br>import_monitor.log.
    <br>****************************************************************************************************************************************************
    <br>INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
    Loading of 'SAP0000' import package is successfully completed.
    <br>
    INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL0' import package is successfully completed.
    <br>
    INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC' import package is successfully completed.
    <br>
    WARNING: 2009-09-30 23:31:31
    Cannot start import of packages with views because not all import packages with tables are loaded successfully.
    WARNING: 2009-09-30 23:31:31
    1 error(s) during processing of packages.
    INFO: 2009-09-30 23:31:31
    Import Monitor is stopped.
    <br>*************************************************************************************************************************************************
    <br>SAPAPPL02.LOG
    <br>**************************************************************************************************************************************************
    <br>TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
    (IMP) INFO: a failed DROP attempt is not necessarily a problem
    (DB) INFO: TVV1 created #20091001110304
    <br>
    (DB) INFO: TVV1 deleted/truncated #20091001110304
    <br>
    (IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
    <br>
    (DB) ERROR: DDL statement failed<br>
    (ALTER TABLE "TVV1" DROP PRIMARY KEY )<br>
    DbSlExecute: rc = 99<br>
      (SQL error -539)<br>
      error message returned by DbSl:
    Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
    Your inputs will help a lot.
    Regards,
    Prasad

    Hello,
    We are doing an installation of SAP NW 7.01 SR1 on V6R1.
    <br>
    We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
    <br>
    We are again getting error in following steps:
    <br>
    sapinst.log
    <br>
    <br>WARNING 2009-09-30 23:25:28.477
    Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
    java version "1.4.2"
    Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
    IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
    J9VM - 20090309_31291_BHdSMr
    JIT  - 20090210_1447ifx1_r8
    GC   - 200902_24)
    I<br>mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
    <br>Loading of 'SAPNTAB' import package: OK
    <br>Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
    Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28.<br>
    Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28.<br>
    Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28.<br>
    Loading of 'DOKCLU' import package: OK
    Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28.<br>
    Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28.<br>
    Loading of 'SAPAPPL1' import package: OK
    Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28.<br>
    Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28.<br>
    Loading of 'SAPAPPL2' import package: ERROR
    Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28.<br>
    Loading of 'DD03L' import package: OK
    Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28.<br>
    Loading of 'SCPRSVALS' import package: OK
    Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28.<br>
    Loading of 'SAPSDIC' import package: OK
    Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28.<br>
    Loading of 'SCPRVALS' import package: OK
    Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28.<br>
    Loading of 'SAPSSRC' import package: OK
    Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28.<br>
    Loading of 'FUPARAREF' import package: OK
    Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28.<br>
    Loading of 'TODIR' import package: OK
    Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28.<br>
    Loading of 'SEOSUBCODF' import package: OK
    Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28.<br>
    Loading of 'E071K' import package: OK
    Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28.<br>
    Loading of 'SAPPOOL' import package: OK
    Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28.<br>
    Loading of 'SAPSPROT' import package: OK
    Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28.<br>
    Loading of 'SAPSDOCU' import package: OK
    Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28.<br>
    Loading of 'SAPCLUST' import package: OK
    Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28.<br>
    Loading of 'SAPSLOAD' import package: OK
    Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28.<br>
    Loading of 'SAPSLEXC' import package: OK
    Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28.<br>
    Loading of 'SAPUSER' import package: OK
    Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28.<br>
    Loading of 'SAPDDIM' import package: OK
    Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28.<br>
    Loading of 'SAPDFACT' import package: OK
    Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28.<br>
    Loading of 'SAPDODS' import package: OK
    Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28.<br>
    Loading of 'SAPUSER1' import package: OK
    Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28.<br>
    Loading of 'SAP0000' import package: OK
    Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28.<br>
    Loading of 'SAPAPPL0' import package: OK
    Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28.<br>
    Loading of 'SAPSSEXC' import package: OK
    Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28.<br>
    <br>
    WARNING[E] 2009-09-30 23:25:28.524
    CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
    <br>
    ERROR 2009-09-30 23:25:28.914
    FCO-00011  The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
    <br>
    <br>import_monitor.log.
    <br>****************************************************************************************************************************************************
    <br>INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
    Loading of 'SAP0000' import package is successfully completed.
    <br>
    INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL0' import package is successfully completed.
    <br>
    INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC' import package is successfully completed.
    <br>
    WARNING: 2009-09-30 23:31:31
    Cannot start import of packages with views because not all import packages with tables are loaded successfully.
    WARNING: 2009-09-30 23:31:31
    1 error(s) during processing of packages.
    INFO: 2009-09-30 23:31:31
    Import Monitor is stopped.
    <br>*************************************************************************************************************************************************
    <br>SAPAPPL02.LOG
    <br>**************************************************************************************************************************************************
    <br>TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
    (IMP) INFO: a failed DROP attempt is not necessarily a problem
    (DB) INFO: TVV1 created #20091001110304
    <br>
    (DB) INFO: TVV1 deleted/truncated #20091001110304
    <br>
    (IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
    <br>
    (DB) ERROR: DDL statement failed<br>
    (ALTER TABLE "TVV1" DROP PRIMARY KEY )<br>
    DbSlExecute: rc = 99<br>
      (SQL error -539)<br>
      error message returned by DbSl:
    Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
    Your inputs will help a lot.
    Regards,
    Prasad

  • Program updating the value with succeeding 0

    Hi
    We have got a problem.
    We have developed a program to update the value of the condition type. The upload file will have the SO, line item, condition type and value.
    In the background, the sales order change BAPI is called and the value of the condition type is updated. There is no bug in the program for this functionality with reference to the problem.
    When I upload, the value is getting uploaded correctly. But for some users, the value is updated with an additional 0 at the end. For example if 78 is the value of a condition type, the update happens as 780. The strange behaviour is that if I take that user id and password and upload in my laptop, the value is correctly uploaded without any addtional 0.
    We have checked the user profile of all the problamatic users. They are fine. The xls sheet decimal notation is checked and they are also fine. There is no bug in the program, as it is working fine for many users.
    What else should I be checking to solve this issue. An ABAPer advised to check the GUI level difference. I dont know how to do that but there should not be any such difference in the GUI versions for the users.
    Can somebody put some light on this issue.

    Hi Navaneetha,
    The Excel version is the same for you and the user?
    Can the same be debugged and rectified?
    Regards
    Saurabh

  • I downloaded an update for my Safari web browser to "snow leopard". When I click on the .dmg file, a window opens up with a .pkg file but when I click on the .pkg file I get a prompt saying that it doesn't know what program to open it with. with a

    I downloaded an update for my Safari web browser to "snow leopard". When I click on the .dmg file, a window opens up with a .pkg file but when I click on the .pkg file I get a prompt saying that it doesn't know what program to open it with.

    I suspect if you're trying to open a file in 08 that's been opened in 09 the file has been updated to 09 and will not open in 08.

  • How to program a midi foot controller on Mainstage? Does anyone knows how to program the foot controller with exclusive solo channel in order not to dance "tip tap" while from clean guitar I go to crunch or solo? How to do this programming on Mainstage?

    How to program a midi foot controller on Mainstage? Does anyone knows how to program the foot controller with exclusive solo channel in order not to dance "tip tap" while from clean guitar I go to crunch or solo? How to do this programming on Mainstage?
    I basically managed to learn how to invert parameters which allows me to be as default in the clean guitar channel and if I switch the first button on the midi foot controller I switch to crunch, but at this point I tryied so hard to programm the second and third button to switch, only through a button in one step, to a third channel for distorsion or a 4th channel for solo guitar but I couldn't figured out how this work can be done!
    I would appreciate if anyone could help or share this experience with others who are experiencing the same problem.
    Cheers.
    F.

    I cannot seem to get mainstage to recognize my FCB either. I am using IFCB. Anyone figure this out?
    Thanks,
    Eric

  • I Have a Mac 10.9.5 I have Photoshop CS 5.. Also have Photoshop CC. As of last month was able to edit any image with either program,as of today I can't edit images in either program. I can't see and editing I've done ,but when close the image both program

    I Have a Mac 10.9.5 I have Photoshop CS 5.. Also have Photoshop CC. As of last month was able to edit any image with either program,as of today I can't edit images in either program. I can't see and editing I've done ,but when close the image both program ask (do you want to save changes) I look at the image I don't see any changes to save. Please help Thanks for time in advance

    Please describe the steps involved in the issue exactly (with screenshots maybe).
    What have you done for trouble-shooting so far?
    http://blogs.adobe.com/crawlspace/2012/07/photoshop-basic-troubleshooting-steps-to-fix-mos t-issues.html

  • What word processing program should I use with my Mac, what word processing program should I use with my Mac, what word processing program should I use with my Mac

    what word processing program should I use with my Mac?

    steve359 wrote:
    For free you can download NeoOffice
    Not quite. Downloading the current version of NeoOffice is definitely not free (downloading the previous version is). The developers of NeoOffice (the most Mac-like of the StarOffice descendants) make a distinction between the application itself (which is free) and downloading it, for which they require what they are pleased to call a "donation" (since it's mandatory, I would call it a fee).
    shldr2thewheel wrote:
    I totally forget about TextEdit all the time..
    Indeed. For basic WP tasks, TextEdit can be quite satisfactory.
    embauerxz
    I only need it for reports
    Would that include the report on the state of the US economy -- you know, the one President Obama asked you to deliver to the White House no later than 7AM on January 4? The one in two columns, with numbered paragraphs, table of contents, footnotes, mathematical formulae, 40 figures, 60 charts, quotations in Arabic, Japanese, and classical Greek, and 15 pages of references in APA style?
    Grant Bennet-Alder is right -- "the real answer depends on what work you expect to do with it, and with whom you expect to do this work". There are dozens of word processors for Mac, from the venerable Word to the no less venerable Tex-Edit+. It would pointless to start listing them all, when many of them might be either too little or too much for your needs.

  • Programming multiple smart cards with multiple smart card readers in a PC causes a PCSCException in a smart card that is in progress

    Hi,
    I develop a Java code using smartcardio API to program a smart card. My GUI allows to add at most 5 smart card readers that will wait for card present, then do authentication and program the smart card with an application, then wait for card removal. This is a separate thread running in a loop for each smart card reader added as programmer.
    The problem occurs when a certain smart card is in progress and I inserted another smart card to another smart card reader.  Both smart card reader halts and throw sun.security.smartcardio.PCSCException: Unknown error 0x8010002f.
    I also observed that every time there is an attempt to insert/remove a smart card in the smart card reader that is connected to the USB port would cause the programming in progress to be interrupted and throw the PCSCException.
    These are some exceptions I got during my testing:
    sun.security.smartcardio.PCSCException: Unknown error 0x8010002f
      at sun.security.smartcardio.PCSC.SCardTransmit(Native Method)
      at sun.security.smartcardio.ChannelImpl.doTransmit(ChannelImpl.java:171)
    java.lang.Exception: Loader Record Failed: 6E | 0 //Sometimes I got this return code SW1 0x6E SW2 0x00 which means an APDU with an invalid 'CLA' bytes was received. I had check the command before it was sent and it was correct.
    Help me understand this issue. I think the CardTerminal.isCardPresent(), CardTerminal.waitForCardPresent(0), and CardTerminal.waitForCardAbsent(0) cause this issue that CardChannel.transmit(apduCommand) is interrupted or the smart card insertion/removal causes the CardChannel.transmit(apduCommand) is interrupted.
    Regards,
    Knivez

    Hi,
    when you work with one smartcard reader only usually you address the slot -1 that means "the first found".
    But to deal with multiple readers you have to use slots of course since one reader will be slot 0, next reader will be slot 1 and so on...
    So a credential object will be identified on a system by a couple
    <slot,alias>
    After that, the way to address slots (I mean the syntax) depends on the classes you are using...
    Bye

  • A problem caused this program to stop interacting with Windows

    I try to run Photoshop.exe, but it doesn't respond. I get this error message. How to fix it? I have no idea where is a problem? I had no problems with it earlier.
    ERROR MESSAGE:
    Description:
    A problem caused this program to stop interacting with Windows.
    Problem signature:
    Problem Event Name: AppHangB1
    Application Name: Photoshop.exe
    Application Version: 8.0.0.0
    Application Timestamp: 3fce5708
    Hang Signature: 1875
    Hang Type: 0
    OS Version: 6.0.6001.2.1.0.256.1
    Locale ID: 1063
    Additional Hang Signature 1: 3732c99c21cdca196fbfee3cc7094b85
    Additional Hang Signature 2: 848c
    Additional Hang Signature 3: 5c7261f725b6a443e8327138a3fe0208
    Additional Hang Signature 4: 1875
    Additional Hang Signature 5: 3732c99c21cdca196fbfee3cc7094b85
    Additional Hang Signature 6: 848c
    Additional Hang Signature 7: 5c7261f725b6a443e8327138a3fe0208
    Read our privacy statement:
    http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409

    I suspect a RAM or hardware problem.

  • How can I transfer old Palm Pilot (Z22) info (calendar/to do lists/memos/contacts is synced to a Windows XP) to a program I can access with an iPod?

    How can I transfer old Palm Pilot (Z22) info (calendar/to do lists/memos/contacts is synced to a Windows XP) to a program I can access with an iPod? Thanks.

    Maybe by the link provided here:
    Palm Desktop and iPhone

  • Description: A problem caused this program to stop interacting with Windows. Problem signature: Problem Event Name: AppHangB1 Application Name: firefox.exe Application Version: 1.9.2.3855 Application Timestamp: 4c48d5ce Hang Signature: 9962

    I am having this problem, in the first window when I try to do anything.
    Description:
    A problem caused this program to stop interacting with Windows.
    Problem signature:
    Problem Event Name: AppHangB1
    Application Name: firefox.exe
    Application Version: 1.9.2.3855
    Application Timestamp: 4c48d5ce
    Hang Signature: 9962
    Hang Type: 0
    OS Version: 6.0.6002.2.2.0.768.3
    Locale ID: 1033
    Additional Hang Signature 1: 5df72ce88195c0212c542e9c8c172716
    Additional Hang Signature 2: 2b94
    Additional Hang Signature 3: 9acafbb8ad01bf9d2eb258d8fddad3ca
    Additional Hang Signature 4: 9962
    Additional Hang Signature 5: 5df72ce88195c0212c542e9c8c172716
    Additional Hang Signature 6: 2b94
    Additional Hang Signature 7: 9acafbb8ad01bf9d2eb258d8fddad3ca
    == This happened ==
    Every time Firefox opened
    == User Agent ==
    Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.99 Safari/533.4

    I suspect a RAM or hardware problem.

  • A contact and calander program that can sync with iTunes

    Hi There Everydoby-
      I was wondering if anybody know of a free calander and contact program that can sync with iTunes and my iPod touch. I do not have Microsoft Office, I currently use Open Office for my word and Excel documents. But I do not have a clalander or contact program that will sync with iTunes.
      So if anybody can let me know if anybody is using or know's of what I can use that will work with iTunes, i'd really appriciate it.
    Thanks- Doug

    Hey Galilio,
    You can try restoring the iPhone from a backup that is dated before the contacts were erased. This article: http://support.apple.com/kb/HT1766 will walk you through restoring the iPhone from backup.
    You can also Reset the Sync History from the iTunes preferences window, under Devices. This would force iTunes to prompt you again, asking if you want to merge or replace contacts. This article: http://support.apple.com/kb/HT1692 provides more information.
    -Jason

Maybe you are looking for