Lpc2000

--- In lpc2000@yahoogroups.com, "lpc2100_fan" <lpc2100_fan@y...> 
wrote:

Bob, you are getting a bit silly now!
> 
> Karl,
> 
> can't help it, have to answer. 
> Is it just my limited knowledge of the English language why I missed
> the constructive element in your previous 3 postings or ..?

Yes you missed it.

> or your customer buy millions of devices, you have a very
> personal caretaker at any semiconductor vendor who will dig out any
> relevant information, assumed it does exist because your business > 
>pays for several heads at this vendor.

Im sorry to say but in your dreams there might be so, its clear
that you dont have had the experience you get from beeing involved
in millions of units purcasing.There is a big difference between
vendor and manufacturer you can only get indepth info from the
manufacturer "if" they are willing to give you the info, and that
is certanily not the case always.Anything thats baad for sales, 
they wont even give you a hint.This is nothing new it has been
there all the time and will continue to be there. This is not
a particular named manufacturer issue, not even a engineering
issue,its a money issue. 

> It would be nice if you could stop wining because I am convinced you
> have a lot of valuable know-how that this group could really benefit
> from. We have all been burned some time in the past but usually we
> pull the project off anyhow, often with, sometimes without the help 
> of the semiconductor vendor. So, let's pull together and be a
> little bit more constructive again, please :-)  
> Every ARM device has some unmentioned issues, e.g. the LPC has an
> Errata Sheet for the CAN block that tells you the FullCAN option is
> not functional at this time but there is a good basic CAN example
> posted here in the files section.  Another weakness of the LPC is 
> the poor EEPROM simulation capability.
> On the other hand the Atmel > devices with 64 pins offer about as 
>much I/O capability as the 
> Philips devices with 48-pins. 

I think its the opposite. And Atmel offers more I/O.

>Also ST and Atmel devices are
>substantially slower in code execution from Flash.

Offcourse they are but they are faster in IO as some users say!
Peculiar isnt it!

> For limitations concerning vendor 1 one you  have to ask vendor 2
> and 3 (not vendor  1) This has nothing to do with
> hiding information but everything to do with selling what is best
> about a device.

That has nothing to do with the LPC2106 GPIO issue discussed earlier.
I get the impression that you sound like more of a philips sales 
men not an engineer!

> Did you ever hear in a commercial for the Dodge Hemi
> any mentioning of the mileage? This engine is powerful, so the
> advertising is about being powerful, not about fuel efficiency. The
> LPC is small, low power and fast executing from Flash. That is what
> Philips is advertising and it seems correct to me.

What as advertising to do with the discussion about GPIO?
Absolutely nothing!Please stay to the issue bob you get
confused otherwhise!;-)

You see,different things concerns different people if you have 
noticed, some concerns SPI other about the CAN others and i about
GPIO, some about software etc, etc.

You are talking about sales techniques im and others are talking
about engineering issues, who cares if the Dodge Hemi draws a
litre or a million litre a european mile! Whats the point contra
LPC2106????

Now Bob, im getting realy tierd ,what you  are saying is a platitude!
You could had swap what you previously said for:

"My boeing 747 is so powerful, it draws 10000 litre per second and
"we marketing it as super powerful and 350 people can fly with it.

There is simply no point,you are comparing apple and grapes
using sales terms!

> Please continue to provide challenging feedback for Philips
> but try to be a little more constructive.

Bob, i dont buy your tesings,only this single one because of 
your complainits about wining wich in turn is not very constructive
either.

If you don't understand the content of folks mailings regarding
problematic issues, ask for futher explenation. If other peoples
style of writing dont fit you or it triggers your wine nerve
simply ignore mail in question. If it do conserns you, focus
on mail contents on device issues discussed in first place
and not on the person who happends to write it.

For my part matter ended. 

Regards
KD