Yes, it's possible!
And it doesn't involve rebooting, either (though I changed the launch incantation to get around that... and this system does need rebooting one of these months).
I installed the evaluation version of the LPCXpresso software on both Linux and Windows... the latter to make sure the problem wasn't with the board. On Windows, I needed to futz around in the Device Manager to make sure the driver got installed, but that's Windows for ya.
On the Debian front, I kept getting the messages about the emulator not being found. The software found it, reconfigured it as a Code Red LPC-Link Probe, and then couldn't find it again. Much tinkering on three different machines didn't turn up anything informative... until....
I couldn't remember the correct incantation, so I tried "crt_emu_lpc11_13_nxp -wire=winusb" and ENTER... and got
Et: Failed emulator initialization: E(xx). WinUSB driver load/install error: libLPC_Link.so. /lib/i686/cmov/libc.so.6: version `GLIBC_2.8' not found (required by /usr/lib/libusb-1.0.so.0)
Well, yeah. Lenny has glibc 2.7, not 2.8. So why do I have a mismatched libusb in /usr/bin?
Anyway: install the official Debian libusb-1.0-0, and try again.
I can now talk to the 1114 stick from Linux. Probably also the 1343 stick, but that's out on the dining table with one of the laptops at the moment. After that, a 1768 stick, but those are currently on backorder.
Now if only I could get the STM32VL Discovery board working on similar terms... 'twas a freebie at the trade show, and it works with the Keil software (eval version) on Windows, but I'd really like to have the debugger available on Linux.
Heck, if the chip vendors would just release open-source GDB servers that worked with their USB debug bridges, that'd be useful.
And, while we're wishing for ponies, I'd like a straight-up GUI debugger, not tightly bound to an IDE, that would let me load my own smegging binaries from my own build process, and debug them... in disassembly view, if necessary. (Yeah, there may be some way to configure this LPCXpresso thing to work with my preferred toolchain, but it seems to be seriously project-oriented, and I have my own configuration and my own build process, which I don't want messed with. Oh, well. I think I'll just use the debugger to get my low-level support code working. Once I've got printf going and task switching working, the debugger becomes much less important.)