LPCXpresso for Linux: Connection to LPC-Link failed

[lpcware]

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?

[lpcware]

Content originally posted in LPCWare by alessio.margan on Mon Jun 13 08:12:22 MST 2011

---

Quote: CodeRedSupport
The only time I can remember seeing segmentation faults like this in the  past, the cause was eventually identified as being that something had  changed the access permissions on the LPCXpresso IDE installation. More  details at:

http://knowledgebase.nxp.com/showthread.php?t=1541

[the last couple of pages are the most relevant]

Thanks ... using strace solve my problems.

1) there a was permissions problem on /dev/bus/usb/0XX/0YY
adding a permission rule like this
SUBSYSTEMS=="usb",ATTRS{idVendor}=="0471",ATTRS{idProduct}=="df55",GROUP="users",MODE="0666"
SUBSYSTEMS=="usb",ATTRS{idVendor}=="1fc9",ATTRS{idProduct}=="0009",GROUP="users",MODE="0666"
give me access on usb device

2) since I have reinstalled the IDE I need to regenerate serial and activation code.

Alessio

---

[lpcware]

Content originally posted in LPCWare by CodeRedSupport on Fri Jun 17 00:27:38 MST 2011
You have asked the same question in a different thread. The answer is the same. The messages that you have posted ARE COMPLETELY NORMAL. There is nothing wrong!

If you have a problem:
1. Create a new Thread and don't post in existing thread
2. Explain what the problem is, and any error dialogs that are displayed. I repeat, what you have posted so far is completely normal - there is no error.

[lpcware]

Content originally posted in LPCWare by Spencer on Thu Jun 16 17:25:26 MST 2011
dear sir:

I use LPCXpresso 3.6.3 version(317) to work.
IC: NXP LPC1114(202)

But it shows following message:
***********************************
[COLOR=black]set remotetimeout 60000
set mem inaccessible-by-default off
Debugging a target over a serial line.
Program stopped at 0x75e.
Type "info stack" or "info registers" for more information.
mon ondisconnect cont
set arm force-mode thumb
info proc
Undefined info command: "proc".  Try "help info".
info program
Note: automatically using hardware breakpoints for read-only addresses.
***********************************[/COLOR]

How to deal with?

[lpcware]

Content originally posted in LPCWare by CodeRedSupport on Mon Jun 13 05:23:53 MST 2011

---

Quote: alessio.margan

5) crt_emu_lpc11_13_nxp -info-target -pLPC1114/302 -wire=winusb -4
Ni: LPCXpresso Debug Driver v2.0 (Apr  1 2011 10:53:18)
GetModuleFileName path == /usr/local/src/LPCXpresso/bin/crt_emu_lpc11_13_nxp
Nc: Looked for chip XML file in /usr/local/src/LPCXpresso/bin/LPC1114/302.xml
Nc: Looked for vendor directory XML file in /usr/local/src/LPCXpresso/bin/nxp_directory.xml
Nc: Found generic directory XML file in /usr/local/src/LPCXpresso/bin/crt_directory.xml
AP Ack: 04
Nc: Mem-AP ID: 0x04770021  ROM Addr: 0xE00FF003
Nc: Emu(0): Conn&Reset. DpID:  BB11477. Info: LPCLINK_1_1
Nc: SWD Frequency: 3000 KHz. RTCK: False. Vector catch: False.
Nc: Packet delay: 0  Poll delay: 0.
Nc: NXP: LPC1114/302  Part ID: 0x2540102B
Segmentation fault

---

The only time I can remember seeing segmentation faults like this in the  past, the cause was eventually identified as being that something had  changed the access permissions on the LPCXpresso IDE installation. More  details at:

http://knowledgebase.nxp.com/showthread.php?t=1541

[the last couple of pages are the most relevant]

Regards,
CodeRedSupport.

[lpcware]

Content originally posted in LPCWare by alessio.margan on Mon Jun 13 03:01:08 MST 2011
Hi,

I've got problem with LPCXpresso board with target LCP1114/302.

I follow the diagnostics on http://support.code-red-tech.com/CodeRedWiki/LPCLinkDiagnostics
the result are :
1) dfu-util -l
dfu-util - (C) 2007-2008 by OpenMoko Inc.
This program is Free Software and has ABSOLUTELY NO WARRANTY

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

2) dfu-util -d 0x471:0xdf55 -c 0 -t 2048 -R -D LPCXpressoWIN.enc
dfu-util - (C) 2007-2008 by OpenMoko Inc.
This program is Free Software and has ABSOLUTELY NO WARRANTY
Opening USB Device 0x0471:0xdf55...
Claiming USB DFU Runtime Interface...
Determining device status: state = dfuIDLE, status = 0
WARNING: Runtime device already in DFU state ?!?
Found Runtime: [0x0471:0xdf55] devnum=11, cfg=0, intf=0, alt=0, name="UNDEFINED"
Claiming USB DFU Interface...
Setting Alternate Setting ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
Transfer Size = 0x0800
bytes_per_hash=604
Starting download: [##################################################] finished!
state(8) = dfuMANIFEST-WAIT-RESET, status(0) = No error condition is present
Done!
can't detach: error sending control message: Broken pipe
Resetting USB to switch back to runtime mode

3) lsusb
...
Bus 001 Device 012: ID 1fc9:0009
....

4) crt_emu_lpc11_13_nxp -info-emu -wire=winusb
Ni: LPCXpresso Debug Driver v2.0 (Apr  1 2011 10:53:18)
1 Emulators available:
0. LPCLINK_1_1    LPC-Link Driver LINUX32 v1.1 (Code Red - LPCXpresso)

5) crt_emu_lpc11_13_nxp -info-target -pLPC1114/302 -wire=winusb -4
Ni: LPCXpresso Debug Driver v2.0 (Apr  1 2011 10:53:18)
GetModuleFileName path == /usr/local/src/LPCXpresso/bin/crt_emu_lpc11_13_nxp
Nc: Looked for chip XML file in /usr/local/src/LPCXpresso/bin/LPC1114/302.xml
Nc: Looked for vendor directory XML file in /usr/local/src/LPCXpresso/bin/nxp_directory.xml
Nc: Found generic directory XML file in /usr/local/src/LPCXpresso/bin/crt_directory.xml
AP Ack: 04
Nc: Mem-AP ID: 0x04770021  ROM Addr: 0xE00FF003
Nc: Emu(0): Conn&Reset. DpID:  BB11477. Info: LPCLINK_1_1
Nc: SWD Frequency: 3000 KHz. RTCK: False. Vector catch: False.
Nc: Packet delay: 0  Poll delay: 0.
Nc: NXP: LPC1114/302  Part ID: 0x2540102B
Segmentation fault

dmesg report
crt_emu_lpc11_1[6792]: segfault at bfc6000b ip 00277dca sp bfc4af34 error 4 in libc-2.11.1.so[203000+153000]

I run Version: LPCXpresso 3.8.3 [Build 317] [08/04/2011] on ubuntu 10.04 LTS

what I miss ?

TIA

Alessio

[lpcware]

Content originally posted in LPCWare by the-canary-islands on Sun May 22 13:17:47 MST 2011
Hi guys,

I wanted to report what I did to install lpcxpresso on a linux compiled from scratch.

I've been skimming previous posts this last week before attempting to install, mostly to get familiarized with the whole thing.

It seems to me many of those reporting problems had the very same one as me.

In my case, udev sets devices up under `dev/bus/usb' like `/dev/bus/usb/X/Y', where X is the bus, and Y the device no.

Through an strace, I found out redcode tools expect to access it as `/dev/bus/usb/00X/00Y'.

This is how they can be found under `/sys' and believe is the "current standard" way udev even creates them (it's just that mine is a bit old).

I haven't dig any deeper than this so as to know if the problem is caused by libusb or redcode tools (believe the latter, as I've used libusb before and have never had such problem)

So, all I had to was a couple udev rules and scripts, which I'm pasting bellow:

SUBSYSTEM=="usb_device", SYSFS{idVendor}=="0471", SYSFS{idProduct}=="df55", MODE="0666", PR\
OGRAM="/bin/udev-pad %k", NAME="%c", RUN="/bin/dfu-lpcxpresso"

The above should be in a single line, and must live before any `usb_device' rule proccessed by udev (normally found in separate ascending-numbered files under `/etc/udev.d/rules').

What this rule does is to call `/bin/udev-pad' when the device 0x0471:0xdf55 is plugged. This script returns udev the full path where this device's node should be created (`%c').

Also, after the device's node has been setup, udev will call
`/bin/dfu-lpcxpresso' which will actually flash the device with
`LPCXpressoWIN.enc'.

Another similar rule is needed bellow the previous one  (remember, better in a single line). After being flashed, the hardware will reenumerate and will take whatever the vid/pid the firmware has been hardcoded with:

SUBSYSTEM=="usb_device", SYSFS{idVendor}=="1fc9", SYSFS{idProduct}=="0009", MODE="0666",
PROGRAM="/bin/udev-pad %k", NAME="%c"

Again, this rule will ask `/bin/udev-pad' for a suitable name, and from them on, the device should available and ready from both the ide, and the command-line.

The `MODE="0666"' is to allow your regular non-priviledged system's user actually use the hardware.

The scripts above mentioned follows:

----------------- /bin/udev-pad -------------------------------------------

#!/bin/sh

x=${1#usbdev}
bus=${x%%.*}
device=${x#*.}

# print bus and device number three-digits padded
printf "bus/usb/%03d/%03d\n" ${bus} ${device}

--------------- /bin/dfu-lpcxpresso ---------------------------------------

#!/bin/sh

# for logger
TAG=lpcxpresso

# hardware specific stuff
VID=0x0471
PID=0xdf55

# I've moved the firmware to /lib/firmware, and changed it's permissions to 644
FIRMWARE=/lib/firmware/LPCXpressoWIN.enc

# only perform the following if `ACTION' environment variable is "add", thus, if the device is being plugged in
if [ ${ACTION} = "add" ]; then

    # upload the firmware
    /usr/bin/dfu-util -d ${VID}:${PID} -c 0 -t 2048 -R -D  ${FIRMWARE}

    # check error code and write a message to the syslog, just to have some
    # feedback
    str="successfully flashed"

    if [ "$?" != "0" ]; then
        str="unable to flash the device!"
    fi
    /bin/logger -t ${TAG} ${str}
fi

------------------------------------------------------------

Also, and not willing to offend anybody, being an emacs user for quite a time, I couldn't resist completely avoiding the ide, which fortunately is possible.

I personally prefer using autoconf for my projects, overall when they have not only firmware, but also host-side  software, docs, schematics, etc.

So as I already have a cross-toolchain:

Created `/opt/lpcxpresso', and moved there the whole `bin/' directory, thus all the `crt_emu_*' binaries, the xml files, and the xme ones. I also chmod'ed everything but the binaries to a suitable 644.

Then just moved `arm-none-eabi-gdb' there as well. It's not the same gdb you get with your regular cross-toolchain, it has specific support from redcode.

And that's all. I hope this can help others with the same problem I had, or otherwise be useful some way or another.

It would be really nice if we could see in a future firmware's source code, though, or if provisions were taken to allow users write their own.

The lpc-link is quite a nice piece of hardware.

Regards,

[lpcware]

Content originally posted in LPCWare by rattus on Wed May 18 08:03:42 MST 2011
OK - I did a bit more exploration and found the solution in the "Linux IDE hangs initializing LPC-Link" thread.

The Code Red "LPCLinkVMissue" page at:

http://support.code-red-tech.com/CodeRedWiki/LPCLinkVMissue

perfectly described the issue; it was clear that the LPC-Link was being initialized, but the VM did not register the USB's switch from 'Philips-Composite' (pre-DFU), to 'LPC-Link Probe v1.1' (after reconnect in the VM).

I'm pretty sure this will also work for Windows, but I really have no interest in that environment.

So once again, for Parallels v4 at least using Ubuntu 11.04, this works:

connect the LPCXpresso USB
connect the USB to the Virtual Machine in the window that pops up

cd /usr/local/LPCXpresso/bin
dfu-util -d 0x471:0xdf55 -c 0 -t 2048 -R -D LPCXpressoWIN.enc

pop up the Parallels toolbar with ctrl+alt
From Devices, select USB -> Philips - Composite
connect the USB to the Virtual Machine again
confirm that ctrl+alt, Devices->USB now contains LPC-Link Probe v1.1

invoke LPCXpresso and debug away.

Hope this helps someone running Parallels on a Mac. I'll test Parallels v6 once they get their Parallels Tools for Linux act together for that version.

As noted elsewhere, try not to use the Unity UI in Ubuntu, as it tends to chop off some of the buttons in LPCXpresso.

Mike

[lpcware]

Content originally posted in LPCWare by CodeRedSupport on Wed May 18 01:05:04 MST 2011
If you find the need to use dfu-util, then use the parameters exactly as described at http://support.code-red-tech.com/CodeRedWiki/LPCLinkDiagnostics#Linux
These parameters are defined by the boot firmware in the ROM of the LPC3154 and are not changeable.

The output you have posted indicates that it has successfully loaded the firmware onto LPC-Link.

When the firmware has been loaded, the LPC-Link is disconnected from USB and then re-enumerated (as a different device). Your VM is going to need to cope with this, and allow the device to be reconnected. To check this is happening, after running dfu-util, use lsusb and see whether there is a device present with an ID of 1fc9:009.

[lpcware]

Content originally posted in LPCWare by larryvc on Tue May 17 22:46:12 MST 2011

---

Quote: rattus

Larry, you seem to have gotten past the  crt_emu_cm3_nxp issue; I installed all the 32-bit compatibility bits but still no joy. What was the secret?

---

Hi Mike,

I never fully discovered the secret.

I had to set up the USB filters in VirtualBox so that Ubuntu could detect the change in the USB device.  That was the only change other than the 32-bit compatibility stuff.  I did have to do a cold reboot of the system to insure that everything in Win7, Virtualbox, and Ubuntu came up clean.

I think mileage varies depending on the host OS, the VM, and Linux distribution.  I'm sorry but I'm at a loss for providing a solution for you.

Larry

[lpcware]

Content originally posted in LPCWare by rattus on Tue May 17 22:00:11 MST 2011

---

Quote: larryvc
Well at least you have a distress beacon.:)  Maybe its telling you to run a Superior OS.:rolleyes:

Sorry I couldn't help myself.  Bad day here too, smoked a board.:mad:

Larry - W7PAN

---

I also tried the tool set on an XP VM as well. No luck there. At all. In so many ways.

It's strange - everyone seems to be asking similar questions, are seeing the same symptoms, and then disappear. Are they discovering the solution and not passing it on, or just giving up?

Larry, you seem to have gotten past the  crt_emu_cm3_nxp issue; I installed all the 32-bit compatibility bits but still no joy. What was the secret?

Mike

[lpcware]

Content originally posted in LPCWare by larryvc on Tue May 17 21:45:00 MST 2011

---

Quote: rattus

To add insult to injury, every time I plug the LPC1769 into the USB, it now just flashes "SOS".

---

Well at least you have a distress beacon.:)  Maybe its telling you to run a Superior OS.:rolleyes:

Sorry I couldn't help myself.  Bad day here too, smoked a board.:mad:

Larry - W7PAN

[lpcware]

Content originally posted in LPCWare by rattus on Tue May 17 20:33:38 MST 2011
Hi - I'm running the latest build of LPCXpresso on Ubuntu 11.04 (64-bit, but with all the 32 compatibility components installed) in a Parallels v4 VM on my MacBook Pro.

I get normal results on lsusb (one DFU device, the LPC-Link) and the same dfu-util results as previous posters:

mike@highline-linux:/usr/local/LPCXpresso/bin$ dfu-util -d 0x0471:0xdf55 -c 0 -t 2048 -R -D LPCXpressoWIN.enc
dfu-util - (C) 2007-2008 by OpenMoko Inc.
This program is Free Software and has ABSOLUTELY NO WARRANTY

Opening USB Device 0x0471:0xdf55...
Claiming USB DFU Runtime Interface...
Determining device status: state = dfuIDLE, status = 0
WARNING: Runtime device already in DFU state ?!?
Found Runtime: [0x0471:0xdf55] devnum=3, cfg=0, intf=0, alt=0, name="UNDEFINED"
Claiming USB DFU Interface...
Setting Alternate Setting ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
Transfer Size = 0x0800
bytes_per_hash=604
Starting download: [##################################################] finished!
state(8) = dfuMANIFEST-WAIT-RESET, status(0) = No error condition is present
Done!
can't detach: error sending control message: Broken pipe
Resetting USB to switch back to runtime mode

mike@highline-linux:/usr/local/LPCXpresso/bin$ crt_emu_cm3_nxp -info-target -pLPC1769 -wire=winsub -4
Ni: LPCXpresso Debug Driver v2.0 (Apr  1 2011 10:54:24)
GetModuleFileName path == /usr/local/LPCXpresso/bin/crt_emu_cm3_nxp
Nc: Looked for chip XML file in /usr/local/LPCXpresso/bin/LPC1769.xml

Nc: Looked for vendor directory XML file in /usr/local/LPCXpresso/bin/nxp_directory.xml

Nc: Found generic directory XML file in /usr/local/LPCXpresso/bin/crt_directory.xml

Ed:02: Failed on connect: Ee(05). No matching emulator found - make sure power is on and not in use already.
Et:31: No connection to emulator device

****Interesting thing is, LPCXpresso gave me a good working session in debug - ONCE. I wrote an example blinky program that flashed out "SOS" in Morse Code, declared success and called it a day.

Next time I rebooted Ubuntu and invoked LPCXpresso, I get the same link timeout errors everyone else has been posting. Repeated invocations of dfu-util with varying transfer size values have not improved the situation; 2048 is the way to go.

To add insult to injury, every time I plug the LPC1769 into the USB, it now just flashes "SOS".

Thoughts?

Thanks,

Mike

[lpcware]

Content originally posted in LPCWare by whitecoe on Tue Apr 05 03:23:57 MST 2011

---

Quote: sskriblo
I've very similar issue:
[COLOR=Blue][I]Ed:02: Failed on connect: Ee(07). Bad ACK returned from status - wire error.[/I][/COLOR]

---

Try this thread...
http://knowledgebase.nxp.com/showthread.php?t=1637

and this FAQ...
http://support.code-red-tech.com/CodeRedWiki/DebugAccessChip

[lpcware]

Content originally posted in LPCWare by sskriblo on Tue Apr 05 02:52:36 MST 2011
I've very similar issue:
[COLOR=Blue][I]Ed:02: Failed on connect: Ee(07). Bad ACK returned from status - wire error.[/I][/COLOR]
My setup:
Ubuntu 10.4.2,
IDE LPCXpresso 3.8.2,
LPCXpresso LPC1114 board
[B]lsusb[/B]

sskriblo@sskriblo-ubuntu:/usr/local/LPCXpresso/bin$ lsusb
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 0458:003a KYE Systems Corp. (Mouse Systems) 
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
[COLOR=Blue]Bus 001 Device 028: ID 0471:df55 Philips [/COLOR]
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[B]dfu-util -d 0x471:0xdf55 -c 0 -t 2048 -R -D LPCXpressoWIN.enc[/B]

sskriblo@sskriblo-ubuntu:/usr/local/LPCXpresso/bin$ dfu-util -d 0x471:0xdf55 -c 0 -t 2048 -R -D LPCXpressoWIN.enc
dfu-util - (C) 2007-2008 by OpenMoko Inc.
This program is Free Software and has ABSOLUTELY NO WARRANTY

Opening USB Device 0x0471:0xdf55...
Claiming USB DFU Runtime Interface...
Determining device status: state = dfuIDLE, status = 0
WARNING: Runtime device already in DFU state ?!?
Found Runtime: [0x0471:0xdf55] devnum=28, cfg=0, intf=0, alt=0, name="UNDEFINED"
Claiming USB DFU Interface...
Setting Alternate Setting ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
Transfer Size = 0x0800
bytes_per_hash=604
Starting download: [##################################################] finished!
state(8) = dfuMANIFEST-WAIT-RESET, status(0) = No error condition is present
Done!
[COLOR=Blue]can't detach: error sending control message: Broken pipe[/COLOR]
Resetting USB to switch back to runtime mode

[B]lsusb[/B]

sskriblo@sskriblo-ubuntu:/usr/local/LPCXpresso/bin$ lsusb
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 0458:003a KYE Systems Corp. (Mouse Systems) 
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
[B][COLOR=Blue]Bus 001 Device 029: ID 1fc9:0009[/COLOR][/B]  
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[B]crt_emu_lpc11_13_nxp -g -2  -info-emu -wire=winusb[/B]

sskriblo@sskriblo-ubuntu:/usr/local/LPCXpresso/bin$ crt_emu_lpc11_13_nxp -g -2  -info-emu -wire=winusb
Pc: (  0) Reading remote configuration
Ni: LPCXpresso Debug Driver v2.0 (Jan 11 2011 16:08:54)
1 Emulators available:
0. LPCLINK_1_1LPC-Link Driver LINUX32 v1.1 (Code Red - LPCXpresso)

[B]crt_emu_lpc11_13_nxp -g -2  -wire=winusb -info-target[/B]

sskriblo@sskriblo-ubuntu:/usr/local/LPCXpresso/bin$ crt_emu_lpc11_13_nxp -g -2  -wire=winusb -info-target
Pc: (  0) Reading remote configuration
Ni: LPCXpresso Debug Driver v2.0 (Jan 11 2011 16:08:54)
GetModuleFileName path == /usr/local/LPCXpresso/bin/crt_emu_lpc11_13_nxp
Nc: Looked for vendor directory XML file in /usr/local/LPCXpresso/bin/nxp_directory.xml

Nc: Found generic directory XML file in /usr/local/LPCXpresso/bin/crt_directory.xml

Pc: (  5) Remote configuration complete
[B][COLOR=Blue]Ed:02: Failed on connect: Ee(07). Bad ACK returned from status - wire error[/COLOR][/B].
Et: Emu(0): Connected. Was: None. DpID:     EDB6. Info: LPCLINK_1_1
Error 0: (null)
Last sticky: 0. AIndex: 0
No MemAp selected
No Speed test
SWD Frequency: 50 KHz. RTCK: False. Vector catch: False.
Packet delay: 0  Poll delay: 0.
[COLOR=Blue]Pc: (100) Target Connection Failed[/COLOR]

The same prompt I see from graphic IDE:
[COLOR=Blue][I]Ed:02: Failed on connect: Ee(07). Bad ACK returned from status - wire error.[/I][/COLOR]
I appreciate any help!

[lpcware]

Content originally posted in LPCWare by CodeRedSupport on Sun Feb 20 10:24:30 MST 2011
First of all, as I am sure you have read elsewhere, Centos is not a supported distro. However, it would be helpful if you said which version of Centos you are trying to run on (Centos is the 'free' version of RHEL).

However, as you have found, the version of libusb that we supply with the product, requires glibc 2.8. I would suggest you try to find a version of libusb1.0.so.0 that is compatible with your version of Centos and use it to replace the version that we supply.

[lpcware]

Content originally posted in LPCWare by toulzam on Sun Feb 20 08:27:45 MST 2011
Hello everybody,

I have this problem under Centos. Lpc-xpresso GUI issue a timeout error when connecting to lpc-link.
Troubleshooting in command line gives the following:
[B]


dfu-util -d 0x471:0xdf55 -c 0 -t 2048 -R -D [/B][SIZE=2][I]LPCXpressoWIN.enc
dfu-util - (C) 2007-2008 by OpenMoko Inc.
This program is Free Software and has ABSOLUTELY NO WARRANTY
Opening USB Device 0x0471:0xdf55...
Claiming USB DFU Runtime Interface...
Determining device status: state = dfuIDLE, status = 0
WARNING: Runtime device already in DFU state ?!?
Found Runtime: [0x0471:0xdf55] devnum=34, cfg=0, intf=0, alt=0, name="UNDEFINED"
Claiming USB DFU Interface...
Setting Alternate Setting ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
Transfer Size = 0x0800
bytes_per_hash=604
Starting download: [##################################################] finished!
state(8) = dfuMANIFEST-WAIT-RESET, status(0) = No error condition is present
Done!
can't detach: error sending control message: Broken pipe
Resetting USB to switch back to runtime mode[/I][/SIZE]
[B]


lsusb[/B]
[SIZE=2][I]Bus 002 Device 035: ID 1fc9:0009[/I][/SIZE]  

(with no string ID)



[B] crt_emu_lpc11_13_nxp -mi -info-emu -wire=winUSB[/B]
[I][SIZE=2]Ni: LPCXpresso Debug Driver v2.0 (Jan 11 2011 16:08:54)
<emulators available="0" type="Debug">
</emulators>[/SIZE][/I]

[B]
crt_emu_lpc11_13_nxp -info-target -pLPC1343 -wire=winusb -4[/B]
[I][SIZE=2]Ni: LPCXpresso Debug Driver v2.0 (Jan 11 2011 16:08:54)
Et: Failed emulator initialization: E(xx). WinUSB driver load/install error: libLPC_Link.so. /lib/libc.so.6: version `GLIBC_2.8' not found (required by /usr/lib/libusb-1.0.so.0)[/SIZE][/I]

I can't get [I][SIZE=2]GLIBC_2.8[/SIZE][/I]. Any thoughts?



[B]/sbin/lsusb -d 1fc9:0009 -v[/B]

[I][SIZE=2]Bus 002 Device 035: 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
  iProduct                2
  iSerial                 3
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
    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
[COLOR=Red]can't get device qualifier: Operation not permitted
can't get debug descriptor: Operation not permitted[/COLOR][/SIZE][/I]



Strange, isn't it?

[lpcware]

Content originally posted in LPCWare by tymon_x on Mon Jan 31 02:17:23 MST 2011

---

Quote: CodeRedSupport
Cycle power to your board by disconnecting the USB cable. When the board is powered up, it will enumerate as a DFU device. This has to happen before you use dfu-util.

It appears you've DFU'd the HID software probe (VID:0x1FC9 PID:0x0007) to your LPCXpresso. This probe is not supported on Linux. This could happen if you replaced LPCXpressoWIN.enc on the dfu-util command line with LPCXpressoHID.enc, or, if somehow the LPCXpressoHID.enc file copied over LPCXpressoWIN.enc.

---

Thank you for hint. The *.enc file was loaded correctly anyway.
When I try program flash from command line with [B]crt_emu_cm3_nxp[/B], there was link error to ftdixx.so and libusb.so. I installed that libraries, reboot system and works fine now. Now I can debug from IDE (;

[lpcware]

Content originally posted in LPCWare by CodeRedSupport on Sun Jan 30 12:33:12 MST 2011
Cycle power to your board by disconnecting the USB cable. When the board is powered up, it will enumerate as a DFU device. This has to happen before you use dfu-util.

It appears you've DFU'd the HID software probe (VID:0x1FC9 PID:0x0007) to your LPCXpresso. This probe is not supported on Linux. This could happen if you replaced LPCXpressoWIN.enc on the dfu-util command line with LPCXpressoHID.enc, or, if somehow the LPCXpressoHID.enc file copied over LPCXpressoWIN.enc.

[lpcware]

Content originally posted in LPCWare by tymon_x on Sun Jan 30 09:21:30 MST 2011
Thank for your reply.

[B]lsusb[/B]

Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 002: ID 1532:0109 Razer USA, Ltd Lycosa Keyboard
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 1532:000c Razer USA, Ltd 
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 025: ID 0471:df55 Philips (or NXP) LPCXpresso LPC-Link
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

In LPCXPresso/bin folder:
[B]dfu-util -d 0x471:0xdf55 -c 0 -t 2048 -R -D LPCXpressoWIN.enc[/B]

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

Opening USB Device 0x0471:0xdf55...
Claiming USB DFU Runtime Interface...
Determining device status: state = dfuIDLE, status = 0
WARNING: Runtime device already in DFU state ?!?
Found Runtime: [0x0471:0xdf55] devnum=25, cfg=0, intf=0, alt=0, name="UNDEFINED"
Claiming USB DFU Interface...
Setting Alternate Setting ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
Transfer Size = 0x0800
bytes_per_hash=604
Starting download: [##################################################] finished!
state(8) = dfuMANIFEST-WAIT-RESET, status(0) = No error condition is present
Done!
can't detach: error sending control message: Broken pipe
Resetting USB to switch back to runtime mode

[B]lsusb[/B]

Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 002: ID 1532:0109 Razer USA, Ltd Lycosa Keyboard
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 1532:000c Razer USA, Ltd 
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 026: ID 1fc9:0007  
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Why the ID number is changed? (VID & PID?)

[lpcware]

Content originally posted in LPCWare by CodeRedSupport on Sun Jan 30 08:38:26 MST 2011
Try doing the following, and report what happens:
- disconnect the LPCExpresso board, and reconnect it
- lsusb
- [B]dfu-util -d 0x471:0xdf55 -c 0 -t 2048 -R -D LPCXpressoWIN.enc
- lsusb

[/B]