Hi,
I am using a precision ADC ADS8556 (TI's document SBAS404A) on my board
interfaced to a C6713 DSP through a McASP.
I have the GPIO5/EXT_INT5 pin of the DSP connected to the CONVST_x pins of
the ADS8556.
The CONVST_x pin has to be synchronized with the Frame-sync from the McASP.
(please look at page 14 of SBAS404A ADC datasheet for the serial interface
timing).
Can I synchronize the GPIO with the McASP framesync and generate the
required signal?
Thanks
Aditi
Generate a CONVST signal to ADS8556 using a GPIO pin from C6713
Started by ●June 15, 2011
Reply by ●June 16, 20112011-06-16
Aditi-
> I am using a precision ADC ADS8556 (TI's document SBAS404A) on my board
> interfaced to a C6713 DSP through a McASP.
>
> I have the GPIO5/EXT_INT5 pin of the DSP connected to the CONVST_x pins of
> the ADS8556.
>
> The CONVST_x pin has to be synchronized with the Frame-sync from the McASP.
> (please look at page 14 of SBAS404A ADC datasheet for the serial interface
> timing).
>
> Can I synchronize the GPIO with the McASP framesync and generate the
> required signal?
I might be missing something tere, but why not connect the McASP framesync to the CONVST_x pins, or run through an
inverter? Is there some reason why you "can't touch" the board?
Embedded engineering is always about combined software + hardware. Trying to find a software fix for every hardware
problem can lead to code that is confusing, too complex to be reliable (has very touchy timing), can't be maintained
over time, etc.
-Jeff
_____________________________________
> I am using a precision ADC ADS8556 (TI's document SBAS404A) on my board
> interfaced to a C6713 DSP through a McASP.
>
> I have the GPIO5/EXT_INT5 pin of the DSP connected to the CONVST_x pins of
> the ADS8556.
>
> The CONVST_x pin has to be synchronized with the Frame-sync from the McASP.
> (please look at page 14 of SBAS404A ADC datasheet for the serial interface
> timing).
>
> Can I synchronize the GPIO with the McASP framesync and generate the
> required signal?
I might be missing something tere, but why not connect the McASP framesync to the CONVST_x pins, or run through an
inverter? Is there some reason why you "can't touch" the board?
Embedded engineering is always about combined software + hardware. Trying to find a software fix for every hardware
problem can lead to code that is confusing, too complex to be reliable (has very touchy timing), can't be maintained
over time, etc.
-Jeff
_____________________________________