LPCXpresso IDEのトピックRe: LPCXpresso for Linux: Connection to LPC-Link failed

LPCXpresso for Linux: Connection to LPC-Link failed

lpcware — Wed, 15 Jun 2016 23:04:22 GMT

Content originally posted in LPCWare by mrib on Mon Sep 20 11:46:22 MST 2010
After connecting LPCXpresso LPC1768 board, lsusb shows following:
ID 0471:df55 Philips

When clicking debug button an error message appears, see first attached file.
Lsusb shows following ID after clicking ok:
ID 1fc9:0009

Again clicking debug different error messages appear, see last 2 files.

The system is ubuntu 9.10 (Karmic Koala). Any idea what could be the reason?

Re: LPCXpresso for Linux: Connection to LPC-Link failed

lpcware — Wed, 15 Jun 2016 23:04:23 GMT

Content originally posted in LPCWare by CodeRedSupport on Mon Sep 20 11:59:37 MST 2010
This problem is normally when the PATH is not being seen correctly by the IDE.

Could you try logging out and logging back in again, and then try running lpcxpresso again.

Thanks

Re: LPCXpresso for Linux: Connection to LPC-Link failed

lpcware — Wed, 15 Jun 2016 23:04:23 GMT

Content originally posted in LPCWare by mrib on Mon Sep 20 12:06:47 MST 2010
Yes, you are right. After rebooting the system LPCXpresso for Linux works like a charm!
Thanks for the hint.

Re: LPCXpresso for Linux: Connection to LPC-Link failed

lpcware — Wed, 15 Jun 2016 23:04:24 GMT

Content originally posted in LPCWare by kredz on Mon Sep 20 12:27:40 MST 2010
Hi,

I have the same problem with LPC-link as mrib - "No emulator or board available". lsusb tells me that firmware was correctly uploaded, I added all vendor/product ids to udev rules, so there are proper rights set. I have Ubuntu 10.04 64-bit, tried restart/logout without success. Any idea what is wrong?

BR,
Krzysztof

P.S. Some logs:

!ENTRY com.crt.utils 4 -1 2010-09-20 21:35:23.758
!MESSAGE crt_emu_lpc11_13_nxp -mi -info-emu
!STACK 0
org.xml.sax.SAXParseException: Premature end of file.
    at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown Source)
    at org.xml.sax.helpers.XMLFilterImpl.parse(Unknown Source)
    at com.crt.utils.xmlparser.XMLParser.parse(XMLParser.java:267)
    at com.crt.utils.xmlparser.XMLParser.processInput(XMLParser.java:513)
    at com.crt.utils.general.ExecCommand.execCommand(ExecCommand.java:329)
    at com.crt.utils.general.ExecCommand.exec(ExecCommand.java:229)
    at com.crt.utils.xmlparser.XMLParser.parseXML(XMLParser.java:396)
    at com.crt.ctrlcenter.emulator.EmulatorsDB.createFromCommand(EmulatorsDB.java:104)
    at com.crt.ctrlcenter.emulator.EmulatorsDB.getEmulatorInfo(EmulatorsDB.java:213)
    at com.crt.ctrlcenter.emulator.EmulatorsDB.getEmulatorInfo(EmulatorsDB.java:140)
    at com.crt.ctrlcenter.emulator.EmulatorsDB.<init>(EmulatorsDB.java:90)
    at com.crt.ctrlcenter.emulator.EmulatorsDB.<init>(EmulatorsDB.java:77)
    at com.crt.ctrlcenter.launch.CRTMCUDebugger.getEmulatorInfo(CRTMCUDebugger.java:789)
    at com.crt.ctrlcenter.launch.CRTMCUDebugger.<init>(CRTMCUDebugger.java:281)
    at com.crt.ctrlcenter.launch.CRTMCULaunchConfigurationDelegate.syncLaunch(CRTMCULaunchConfigurationDelegate.java:241)
    at com.crt.ctrlcenter.launch.CRTMCULaunchConfigurationDelegate.launch(CRTMCULaunchConfigurationDelegate.java:193)
    at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:853)
    at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703)
    at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:866)
    at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1069)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

!ENTRY com.crt.log 1 0 2010-09-20 21:35:25.417
!MESSAGE Drivers loaded in 1425 milliseconds

!ENTRY com.crt.utils 4 -1 2010-09-20 21:35:25.461
!MESSAGE crt_emu_lpc11_13_nxp -mi -info-emu -wire=winUSB
!STACK 0
org.xml.sax.SAXParseException: Premature end of file.
    at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown Source)
    at org.xml.sax.helpers.XMLFilterImpl.parse(Unknown Source)
    at com.crt.utils.xmlparser.XMLParser.parse(XMLParser.java:267)
    at com.crt.utils.xmlparser.XMLParser.processInput(XMLParser.java:513)
    at com.crt.utils.general.ExecCommand.execCommand(ExecCommand.java:329)
    at com.crt.utils.general.ExecCommand.exec(ExecCommand.java:229)
    at com.crt.utils.xmlparser.XMLParser.parseXML(XMLParser.java:396)
    at com.crt.ctrlcenter.emulator.EmulatorsDB.createFromCommand(EmulatorsDB.java:104)
    at com.crt.ctrlcenter.emulator.EmulatorsDB.getEmulatorInfo(EmulatorsDB.java:213)
    at com.crt.ctrlcenter.emulator.EmulatorsDB.getEmulatorInfo(EmulatorsDB.java:140)
    at com.crt.ctrlcenter.emulator.EmulatorsDB.<init>(EmulatorsDB.java:90)
    at com.crt.ctrlcenter.emulator.EmulatorsDB.<init>(EmulatorsDB.java:77)
    at com.crt.ctrlcenter.launch.CRTMCUDebugger.getEmulatorInfo(CRTMCUDebugger.java:789)
    at com.crt.ctrlcenter.launch.CRTMCUDebugger.<init>(CRTMCUDebugger.java:281)
    at com.crt.ctrlcenter.launch.CRTMCULaunchConfigurationDelegate.syncLaunch(CRTMCULaunchConfigurationDelegate.java:241)
    at com.crt.ctrlcenter.launch.CRTMCULaunchConfigurationDelegate.launch(CRTMCULaunchConfigurationDelegate.java:193)
    at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:853)
    at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703)
    at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:866)
    at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1069)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

!ENTRY com.crt.utils 4 -1 2010-09-20 21:35:25.484
!MESSAGE crt_emu_lpc11_13_nxp -mi -info-emu -wire=hid
!STACK 0
org.xml.sax.SAXParseException: Premature end of file.
    at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown Source)
    at org.xml.sax.helpers.XMLFilterImpl.parse(Unknown Source)
    at com.crt.utils.xmlparser.XMLParser.parse(XMLParser.java:267)
    at com.crt.utils.xmlparser.XMLParser.processInput(XMLParser.java:513)
    at com.crt.utils.general.ExecCommand.execCommand(ExecCommand.java:329)
    at com.crt.utils.general.ExecCommand.exec(ExecCommand.java:229)
    at com.crt.utils.xmlparser.XMLParser.parseXML(XMLParser.java:396)
    at com.crt.ctrlcenter.emulator.EmulatorsDB.createFromCommand(EmulatorsDB.java:104)
    at com.crt.ctrlcenter.emulator.EmulatorsDB.getEmulatorInfo(EmulatorsDB.java:213)
    at com.crt.ctrlcenter.emulator.EmulatorsDB.getEmulatorInfo(EmulatorsDB.java:140)
    at com.crt.ctrlcenter.emulator.EmulatorsDB.<init>(EmulatorsDB.java:90)
    at com.crt.ctrlcenter.emulator.EmulatorsDB.<init>(EmulatorsDB.java:77)
    at com.crt.ctrlcenter.launch.CRTMCUDebugger.getEmulatorInfo(CRTMCUDebugger.java:789)
    at com.crt.ctrlcenter.launch.CRTMCUDebugger.<init>(CRTMCUDebugger.java:281)
    at com.crt.ctrlcenter.launch.CRTMCULaunchConfigurationDelegate.syncLaunch(CRTMCULaunchConfigurationDelegate.java:241)
    at com.crt.ctrlcenter.launch.CRTMCULaunchConfigurationDelegate.launch(CRTMCULaunchConfigurationDelegate.java:193)
    at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:853)
    at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703)
    at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:866)
    at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1069)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Re: LPCXpresso for Linux: Connection to LPC-Link failed

lpcware — Wed, 15 Jun 2016 23:04:25 GMT

Content originally posted in LPCWare by mrib on Mon Sep 20 12:32:25 MST 2010
Okay, I was a little too fast...

Connection to LPC-Link works fine the first time after connecting the board to USB. The 2nd time invoking a debug session fails. Error messages like attached file 2 and 3 on initial post.

Any idea why I have to physically re-connect the board every time a debug session terminated?

Re: LPCXpresso for Linux: Connection to LPC-Link failed

lpcware — Wed, 15 Jun 2016 23:04:25 GMT

Content originally posted in LPCWare by CodeRedSupport on Mon Sep 20 12:41:51 MST 2010
Kredz

This looks like a permissions problem.

As an experiment can you try running the who IDE as Sudo and let me know what happens?

Re: LPCXpresso for Linux: Connection to LPC-Link failed

lpcware — Wed, 15 Jun 2016 23:04:26 GMT

Content originally posted in LPCWare by CodeRedSupport on Mon Sep 20 12:53:40 MST 2010
mrib

When you get this error, what does lsusb (from the commamd line) report?

Re: LPCXpresso for Linux: Connection to LPC-Link failed

lpcware — Wed, 15 Jun 2016 23:04:26 GMT

Content originally posted in LPCWare by kredz on Mon Sep 20 12:54:57 MST 2010

Quote: CodeRedSupport
Kredz

This looks like a permissions problem.

As an experiment can you try running the who IDE as Sudo and let me know what happens?

Nothing changed, there is the same problem. What is command if I would like to run gdb directly in the terminal?

P.S. I notticed that I have following error:
/usr/lib/gio/modules/libgvfsdbus.so: wrong ELF class: ELFCLASS64
Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so

Re: LPCXpresso for Linux: Connection to LPC-Link failed

lpcware — Wed, 15 Jun 2016 23:04:27 GMT

Content originally posted in LPCWare by mrib on Mon Sep 20 13:29:18 MST 2010
After connecting the board to USB, lsusb shows:
ID 0471:df55 Philips

and lsusb -d 0471:df55 -v:

Bus 001 Device 017: ID 0471:df55 Philips
Device Descriptor:
bLength                18
bDescriptorType         1
bcdUSB               2.00
bDeviceClass            0 (Defined at Interface level)
bDeviceSubClass         0
bDeviceProtocol         0
bMaxPacketSize0        64
idVendor           0x0471 Philips
idProduct          0xdf55
bcdDevice            0.01
iManufacturer           0
iProduct                0
iSerial                 0
bNumConfigurations      1
Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           25
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           0
      bInterfaceClass       254 Application Specific Interface
      bInterfaceSubClass      1 Device Firmware Update
      bInterfaceProtocol      0
      iInterface              0
      Device Firmware Upgrade Interface Descriptor:
        bLength                             7
        bDescriptorType                    33
        bmAttributes                        1
          Will Not Detach
          Manifestation Intolerant
          Upload Unsupported
          Download Supported
        wDetachTimeout                  65535 milliseconds
        wTransferSize                    2048 bytes
Device Qualifier (for other device speed):
bLength                10
bDescriptorType         6
bcdUSB               2.00
bDeviceClass            0 (Defined at Interface level)
bDeviceSubClass         0
bDeviceProtocol         0
bMaxPacketSize0        64
bNumConfigurations      1
Device Status:     0x0000
(Bus Powered)

During debugging, lsusb shows:
ID 1fc9:0009

And lsusb -d 1fc9:0009 -v:

Bus 001 Device 018: ID 1fc9:0009
Device Descriptor:
bLength                18
bDescriptorType         1
bcdUSB               2.00
bDeviceClass            0 (Defined at Interface level)
bDeviceSubClass         0
bDeviceProtocol         0
bMaxPacketSize0        64
idVendor           0x1fc9
idProduct          0x0009
bcdDevice            1.00
iManufacturer           1 Code Red Technologies
iProduct                2 LPC-Link Probe v1.1
iSerial                 3 T1S6RGRIA
bNumConfigurations      1
Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82 EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200 1x 512 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02 EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200 1x 512 bytes
        bInterval               1
Device Qualifier (for other device speed):
bLength                10
bDescriptorType         6
bcdUSB               2.00
bDeviceClass            0 (Defined at Interface level)
bDeviceSubClass         0
bDeviceProtocol         0
bMaxPacketSize0        64
bNumConfigurations      1
Device Status:     0x0000
(Bus Powered)

After termination of debug session, lsusb shows still:
ID 1fc9:0009

Relaunching a debug session again fails. Lsusb has the same output as before.

I have to power cycle the board (dis- and re-connect to USB) before I can start debugging again.

Re: LPCXpresso for Linux: Connection to LPC-Link failed

lpcware — Wed, 15 Jun 2016 23:04:28 GMT

Content originally posted in LPCWare by CodeRedSupport on Mon Sep 20 14:16:45 MST 2010
Kredz

Can you run this command and post the output
crt_emu_lpc11_13_nxp -mi -info-emu -wire=winUSB

Can you also run with strace and post that output?

Also when is the elf error reported?

Re: LPCXpresso for Linux: Connection to LPC-Link failed

lpcware — Wed, 15 Jun 2016 23:04:28 GMT

Content originally posted in LPCWare by jeffg on Mon Sep 20 15:03:44 MST 2010
Hi,

Firstly thanks so much for Linux support! I bought an LPCXpresso board when it came out, and it's been sat in a drawer since the moment I discovered it was windows-only. Today I installed the software (on my Fedora 13) and started developing!

Unfortunately I'm experiencing exactly the same symptoms. I plug in the board, build the blinky demo and click on the Debug (bug) button. It works the first time without a hitch. Then I click Stop, make a code change and click Debug again, and I get the "Unable to initialise LPC link" popup box as shown in mrib's second screenshot, followed by the "no emulator or board available" box, as shown in his third.

Executing your command suggested above yields:

[jeff@chisel ~]$ crt_emu_lpc11_13_nxp -mi -info-emu -wire=winUSB#
Ni: LPCXpresso Debug Driver v2.0 (Sep 17 2010 18:37:43)
<emulators available="1" type="Debug">
 <emu index="0" is_connected="false" shortname="LPCLINK_1_1" manu="Code Red - LPCXpresso">LPC-Link Driver LINUX32 v1.1</emu>
</emulators>

On a fresh installation, I had problems like the "Cannot run program arm-none-eabi-gdb" until I added "/usr/local/LPCXpresso/tools/bin" to my PATH variable by adding

export PATH=$PATH:/usr/local/LPCXpresso/tools/bin

to my ~/.bashrc file.

Re: LPCXpresso for Linux: Connection to LPC-Link failed

lpcware — Wed, 15 Jun 2016 23:04:29 GMT

Content originally posted in LPCWare by kredz on Mon Sep 20 21:31:12 MST 2010

Quote: CodeRedSupport
Kredz

Can you run this command and post the output
crt_emu_lpc11_13_nxp -mi -info-emu -wire=winUSB

Can you also run with strace and post that output?

Also when is the elf error reported?

I will try this later. 64bit compatibility error is reported when I start debugging. Today I will check LPCXpresso on 32-bit Ubuntu 10.04, I will tell you results later.

Re: LPCXpresso for Linux: Connection to LPC-Link failed

lpcware — Wed, 15 Jun 2016 23:04:30 GMT

Content originally posted in LPCWare by kredz on Mon Sep 20 22:10:20 MST 2010

Quote: kredz
I will try this later. 64bit compatibility error is reported when I start debugging. Today I will check LPCXpresso on 32-bit Ubuntu 10.04, I will tell you results later.

I installed LPCXpresso on 32-bit Ubuntu 10.04 and it works correctly from the beginning. So, there are some 64-bit compatibility issues.

Re: LPCXpresso for Linux: Connection to LPC-Link failed

lpcware — Wed, 15 Jun 2016 23:04:30 GMT

Content originally posted in LPCWare by CodeRedSupport on Mon Sep 20 23:39:28 MST 2010
kredz,

Did you install *all* of the 32-bit compatibility components as required in the Release notes? To install all of the components:
sudo apt-get install linux32 ia32*
(Note that the '*'' is required.)

Re: LPCXpresso for Linux: Connection to LPC-Link failed

lpcware — Wed, 15 Jun 2016 23:04:31 GMT

Content originally posted in LPCWare by mrib on Tue Sep 21 00:12:42 MST 2010

Quote: kredz
I installed LPCXpresso on 32-bit Ubuntu 10.04 and it works correctly from the beginning.

Did you try to debug on the target? Does it work multiple times (terminate debug session and start a new one)?

Re: LPCXpresso for Linux: Connection to LPC-Link failed

lpcware — Wed, 15 Jun 2016 23:04:31 GMT

Content originally posted in LPCWare by CodeRedSupport on Tue Sep 21 00:46:53 MST 2010
mrib,

Can you run the following commands from the command line, before LPC-Link is booted, after LPC-Link is booted, and again when you are unable to debug for the 2nd time.. Please post *all* of the output:

dfu-util -V
dfu-util -l
lsusb

Can you please also state which Linux distribution and version your are using, and confirm that it is completely up-to-date.

Thanks

Re: LPCXpresso for Linux: Connection to LPC-Link failed

lpcware — Wed, 15 Jun 2016 23:04:32 GMT

Content originally posted in LPCWare by kredz on Tue Sep 21 04:49:03 MST 2010

Quote: mrib
Did you try to debug on the target? Does it work multiple times (terminate debug session and start a new one)?

Hi, I tried multiple times launch debug session and there is no problem. On 32-bit Ubuntu 10.04. When I'll get home, I will try 64-bit version.

Re: LPCXpresso for Linux: Connection to LPC-Link failed

lpcware — Wed, 15 Jun 2016 23:04:32 GMT

Content originally posted in LPCWare by kredz on Tue Sep 21 08:52:04 MST 2010

Result is following:

./crt_emu_lpc11_13_nxp -mi -info-emu -wire=winUSB
Ni: LPCXpresso Debug Driver v2.0 (Sep 17 2010 18:37:43)
<emulators available="1" type="Debug">
<emu index="0" is_connected="false" shortname="LPCLINK_1_1" manu="Code Red - LPCXpresso">LPC-Link Driver LINUX32 v1.1</emu>
</emulators>

But what is the most amazing - today I just boot computer and run LPCXpresso IDE on Ubuntu 64-bit and everything worked fine. Very strange - I rebooted many times yesterday :)

Re: LPCXpresso for Linux: Connection to LPC-Link failed

lpcware — Wed, 15 Jun 2016 23:04:33 GMT

Content originally posted in LPCWare by CodeRedSupport on Tue Sep 21 09:16:50 MST 2010
OK - Thanks for letting us know. We have had it working on Ubuntu 64-bit for a while, so it was always a little strange why yours didn't work. Please report back if you find out why yours has suddenly started working.

Re: LPCXpresso for Linux: Connection to LPC-Link failed

lpcware — Wed, 15 Jun 2016 23:04:33 GMT

Content originally posted in LPCWare by mrib on Tue Sep 21 11:08:34 MST 2010

Quote: CodeRedSupport
mrib,

Can you run the following commands from the command line, before LPC-Link is booted, after LPC-Link is booted, and again when you are unable to debug for the 2nd time.. Please post *all* of the output:

dfu-util -V
dfu-util -l
lsusb

Can you please also state which Linux distribution and version your are using, and confirm that it is completely up-to-date.

Thanks

Before first debug launch:

$ dfu-util -V
dfu-util - (C) 2007-2008 by OpenMoko Inc.
This program is Free Software and has ABSOLUTELY NO WARRANTY

dfu-util version 0.1+svn

$ dfu-util -l
dfu-util - (C) 2007-2008 by OpenMoko Inc.
This program is Free Software and has ABSOLUTELY NO WARRANTY

Found Runtime: [0x049f:0x0086] devnum=3, cfg=0, intf=2, alt=0, name="UNDEFINED"
Found Runtime: [0x0471:0xdf55] devnum=11, cfg=0, intf=0, alt=0, name="UNDEFINED"

$ lsusb
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 003: ID 049f:0086 Compaq Computer Corp. Bluetooth Device
Bus 004 Device 002: ID 046d:c016 Logitech, Inc. M-UV69a/HP M-UV96 Optical Wheel Mouse
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 011: ID 0471:df55 Philips
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

After termination of first debug session:

$ dfu-util -V
dfu-util - (C) 2007-2008 by OpenMoko Inc.
This program is Free Software and has ABSOLUTELY NO WARRANTY

dfu-util version 0.1+svn

$ dfu-util -l
dfu-util - (C) 2007-2008 by OpenMoko Inc.
This program is Free Software and has ABSOLUTELY NO WARRANTY

Found Runtime: [0x049f:0x0086] devnum=3, cfg=0, intf=2, alt=0, name="UNDEFINED"

$ lsusb
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 003: ID 049f:0086 Compaq Computer Corp. Bluetooth Device
Bus 004 Device 002: ID 046d:c016 Logitech, Inc. M-UV69a/HP M-UV96 Optical Wheel Mouse
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 012: ID 1fc9:0009
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

After error message of unsuccessful 2nd debug launch:

$ dfu-util -V
dfu-util - (C) 2007-2008 by OpenMoko Inc.
This program is Free Software and has ABSOLUTELY NO WARRANTY

dfu-util version 0.1+svn

$ dfu-util -l
dfu-util - (C) 2007-2008 by OpenMoko Inc.
This program is Free Software and has ABSOLUTELY NO WARRANTY

Found Runtime: [0x049f:0x0086] devnum=3, cfg=0, intf=2, alt=0, name="UNDEFINED"

$ lsusb
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 003: ID 049f:0086 Compaq Computer Corp. Bluetooth Device
Bus 004 Device 002: ID 046d:c016 Logitech, Inc. M-UV69a/HP M-UV96 Optical Wheel Mouse
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 012: ID 1fc9:0009
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Distribution is Ubuntu 9.10 - Karmic Koala and is up to date.