USB-to-Serial Adapters

Started by "see...@yahoo.com [rabbit-semi]" February 6, 2018
Any recommended USB-to-Serial adapters for programming the RCM6000 module? The one Rabbit used to recommend for the R3000 doesn't work.
On 2/6/2018 6:12 PM, s...@yahoo.com [rabbit-semi] wrote:
> Any recommended USB-to-Serial adapters for programming the RCM6000
> module? The one Rabbit used to recommend for the R3000 doesn't work.
I used one from Saelig:

http://www.saelig.com/USSP/USSP004.htm
Any FTDI-based one should work. I found you need to change the latency
to 1 in the driver.
--
------
Scott G. Henion, Consultant
Web site: http://SHDesigns.org
------


Posted by: Scott Henion



I assume you’re talking about the RCM6xxx “MiniCore” modules. They don’t have a dedicated programming header like the 4000-based products, so I’ve always used one of the MiniCore development boards with integrated FTDI chip.

If you want to program a module installed in your own hardware, you’ll need to design in the equivalent circuitry from the development board.. I’m a fan of using FTDI’s TTL-level cables (http://www.ftdichip.com/Products/Cables/USBTTLSerial.htm ) for connections like this.

-Tom
> On Feb 6, 2018, at 3:12 PM, s...@yahoo.com [rabbit-semi] wrote:
>
> Any recommended USB-to-Serial adapters for programming the RCM6000 module? The one Rabbit used to recommend for the R3000 doesn't work.
Correct, the RCM6xxx mini-core modules. I can program the modules using a standard RS-232 port. The problem is programming them via a USB-to-Serial adapter. Serial ports are getting harder to come by these days, especially for laptops. When's the last time you saw an RS-232 port on a laptop? I have one on mine, but you have to use a docking station to get access to it. With a desktop you can drop in a serial board in one of the expansion slots.

In any case, we have a couple of different adapters, and they both use an FTDI chip. Per Scott's suggestion, we've been playing with the driver timing parameters. But we haven't been able to get it to work for programming. One is a Tripp-Lite, the other is CHIPI-X. It looks like the CHIPI-X device is made by FTDI.
So, it turns out that the problem is that the adapter we bought is using the latest (or very new) FTDI chip, and the FDTI tools don't recognize it and therefore can't configure it. So you need an adapter that uses the same FTDI device that's used on R6000 Dev Kit motherboard. Then it works great.