Exact match. Not showing close matches.
'[PIC] How do you become a microchip certified cons'
I'm looking for it on the web page, but all I can find is a list of
Shawn Wilton (b9 Systems)
Shawn Wilton wrote:
>I'm looking for it on the web page, but all I can find is a list of
>Shawn Wilton (b9 Systems)
This is generally offered through Microchip's FAEs who become familiar
capabilities. After all, Microchip can't afford to recommend someone
without a bit
of a track record, so usually you need to be sucessful a few times. They
unlikely to recommend someone without most of the Microchip development
FAE's know very well that MOST problems with designs are NOT the PIC itself,
but other issues, like electrical noise, PCB layout problems, rejection
of static, and
a CLEAR understanding of ground problems.
One problem with the idea was that Microchip wanted regular feedback info on
the designs you were doing, what chips, etc. My clients were mostly
government contractors, and my NDA's always nix'd that, so I never followed
through on advice of my attorney. But that requirement might be relaxed
now that Microchip is sitting pretty on top of the Microcontroller world.
But it has never shaken my confidence in PIC controllers, and certainly
proven me right. PIC controllers are at the heart of some really superb
Note: To protect our network,
attachments must be sent to
engineer.cotse.net . attach
In message <cotse.net> 43BDB7E5.5030601
Bob Axtell <cotse.net> wrote: engineer
> But it has never shaken my confidence in PIC controllers, and certainly
> time has
> proven me right. PIC controllers are at the heart of some really superb
It's no small wonder. In my experience, SX development tools are dire at
best. My ICD2 has never missed a beat, but my SV-TEHS "SX-DEV" SX ICD likes
nothing more than to interrupt a debugging session with a generic
"Communications error". The Microchip stuff "just works".
Then you have Atmel. "You'll get the chips in about ten weeks, if you're
lucky". Nuff said. I can get most PICs with a leadtime of a week at most.
Last time I tried to get some Atmel stuff it took them (or rather their
distributors) a good twelve weeks to deliver the stuff I'd ordered ("the
factory still hasn't sent the chips out"), and by that time I'd already
finished the design with a PIC...
If Mchip are on top, I'm certainly not surprised.
Phil. | Acorn RiscPC600 SA220 64MB+6GB 100baseT
dsl.pipex.com | Athlon64 3200+ A8VDeluxe R2 512MB+100GB philpem
http://www.philpem.me.uk/ | Panasonic CF-25 Mk.2 Toughbook
... Doing my part to preserve order in the universe
|On Fri, 06 Jan 2006 00:50:30 GMT, you wrote:
>In message <cotse.net> 43BDB7E5.5030601
> Bob Axtell <cotse.net> wrote: engineer
>> But it has never shaken my confidence in PIC controllers, and certainly
>> time has
>> proven me right. PIC controllers are at the heart of some really superb
>It's no small wonder. In my experience, SX development tools are dire at
>best. My ICD2 has never missed a beat, but my SV-TEHS "SX-DEV" SX ICD likes
>nothing more than to interrupt a debugging session with a generic
>"Communications error". The Microchip stuff "just works".
>Then you have Atmel. "You'll get the chips in about ten weeks, if you're
And once you do get into production, chances are they'll obsolete them in a few years. In contrast,
you can still buy PIC1654XT's if you want to.
Their devtools are also a sorry mess. Umpteen different emulation systems depending on the chips
being used, mostly using generic FPGA based cores with peripheral emulation tacked on the side using
discrete devices that approximate the function of the actual chip.
Took them several years to improve their assembler with such "innovative" features as conditional
assembly, macros and proper checking of relative branch ranges.
Tools are a bit better now (although assembler syntax is still somewhat quirky), but the track
record does not look good for the future.
More... (looser matching)
- Last day of these posts
- In 2006
, 2007 only
- New search...