Electronics > Beginners
"Chained" uControllers to configure an I2C device
<< < (3/3)
jhpadjustable:
Oh, if it's supposed to be open-ended, the proxy uC is the way to go. Then you can load firmware to emulate any gain/frequency control block you like (TDA7439 etc.). You might even add a couple of volume up/down buttons to the uC to make the board that much more useful in the I2S-only case.
jmf11:

--- Quote from: jhpadjustable on November 23, 2019, 02:38:45 am ---Oh, if it's supposed to be open-ended, the proxy uC is the way to go. Then you can load firmware to emulate any gain/frequency control block you like (TDA7439 etc.). You might even add a couple of volume up/down buttons to the uC to make the board that much more useful in the I2S-only case.

--- End quote ---

What do you mean by proxy uC ? Is it the RPi (for example) talking to the board uC, then the board uC talking the TAS3251 ?

Having come pins to connect Volume and buttons to the board uC is the idea

JMF
jhpadjustable:

--- Quote from: jmf11 on November 23, 2019, 07:50:18 am ---What do you mean by proxy uC ? Is it the RPi (for example) talking to the board uC, then the board uC talking the TAS3251 ?

Having come pins to connect Volume and buttons to the board uC is the idea

--- End quote ---
Exactly. You use the hardware I2C interface on the uC to receive commands from the Pi (or other controller) and buttons, and translate/replay them out another interface, bit-banged or hardware, depending on what uCs will fit your design.
Navigation
Message Index
Previous page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod