rickman says...
> Good news on the modules. So how do we tell which
> vendors sell the good board and which sell the dodgy
> board?
Well, I know of one seller for the good boards. Other than
that, a buyer would have to ask the seller whether his stock
actually has the CJMCU legend on the back, or is blank, blank
being what you want.
> Let me ask you to explain why this device is so
> important. I read your other post but I'm still not
> completely clear. Let me restate what I perceive is
> going on.
Well, I would admit that it makes less sense to me now than
in the beginning.
> You are building a board with an MSP430 processor. As a
> means to program the MSP430, you want the CP2102 device
> to be built onto your board so it is always there, but
> it will be added as a chip, not the module. That is the
> primary reason you are doing any of this, right?
Not necessarily. If someone is fluent in surface mount,
then both the CP2102 (QFN) and the buffer (TSSOP) would just
be additional parts to provide space and route. But the
two MSP430 processors I'm working with also come in DIP
packages. So someone could actually do a through-hole board
and use the module instead of the QFN, and the buffer in
SOIC, which even I can solder by hand, although it's not
pretty to watch.
This started with a friend who thinks there may be a lot of
interest in an MSP project he's doing, but is concerned that
flashing new firmware versions would require a user to buy a
Launchpad. I was just trying to figure out if it's
feasible to build the USB function into the project so BSL
could be done with just a USB cable which most already have.
And having started on this, I just thought I would finish it
up and provide a complete system that anyone could use if
needed. That includes the hardware side, but also software
at both ends.
Of course TI makes MSP processors with built-in USB, but I
think those would be more expensive, and only surface mount.
And an Arduino with built-in USB could also be used, but at
those would require much higher power than MSP, so batteries
wouldn't last as long. But I would say at this point that
the requirement for the buffer makes this a marginal idea at
best. Anyway, the software is done, so I just want to make
sure the hardware actually works, then write it up and be
done with it.
> For prototyping you are buying these very small modules
> with the chip and micro-usb connector. I don't recall
> just what your requirements are to interface these
> modules to the prototype MCU board (which I assume is
> one of the launchpads or other TMS340 prototyping
> boards), but it requires that you use a buffer chip to
> isolate the CP2102 when it has no power via the USB
> connector. So your board will need the CP2102 and the
> buffer chip to be built in.
I don't have in mind a prototyping board. I assume a project
using this stuff would be designed and routed and purchased
from service like OSHPark. So a board designed for the
particular project. The module has six through-hole
connections, so it could be soldered to matching holes in
the main board if someone didn't want to do surface mount.
So that's why the smaller the module, the better.
> On top of that there is a problem with some unknown
> number of these micro-USB CP2102 modules that it outputs
> 4.3 volts instead of 3.3 volts both on the Vcc pin and
> the signal pins. In addition, this module does not
> bring out to an I/O connector the handshake signal
> needed to reset the MCU. I assume you have a way of
> soldering to the handshake pin or something.
Yes, the voltage issue is a problem. But if the processor
is to be powered by USB through the buffer, it will know on
boot that it should go into BSL because its RXD pin, with
pulldown enabled, will be high. In any case, the software
on the Windows side can always toggle the DTR->Reset line
low and reset the processor. So I don't think there's a
need for a reset button.
> So the part I still don't get is why you are so wedded
> to this module and why it needs to be so small and so
> inexpensive. You talk as if this will be something
> others will be able to use, but other than the devices
> built into your board, this will not be an easy solution
> for others. They will have to buy the CP2102 module,
> test it to see if it is the wrong voltage, buy the
> buffer chip and then find a way to connect these
> components together.
Well, I expect all of this to be done by whoever is creating
a project, not the ultimate users. So it's just two
additional items they have to procure and deal with.
> Since this will only be used with the MSP430 and nearly
> all the prototyping boards available with these chips
> also contain a programmer USB interface chip, why is
> this even useful? Why doesn't it make more sense for
> you to just get your prototype done using whatever
> boards you can find that work and then focus on the
> board you are fabricating?
I guess I gave the wrong impression somewhere along the
line. There is no prototyping board involved.
As to whether it will be useful, I don't really know. But
it's been interesting to work on.