Installing FTDI drivers to LPC-E2294 rev.B programming

Development Boards MicroMod
1

Hello friends,

I’m trying to install FTDI drivers to create a VCP (Virtual ComPort) and then start using Philips Flash Utility but with no success.

Actually I’ve used H-JTAG but suddenly it stop to work and I saw that programming with Philips Flash Utility could recover the environment.

But I can’t install the FTDI drivers. The device is not recognized. Researching I decided to use USBVIEW to find a solution and the result was as follow below:

Device Descriptor:
bcdUSB:             0x0000
bDeviceClass:         0x00
bDeviceSubClass:      0x00
bDeviceProtocol:      0x00
bMaxPacketSize0:      0x00 (0)
idVendor:           0x0000
idProduct:          0x0000
bcdDevice:          0x0000
iManufacturer:        0x00
iProduct:             0x00
iSerialNumber:        0x00
bNumConfigurations:   0x00

ConnectionStatus: DeviceFailedEnumeration
Current Config Value: 0x00
Device Bus Speed:      Low
Device Address:       0x00
Open Pipes:              0

I’m using Windows XP SP2.

Somebody have any idea of what can I do to install correctly these drivers?

Thanks all in advance,

Eduardo Garcia

2

Any ideas? I’m still with the same problem. :frowning:

I think I’ll neet to bypass the FT232BL but it’s a very dirt way to do it.

I tryied with 2 computers with Windows XP SP2 and the result is the same.

Thanks again,

Eduardo Garcia

3

eduardogarcia:
Any ideas? I’m still with the same problem. :frowning:

I think I’ll neet to bypass the FT232BL but it’s a very dirt way to do it.

I tryied with 2 computers with Windows XP SP2 and the result is the same.

Thanks again,

Eduardo Garcia

Since you have not mentioned which USB JTAG/SERIAL dongle you are trying to connect, or whose drivers you are trying to install, there probably is not much that anyone can do to help. I know that the drivers included with the YAGARTO distribution work fine with the USB JTAG/SERIAL dongles that it supports, if that is any help.

–Dave

4

Hello Dshuman! Thanks a lot your help.

Well, actually, I was using a parallel part wiggler (olimex J-TAG) to program the board.

Since it stops I’m trying do the same with Philips Flash Utility (it’s only a test because I don’t know really the reason to my board stops to work… maybe a mismatch while configuring PLL system values but I’m not sure).

The board that I’m using is LPC-E2294. I’m trying to create a Virtual Com Port installing FTDI drivers located on http://www.ftdichip.com/Drivers/VCP.htm but with no success.

If there is another informations that are missing, please, tell me and I’ll post as fast as possible.

Thanks again,

Eduardo Garcia

5

eduardogarcia:
Hello Dshuman! Thanks a lot your help.

Well, actually, I was using a parallel part wiggler (olimex J-TAG) to program the board.

Since it stops I’m trying do the same with Philips Flash Utility (it’s only a test because I don’t know really the reason to my board stops to work… maybe a mismatch while configuring PLL system values but I’m not sure).

If you have killed the ARM clock with bad PLL code, that would explain why your JTAG does not work any longer. To enter debug mode, ARM must synchronize the ARM clock to the debug clock, but with no ARM clock the synchronization just stalls and nothing happens after that. I have had a similar problem to that years ago. On the NXP parts you can get around that by simply forcing forcing them to start up in ISP mode, so that the buggy code never gets a chance to run. Then the JTAG will work normally, IF you have not set Code Read Protection too!!! The Philips Flash Utility obviously also needs an ARM clock to operate, but it does put the chip into ISP right after reset, and keeps it there. If CRP is set it will honor it, but it will let you totally erase the FLASH.

The board that I’m using is LPC-E2294. I’m trying to create a Virtual Com Port installing FTDI drivers located on http://www.ftdichip.com/Drivers/VCP.htm but with no success.

If there is another informations that are missing, please, tell me and I’ll post as fast as possible.

Thanks again,

Eduardo Garcia

Ahhhhh, the board has it’s own USB/SERIAL dongle built in!!! In that case it might still be worthwhile to try the YAGARTO distro, because the FTDI drivers there really do work and install easily. The problem there would most likely be getting the virtual SERIAL port operating on the correct FTDI pins.

If there is really a good possibility that the ARM clock has been stopped by faulty PLL code, then the whole USB exercise is probably not necessary though. You can simply start the chip in ISP mode to get the JTAG working again.

–Dave

6

Hi Mr. Dave,

Thanks a lot your help.

You’re right and, putting P0.14 low the device started in the ICSP mode and I was able to erase the wrong code.

Now see the board working with a serial utility is not my priority.

I will take care to don’t repeat this accident.

Thanks again!

7

eduardogarcia:
Hi Mr. Dave,

Thanks a lot your help.

You’re right and, putting P0.14 low the device started in the ICSP mode and I was able to erase the wrong code.

Now see the board working with a serial utility is not my priority.

I will take care to don’t repeat this accident.

Thanks again!

I am glad to see that you have it working again!!! :smiley:

FWIW, I usually test critical code fragments like the PLL clock configuration by running them in RAM before I commit them to the FLASH build. Then, if it does not work correctly, you can just reset before trying to improve the code for the next try.

–Dave