There are books, volumes even, written about embedded development and
drivers specifically. An appropriate response is not possible without
more details of you project.
Also, most chip makers provide sample driver source code, etc. that
can be used as a basis for your own code. Or, at least, they have
extensive command specifications, etc. I don't think you'll really
need to write drivers for _everything_.
I'm currently reading this excellent book on the subject, from a TDD
perspective:
http://www.pragprog.com/titles/jgade/test-driven-development-for-embedded-c
If you want more answer than this, please describe your goals and
hardware with more detail.
Alan
On Tue, Aug 17, 2010 at 2:39 PM, Eric Cope <
eric.cope@gmail.com> wrote:
> Hello all,
> I am starting a project that requires me to write all hardware drivers for
> an embedded system. Has anyone done this type of development? Any lessons
> learned? Any good resources out there for testing, static analysis, etc?
>
> Thanks,
> Eric
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
(text/plain)