MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-243819821-1219920715=:9860"
--0-243819821-1219920715=:9860
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Hi,=0AI'm trying to implement the SPI interface to communicate with a CS840=
6 and a CS8416 audio chip. The idea is to send serial data to the chip to b=
e encoded as AES audio.=0AThe serial=A0interface is a 3-pin I2S audio conne=
ction which acts in a similar manner to SPI, with the chips acting as maste=
rs and the=A02129 as a slave.=A0I'm hoping I can fudge them together,=A0how=
ever the data length of the AES=A0chip=A0is only=A0configurable as 16, 20 o=
r 24 bit. From looking at the LPC2129 user manual, it appears that it can o=
nly be configured as 8-bit data length. Is this the case? =0AI'm working we=
ll above my required data rate so if the SPI on the 2129 can be used with 1=
6 received=A0clock edges and only 8 data bits transmitted from the 2129, th=
en it would be an option for me.=0AThe other option I've considered is to r=
un the GPIO as controlling and=A0clock=A0lines, but I can't seem to get the=
required oscillation frequency (in the order of MHz, ~1-4MHz). I'd rather =
not approach this method as I'm not sure I can rely on the produced clock (=
and also whether its feasibly possible).=0AAny feedback, in particular on t=
he data length of the=A0SPI interface, would be welcomed.=0ARegards,=0ARob=
=0A=0A=0A
--0-243819821-1219920715=:9860
Content-Type: text/html; charset=us-ascii
Hi,
I'm trying to implement the SPI interface to communicate with a CS8406 and a CS8416
audio chip. The idea is to send serial data to the chip to be encoded as AES
audio.
The serial interface is a 3-pin I2S audio connection which acts in a similar
manner to SPI, with the chips acting as masters and the 2129 as a slave. I'm
hoping I can fudge them together, however the data length of the
AES chip is only configurable as 16, 20 or 24 bit. From looking at the
LPC2129 user manual, it appears that it can only be configured as 8-bit data length. Is
this the case?
I'm working well above my required data rate so if the SPI on the 2129 can be used
with 16 received clock edges and only 8 data bits transmitted from the 2129, then it
would be an option for me.
The other option I've considered is to run the GPIO as controlling
and clock lines, but I can't seem to get the required oscillation frequency (in
the order of MHz, ~1-4MHz). I'd rather not approach this method as I'm not sure I can rely
on the produced clock (and also whether its feasibly possible).
Any feedback, in particular on the data length of the SPI interface, would be
welcomed.
Regards,
Rob
--0-243819821-1219920715=:9860--
------------------------------------

(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
> -----Original Message-----
> From: l...@yahoogroups.com [mailto:l...@yahoogroups.com] On Behalf
Of
> Robert Genders
> Sent: 28 August 2008 11:52
> To: l...@yahoogroups.com
> Subject: [lpc2000] LPC2129 SPI Concerns
>
> MIME-Version: 1.0
> Content-Type: multipart/alternative;
boundary="0-243819821-1219920715=:9860"
>
> --0-243819821-1219920715=:9860
> Content-Type: text/plain; charset=iso-8859-1
> Content-Transfer-Encoding: quoted-printable
>
> Hi,=0AI'm trying to implement the SPI interface to communicate with a
CS840=
> 6 and a CS8416 audio chip. The idea is to send serial data to the chip to
b=
> e encoded as AES audio.=0AThe serial=A0interface is a 3-pin I2S audio
conne=
WHY DON'T YOU TRY POSTING USING PLAIN TEXT&exclam;
--
Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
CrossWorks for ARM, MSP430, AVR, MAXQ, and now Cortex-M3 processors
------------------------------------

(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )