24 bit ADC interfacing with ARM using I2S

hi, i want to interface 24 bit ADC interfacing with ARM using I2S protocol. i am using ADC CS5361.if i shall enable 32 bit word width. then how can it read 24 bit data.because it will change WS after recieving 32 bit data.but ADC will give 24 bit after that it expected that WS should be changed to show 24 bit data of another channel.

how can i manage this problem?

Kindly help me.i will be grateful for your help.

Thanks

Reply to
learner
Loading thread data ...

Why do Indian contributors generically seem incapable of following punctuation with blanks?

--
 [mail]: Chuck F (cbfalconer at maineline dot net) 
 [page]: 
            Try the download section.
Reply to
CBFalconer

Perhaps it's because their native written language doesn't use spaces (or capital letters) in the same way as English.

I probably assign that error less importance than a Frenchman would assign to my inability to use the proper accent mark and gender endings when I try to write French.

Mark Borgerson

Reply to
Mark Borgerson

Just wait until you use the incorrect version (case, gender, number) of "the" to a German.

Reply to
larwe

It has to do with the structure of the language. The word "India" is phonetically similar to the word "idiot", the word "student" is consonant with "stupid". Here we go, just look around.

VLV

Reply to
Vladimir Vassilevsky

Ja, Das ist richtig! Two years of high-school German and 1 semester in college were sufficient for my visit to the Oktoberfest in Munich. I suspect that attention to grammatical detail declines in proportion to consumption of beer.

Mark Borgerson

Reply to
Mark Borgerson

I think I once figured out there were 27 different combinations. (or was it 36?) Many of them share the same version of "the", but that doesn't help much if you've got a brain that's wired for English which has just the one version.

English brains are so poorly wired for that sort of thing that most native English speakers regularly make mistakes when choosing betwen I/me, he/him, she/her, who/whom.

There's a very funny essay by Mark Twain on the German language.

formatting link

--
Grant Edwards                   grante             Yow! WHO sees a BEACH BUNNY
                                  at               sobbing on a SHAG RUG?!
                               visi.com
Reply to
Grant Edwards

I asked for an explanation, not a didactic flood of bias.

--
 [mail]: Chuck F (cbfalconer at maineline dot net) 
 [page]: 
            Try the download section.
Reply to
CBFalconer

Good question. One would expect that they'd follow the British convention of a single space following punctuation. I was taught two spaces after the punctuation mark at the end of a sentence, but I gather that's a USian thing...

--
Grant Edwards                   grante             Yow! ... I don't like FRANK
                                  at               SINATRA or his CHILDREN.
                               visi.com
Reply to
Grant Edwards

Anyone learning to type in the US was taught two spaces. I've since been told that one space is correct for typeset copy.

Reply to
Jim Stewart

One solution is to use digital IOs of ARM, instead of its I2S port, to simulate the I2S protocol sequence. That is the way we used in our indicator applications. For sure it adds burden on software. I really don't know if any micro has serial port with capability of 24-bit communication.

Reply to
Rong

For typeset copy, talking about "spaces" is a non sequitur. In typesetting "space" is a real quantity instead of an integer quantity. In typesetting there isn't such a thing as "one space" or "two spaces". There is just space of various sizes.

Whether or not the space between typeset sentences is larger than the space between words within a sentence is a matter of design style that varies. My impression is that larger spacing is the tradition in the US (TeX does it by default, and US government style guides specify it), but the trend seems to be towards uniform spacing.

--
Grant
Reply to
Grant Edwards

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.