EEPROM is in I2C0 which does not connect to the expansion headers. I2C2 is a shared bus. As long as no tow devices have the same address, you are limited to 255 different devices on an I2C bus.
SPI has a dedicated CS line. You can and that with a GPIO pin and create more CS signals if you like. CODECS typically uses I2S which is a totally different animal. But there are SPI and I2C CODECs out there. Gerald On Thu, Sep 3, 2015 at 6:34 AM, Rick Mann <[email protected]> wrote: > I'm having trouble figuring out which SPI ports are available on the BBB > if I want to continue to use the eMMC. > > I also need to connect I2C and SPI to an audio codec IC. I think I can use > any I2C/SPI port combination, right? Just might have to modify the driver a > bit? I'm using the same codec as on the BBB Audio Cape. > > But I was hoping there'd be an additional SPI port I could use for > something else on my cape, and still be able to use the eMMC. > > Lastly, the EEPROM is on I2C2, right? Can I share that with the audio > codec? That would let me wire it the same as the Audio Cape, might make it > easier to get the software working. > > Thanks, > > -- > Rick Mann > [email protected] > > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Gerald [email protected] http://beagleboard.org/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
