Lpc2000

Eric, 

> > We are currently in two (or maybe three) minds as to 
> whether to open 
> > up the CrossConnect API.  There's good reasons to keep it 
> closed and 
> > good reasons to open it up.
> 
> I'm sure you understand the pros and cons of opening the interface.
> 
> In favor of opening the API:
> 
> 1. If the interface is open you may sell more CrossConnect parts.

Yes, this is true.  One other question is how much we provide in the
API.

> 2. You would foster "good will" by having an open interface.

I find that doesn't cut much ice when paying for groceries at the local
Tesco store.

> Reasons not to open the API:
> 
> 1. You might lose a competitive advantage because there would 
> be less need for people to buy CrossWorks.

I don't think people purchase CrossWorks because they chose a
CrossConnect.  I might be wrong.

> 2. Further, your competitors might even take advantage of 
> your own device. They wouldn't make a clone, but rather, if 
> they support your devices you'd make a small amount on the 
> devices themselves, but they would get the higher profit 
> margin on selling their software tools to people who buy your parts.

Certainly true, but I wonder how many competitors would go to all this
trouble?

> Obviously #1 on the "in favor" list is mitigated by the fact 
> that you are not really in business to sell CrossConnect 
> parts. Rather, it's likely being done specifically as a 
> "value added" addition to help CrossWorks users. In fact, I 
> am guessing that you're probably making very little profit 
> selling CrossConnect.

Correct, we are not making much profit on the CrossConnect--but then
there's a big investment in developing CrossWorks too.  The fact we have
our own software from top to bottom and in the JTAG interface means that
we can't lay the blame with anybody else when things go wrong.  (That's
not 100% true as we use the FTDI USB to FIFO device, but that will
probably be engineered out in the next revision.)

> I'm definitely in favor of open source tools (I write some of 
> my own for the hc11/hc12), but I understand that businesses 
> have to pay attention to all of the items mentioned above.
> 
> We all love to hate the "bean counters", but we also need to eat :-)

Yep.  :-)

In fact, there is another axis to this discussion.  You'll see what I
mean when we announce something.

--
Paul Curtis, Rowley Associates Ltd  http://www.rowley.co.uk
CrossWorks for MSP430, ARM, AVR and now MAXQ processors