Reply by Johnson, Jerry April 19, 20022002-04-19
While you may not be able to do exactly what you want with a specific driver
and its API, there is always the basic system API.
periphMemWrite();
periphMemRead();
periphBitTest();
Etc...

These are defined in periph.h.

It has been my experience, that as I become more familiar with a specific
peripheral, the less I use the SDK drivers, and the more I gravitate to
optimizing the specific features I need via direct manipulation of the
peripheral registers, even resorting to my own interrupt routines in
assembly language when necessary.

I very much appreciate the SDK as a starting point, and for providing the
building blocks for a complete system. Working within its framework,
provides early success, and early feedback on the usefulness and viability
of the hardware as implemented. However, as my application has progressed,
I find that the only parts of the SDK that are left, are initialization, the
framework for register context, certain functions that are "just what the
doctor ordered," and other non-critical parts of my application.

I have never expected it to be anything else, that what it is. Taken
individually, most drivers and API's are of production quality. However,
would I build a system without replacing a few of the critical API's or
drivers with my own specialized routines? I sincerely doubt it.

Hope this helps, without stirring up too much controversy.

JJ

-----Original Message-----
From: Roelof Oelofsen [mailto:]
Sent: Friday, April 19, 2002 2:54 AM
To:
Subject: [motoroladsp] A/d sdk driver for 56f807 question Hi group,

I just started to explore the A/D SDK driver for the 56f807. My
question is this:
If I set the A/D up in loop sequential mode, the conversion complete
interrupt will be disabled. In the header file the auther states that I
must use the ADC_STATE_READ ADC ioctl command. Howver, how will I know
if the conversion is still in progress (No macro to read CIP bit in API)
or if I am reading the ADC register too frequent (Read one sample more
than once)?

Thank you in advance

Roelof Oelofsen
Telkom Development Laboratory
Telkom SA _____________________________________
Note: If you do a simple "reply" with your email client, only the author of
this message will receive your answer. You need to do a "reply all" if you
want your answer to be distributed to the entire group.

_____________________________________
About this discussion group:

To Join:

To Post:

To Leave:

Archives: http://www.yahoogroups.com/group/motoroladsp
<http://www.yahoogroups.com/group/motoroladsp>

More Groups: http://www.dsprelated.com/groups.php3
<http://www.dsprelated.com/groups.php3 ">http://docs.yahoo.com/info/terms/> .


Reply by Roelof Oelofsen April 19, 20022002-04-19
Hi group,

I just started to explore the A/D SDK driver for the 56f807. My
question is this:
If I set the A/D up in loop sequential mode, the conversion complete
interrupt will be disabled. In the header file the auther states that I
must use the ADC_STATE_READ ADC ioctl command. Howver, how will I know
if the conversion is still in progress (No macro to read CIP bit in API)
or if I am reading the ADC register too frequent (Read one sample more
than once)?

Thank you in advance

Roelof Oelofsen
Telkom Development Laboratory
Telkom SA