ICD-U40 and FTDI chips Don't work together

[treitmey]

Has anyone had problems with the ICD-U40 working while another board using an FTDI chip is also running.


I am using an B&B electronics USB-RS485 converter, .. model USOTL4.
Inside it uses the FTDI FT232AM chip and I use the latest direct drivers.
After I start the above board I try to also program with the ICD-U40

If fails with an invaid USB handle.

Is the drivers stepping on each other?

The ICD-U40 is using the FTDI FT232BM chip.

During install I install the ICD-U40 then the USOTL4.
I've also uninstall both and reversed the install order, but without help.

Does anyone at CCS know the handle of the ICD-U40 ?

[treitmey]

Well I Still would like some insigt from CCS or anyone else that knows about the USB handle and PID VID of the FTDI chips.

I switched the USOTL4 to VID_0856&PID_AC01
That is what came from the manufaturer.

But I was given a block of VID from FTDI. EFF0 to EFF7
so a VID_0403&PID_EFF1 should be valid.

It seems that CCS must check the VID and then use that handle.
THAT SEEMS BAD. VERY BAD.
You are not the only kid on the block using FTDI's chip and a FTDI generated id (ie: ICD-40 has a VID_0403&PID_F9D0)
The vender ID of 0403(FTDI) is used by many people and many boards.
CCS. Try using the name of the deice,... or something else

[kypec]

Hello treitmey,

have you sent an e-mail notice about this issue directly
to CCS tech.support?
I'm very interested on their reply because I'm also developing
a proprietary USB device with FT245BM and FTDI have allocated
VID=0403 and PID=E550 to E557 for me.
I wouldn't like to face the problem you have when
I connect simultaneously my USB device and ICD-U40 to the
same PC in the future.
I think that there shouldn't be a problem with D2XX drivers
as long as they are installed with unique VID & PID for each
USB device.

good luck,
kypec

[treitmey]

No I haven't wrote them an Email. Who would it go to?

[kypec]

[Darren Rook]

Yesterday I had an ICD-U40 connected at the same time I had another device connected that was using the VCP driver. Both devices worked fine. Maybe it has something to do with the D2XX driver?

[treitmey]

Daren, You seem to be in the know(about CCS). At least you live close to them.
The problem came up with the DIRECT drivers. D2XX.
I have software writen in VB to talk to a USB-RS485 box with VID_0403&PID_EFF1.

Then I try to talk to ICD-U40 at VID_0403&PID_F9D0 I can't find the handle.

When I open the device in VB I use a custom name.

AND I THINK ??
that when CCS opens it they are looking at the VID of 403

The more i think of this the more it sounds like when i unplug the USB device while the handle is open. IT DOESN"T close properly and then you can't reopen it.

I'M sory.
But i found a work-around and I'm under timeline pressure.

I'll write more when I have a chance to test it properly.

[treitmey]

Well I had time to run the test again.
Darin, tell me if my test isn't valid.

1) I run my USB_to_RS485 converter, with my VID=0403 PID=EFF1.
all is well

2) I plug in my ICD-U40
3) New hardware wizzard comes up and I load the drivers.
all is well,
my device is talking and both devices are seen with usbview.exe

4) I run the ICD software and the ICD-U40 isn't seen
--problem--
5) I unplug my USB_to_RS485
6) I run the ICD software and now it finds the ICD-U40

- - - The only thing in common is they are both USB and both have the same VID of VID=0403

Anyone know why this is causing a problem?

[treitmey]

sorry for the typo
that should read
Daren, tell me if my test isn't valid.

[Ken Macfarlane]

I too have problems. My ICD-U only works when its the only device on my USB bus. My other devices are ftdi'd, a Quasar 3150 pic flash programmer (using an ft232bm and Virtual Com Port drivers, just like the CCS ICD-U) and a ftdi DLP245PB, which contains a 74245 lookalike fifo, and uses the ftdi 2xx drivers.

I had to reprogram the 245 to have different pid, so that it and the flash programmer could coexist. FTDI gave me MProg for this purpose.

I've asked CCS if there's a problem, but had no reply as yet. Which might mean that they are considering their options!

[treitmey]

Yup, when I changed my VID with mprog it all started working.
That is why I asked if they "opened" the port with PID and vid.
If they use both,..there shouldn't be a problem.

They should do a FT_ListDevices then find device string and handle and use FT_OpenEx. I think they use FT_Open(which assumes 1 FTDI device)

Still they say that there isn't a problem.
More people need to let them know if it is realy a problem.


btw CCS: small spelling error in Ccsc.chm.
(%) operator I think should be spelled modulus[not modules]
It is listed as modules under the 'c statements' --- 'operators'
... K&R pg.268

[Matthew J]

I am having odd problems concerning FTDI chips also. I had a clue during the driver installation for the U40 ICD that they are using an FTDI USB-SERIAL IC inside (i will check physically later), and I am using an official "FTDI USB to Serial adapter" at the same time as the ICD. I experience very sporadic comms failures with the ICD unit and it is completely driving me nuts. I am sure it is because both devices are employing the use of an FTDI usb-serial converter IC and there might be some erroneous code on CCS' behalf which does not account for the possibility of doing this. Just adding my experiences, hopefully it is similar to your probs.

-matt

[Matthew J]

Now I am getting a blue screen of death, every time I try to sync the chip in the debug window at 69% every time... I have reset and tried 4 times, even without the FTDI USB->Serial Adapter in, every time, BSOD and then a reset... fun! This product seems great, and has a lot of potential... I thought we left Blue Screen serious hardware crashes with Windows 98 though ;)