| View previous topic :: View next topic |
| Author |
Message |
treitmey
Joined: 23 Jan 2004
Posts: 1094
Location: Appleton,WI USA
|
| ICD-U40 not working with another board using an FTDI |
 Posted: Wed Jul 14, 2004 1:16 pm |
 |
|
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
It fails with an invaid USB handle.
Are 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.
Latter on I switched the USOTL4 to VID_0856&PID_AC01
That is what came from the manufaturer.
I was given a block of PIDs from FTDI. xxxx to xxxx
so a VID_0403&PID_xxxx 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-U40 has a VID_0403&PID_F9D0)
The vender ID of 0403(FTDI) is used by many people and many boards.
CCS.
Instead of using the VID, try using the name of the device,... or something else like VID&PID
Last edited by treitmey on Wed Jan 23, 2008 3:04 pm; edited 1 time in total |
|
 |
Haplo
Joined: 06 Sep 2003
Posts: 659
Location: Sydney, Australia
|
|
| Posted: Wed Jul 14, 2004 5:58 pm |
|
|
A quick question, what ooperating system are you using?
Windows 98 has serious problems with having two of the same USB 'devices' connected to the PC at the same time. |
|
|
treitmey
Joined: 23 Jan 2004
Posts: 1094
Location: Appleton,WI USA
|
|
| Posted: Thu Jul 15, 2004 8:31 am |
|
|
| Nope, not the case. I have windows XP pro. |
|
|
Darren Rook
Joined: 06 Sep 2003
Posts: 287
Location: Milwaukee, WI
|
|
| Posted: Thu Jul 15, 2004 9:27 am |
|
|
| CCS does check the PID. |
|
|
planix
Joined: 20 May 2006
Posts: 5
|
|
| Posted: Sun Mar 18, 2007 4:10 am |
|
|
i have the same problem as you mentioned.
i have another usb programmer using ftdi232 after installing icd-u40 drivers it fails programming. this is verified by removing ucd drivers and installling original ftdi drivers.
i don't know if ccs c checks for pid or what but this can cause really big problems as we think lots of boards using fdti chips. |
|
|
Neutone
Joined: 08 Sep 2003
Posts: 839
Location: Houston
|
| Re: ICD-U40 not working with another board using an FTDI |
| Posted: Tue Mar 20, 2007 1:39 pm |
|
|
| treitmey wrote: | 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
It fails with an invaid USB handle.
Are the drivers stepping on each other? |
I have had a problem. The drivers supplied by CCS are older than the ones supplied by B&B. For some reason the ICD-U40 will not work with the newer drivers. The USOTL4 will work with the older drivers that CCS supply. To get this working you have to force the USOTL4 to uses the drivers already installed by CCS.
I don't think problem this has anything to do with VID or PID.
I don't know how CCS implemented the FTDI chip but simply upgrading to a newer version of FTDI drivers breaks the ICD. I don't know if this problem is due to FTDI , CCS or both but it should be fixed. The impression it gives is bad. Maybe CCS can switch to the newer driver version as a way to fix this. |
|
|
Saraoga_
Guest
|
| ftdi |
| Posted: Fri May 11, 2007 6:06 am |
|
|
Donwload Mprog from this page;
www_ftdichip._com/Resources/Utilities.htm
And clone FT232bm config via usb. |
|
|
Martin Berriman
Joined: 08 Dec 2005
Posts: 66
Location: UK
|
| Re: ICD-U40 not working with another board using an FTDI |
| Posted: Fri May 25, 2007 7:59 am |
|
|
It is true, CCS does not play nicely when other FTDI devices are plugges in - it is pretty poor really - I have been putting up with it for over a year now and just checked on here today to see if there were any recent thoughts.
I have designed a couple of products using FTDI devices and had trouble getting the CCS debugger to work - I have to fudge it by starting the debugger with my board unplugged then once CCS says Attaching, I plug my board in and normally everything is ok - If I don't follow that procedure then I get the error - 'Access violation in ftd2xx.dll'.
| treitmey wrote: | It seems that CCS must check the VID and then use that handle.
THAT SEEMS BAD. VERY BAD. |
It definitely seems like that. I was concerned about that with my products so I actually rename the FTDI drivers so that I can be sure they do not get overridden with older versions. When I open my FTDI devices, I use the FT_OpenEX and specify OpenByDescription whereas CCS seem to get confused if there is any other FTDI device attached.
| Darren Rook wrote: | | CCS does check the PID. |
Well CCS definitely does something nasty - see the crash message above.
| Neutone wrote: | | I don't know how CCS implemented the FTDI chip but simply upgrading to a newer version of FTDI drivers breaks the ICD. I don't know if this problem is due to FTDI , CCS or both but it should be fixed. The impression it gives is bad. Maybe CCS can switch to the newer driver version as a way to fix this. |
I've been hoping they would fix this for a long time but seeing as this thread was started in 2004 I will not hold my breath. 
Edit:
Treitmey has a neat solution to workaround the CCS problems - see this post. |
|
|
|
FAQ 
Search
Register
Profile 
Log in to check your private messages 
Log in
