Forums

Clock problems with SSC on AT91SAM7S64

Started by Count Down August 4, 2005
I'm trying to use the Synchronous Serial Controller (SSC) on the Atme
AT91SAM7S64 development kit (AT91SAM7S-EK) to interface with a Nordi
nRF2401 radio transceiver.  The Atmel documentatio
(6175A-ATARM-13-Jul-05, page 352) indicates that the SSC's transmit cloc
can "drive the TK I/O pad continuously or be limited to the actual dat
transfer."  However, the options for controlling the output of the SS
transmit clock allow only for continuously outputting the clock or settin
the clock pin as an input, both of which work as expected.  There is n
setting to allow for outputting the clock only when needed fo
transmission.  Am I missing something?  Is there a good workaround fo
this?

Thanks,
CD


		
This message was sent using the comp.arch.embedded web interface o
www.EmbeddedRelated.com
"Count Down" <lifton.liftoff@gmail.com> wrote:

>I'm trying to use the Synchronous Serial Controller (SSC) on the Atmel >AT91SAM7S64 development kit (AT91SAM7S-EK) to interface with a Nordic >nRF2401 radio transceiver. The Atmel documentation >(6175A-ATARM-13-Jul-05, page 352) indicates that the SSC's transmit clock >can "drive the TK I/O pad continuously or be limited to the actual data >transfer." However, the options for controlling the output of the SSC >transmit clock allow only for continuously outputting the clock or setting >the clock pin as an input, both of which work as expected. There is no >setting to allow for outputting the clock only when needed for >transmission. Am I missing something? Is there a good workaround for >this?
IMHO, the SSC documentation could use a lot of improvement. I happen to by trying to use that same subsystem on an AT91RM9200 design and have downloaded a few other AT91' datasheets hoping that one might contain slightly different SSC wording that would enlightenment me. Requests to Atmel for more detailed information of the SSC "internals" (even if NDA is required) have fallen on deaf ears. My answer to your two questions are: 1) You are not missing anything. The SSC documentation is. 2) I can't think of a standalone workaround. -- Dan Henry