FTDI USB - As good as they claim?

Go To Last Post
88 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Having had a search around the forums here, I gather that the general opinion of the FTDI USB chips is that they are pretty good.

If the salesman is to be believed, using simple RS232 at the microcontroller end and their driver at the PC end, bidirectional comms miraculously occurs and I never need to worry about the USB transport mechanism.

For an application we have, we need to keep about 4Kbytes of data in synch between an embedded micro and a PC more often than roughly once per second.

Notwithstanding the fact that we have to implement a protocol to achieve the synchronisation (my problem, I realise) are these chips really up to the job?

How about if somebody else has a device using the same technology? Is their driver clever enough to be able to address MY device rather than the other one?

Thanks for advice in advance.

Andy

If we are not supposed to eat animals, why are they made out of meat?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

They truly are as good as they claim. I use them daily at 3,000,000 bps here!

If you are using the FT232 chip, you better hook up 2 more lines for RTS/CTS or you will have problems with overflows at high baud rates.

I prefer the FT245 but it requires 4+8 lines.

Regards

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I recently bought a Keyspan USB to serial adapter to use on my laptop and it uses one of the FTDI chips. I figured out which one it was by the specs but couldn't even begin to tell you which one it is from memory now.

Anyway, it works like a charm. The laptop doesn't seem to have a clue it is communicating with RS-232 devices. It thinks it's a USB or maybe is fooled into thinking it really does have a serial port.

What I do know is all I did was plug it in and it worked.

Please note - this post may not present all information available on a subject.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi all

I also use the FT245BM and am very fond of it.
I have designed a small board wit it an an ATMEGA128 on it:
http.//www.megausb.de (german)

It is fast, and easy to use. We work both with Windows and Linux.
And YES, you have the ability to store your own PID and VID into a serial EEPROM connected to the FT245. With this your USB device is unique. Also you can configure:
your * serialnumber * vendor name * device name * power requirement of your application * timing * other functions * and mode of transmission. For example you can use isochronous mode for transferring data with a certain bandwidth.

There are VCP and D2xx Driver. While VCP is the easy way, the D2xx is the more flexible. I recommend starting with VCP and if necessary then step over to D2xx.

Have a lot of fun!

Klaus
********************************
Look at: www.megausb.de (German)
********************************

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Thanks, folks.

I suppose that "wow" is the appropriate response.

Cheers
A

If we are not supposed to eat animals, why are they made out of meat?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Andy - have you heard of the CP2101 made by Silicon Labs? Here in the states it is much cheaper and easier to get than the FTDI chips. Seems to be well regarded but less well known compared to the FTDI chips. Best regards..

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

ezcomp wrote:
Andy - have you heard of the CP2101 made by Silicon Labs? Here in the states it is much cheaper and easier to get than the FTDI chips. Seems to be well regarded but less well known compared to the FTDI chips. Best regards..

It may be a fine chip, ez, but "much cheaper" and "easier to get"?

--I did not find any listing of distributors on the Silabs Web site, so I actually found it >>harder<< to get info. :)

--On-line buying kicked into Mouser
Qty. 1 price: $5.70
Qty. 100 price: $4.02

--FTDI from Saelig:
Qty. 1 price: $5.80
Qty. 100 price: $4.30

--We have had good and fast service from Saelig.

Is there a disti that sells the chip "much cheaper"?

Lee

You can put lipstick on a pig, but it is still a pig.

I've never met a pig I didn't like, as long as you have some salt and pepper.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Thanks for the alternative gentlemen.

I will point our hardware guy at the site.

That is assuming he can still access the Net following the hurricane that is about to pass right over him on Monday evening.

I can't help feeling he could have picked a better time to visit his sister in Florida. :D

Cheers
A

If we are not supposed to eat animals, why are they made out of meat?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

MegaUSBFreak wrote:

And YES, you have the ability to store your own PID and VID into a serial EEPROM connected to the FT245. With this your USB device is unique.

Don't you wish they would just stick some EEPROM in the damn thing anyway, I'd be more than happy to pay the extra $$ if it ment losing 1 IC and a few resistors that are needed if you run the EEPROM.

Apart from that they are a very good choice.

Cheers.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

vimfuego2 wrote:
MegaUSBFreak wrote:

And YES, you have the ability to store your own PID and VID into a serial EEPROM connected to the FT245. With this your USB device is unique.

Don't you wish they would just stick some EEPROM in the damn thing anyway, I'd be more than happy to pay the extra $$ if it ment losing 1 IC and a few resistors that are needed if you run the EEPROM.

Apart from that they are a very good choice.

Cheers.

Just in case you are not aware, one of the things that make the CP2101 atttractive is that there is no need for a separate EEPROM and crystal. It is truly a one chip solution (plus a single bypass cap).

Scott

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Another note - the CP2101 is IN STOCK at Digikey :D FTDI Chips didn't seem to share that ...

-Colin

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Thanks Colin,

I know what I will be getting...

Caleb

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

BTW - for anyone who hasn't found this site yet, www.findchips.com is a great resource when new chips are announced. It will search a bunch of distributors so you can get an idea of how available it is.

-Colin

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

sarmitage wrote:
Just in case you are not aware, one of the things that make the CP2101 atttractive is that there is no need for a separate EEPROM and crystal. It is truly a one chip solution (plus a single bypass cap).
Scott

One question though: anybody can tell me how on the Earth to solder the 28MLP CP2101? (I, Hobbyist).

Bogdan

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

lethal wrote:
sarmitage wrote:
Just in case you are not aware, one of the things that make the CP2101 atttractive is that there is no need for a separate EEPROM and crystal. It is truly a one chip solution (plus a single bypass cap).
Scott

One question though: anybody can tell me how on the Earth to solder the 28MLP CP2101? (I, Hobbyist).

Infrared oven will work quite nicely, as will a 'hot air pencil' type soldering iron.

I have experimented with the CP2101 which we chose simply because of its size! We are starting to use the MLFP packages for AVR parts and whilst we have yet to produce a finished product we have found the MLFP quite usable in prototypes.

One robotics supplier, ( http://www.pololu.com/products/pololu/0391/ ) is usaing the CP2101 on a triny little board with a mini-B USB connector.

...John

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I have done small prototype builds using Atmel and SiLabs MLF packages using a modified toaster oven (Google for "toaster oven soldering"). Out of about 10 chips that I have soldered this way, I have had 100% success with no rework required on any of them. Typically on a fine pitch QFP I need to touch up about 10% of the pins.

Scott

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

hi
what about philips PDIUSBD12 ics?

Atmel used them in jtag mk II!

Is it better that FTDI in performance ? and in price?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

yaaavar wrote:
hi
what about philips PDIUSBD12 ics?

Atmel used them in jtag mk II!

Is it better that FTDI in performance ? and in price?


I beleive you need to write a lot of software to interface this chip, it's only the phsical interface. It's much more complicated to interface than a simple RS232 interface as on the FTDI232, CP2101 and Prolific PL-2303 / PL-2313.

Link to PL-2303 and 2313: http://www.prolific.com.tw/eng/P...

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

CP2101 can be bought cheaper at Sparkfun in small quantities than at Mouser and Digikey:
http://www.sparkfun.com/shop/ind...

CP2101 prices:

Dealer    Price

Spark Fun $5.25
Mouser    $5.70
Digikey   $5.70
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Got experience with the CP2101? They look like a really nice chip (only problem is extra-tiny size) on paper, haven't heard yet though of people's experience so would be very interested in it!

Regards,

-Colin

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I have no experience with the CP2101, but lots with most of the FTDI chips. But after a quick look at the CP2101 I might consider switching. The only thing I dont like is thier method of driver distribution. FTDI does this part for you, at least for the generic drivers. To get the CP2101 drivers you need to get the DEVKIT. Still thats not too bad, only $50. But you still have the pain of distributing the drivers which can cost bandwidth and/or media. What happens when they have a driver update, do I have to buy another DEVKIT?

Vern

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi,

Once you buy the dev-kit you get free driver updates:

Quote:
For driver updates, contact MCU Tools Support to receive instructions on downloading the latest VCP drivers. To receive this information a valid CP2101EK serial number must be included with the request.

-Colin

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

snafles wrote:
I have no experience with the CP2101, but lots with most of the FTDI chips. But after a quick look at the CP2101 I might consider switching. The only thing I dont like is thier method of driver distribution. FTDI does this part for you, at least for the generic drivers. To get the CP2101 drivers you need to get the DEVKIT. Still thats not too bad, only $50. But you still have the pain of distributing the drivers which can cost bandwidth and/or media. What happens when they have a driver update, do I have to buy another DEVKIT?

Vern

ftp://cp2101:cp2101xfer@ftp.sila...

The Readme.txt on the ftp site describes how to uninstall the old drivers and install the new ones.
You can also download the latest drivers using Windows Update.

So, just use Windows Update, it doesn't get any easier than that!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi all,

I've used the CP2101 with a Mega32L and it was extreamly easy to use. It was actually quite surprising how easy it was.

The only "issue" I had was that I had to buy the development kit in order to get the USB drivers. This was some time ago so I do not know if they still require that. It might be something to look into before you use this chip.

I would have to say soldering the chip to my PCB was actually the hardest part though I was still able to HAND solder it to my PCB.

On a side note...I paid about $60. CND for the kit....(make that $63.98 digikey.ca :o ) and I sampled the chips from Insight.

I'll post a picture of my PCB with the CP2101 attached later when I get home from work if you like..

ocnek.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

ocnek wrote:
The only "issue" I had was that I had to buy the development kit in order to get the USB drivers.

I can see you didn't read the post above I just made.
There's a link to download the drivers from their ftp.
But it's even easier just to use Windows Update and download the driver from Microsoft.

You can even download the driver from Microsoft manually without having the chip yet.
I did that some time ago.

There's no reason to waste your money on this kit I think.
Just buy the chip and connect it and let Windows Update handle the rest. Or download the driver manually from Microsoft or the Silabs ftp.

Here the link once more to download the drivers:
ftp://cp2101:cp2101xfer@ftp.sila...

You can also download it manually from Windows Update here:
http://v4.windowsupdate.microsof...
1) Click "Find hardware driver updates"
2) Go to the bottom of the list and click "Other Hardware"
3) In "Manufacturer name:", choose "Silicon Laboratories Inc."
4) Choose your Windows operating system
5) Choose your Windows language
6) Click "Search"
7) Find "Silicon Laboratories usb software update released on March 11 2004." and click "Add"
8) Click "Go to Download Basket"
9) Click "Browse" and specify the download location of your choice
10) Click "Download now"

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

AndersAnd wrote:

There's a link to download the drivers from their ftp.

There's no reason to waste your money on this kit I think.
Just buy the chip and connect it and let Windows Update handle the rest. Or download the driver manually from Microsoft or the Silabs ftp.

Here the link once more to download the drivers:
ftp://cp2101:cp2101xfer@ftp.sila...

I'm also interested on other people's experience with this chip and especially the driver. I've had problems with their "latest" driver and Windows XP, even though the claim it's for XP.

Thanks
Eric

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

EW wrote:
I'm also interested on other people's experience with this chip and especially the driver. I've had problems with their "latest" driver and Windows XP, even though the claim it's for XP.

Have you tried to to download it with Windows Update instead of from Silabs ftp?
Maybe this version is different.

What kind of problems have you had?

Now you can also download FTDI drives with Windows Update, you coudn't do this half a year ago.
Just choose "Future Technology Devices International Ltd." instead of "Silicon Laboraties Inc."

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

AndersAnd wrote:
EW wrote:
I'm also interested on other people's experience with this chip and especially the driver. I've had problems with their "latest" driver and Windows XP, even though the claim it's for XP.

Have you tried to to download it with Windows Update instead of from Silabs ftp?

No.

AndersAnd wrote:

Maybe this version is different.

I can't fathom why it would be different.

AndersAnd wrote:

What kind of problems have you had?

The driver will work fine for a while and then suddenly upon connecting the USB device, the PC will no longer recognize it. After that, it will continue to not recognize the USB device until the driver is reinstalled. :( It's sporadic and there no one way that I can get it to consistently fail, but it's happening often enough.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

What does Silabs support say about your problem?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

EW wrote:
The driver will work fine for a while and then suddenly upon connecting the USB device, the PC will no longer recognize it. After that, it will continue to not recognize the USB device until the driver is reinstalled. :( It's sporadic and there no one way that I can get it to consistently fail, but it's happening often enough.

I had a similar problem when I first started using the FTDI chips. I was doing a lot of testing, connecting and reconnecting the USB cable (the device was USB powered, so the easiest way to reset was disconnecting). After a couple times the PC would not recognize the FTDI chip anymore. I would do the same thing you discribed to get it to work again, but after some frustration with that, I found it easier to just disable, then reenable the COM port. That did the trick with FTDI chips, maybe it would also work for the CP2101 instead of the reinstall.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I've got an FTDI kit that I haven't started playing with yet, BUT, I do remember reading somewhere on their web site about this problem. It's because the PC "thinks" that every re-connection is a new device. I believe there is some "fix" for OEM's who want to test stuff before it goes out of the door without having to constantly reset the PC.

Four legs good, two legs bad, three legs stable.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Here is an interesting module for prototyping or us that can't solder mlf

http://www.qortek.com/ProductDet...

Dunno about pricing or availability.

/Bingo

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

@John Brown

The "fix" can be found here, John, third item down the page.

http://www.ftdichip.com/FTApp.htm

/A

If we are not supposed to eat animals, why are they made out of meat?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

AndersAnd wrote:
ocnek wrote:
The only "issue" I had was that I had to buy the development kit in order to get the USB drivers.

I can see you didn't read the post above I just made.

I was just posting my experience with the part which was where this thread was going was it not?? Is that ok with you? Maybe I should have asked for your approval before I posted??!!…... :roll:

I first used this part when Cygnal was a separate company from SiLabs and the CP2101 was relatively new so buying the DEV kit was the only way to get the driver.

This might not be the case now as you pointed out, but at the time of MY development it was.

Quote from my distributor:
“Are you going to get a kit? I checked and you can't get the drivers without the kit. The kit is $49US.”

I beg for your forgiveness,

Ocnek.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

AndersAnd wrote:
What does Silabs support say about your problem?

Um, nothing. We haven't contacted them about it yet. :oops:

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

snafles wrote:
EW wrote:
The driver will work fine for a while and then suddenly upon connecting the USB device, the PC will no longer recognize it. After that, it will continue to not recognize the USB device until the driver is reinstalled. :( It's sporadic and there no one way that I can get it to consistently fail, but it's happening often enough.

I had a similar problem when I first started using the FTDI chips. I was doing a lot of testing, connecting and reconnecting the USB cable (the device was USB powered, so the easiest way to reset was disconnecting). After a couple times the PC would not recognize the FTDI chip anymore. I would do the same thing you discribed to get it to work again, but after some frustration with that, I found it easier to just disable, then reenable the COM port. That did the trick with FTDI chips, maybe it would also work for the CP2101 instead of the reinstall.

Sure, it might. But it's not a good long term solution for customers using the product out in the field.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

ocnek wrote:
AndersAnd wrote:
ocnek wrote:
The only "issue" I had was that I had to buy the development kit in order to get the USB drivers.

I can see you didn't read the post above I just made.

I was just posting my experience with the part which was where this thread was going was it not?? Is that ok with you? Maybe I should have asked for your approval before I posted??!!…... :roll:

I first used this part when Cygnal was a separate company from SiLabs and the CP2101 was relatively new so buying the DEV kit was the only way to get the driver.

This might not be the case now as you pointed out, but at the time of MY development it was.

Quote from my distributor:
“Are you going to get a kit? I checked and you can't get the drivers without the kit. The kit is $49US.”

I beg for your forgiveness,

Ocnek.


You canpost whatever you like, but from your previous post it loked like you had not read my post:
ocnek wrote:
The only "issue" I had was that I had to buy the development kit in order to get the USB drivers. This was some time ago so I do not know if they still require that. It might be something to look into before you use this chip.

You wrote that you did not know if you still needed the dev. kit to get the drivers.
But if you had read my post you would know that you don't have to buy the dev. kit, because I told about two places to get the drivers without ordering the kit.
So if you really had read my post I find it strange that you write that you don't know if they still require you to buy the kit to get the drivers.
So I reallydid thought that you must had missed my post.
So I'm sorry if my English isn't good enough, so you didn't understood my first post.

But I don't mind if you read my post or not, lets just let it rest.
It doesn't really matter if you read my post or not, I guess you have read it now.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

AndyG wrote:
@John Brown

The "fix" can be found here, John, third item down the page.

http://www.ftdichip.com/FTApp.htm

/A


Well, thanks for that, as I said I'm not actually using it yet, I was just trying to point these other people in the right direction. Judging by some of the recent posts, I was wasting my time, as usual.

John

Four legs good, two legs bad, three legs stable.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

@AndersAnd

I think you are being a bit harsh here.

You might have given an alternate way to obtain the drivers but according to this text "snipped" from the Silabs Eval kit page , you could easily get the impression that the way you described were not the desired way.

At least in Silabs way of thinking ....

Quote:

Note: Virtual COM Port (VCP) device drivers are required for CP2101 device operation and are only distributed as part of the CP2101EK evaluation kit. Therefore, a CP2101EK kit must be purchased to use CP2101 devices. For driver updates, contact MCU Tools Support to receive instructions on downloading the latest VCP drivers. To receive this information a valid CP2101EK serial number must be included with the request.

/Bingo

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I'm sorry but I was not trying to offend anyone.
But from his post, I was really sure that he had not read my post, otherwise I don't understand why he wrote what he did.
Maybe I misunderstod something, but I can only understand his post as he don't know where to get the driver without ordering the kit.
I wasn't tying to offend anyone, but just wanted to point out that I had already given the answer to his question in the previous post.
I have never bought the kit, but just mailed Silabs to get the drivers.

I don't want to discuss who read what or not anymore, I don't really care I just wanted to give the answer to the question.
I think everyone know where to get the drivers by now.
.
The other discussion leads nowhere, I only want to discuss the topic from now on.
Write what you want about my posts, but I don't want to discuss it anmore. I was not trying to offend anyone. If you want to offend me go ahead, but I don't want to answer this anymore.
Let's keep to the topic insead, at least I will from now on.
Sorry I went a bit off topic.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

After reading about the fix at FTDI, it looks to me that the device will not get a new COM port every time, if it is given a unique serial number.

Do you have this problem with the FTDI or CP2101 chips if you have stored a serial number in the EEPROM?
If it recognises the serial number, I think it will be assigned the same COM port nuber again, so you wont run out of COM ports after 256 inserts.

To all with this problem:
Have you stored a serial number in the EERPOM?
I think this would solve the problem. Of course this would only work if you are not testing more than 256 different CP2101 or FTDI. But for noraml use with only a few different devices conected to the same PC I think it would work to assign induvidual serial number to the EERPOMs.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

AndersAnd wrote:
To all with this problem:
Have you stored a serial number in the EERPOM?
I think this would solve the problem. Of course this would only work if you are not testing more than 256 different CP2101 or FTDI. But for noraml use with only a few different devices conected to the same PC I think it would work to assign induvidual serial number to the EERPOMs.

I think there are three problems being discussed here:

1) The CP2101 drivers hang up on EW when he connects and reconnects the same device. I cant really speak to this problem since I have never touched the chips or drivers.

2) The FTDI drivers hang up when I connect and reconnect the same device. In my case it was the Demo board for the FT232 (DLP-USB232M). I kept the default settings for device and serial # and all that. My problem was it would just stop recognizing the device at a random number of disconnects connects. It wasnt really a problem because the driver never failed in the first few times, it really was a higher amount. It only ever happened during my testing, never had tester or customer complain with everyday use.

3) The FTDI "fix" is when you connect and reconnect many different devices. The example they give is a manufacturer testing thier product coming off the line. This shouldnt really apply to the hobbiest who is working on the same device.

Hope this clears up the confusion, or maybe made it worse.

Vern

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Actually I think it all the same problem and not three different.

When the have not been programmed with a serial in theEEPROM, the driver will think it's a new device every time the same IC is connected because it can't find it's serial number.

Have anyone with this problem programmed an serial number in the EEPROM, so the PC will realise it's the same device every time it's inserted?

I think the PC will regard a single IC without a serial as differnt devices every time it's inserted. If it has a serial I think the problems will disappear.

Can someone confirm this or prove otherwise? Have anyone with this problem programmed a serial number in the IC?
You said you used the default setting, but is there already programmed a serial number in the default setting, don't you have to do this yourself first?
HAve you tried to give it your own USB VID, PID , Serial Number and Product and see if the problem still exists.
I can't find any info in the DLP-USB232M datasheet that says this information has already been programmed from the factory.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I cant speak to the CP2101, but the FTDI 232BM chip will not send a serial number if an eeprom is not attached. I cant remember what effects that has on the PC. As for the DLP-USB232M devkit for the FTDI 232BM chip, it has a default serial number programmed into it, I just checked mine. So its should not have made a difference. The same device was being plugged in over and over. This was a couple years back, but I am pretty sure I wasnt even close to the 256 limit suggested. My problem, guessing here, was happening between 30 and 50 times.

Vern

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Ok, I see, then I don't know what the problem is

snafles wrote:
I cant speak to the CP2101, but the FTDI 232BM chip will not send a serial number if an eeprom is not attached.

The Silabs CP2101 has integrated EEPROM and resonator. That's the biggest advantage vs. the FTDI 232BM.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

All that being said, I think for the next project using serial comms, I will be trying the CP2101. The reduced component count should make it worth its weight in gold. I will be ordering a dev board this week.

Vern

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I just connected up my FTDI 232 module today, talking to a hard disc video capture unit. Very trivial application. Works fine, but there is a BIG delay (several seconds) when I connect the USB cable( WIN98SE).
I now want to try the Silabs chip, like everybody else, I'm attracted by the in-built EEPROM and resonator.
Has anyone noticed a similar delay with the CP2101?
Has anyone managed to purchase a CP2101-EK in the UK?

Four legs good, two legs bad, three legs stable.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

John_A_Brown wrote:
Works fine, but there is a BIG delay (several seconds) when I connect the USB cable( WIN98SE).

With WIN98SE, I'd consider >>any<< successful USB communication with any of the chip brands a moral victory.

Before worrying about the delay part I'd try it on one of the newer operating systems with full USB support. I'm confused though about "BIG" and "several seconds". I haven't paid that close attention but we've got digital cameras, PDAs, FTDI devices, commercial USB-to-serial adapters, etc. in the office. We use them and test them on different Windows types including 98SE, XP/Home, XP/Pro, 2000. [Apps are checked on W95 & NT4 also.] I can't recall any device that "snaps to life" instantly. "Several seconds" does not seem "BIG". I'll have to pay more attention the next time we make the rounds. How do you measure the time?

Lee

You can put lipstick on a pig, but it is still a pig.

I've never met a pig I didn't like, as long as you have some salt and pepper.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Unfortunately I can't tell every customer that they need to "upgrade" to WIN XP or NT.
I wouldn't care so much about the delay if there was a message of some sort, or even if the cursor stayed in "egg timer" mode, but what actually happens is that the computer stops responding to mouse/keyboard events.
How do I measure time? "One Mississippi, two Mississippi" etc. Is there another way?
But I take your point, and I will try it on XP.

Four legs good, two legs bad, three legs stable.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

John_A_Brown wrote:
Unfortunately I can't tell every customer that they need to "upgrade" to WIN XP or NT.

Actually, you could--assuming all USB devices operate the same way on 98SE. Then it is just the nature of the beast: upgrade, live with it, or you can develop the proper patch for '98. :twisted:

"How do you measure?" I mean from when (the time you plug the device in?) till when (the time the forst message is successfully transmitted/received?). What about other commercial USB devices--cameras, PDAs etc. [Here is my wager of a cold one: You and yours have probably not done much of that, because: A. the devices aren't supported on 98SE; and/or B. they work so crappy no-one wants to use them under 98SE, so they don't.]

But I'll take note of it when we're making the rounds with our USB devices and see if I get the same symptoms. We just rolled out a small lot of USB-to-RS485 converters using FT232BM & DS485, and plugged each into a 98SE system as well as the other Windows flavours that I listed, and didn't notice any particular anomalies. That is always like comparing apples and oranges, of course, since different drivers may be needed (and some XP machines need no driver load), etc.

Lee

You can put lipstick on a pig, but it is still a pig.

I've never met a pig I didn't like, as long as you have some salt and pepper.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I'm kind of fuzzy on this. If I connect an AVR project to a PC using this Silabs chip, then what can I do with it? Can I flash the AVR? Does it just act like a serial link, like I could talk to it using Windows Terminal? Would I have to write a PC program to communicate with it?

j.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Can I flash the AVR?

Sure, if it has a bootloader already on it.

Does it just act like a serial link

From the AVR's point of view, yes. From the PC's point of view, its a virtual COM port

like I could talk to it using Windows Terminal?

Yes

Would I have to write a PC program to communicate with it?

Strictly speaking, no

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

j_sorensen wrote:
I'm kind of fuzzy on this. If I connect an AVR project to a PC using this Silabs chip, then what can I do with it? Can I flash the AVR? Does it just act like a serial link, like I could talk to it using Windows Terminal? Would I have to write a PC program to communicate with it?

j.


As far as the AVR is concerned, it might just as well be talking to a MAX232 chip. At the PC end, if you install the virtual com port drivers, the the PC believes that it's talking to a conventional com port.
P.S. I'd still like to know if anyone's managed to buy the Silabs part in the UK.

Four legs good, two legs bad, three legs stable.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

John_A_Brown wrote:
Has anyone managed to purchase a CP2101-EK in the UK?

You can order it from Digikey UK:
http://uk.digikey.com/scripts/Dk...

Price is £ 27.49

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

AndersAnd wrote:
John_A_Brown wrote:
Has anyone managed to purchase a CP2101-EK in the UK?

You can order it from Digikey UK:
http://uk.digikey.com/scripts/Dk...

Price is £ 27.49

From what I've read, that's really ordering from the states, big delivery charge.But many thanks anyway.

Four legs good, two legs bad, three legs stable.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

John_A_Brown wrote:
From what I've read, that's really ordering from the states, big delivery charge.But many thanks anyway.

Shipping charge:
£12.00

Handling Charge:
A £10.00 handling charge applies to all orders less than £75.00. This fee will be waived on orders of £75.00 or more.

So if you order other things at the same time so the total will be more than £ 75, then you will save the £ 10 handling charge and only pay the £ 12 shipping charge.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

John_A_Brown wrote:
I'd still like to know if anyone's managed to buy the Silabs part in the UK.

You can also buy it from Farnell UK:

CP2101EK http://uk.farnell.com/jsp/endeca...

Quantity  Price 
  1 -     £39.29

CP2101 https://secure.farnell.com/jsp/e...

Quantity  Price 
  1 - 9   £4.16  
 10 - 99  £3.40  
100 -     £2.88
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Anders,

Thanks again!

John Brown

Four legs good, two legs bad, three legs stable.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hey guys,

Excellent find regarding the CP2101 chip! I'm going to be using it in a project in the next couple weeks with a piece of hardware that is designed to either communicate with a PC over USB, OR communicate with another piece of hardware hopefully also using USB to minimize extra connections.

My question is regarding connecting two pieces of hardware together over USB, both of which using CP2101 chips. Specifically, is this possible? Is the chip designed just to communicate with it's drivers to function properly? I would assume that they've built in the functionality for two CP2101 chips to communicate with each other seamlessly just like a direct TX/RX connection, but I find no mention of this in the data sheet.

Thanks for any insight!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

jimbotko wrote:
Hey guys,

Excellent find regarding the CP2101 chip! I'm going to be using it in a project in the next couple weeks with a piece of hardware that is designed to either communicate with a PC over USB, OR communicate with another piece of hardware hopefully also using USB to minimize extra connections.

My question is regarding connecting two pieces of hardware together over USB, both of which using CP2101 chips. Specifically, is this possible? Is the chip designed just to communicate with it's drivers to function properly? I would assume that they've built in the functionality for two CP2101 chips to communicate with each other seamlessly just like a direct TX/RX connection, but I find no mention of this in the data sheet.

Thanks for any insight!


As far as I know, (and I now have the dev kit) the CP2101 is a USB slave device, so the answer is no. You could probably communicate between two PC's by using two CP2101s back to back, but that's about it.

Four legs good, two legs bad, three legs stable.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

John_A_Brown wrote:

As far as I know, (and I now have the dev kit) the CP2101 is a USB slave device, so the answer is no. You could probably communicate between two PC's by using two CP2101s back to back, but that's about it.

Ouch. Anybody know of any of these one-chip solution deals for a USB master? :(

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

jimbotko wrote:
Ouch. Anybody know of any of these one-chip solution deals for a USB master? :(

Yes, Cypress Semiconductor makes USB Embedded Hosts, you can use this in one end and use CP2101 as slave in the other end.

http://www.cypress.com/products/...

http://www.cypress.com

http://www.cypressmicro.com

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

a bit delayed but..

does exist any or planned any chip like FT232/254 etc in
DIP package ?
i mean SMD are fine and even hobyist can solder them but as easy
and especialy at HOME made PCB (at least not everyone)

imho a FT232/245 in DIP package it should sell lenoughp in hobyist/prototyping market
just like vast majority of them use DIP mcu's
(its also easier to stick in a breadboard )

there is IgorUSB ofcourse (i have not rtry it yet though) except this ?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

plouf wrote:
does exist any or planned any chip like FT232/254 etc in
DIP package ?

Just use one of these DIL boards, they are made for this purpose:
Evaluation Kits : http://ftdichip.com/FTEval.htm
FTDI Evaluation Kits - Dual in Line Modules: http://ftdichip.com/FTModule.htm
3rd Party - Dual in Line Modules: http://ftdichip.com/3PModule.htm

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

yes i know about these but the cost increased ,
33USD from just 6.75USDof single chip and a usb conector + crystal do not cost
the 26.25 of the diffirence,
epsecialy if its hard to impossible to find a distributor in your country
(greece) and exespt the extra cost it also add extra time to get one
and you think twice if you burn one (;))
i have order a few PCB in a pcb maker here to solder a few FT245/32 i just get...

i can live with that offcourse but makes my life harder :wink:

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

AndersAnd wrote:

Yes, Cypress Semiconductor makes USB Embedded Hosts, you can use this in one end and use CP2101 as slave in the other end.

http://www.cypress.com/products/...

http://www.cypress.com

http://www.cypressmicro.com

Hmm, from the data sheet it looks like these chips are much more difficult to implement. I assume that the CTS/DTS/etc emulation on the CP2101 would no longer function as that must be implemented by the PC drivers.

Has anybody used those chips that can comment on how easy they were to integrate? I'm basically just sending a receiving simple serial streams of data, and would like the ability to connect to the PC or another mini-PC like device that is just a uC with some display hardware, all over USB.

I've only got about 4-5 weeks from today to do all of the programming / hardware design / PCB fabrication / testing, which is why I'm turned off by any chips that seem like they would take a significant investmen in time to learn how to use properly.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Yes USB Hosts are much more complicated to implement than USB slaves.
I would forget about this idea with only 4 weeks, it's also much more expensive.

Why don't you just connect your two devices by simple RS232 DSUBs instead. When you want to connect it to a PC's USB instead, then just use a readymade USB<->RS232 adapter cable and plug in the DSUB instead. This is very easy two implement.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

AndersAnd wrote:
Yes USB Hosts are much more complicated to implement than USB slaves.
I would forget about this idea with only 4 weeks, it's also much more expensive.

Why don't you just connect your two devices by simple RS232 DSUBs instead. When you want to connect it to a PC's USB instead, then just use a readymade USB<->RS232 adapter cable and plug in the DSUB instead. This is very easy two implement.

I would love to, but I need a reliable data rate of preferrably 920.6 kbps. This seems difficult to guarantee over RS-232.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Then use RS422 or RS485 instead, it uses differential data transmission and are more reliable than RS232 single ended transmission.
It's very common in industrial applications.
http://www.rs485.com/rs485spec.html

You can use an USB to RS422/485 converter to interface it to your PC. Youcan buy these converters readymade or make your own from one of the chips mentioned in this topic.

FTDI has an application note on how to make USB to RS422/485 converters.

You can use standard Cat. 5 twisted pair network cable for your RS422/485 cable.

Compnies like Maxim makes RS422/485 to TTL UART level translators.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

AndersAnd wrote:
Then use RS422 or RS485 instead, it uses differential data transmission and are more reliable than RS232 single ended transmission.
It's very common in industrial applications.
http://www.rs485.com/rs485spec.html

You can use an USB to RS422/485 converter to interface it to your PC. Youcan buy these converters readymade or make your own from one of the chips mentioned in this topic.

FTDI has an application note on how to make USB to RS422/485 converters.

You can use standard Cat. 5 twisted pair network cable for your RS422/485 cable.

Compnies like Maxim makes RS422/485 to TTL UART level translators.

The current plan has been to use RS422 between the slaves and the master, with an additional USB chip for a USB slave connection between the slaves and the PC if need be. I was just looking for a "slicker" solution that would let me just plug the USB cable in to the master.

I hadn't considered just using RS422, and then unplugging the RS422 cable from tha master and plugging it in to an RS422 to USB adapter to a PC... that may be an option.

I'll probably just stick with RS422 between the master and slave, and have USB available on the slave so it can talk to the PC at the same time if need be. I'm not sure if I'll go with an actual RS422 chip or just encode the RX/TX lines with LVDS between the two boards (probably works out to the same number of chips in the end either way). :)

Thanks for the input!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

plouf wrote:
yes i know about these but the cost increased ,
33USD from just 6.75USDof single chip and a usb conector + crystal do not cost
the 26.25 of the diffirence,
epsecialy if its hard to impossible to find a distributor in your country
(greece) and exespt the extra cost it also add extra time to get one
and you think twice if you burn one (;))
i have order a few PCB in a pcb maker here to solder a few FT245/32 i just get...

i can live with that offcourse but makes my life harder :wink:

Don't forget the I2C eeprom he has on the board hehe..

It's worth it. You have to remember he has to have the little 24 pin dip circuit board made in a board house and these costs all add up in the design.

From the standpoint of ease of use, they are worth the $30! Mouser Electronics sells them now too.

I use them daily at 3 mpbs and have no issues ever.

Regards

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

sxpilot450 wrote:
Don't forget the I2C eeprom he has on the board hehe.
Just a minor detail, but it's not an I2C EEPROM, but a Microwire 93C46 EEPROM.
FTDI chips can't use I2C EEPROMs.
The 24xx series are I2C EEPROMs, the 25xx series are SPI EEPROMs and the 93xx series are Microwire EEPROMs.

Last Edited: Sun. Oct 31, 2004 - 06:04 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

sxpilot450 wrote:
plouf wrote:
yes i know about these but the cost increased ,
33USD from just 6.75USDof single chip and a usb conector + crystal do not cost
the 26.25 of the diffirence,
epsecialy if its hard to impossible to find a distributor in your country
(greece) and exespt the extra cost it also add extra time to get one
and you think twice if you burn one (;))
i have order a few PCB in a pcb maker here to solder a few FT245/32 i just get...

i can live with that offcourse but makes my life harder :wink:

Don't forget the I2C eeprom he has on the board hehe..

It's worth it. You have to remember he has to have the little 24 pin dip circuit board made in a board house and these costs all add up in the design.

From the standpoint of ease of use, they are worth the $30! Mouser Electronics sells them now too.

I use them daily at 3 mpbs and have no issues ever.

my point was that i only need ft232 and if they exist in DIP package it would cost me
lower

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

plouf wrote:
my point was that i only need ft232 and if they exist in DIP package it would cost me
lower

You can't use the FTDI chip for anything without the surrounding external components like crystal, capacitors and resistors.
I most designs the EERPOM is used too.

I don't think they will ever make a DIP package, beacuse the hobby market is way to small to make any money by doing this.
And for professional use, the costs for the DIL PCB with all the components is very small.
It's also a high-speed design, so it's important to make a good PCB layout to avoid EMI problems. This is easier with an SMD package than a DIP package mounted in a socket.
I have also used the FTDI chip for hobby use, and I must say that I prefer SMD packages instead of big DIP packages even for hobby use.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

AndersAnd wrote:
sxpilot450 wrote:
Don't forget the I2C eeprom he has on the board hehe.
Just a minor detail, but it's not an I2C EEPROM, but a Microwire 93C46 EEPROM.
FTDI chips can't use I2C EEPROMs.
The 24xx series are I2C EEPROMs, the 25xx series are SPI EEPROMs and the 93xx series are Microwire EEPROMs.

Thanks for the correction. I thought they were using I2C. As you can see, I am just an end-user of the DLP products ;)

I wish I could find a USB 2.0 version of this type of device.

Regards

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Now that I have my CP2101 evaluation kit Silicon Labs have released the CP2102, which is recommended for new products! Typical.
However, now that I have the FTDI and the SiLabs parts, I think that I'm right in saying that the FTDI part has built-in RS485 half-duplex funcionallity, whereas the SiLabs does not.
I e-mailed SiLabs, and, if I understand the reply correctly, I would have to control the RTS line from my PC program to control the transmitter enable. In view of how clumsy this can be from Windows, I shall be choosing FTDI for anything involving RS485.

Four legs good, two legs bad, three legs stable.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

CP2101 and CP2102 are pin compatible, so you should be able to to replace the CP2101 with the CP2102 on the Eval. kit. But it require a hot air gun to desolder the old device.

I tried to make a quick comparison of CP2101 vs. CP2102 features. The CP2102 improvements over CP2101 are higlighted with red text:

CP2101 Features
USB Function Controller and Transceiver
- USB specification 2.0 compliant; full-speed (12 Mbps)
- Integrated 512 byte EEPROM for vendor ID, etc.
- Integrated transceiver; no external resistors required
- Integrated clock; no external crystal required
- USB suspend states supported via SUSPEND pins
Asynchronous Serial Data Bus (UART)
- All handshaking and modem interface signals
- Data formats supported: 8-bit; 1 Stop bit
- Parity: Odd, Even, No Parity
- Baud rates: 300 bps to 921.6 kbps
- 512 byte receive buffer; 512 byte transmit buffer
- Hardware X-On / X-Off handshaking
- Event character support
Power-On Reset Circuit
Supply Voltage

- Self-powered: 3.0–3.6 V
- USB bus powered: 4.0–5.25 V

CP2102 Features
USB Function Controller and Transceiver
-USB specification 2.0 compliant; full-speed (12 Mbps)
-Integrated 1024-byte EEPROM for custom Baud rates, vendor ID, etc.
-EEPROM security lock function
-User programmable custom Baud rates
-Integrated transceiver; no external resistors required
-Integrated clock; no external crystal required
-USB suspend states supported via SUSPEND pins
Asynchronous Serial Data Bus (UART)
-All handshaking and modem interface signals
-Data formats supported: 8, 7, 6, 5-bit; 1, 1.5, 2 Stop bits
-Parity: Odd, Even, Mark, Space, No Parity
-Baud rates: 300 bps to 1 Mbps
-576-byte receive buffer; 640-byte transmit buffer
-Hardware and X-On/X-Off handshaking
-Event character support
Power-On Reset Circuit
Supply Voltage

-Self-powered: 3.0–3.6 V
-USB bus powered: 4.0–5.25 V

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I'm lookin into using the cp2102 in a project, and i was wondering how you configure the baud rates, mfg id, serial number, and all the other configurable stuff. i think i found some place that said you could configure the dev board via usb, so im guessing that the chip itself is configurable by usb also? what software or drivers or whatever will i need to configure it?

The downside to being better than everyone else is that people tend to assume you're pretentious.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

For my application I used the VCP(Virtual Com Port) drivers supplied by Silicon Labs. They take care of all that stuff. As far as the PC end is concerned, it's just another COM port, and as far as the other end is concerned it's a asynch serial stream at logic levels.
If you need to do something else, then I believe that SiLabs provide a bunch of DLLs that you can use.

Four legs good, two legs bad, three legs stable.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

krazykarl wrote:
I'm lookin into using the cp2102 in a project, and i was wondering how you configure the baud rates, mfg id, serial number, and all the other configurable stuff.

Read Silicon Laboratories Application Note AN144:
www.silabs.com/public/documents/...
And download the AN144SW software utilities:
www.silabs.com/public/documents/...
This is used to change Vendor ID (VID), Product ID (PID), Serial Number, Product String etc.

Baud rate are set inside Window/Linux/MAC OS X, just like you set the baud rate for a normal serial port. You don't need the config software to cange the baud rate.

CP210x drivers can be downloaded here:
www.avrfreaks.net/phpBB2/viewtop...
Or just install the CP210x Windows driver with Windos Update.

Also download Serial Communications Guide for CP210x:
AN197 www.silabs.com/public/documents/...
AN197SW www.silabs.com/public/documents/...

And CP2102 EVALUATION KIT USER’S GUIDE:
www.silabs.com/public/documents/...

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I recently had to choose between the FTDI chips and the CP2101. I chose the CP2101 because it doesn't need as many external components. The extra size of the FTDI chip means extra board space, that and the extra components make the cost significantly greater.

Digi-Key has it for $5.70.

I was scared spitless of trying to prototype a 28 pin part that was 5mm square and has the pins under it. I used solder past, an ordinary toaster oven with a themocouple probe connected to a multimeter and hand controlled the temperature. Worked like a champ! It was vastly eaiser than my past clumsy attempts at soldering soic parts.

If you decide to go this route, I can get you more info on how to solder the thing.

Good Luck

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

smileymicros wrote:
I was scared spitless of trying to prototype a 28 pin part that was 5mm square and has the pins under it. I used solder past, an ordinary toaster oven with a themocouple probe connected to a multimeter and hand controlled the temperature. Worked like a champ! It was vastly eaiser than my past clumsy attempts at soldering soic parts.

If you decide to go this route, I can get you more info on how to solder the thing.


Here's a good guide on how to use a toaster oven for soldering:
http://www.seattlerobotics.org/e...
The method used with this toaster oven is based on "IPC/JEDEC J-STD-020C - July 2004":
http://www.jedec.org/download/se...

But I have also read about other members hand soldering the CP2101 IC with good results.

Also check out the Circuit Cellar AVR 2004 Design Contest, there's an AVR regulated soldering oven based on a standard toaster oven:
Low-Cost Reflow Soldering Oven: http://www.circuitcellar.com/avr...

Attachment(s): 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

So I've integrated the CP2101 in to a project and it's working just fine, however I'm having a configuration problem. I had planned on interfacing it with a Windows PC at 921600 baud, but in the device manager configuration for the CP2101 serial port, the highest baud rate that is available is 115200 baud. The CP2101 specs clearly say 921600 max... am I missing something? Perhaps one of you can help me out! Much appreciated, thanks.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

jimbotko wrote:
So I've integrated the CP2101 in to a project and it's working just fine, however I'm having a configuration problem. I had planned on interfacing it with a Windows PC at 921600 baud, but in the device manager configuration for the CP2101 serial port, the highest baud rate that is available is 115200 baud. The CP2101 specs clearly say 921600 max... am I missing something? Perhaps one of you can help me out! Much appreciated, thanks.

I don't know the answer, but maybe it's a Windows problem?
Normal serial ports does not communicate faster than 115200 baud.

Silabs have their own user forum, I would reccomend to ask CP210x related questions there instead. Silabs staff answer questions in their forum.
http://www.cygnal.org/scripts/Ul...

Maybe you can already find the answer in their USB forum:
http://www.cygnal.org/scripts/fo...

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I think I found the answer about CP2101 baudrate here:
http://www.cygnal.org/ubb/Forum9...

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I am surprised that people are having so much trouble with the CP2101. I used it in a project for a client and had no problems. Tested on XP, 2000, and 98se. I used the John Hind article on MSDN:

http://msdn.microsoft.com/msdnma...

To build a C# control that underlies a Windows graphical output panel. The Hind code is excellent and covers all bases from the PC side and it has an excellent article written for it on the above link.

I formerly used C++, but C# is so much easier and perfectly suitable for most PC to Microcontroller Graphical User Interfaces applications. I haven't run into any speed problems yet, but I'm not streaming video either so I can't say about the upper end of the USB speed range.

Maybe this is a little off the main topic, but I figured some lookers might find the link useful.

Good Luck

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

CP210x is now supported by Silabs USBXpress tool:
http://www.cygnal.org/ubb/Forum9...

www2.silabs.com/tgwWebApp/appmanager/tgw/tgwHome?_nfpb=true&_pageLabel=GenericContentPage&contentObjectId=/public/web_content/products/Microcontrollers/USB/en/USBXpress.htm

Quote:
USBXpress™

The USBXpress development kit provides a complete host and device software solution for
interfacing CP210x devices and C8051F32x microcontrollers to the Universal Serial Bus
(USB). No USB protocol or host device driver expertise is required.

The USBXpress development kit includes Windows device drivers, INF driver installation files, host
interface function library (host API) provided in the form of a Windows Dynamic Link Library (DLL) and
device firmware interface function library (device API). Note the Keil 8051 tool chain is required to use the
device firmware library.

The USBXpress development kit now includes support for CP210x USB to RS-232 devices.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

AndersAnd wrote:
jimbotko wrote:
So I've integrated the CP2101 in to a project and it's working just fine, however I'm having a configuration problem. I had planned on interfacing it with a Windows PC at 921600 baud, but in the device manager configuration for the CP2101 serial port, the highest baud rate that is available is 115200 baud. The CP2101 specs clearly say 921600 max... am I missing something? Perhaps one of you can help me out! Much appreciated, thanks.

I don't know the answer, but maybe it's a Windows problem?
Normal serial ports does not communicate faster than 115200 baud.

Silabs have their own user forum, I would reccomend to ask CP210x related questions there instead. Silabs staff answer questions in their forum.
http://www.cygnal.org/scripts/Ul...

Maybe you can already find the answer in their USB forum:
http://www.cygnal.org/scripts/fo...

Thanks for the input! As it turns out, the baud rate selected in Device Manager under the fake COM port doesn't really mean anything. Anything program that connects to the COM port with adjustable baud rates can override this... I selected a custom baud rate of 921600 in my favorite terminal program, and BAM it works no problem. :)

I really like this chip!