This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC8530: Cc8530

Part Number: CC8530
Other Parts Discussed in Thread: TAS2562

I’m looking to use the cc8530 with two digital amplifiers. Looking through the documentation and pure path configuration software I can’t see how to control multiple devices on the I2c bus with the cc8530. The amplifiers have the option to set different I2c addresses, but  the cc8530 doesn’t show how to address multiple devices. I considered just setting the two amplifiers to the same item to the address and controlling them in unison, but I know this is not the “correct“ way to do this and it has the potential to lock up the bus. All that aside, the amplifiers will always function together, output the same audio at the same volume. Is there a way to control multiple amps using the CC8530 or do you believe this method would be functional?

I know some people will say just use a 2 channel amp, but I need a low power (3 W per channel)  high quality amp with minimal quiescent current that functions of a 3.3V supply. I have struggled to find a two channel amp meeting these requirements. I will have to write a driver for it to function with the cc8530 either way, as none of the pre-specified amps function on less than 3.3 V, so drivers are not a concern.

Thank you,

Austin

  • Hi Austin,

    Section 2.1.4 (I2C Master Interface) from the CC85XX User's Guide and the Help Window from PurePath Wireless Configurator (PPWLCFG) show that up to four slave devices can be supported.  You can add four slaves per project and create custom .ppwadd files (inside the Texas Instruments\PurePath Wireless Configurator\audio_devices directory of the software download) to specify different slave addresses.  Please read the "Audio Device Definition Files" section of the PPWLCFG Help Documentation to get a better idea as to how this can be achieved.

    Regards,
    Ryan

  • Yes, but I cannot find how to load multiple device configurations to one cc8530 chip. I have completed the ppwadd file for the tax2562, and can configure the cc8530 to run for one of those devices. I made two copies of the file, one fore each i2c address, but I cannot find where in the software do add two audio devices on the same i2c bus.

  • Have you tried "Add existing" to the Device Configurations section of the main project page?

    Regards,
    Ryan

  • Yes, that is to create a new device configuration for a new cc8530 chip, not to add a second audio device to the same chip. It creates a completely different firmware image.

  • You are correct, that was my mistake.  Have you tried "Enabling" Custom setup from the Audio Interface screen and further configuring the Audio Device Customization tab for further setup options?

    Regards,
    Ryan

  • I can write both of the devices into the same ppwadd devise definition file. The only point where I am unsure if this would work is volume control. There doesn’t seem to be a way to enter more than one I2c address in the volume control section. Everything else is easy to configure both amps from one file.

  • I also thought of using the amp’s i2c global address to control both amps at the same time, but this changes how the amp’s ack bit is transmitted. Because of the cc8530’s limited firmware flexibility I was unsure how it would handle never receiving an ack signal for volume control.

  • Volume control behavior is hard-coded in the audio device definition files and cannot be setup from the Audio Device Customization panel.  At the moment I don't have further recommendations on how to resolve your specific application requirements.

    Regards,
    Ryan

  • I already had to write the audio device definition file myself as the tas2562 is not innately compatible with the configurator. Do you know if in the definition file you can list two I2c addresses in the volume control section? Is there any way to access the software’s source code to allow this?

  • I have not personally tried similar changes to the definition files and the source code cannot be shared or altered to allow such modifications

    Regards,
    Ryan