Embedded C Programming

How do I go about becoming an expert embedded C programmer and how do I do it without purchasing all the hardware necessary to test them with?

I am doing this because I want to get a job as an embedded C programmer and makes lots of money and being really respected.

Use Forth instead.

Get emulators for whatever it is you want to develop for and hope they're reasonably accurate.

Get one of those ~$14 microcontrollers with free toolchains.

You can get development boards for less than $5 (Texas Instruments' Launchpad boards), so there's no excuse not to get some hardware. Atmel's AVR Studio has a passable built-in emulator, and some console emulators have built-in development/debugging support. Arduinos are a bit more expensive, but there's a fuckton of tutorials for total beginners (also get a clone board, they're a lot cheaper than the name brand ones).

Once you get your basic led-blinking code running, start reading up on communications protocols (I2C, SPI etc.), A/D conversion, motor control, real-time systems and anything else related to embedded systems. Note that you will need a workable knowledge of electronics and electronics design. If you want to be a pure software guy, you have to be an embedded Linux guy, DSP maths expert or something.

>>4,5
He asked how to do it without purchasing the hardware. Try again faggots.

>>6
No, he said all the hardware necessary to test them with (whatever 'them' are).

>>6
And I gave some suggestions for that. Read, comprehend, and only then reply.

>>8
And at that moment, >>6-kun was enlightened.

Just program according to the JPL C standard.

>>10
Why would I consult the Jewish Porn League for information on C programming, hymie?

>>11
Was that supposed to be funny?

>>12
It probably is funny to the gentiles. They have a very primitive sense of humor. There is no Lenny Bruce-tier comedian among the goyim.

>>10
Except that the JPL standard strictly prohibits the use of dynamic memory allocation effectively crushing the potential of any program written with it.

>>14
The title of this thread is "embedded C programming". dymelloc is useless for many embedded applications since you know exactly what each byte of RAM is going to be used for.

>>15
Shalom!

>>13
Lenny Bruce
http://www.youtube.com/watch?v=Ua0TT87KNwo

>>1
How would you manage to become an EXPERT EMBEDDED C PROGRAMMER without touching any hardware at all? At best you'll become a toy virtual machine C programmer.

Speaking of which, does anyone know any cheap microcontrollers that could potentially handle half-decent audio and a SATA hard drive?

Sometimes I just put my computer on to listen to music, but that's a bit of a waste of power.

>>19
An AVR + SATA-IDE converter + MP3 decoder (optional if you're fine with WAV) + DAC would be enough.

Or if you want a solution with less hardware, a PIC32MX is enough to decode MP3 without an external decoder:
http://www.youtube.com/watch?v=oHz8sEbGpQQ

>>20
Thanks!

>>21
The second option is not exactly cheap though. If I were you I'd just get one of the cheap HDD MP3 players from DX.

>>20
PIC32 is garbage, MIPS is a terrible core for MCUs.

There are no jews. Please continue with this programming-related discussion.

Write homebrews for the PSP¹

______________________________
^{1: PlayStation Portable}

>>25
GBA is more "embedded" than PSP. PSP has a whole gles-esque API.