IIS snooping? - diyAudio
Go Back   Home > Forums > Source & Line > Digital Source

Digital Source Digital Players and Recorders: CD , SACD , Tape, Memory Card, etc.

Please consider donating to help us continue to serve you.

Ads on/off / Custom Title / More PMs / More album space / Advanced printing & mass image saving
Reply
 
Thread Tools Search this Thread
Old 26th June 2005, 05:40 PM   #1
diyAudio Member
 
Join Date: Jul 2004
Location: Sthlm
Default IIS snooping?

Lets say i have an I2S master and an I2S slave, a controller and a codec. They transfer some audio data between them.

Is it possible to hang an addiitional slave, configure it to listen to the first chip's address, lets say add another codec, and have it output form the same stream. Is this possible? Is some sort of driver needed with respects to current drawn?

Im looking to extract the i2s audio data inside a computer and use it to feed another chip(without messing things up with regards to the already-present codec chip)

rgds Kristian
  Reply With Quote
Old 28th June 2005, 01:02 AM   #2
wa2ise is offline wa2ise  United States
diyAudio Member
 
wa2ise's Avatar
 
Join Date: Apr 2005
Location: NJ
There should be no problem in adding a second slave to that system. You may need to use buffer/line drivers if the connection from inside the computer to the new slave is fairly long. This assumes that the 2nd slave never needs to talk back to the source. Or hope that the 1st slave tells the source the exact same things the 2nd slave wants to tell the source.
  Reply With Quote
Old 28th June 2005, 01:18 AM   #3
guido is offline guido  Netherlands
diyAudio Member
 
guido's Avatar
 
Join Date: Mar 2002
Location: diepe zuiden


i2S does not have chip addresses. It's nothing but continues audio data going over a serial bus. And only one way.

i2C however is meant for (two way) communication between ic's.
With addresses for transmitter and receiver. So more than two can be on the same bus, a slave only reacts to it's address (read or write) provided by the slave.

mvg,
__________________
GuidoB
  Reply With Quote
Old 6th July 2005, 02:19 AM   #4
diyAudio Member
 
Join Date: Sep 2004
Location: Auckland, NZ
If you are just listening to the 'traffic' then there is nothing stopping you.
If you want to communicate (I am assuming IIC here as GuidoB is quite correct) then you need to obey IIC protocols.

If you want to split left and right audio information to run a separate DAC then you will need to set them each up individuallly to be a left, and a right channel... this is where LRCK comes in.

Basically this IIC/IIS needs to be clarified as they are NOT the same, and have vastly different requirements.

apollyon25
  Reply With Quote
Old 6th July 2005, 08:01 PM   #5
guido is offline guido  Netherlands
diyAudio Member
 
guido's Avatar
 
Join Date: Mar 2002
Location: diepe zuiden
And i've spotted (..) a typo

Quote:
Originally posted by guido


i2C however is meant for (two way) communication between ic's.
With addresses for transmitter and receiver. So more than two can be on the same bus, a slave only reacts to it's address (read or write) provided by the MASTER.

mvg,
__________________
GuidoB
  Reply With Quote

Reply


Hide this!Advertise here!
Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off



New To Site? Need Help?

All times are GMT. The time now is 10:41 PM.


vBulletin Optimisation provided by vB Optimise (Pro) - vBulletin Mods & Addons Copyright © 2014 DragonByte Technologies Ltd.
Copyright 1999-2014 diyAudio

Content Relevant URLs by vBSEO 3.3.2