Content originally posted in LPCWare by ogautherot on Wed Feb 09 06:11:01 MST 2011
Hi! Sorry in advance if the post gets somewhat long but I'll try to detail as much as I can to speed up the resolution. Note that this is a topic that I already started to discuss with support but have not resolved it yet.
I'll start on a positive note: I got LPCXpresso up and working on a Windows Vista 32-bit machine with an LPC1343-based module in very little time (the download of the installer was longer than the rest of the procedure :) ) Compiling and debugging the "Blinky" example was a no-brainer. Excellent job, guys.
The story is not quite as nice on my Windows 7 64-bit machine at work (a Dell laptop with Windows preinstalled). I tried to review forums for help and no luck so far. I've hit a number of issues and will try to list them. It would be great if someone could confirm that they have a Windows 7 64-bit machine that they use for debug.
1) License
After some troubleshooting, I finally came across the issue (seems to be Windows-related): The process runs a command called "cscript.exe", which in turn invokes vbscript.dll. cscript.exe works fine if I am in the \Windows\system32 directory but does not find the VisualBasic DLL when I am in another directory. I tried to adjust the path (it now includes \windows\system32 at the beginning) but no luck yet.
2) Open projects and compile them
Here, the standard Eclipse installation works fine and I can successfully generate the ELF files. So far so good.
3) Connect USB device
The USB device is sucessfully recognized as a DFU. The result is consistent. So far so good.
4) Download the executable and debug
Here, things clash again. When I try to download the executable, the DFU fails to convert to an "LPC-Link" (it does under Vista without external action). If I run "...\bin\Scripts\bootLPCXpresso.cmd winusb", I see the LPC-Link device in the USB tree so the board is fine. But again, trying to invoke GDB fails after crt_emu_lpc11_13_nxp.exe aborts silently.
If a Windows 7 64-bit user managed to get the debugger up and running, I would appreciate if they could send me a copy of their %PATH% variable to see if I am missing something obvious.
Thanks in advance
Olivier
