ADAU1452
Production
The ADAU1452 / ADAU1451 / ADAU1450 are automotive qualified audio processors that far exceed the digital signal processing capabilities of earlier SigmaDSP...
Datasheet
ADAU1452 on Analog.com
ADG774A
Production
TThe ADG774A is a monolithic CMOS device comprising four
2:1 multiplexer/demultiplexers with high impedance outputs.
The CMOS process provides low power...
Datasheet
ADG774A on Analog.com
Using a Teensy 4.1 to control ADAU1452, so the tutorial written for the Teensy 4.0 is really helpful, thanks.
My workflow is to develop and test the Sigma Studio design and use a USBi interface to load to the DSP (and to a self-boot 8MBit NAND Flash). This is quick and allows the various features of the DSP to be quickly evaluated and adjusted in rea;-time using the USBi and Sigma Studio/
Once developed, the actual product uses the Teensy processor to control the ADAU1452 to make routing and system adjustments on the fly. I would do this using the 'subordinate' I2C / SPI port on the DSP.
What is the best recommendation for hardware interfacing that would allow the Teensy to co-exist with a USBi adaptor that is plugged in at the same time? So I can perhaps download and test the configuration using the development USBi interface on the actual target hardware.
For final targeting implementation I will probably use the exported files from SS rather than programming the Self-boot Flash (EEPROM) but this is a more convoluted method during development - so useful to be able to plug in and configure directly with Sigma Studio and USBi.
TIA
GKE
Hello GKE,
What is the best recommendation for hardware interfacing that would allow the Teensy to co-exist with a USBi adaptor that is plugged in at the same time? So I can perhaps download and test the configuration using the development USBi interface on the actual target hardware.
Were you initially planning for a parallel connection and asking for any other suggestions?
You can try having a multi pole multi throw switch externally to switch between your uC and USBi or you can also have a MUX circuit to switch between those two.
You can design an eight-pin connector in your board, four pin for uC and four pin for USBi, it will be split by MPMT switch like below.
For I2C
For SPI
Another method may be having a MUX like ADG774A.
You can control the source select either by using your uC or a DIP switch.
Make sure proper GND connections are given between devices.
If you are going to use one for I2C and another for SPI, then note that initially the slave control port is in I2C mode by default, you have to toggle the SS pin three times or write three dummy writes to put the port into the SPI mode. Once it is put into the SPI mode then you can't go back to I2C mode without a power cycle or reset. Refer the slave control port in the datasheet for more info.
Regards,
Harish
Hello GKE,
What is the best recommendation for hardware interfacing that would allow the Teensy to co-exist with a USBi adaptor that is plugged in at the same time? So I can perhaps download and test the configuration using the development USBi interface on the actual target hardware.
Were you initially planning for a parallel connection and asking for any other suggestions?
You can try having a multi pole multi throw switch externally to switch between your uC and USBi or you can also have a MUX circuit to switch between those two.
You can design an eight-pin connector in your board, four pin for uC and four pin for USBi, it will be split by MPMT switch like below.
For I2C
For SPI
Another method may be having a MUX like ADG774A.
You can control the source select either by using your uC or a DIP switch.
Make sure proper GND connections are given between devices.
If you are going to use one for I2C and another for SPI, then note that initially the slave control port is in I2C mode by default, you have to toggle the SS pin three times or write three dummy writes to put the port into the SPI mode. Once it is put into the SPI mode then you can't go back to I2C mode without a power cycle or reset. Refer the slave control port in the datasheet for more info.
Regards,
Harish
