Re: Learning embedded coding, which uC?
- From: paul$@pcserviceselectronics.co.uk (Paul Carpenter)
- Date: Wed, 27 Jul 2005 10:43:05 +0100 (BST)
On Wednesday, in article
<dc6k5b$oq3$1$8302bc10@xxxxxxxxxxxxxxxx>
julian@xxxxxxxxxxxxxxxxxxx "Julian Morrison" wrote:
>Mike Harrison wrote:
>
>> Learn one thoroughly - doesn't really matter which - once you get used
>> to micro programming techniques in general, learning a new chip doesn't
>> take much effort.PIC has the advantage of a quickly-memorized
>> instruction set and vast amount of free resources. Probably best to
>> start on 8 bit as skills scale better upwards than down. Learning
>> assembler will make you able to write much better C code when you move
>> onto bigger systems as you will have a much better understanding of the
>> underlying hardware.
>
>I was hoping folks would say PIC, because there's a Maplin shop nearby
>that sells PIC programmer/tester kits (Velleman K8048), and I can drive
>that from PiKdev on Linux. I figure on turning up to a job interview
>with some 8-bit doohickey I designed, breadboarded and coded, plus spec
>docs and code printouts. Should make up for lack of formal
>qualifications :-)
Better method, try and enter some of the design competitions from magazines
like Circuit Cellar, and keep a copy of all the docs on a website (once
published anyone can get it anyway). Then have the more detailed stuff
on non-searchable pages and that URL is put in the CV as part of your
technical history, if listed in a magazine competition carries more
weight than I just designed something.
Just designing something is not what employers want, with infinite time
anyone can produce all the right documentation and a perfect presentation.
What employers are looking for is working against deadlines!
Anyway half the people at interviews would not know what to look for in the
package you presented and would be looking more at the flashing lights than
documentation and did the design meet the specification etc..
Another advantage of entering a competition is that it often gets you access
to special deals on development kits including compilers, debuggers and the
like. Even if you don't finish the first one, it is a good training ground
and we learn more from our mistakes and experiences. Also it can give good
exposure to different architectures with the differeneces and similarities
between systems.
>I assume it's C all the way, though Ada95 and Forth wouldn't hurt?
These days it is generally C and assembler on a lot of products, good people
should be able to migrate between different language anyway at least to
be able to understand what the programme is doing.
--
Paul Carpenter | paul@xxxxxxxxxxxxxxxxxxxxxxxxxxx
<http://www.pcserviceselectronics.co.uk/> PC Services
<http://www.gnuh8.org.uk/> GNU H8 & mailing list info
<http://www.badweb.org.uk/> For those web sites you hate
.
- References:
- Learning embedded coding, which uC?
- From: Julian Morrison
- Re: Learning embedded coding, which uC?
- From: Mike Harrison
- Re: Learning embedded coding, which uC?
- From: Julian Morrison
- Learning embedded coding, which uC?
- Prev by Date: C question
- Next by Date: Re: C question
- Previous by thread: Re: Learning embedded coding, which uC?
- Next by thread: Re: Learning embedded coding, which uC?
- Index(es):
Relevant Pages
|
