# Connexions

You are here: Home » Content » Audio Conference Bridge

### Lenses

What is a lens?

#### Definition of a lens

##### Lenses

A lens is a custom view of the content in the repository. You can think of it as a fancy kind of list that will let you see content through the eyes of organizations and people you trust.

##### What is in a lens?

Lens makers point to materials (modules and collections), creating a guide that includes their own comments and descriptive tags about the content.

##### Who can create a lens?

Any individual member, a community, or a respected organization.

##### What are tags?

Tags are descriptors added by lens makers to help label content, attaching a vocabulary that is meaningful in the context of the lens.

#### Affiliated with (What does "Affiliated with" mean?)

This content is either by members of the organizations listed or about topics related to the organizations listed. Click each link to see a list of all content affiliated with the organization.
• TI DSP

This module is included inLens: Texas Instruments DSP Lens
By: Texas Instruments

Click the "TI DSP" link to see all content affiliated with them.

Click the tag icon to display tags associated with this content.

#### Also in these lenses

• Lens for Engineering

This module is included inLens: Lens for Engineering
By: Sidney Burrus

Click the "Lens for Engineering" link to see all content selected in this lens.

### Recently Viewed

This feature requires Javascript to be enabled.

### Tags

(What is a tag?)

These tags come from the endorsement, affiliation, and other lenses that include this content.

# Audio Conference Bridge

Module by: Jacob Fainguelernt. E-mail the author

Summary: The Audio Conference Bridge enables a voice call with multiple (n >2) attendants. The algorithm monitors the voice signals from all attendants, and creates the signals to be transmitted to the attendants. In this module the implementation of such a bridge is described, The implementation is based on the integration of user-specific driver with the Simulink environement building blocks.

## Introduction

The Audio Conference Bridge enables a voice call with multiple (n >2) attendants, as described in Figure 1. The algorithm monitors the voice signals from all attendants, and creates the signals to be transmitted to the attendants.

This application cannot be implemented using solely the DSK6713, as it has only 2 analog ports. Therefore two daughterboards, the TLV320AIC20/20KEVM and the DSP/CODEC development platform, are used. In this example we will integrate an algorithm based on Simulink blocks, with a legacy driver.

This module demonstrates the use of the device driver building blocks together with legacy code integration to implement a custom device driver on the DSK6713. This feature allows the use of the Simulink® environment with user-specific drivers.

A wide range of algorithms exist, in the current chapter a simple algorithm based on finding the maximum level among 3 attendants is implemented

## The Platform

The DSK6713 supports stereo analog inputs and outputs. The Audio Conference Bridge application demands more analog ports. In this example we will use TLV320AIC24EVM1(). This board contains two TLV320AIC24 () stereo CODECs, thus supporting 4 audio channels. The system is shown in Figure 2.

The TLV320AIC24 implements the smart time division multiplexed serial port (SMARTDM™). The SMARTDM port is a synchronous 4-wire serial port in TDM format for glue-free interface to TI DSPs. The TLV320AIC24 can be gluelessly cascaded to any SMARTDM-based device to form a multichannel CODEC, and up to eight TLV320AIC2x CODECs can be cascaded2.

The SMARTDM port is connected to the Multichannel Buffered Serial Port (McBSP) in the DSP as shown in Figure 3.

The TLV320AIC24 supports various types of analog interfaces, and can operate with sampling rates to 104 KSPS, with 16 bit samples. The block diagram is shown in Figure 4. The TLV320AIC24 features are summarized in Figure 5.

## The TLV320AIC24 Driver

### Principle of Operation

The driver operates in a double-buffering scheme as shown in Figure 6. There are two buffers in each direction (Receive/Transmit). For each frame to processes occur simultaneously:

1. The CPU processes samples from one of the receive buffers, and stores the results in the correspondent transmit buffer.
2. The EDMA reads and writes samples that belong to the next frame.

The driver uses two EDMA channels. The first will read from a fixed location in the memory, which is the received data register (DRR) of the MCBSP port, to a buffer in the memory that will hold those samples. The second will write from a buffer in the memory to a fixed location that is the transmit register (DXR) of the MCBSP port.

Samples are send/received to/from the CODEC in an interleaved mode. The EDMA receive channel sorts the samples and place the samples of each channel placed in consecutive addresses in the data memory. A symmetric process occurs in the opposite direction. Figure 7 describes the process of receiving samples and Figure 8 describes the process of transmitting samples. Once a buffer is received/transmitted a Callback (please refer to section ) function is called, activating the signal processing procedures.

The driver consists of 4 files:

1. ”aic24_defs.h” – This file contains the definitions of the various registers of the TLV320AIC24.
2. ”aic24.h” – Needed for the DSP configuration.
3. ”aic24.c” – Contains the various initialization routines.
4. “AIC24-C6713.cdb” - DSP-BIOS configuration file.

Those files should be integrated with a user file, explained in the next section.

### The Driver Interface

The driver interface is implemented in the user defined file. This file consists of the main program and the callback processing function.

#### The “main” program

The driver allocates a handle to the chain of CODECs, initializes it and afterwards activates the components.

This file:

1. Initializes the AIC24 handle. This is a structure that contains handles to the EDMA and to the MCBSP port. It also contains their configuration structures, pointers to user buffers (the data is read and written through them) and some more variables like the AIC24 register values, the current buffer etc. handle and the data is exchanged through a callback function. The function AIC24_Init Defaults initializes the handle with the values provided by user and some default values.
2. Configures the TLV320AIC24 mode3.
4. Run the AIC24_Start, the main function that:
• Configures the McBSP
• Activates the McBSP
• Configures the AIC24 (through the McBSP).
• Configures the EDMA
• Activates the EDMA

#### The Callback Function

The user is required to create a callback function were the processing is implemented. This function receives pointers to two buffers as arguments; one buffer contains the latest information read from the CODECs, while the second will contain the data to be written to the CODECs. The callback function template is shown:

##### The Callback Function Template


void process(Int16 *r_data, Int16 *w_data
{
/* Processing functions (user-defined) */
}


### Using the Driver in the CCS Environment

In this section we will describe the way the driver is used in the CCS environment.

1. Create a new project in the CCS environment
2. Copy the following files to the project directory4:
• aic24.c
• aic24.h
• aic24_defs.h
• AIC24-C6713.cdb
• Add the user file with the callback function.

An example of this process is provided in the next section.

### An example

The example creates two audio paths as follows:

Path # 1: J14 ⇒ CODEC#0/INP1 ⇒ SMARTDM/Channel 0 ⇒ McBSP1/Channel 0 ⇒ DSP ⇒ McBSP1/Channel 2 ⇒ SMARTDM/Channel 2 ⇒ CODEC#2/OUTP1 ⇒ J4

Path # 2: J13 ⇒ CODEC#2/INP3 ⇒ SMARTDM/Channel 2 ⇒ McBSP1/Channel 2 ⇒ DSP ⇒ McBSP1/Channel 0 ⇒ SMARTDM/Channel 0 ⇒ CODEC#0/OUTP2 ⇒ J5

The example is illustrated in Figure 9. A user defined function “test.c” was created for this application.

#### The Program

The first part of the program defines the buffers for reading and writing samples.

##### Buffer Allocation


#define NUM_CODECS	4	// The number of CODECs connected
#define DATANUM	128	// The number of samples  in each channel
#define DATAMODE	0	// AIC24 operates in data mode

#if 〔DATAMODE == 1〕
#define BUFS_PER_CHANNEL 1
#else
#define BUFS_PER_CHANNEL 2
#endif

Int16 r_data1[DATANUM*NUM_CODECS*BUFS_PER_CHANNEL];  // data buffer for read
Int16 w_data1[DATANUM*NUM_CODECS*BUFS_PER_CHANNEL];    // data buffer for read
Int16 r_data2[DATANUM*NUM_CODECS*BUFS_PER_CHANNEL];    // data buffer for write
Int16 w_data2[DATANUM*NUM_CODECS*BUFS_PER_CHANNEL];    // data buffer for write



The callback function follows the template introduced in the previous section, and calls the subroutine “copyData”.

##### The Callback Function


void copyData〔Int16 *inbuf, Int16 *outbuf, Int16 length〕
{
Int16 i = 0;

for 〔i = 0; i < length; i++rbbrk; {
outbuf[i] = inbuf[i];
}
}

// The callback function that is called when the EDMA buffers are full
// The function copies the data from channel 0 to channel 2
void process(Int16 *r_data, Int16 *w_data)
{
if (hAIC24.DataMode)
{
int i;
for (i=0; i<DATANUM; i++)
r_data[0*DATANUM+i] ⩓= 0xfffe;
}
copyData(r_data+0*DATANUM, w_data+2*DATANUM, DATANUM);
}


The main program:

• Sets the AIC24 handle
• Maps the analog ports 5
• Starts the AIC24

After this step, the program will enter in an endless loop. Samples will be processed each time an EDMA interrupt occurs.

##### The “main” program


int main()
{
// setting up the AIC24 handle
AIC24_InitDefaults(⩓hAIC24, NUM_CODECS, DATANUM, r_data1, r_data2, w_data1, w_data2, process);

// determining data mode (continuous or programming)
hAIC24.DataMode = DATAMODE;

// example for setting devices input and outputs
// if defaults are ok then this is not necessary
hAIC24.Regs[0].creg6.reg6a.control_bit.mici = 0;
hAIC24.Regs[0].creg6.reg6a.control_bit.inp1 = 1;
hAIC24.Regs[0].creg6.reg6a.control_bit.inp2 = 0;
hAIC24.Regs[0].creg6.reg6a.control_bit.inp3 = 0;
hAIC24.Regs[0].creg6.reg6a.control_bit.inp4 = 0;
hAIC24.Regs[0].creg6.reg6b.control_bit.outp1 = 0;
hAIC24.Regs[0].creg6.reg6b.control_bit.outp2 = 1;
hAIC24.Regs[0].creg6.reg6b.control_bit.outp3 = 0;

hAIC24.Regs[1].creg6.reg6a.control_bit.mici = 0;
hAIC24.Regs[1].creg6.reg6a.control_bit.inp1 = 0;
hAIC24.Regs[1].creg6.reg6a.control_bit.inp2 = 0;
hAIC24.Regs[1].creg6.reg6a.control_bit.inp3 = 0;
hAIC24.Regs[1].creg6.reg6a.control_bit.inp4 = 0;
hAIC24.Regs[1].creg6.reg6b.control_bit.outp1 = 0;
hAIC24.Regs[1].creg6.reg6b.control_bit.outp2 = 0;
hAIC24.Regs[1].creg6.reg6b.control_bit.outp3 = 0;

hAIC24.Regs[2].creg6.reg6a.control_bit.mici = 0;
hAIC24.Regs[2].creg6.reg6a.control_bit.inp1 = 0;
hAIC24.Regs[2].creg6.reg6a.control_bit.inp2 = 0;
hAIC24.Regs[2].creg6.reg6a.control_bit.inp3 = 1;
hAIC24.Regs[2].creg6.reg6a.control_bit.inp4 = 0;
hAIC24.Regs[2].creg6.reg6b.control_bit.outp1 = 1;
hAIC24.Regs[2].creg6.reg6b.control_bit.outp2 = 0;
hAIC24.Regs[2].creg6.reg6b.control_bit.outp3 = 0;

hAIC24.Regs[3].creg6.reg6a.control_bit.mici = 0;
hAIC24.Regs[3].creg6.reg6a.control_bit.inp1 = 0;
hAIC24.Regs[3].creg6.reg6a.control_bit.inp2 = 0;
hAIC24.Regs[3].creg6.reg6a.control_bit.inp3 = 0;
hAIC24.Regs[3].creg6.reg6a.control_bit.inp4 = 0;
hAIC24.Regs[3].creg6.reg6b.control_bit.outp1 = 0;
hAIC24.Regs[3].creg6.reg6b.control_bit.outp2 = 0;
hAIC24.Regs[3].creg6.reg6b.control_bit.outp3 = 0;

// Starting the AIC24
AIC24_Start(⩓hAIC24);


#### Running the Example

Connect an audio source to J14, a speaker / headphone to J4 and check Path #1.

Connect an audio source to J13, a speaker / headphone to J5 and check Path #2.

### Principle of Operation

The main idea is to create a Simulink environment that reads samples form 4 channels, process them and send them to 4 output channels. The example model is shown in Figure 14.

The Simulink driver block is based on the driver described in the previous chapters. Both drivers read and write samples using a double-buffering mechanism, but they differ in the way they activate the processing algorithm.

The algorithm code, in the Simulink environment, runs as a separate free-running task. At the start of the function it checks the semaphore to see if data is ready to read from the buffer – if not then it stays in a wait state until the semaphore is posted by the callback routine (Please refer to section ). Once this has been posted, it reads the data elements from the addresses supplied by the appropriate pointers. Once the algorithm has then processed the data, it writes the data elements from the addresses supplied by the appropriate pointers. After process is concluded, it will wait for the next frame of samples. This process then repeats until halted.

The callback function, in the Simulink environment, needs to set the appropriate pointers each time an EDMA interrupt occur, and post a semaphore for the “Algorithm” task afterwards.

### Driver Structure

The driver consists of 4 files:

1. ”aic24_defs.h” – This file contains the definitions of the various registers of the TLV320AIC24.
2. ”aic24.h” – Needed for the DSP configuration.
3. ”aic24.c” – Contains the various initialization routines.

The first three files are the same files used for the CCS driver. The ai24link.c file is similar to the user defined file (test.c for example) described in ,

This file contains the following functions and definitions:

#### Buffers Definitions:


Int16 r_data1[DATANUM*NUM_CODECS*BUFS_PER_CHANNEL];  // data buffer for read
Int16 w_data1[DATANUM*NUM_CODECS*BUFS_PER_CHANNEL];  // data buffer for read
Int16 r_data2[DATANUM*NUM_CODECS*BUFS_PER_CHANNEL];  // data buffer for write
Int16 w_data2[DATANUM*NUM_CODECS*BUFS_PER_CHANNEL];  // data buffer for write


#### Pointers to each channel buffers (read and write).

Those pointers are used by the Algorithm block in the Simulink model.


Int16 *InSig1;
Int16 *InSig2;
Int16 *InSig3;
Int16 *InSig4;
Int16 *OutSig1;
Int16 *OutSig2;
Int16 *OutSig3;
Int16 *OutSig4;


#### An AIC24 handle and a Semaphore handle

As explained the semaphore will be used to wait for the data to arrive.


AIC24_Handle hAIC24;


It calls the AIC24_Init function and also initializes the semaphore.


{
// setting up the AIC24 handle
AIC24_InitDefaults(⩓hAIC24, NUM_CODECS, DATANUM, r_data1, r_data2, w_data1, w_data2, AIC24LINK_process);

}


#### The callback function.

The callback function AIC24LINK_process simply sets the channel buffer pointers (the pointers the model uses) to the correct places and posts on the semaphore.


{
InSig1 = r_data;
InSig2 = r_data + DATANUM;
InSig3 = r_data + DATANUM*2;
InSig4 = r_data + DATANUM*3;
OutSig1 = w_data;
OutSig2 = w_data + DATANUM;
OutSig3 = w_data + DATANUM*2;
OutSig4 = w_data + DATANUM*3;

}

{
}


This function pends on the semaphore.

This function calls AIC24_start.

The Simulink block will be created from the AIC23 driver used in the “Custom Device Driver/Legacy Code Integration” Simulink demo.

• Open the demo
• Open the model
• Double-click the "AIC23 Codec Driver" box.
• Rename it (TLV320AIC24EVM).
• Delete the EDMA related boxes6.
• Double-click the "System Start" box. Delete the code and replace it by the initialization function AIC24LINK_init () in the execution box.
• Double-click the "System Enable". Delete the code and add the AIC24LINK_Start(), to the execution box.
• Delete the code in the "Model Header" box.
• Double-click the "Model Source" box. Delete the code. Add to the "Top of Model Source" box the line #include "aic24link.h". This will allow calling the functions in the aic24link.c file. Figure 17 summarizes the driver blocks configuration

The next steps will guide you through the “Algorithm” block configuration

• Add 6 terminators (inputs and outputs) both inside and outside the "Algorithm" box and of course wiring them appropriately. Double click on each terminator and set its dimension to 647 (except for the internal terminators). Set the data type to int16.The 8 input and output ports should be linked to the buffers (i.e. the pointers) in the aic24link.c file.
• Right-click the wires connecting the terminators to the algorithm and select "Signal Properties". A new window will be opened window, Select "RealTime Workshop" tab and "ImportedExternPointer". Enter the signal name. It should have the same name of the correspondent pointers in the driver (As defined in the aic24link.c file).
• Double-click the "Algorithm" box again and then open the "System Outputs" block. Delete the code and add a call to AIC24LINK_wait. This way the loop of the task stops each time and waits for the data.

The model is now ready to generate real-time code for processing of 4 audio channels. AN example is shown in the next chapter.

## The Audio Conference Bridge Application

This chapter illustrates the use of the Simulink driver introduced in the previous chapter, to implement a conference bridge.

Figure 15 shows the configuration used for this application. Three headsets8 are used, enabling a 3-port conference. The DSP monitors the 3 input signals, and routes the “loudest” input signal to the three outputs. The algorithm is described in the next section.

### The Algorithm

The algorithm processes 64 samples (each channel). It calculates the absolute power of each channel (sum of absolute values). Three counters are used, each one corresponding to a distinct channel.

For each frame the counter correspondent to the loudest channel is incremented. When a channel counter equals a threshold9, the correspondent channel is selected.

For Each 64 samples frame the following algorithm is implemented:

#### Output Channel Selection Procedure

1. Find Maximum Input Level
2. Increment Counter correspondent to the “loudest” channel
3. If the Counter value =10 THEN:
4. Broadcast correspondent input channel to all outputs
5. Reset Counter

This section will describe the process of generating a real-time application using Simulink blocks for the algorithm itself and the driver introduced in the previous chapter. The Simulink model is shown in Figure 2110.

The block diagram shown in Figure 20 is translated to the model shown in the following figures.

• The conference algorithm routes a selected channel to the 4 outputs:
• The input level is measured for 4 channels:
• The 4 level values compose a 4 element vector. This vector is fed to the “Max abs value” block:
• The index of the Maximum level enters the index selection block. The correspondent channel is incremented and compared to the threshold.
• If the counter value equals the threshold, the index is selected as input to the conference block

The real-time model can be found in the file C67_Simulink_conference.rar.

## References

1. "TLV320AIC20K/24KEVM User's Guide ", TI Document SLAU088A, April 2005 (http://focus.ti.com/lit/ug/slau088a/slau088a.pdf)
2. "DSP−CODEC Development Platform User's Guide", TI Document SLAU090, September 2002 (http://focus.ti.com/lit/ug/slau090/slau090.pdf)
3. "Low Power Highly-Integrated Programmable 16-Bit 26-KSPS Dual Channel CODEC (Rev. D)" TI Document SLAS363D, March 2002 –Revised April 2005 (http://focus.ti.com/lit/ds/slas363d/slas363d.pdf)

## Appendix A – Configuration

### TLV320AIC24K & CODEC Development Platform

#### Analog Ports

The following table is based on the one the Codec’s EVM Datasheet.

It matches the board connectors with the inputs and outputs.

(Notice, this table includes corrections and elaborations in compare to the one in the Datasheet).

• We are using the TLV320AIC24KEVM is 24K.

The Inputs and Outputs of a certain channel are set by its 6a and 6b registers.

Those registers can be set, like before, between the initialization of the Handle and its activation.

If, for example, the input samples of channel 0 in the CODEC should be received from INP311. The configuration should be as follows:



int main()
{
// setting up the AIC24 handle
AIC24_InitDefaults(⩓hAIC24,  4, 64, r_data1, r_data2, w_data1, w_data2, process);

hAIC24.Regs[0].creg6.reg6a.control_bit.mici = 0;
hAIC24.Regs[0].creg6.reg6a.control_bit.inp1 = 0;
hAIC24.Regs[0].creg6.reg6a.control_bit.inp2 = 0;
hAIC24.Regs[0].creg6.reg6a.control_bit.inp3 = 1;
hAIC24.Regs[0].creg6.reg6a.control_bit.inp4 = 0;

// Starting the AIC24
AIC24_Start(⩓hAIC24);
}


Each entry corresponds to a bit that determines whether it should be connected or not to the channel input12. The names of the fields correlate to the table.

A similar procedure applies for the output channel:


hAIC24.Regs[0].creg6.reg6b.control_bit.outp1 = 0;
hAIC24.Regs[0].creg6.reg6b.control_bit.outp2 = 1;
hAIC24.Regs[0].creg6.reg6b.control_bit.outp3 = 0;


In the case above, output of channel 0 is connected to OUTP2 (i.e. J1).

A single channel can be connected to a number of outputs. It is not recommended to connect two CODEC channels to a single output.

The default channel configuration is:

Even Channels (i.e. 0,2,…) Input: MICI

Even Channels (i.e. 0,2,…) Output: OUTP1

Odd Channels (i.e. 1,3,…) Input: INP1

Odd Channels (i.e. 1,3,…) Output: OUTP2

#### Switches and Jumpers

##### Jumper settings for the AIC24 EVM

 Jumper State W1: Closed W2: 2-3 W3: 1-2 W4: 1-2 W5: Closed P1.13-P1.14: Closed P1.9-P1.10: Closed P1.11-P1.12: Closed
##### Jumper settings for the AIC Motherboard

 Jumper State W1: 1-2 W2: 2-3

### DSP

#### MCBSP Configuration

##### McBSP Configuration (Register Values)

 Register Value Remarks Serial Port Control Register (SPCR) MCBSP_SPCR_FREE_YES Used for emulation MCBSP_SPCR_SOFT_YES Used for emulation MCBSP_SPCR_FRST_YES Frame sync generator is in reset (generated by master CODEC) MCBSP_SPCR_GRST_YES Sample rate generator is in reset (generated by master CODEC) MCBSP_SPCR_XINTM_FRM The transmit interrupt is driven by new frame sync MCBSP_SPCR_XSYNCERR_NO No synchronization error detected MCBSP_SPCR_XRST_YES The serial port transmitter is disabled and in reset state MCBSP_SPCR_DLB_OFF Digital Loopback mode off MCBSP_SPCR_RJUST_RZF Receive data right-justified and zero-fill MSBSs in DRR MCBSP_SPCR_CLKSTP_DISABLE The Clock stop mode is disabled MCBSP_SPCR_DXENA_OFF Disable extra delay of DX MCBSP_SPCR_RINTM_FRM Receive interrupt on new frame synch MCBSP_SPCR_RSYNCERR_NO No synchronization error detected MCBSP_SPCR_RRST_YES The serial port receiver is disabled and in reset state Receive Control Register (RCR) MCBSP_RCR_RPHASE_SINGLE receive one phase only MCBSP_RCR_RFRLEN2_OF(0) Don't Care. Phase 2 is not used MCBSP_RCR_RWDLEN2_16BIT Don't Care. Phase 2 is not used MCBSP_RCR_RCOMPAND_MSB No companding, data transfer starts with MSB first MCBSP_RCR_RFIG_NO sync error doesn't cause transfer restart MCBSP_RCR_RDATDLY_1BIT 1 bit data delay MCBSP_RCR_RFRLEN1_OF(NumChannels-1) Each frame contains an element for each channel MCBSP_RCR_RWDLEN1_16BIT Each sample is 16 bit MCBSP_RCR_RWDREVRS_DISABLE Don't Care. Only 16 bit elements are used Transmit Control Register (XCR) MCBSP_XCR_XPHASE_SINGLE Transmit one phase only MCBSP_XCR_XFRLEN2_OF(0) Don't Care. Phase 2 is not used MCBSP_XCR_XWDLEN2_16BIT Don't Care. Phase 2 is not used MCBSP_XCR_XCOMPAND_MSB No companding, data transfer starts with MSB first MCBSP_XCR_XFIG_NO sync error doesn't cause transfer restart MCBSP_XCR_XDATDLY_1BIT 1 bit data delay MCBSP_XCR_XFRLEN1_OF(NumChannels-1) Each frame contains an element for each channel MCBSP_XCR_XWDLEN1_16BIT Each sample is 16bit MCBSP_XCR_XWDREVRS_DISABLE Does not matter, we use 16 bit elements Sample Rate Generator Register (SRGR) 0 Not used, clock and frame sync are generated by the master CODEC (The source code contains the flags but they are 0) Pin Control Register (PCR) MCBSP_PCR_XIOEN_SP All pins are dedicated for MCBSP (Not GPIO) MCBSP_PCR_RIOEN_SP All pins are dedicated for MCBSP (Not GPIO) MCBSP_PCR_FSXM_EXTERNAL Transmit frame sync is generated by the master CODEC MCBSP_PCR_FSRM_EXTERNAL Receive frame sync is generated by the master CODEC MCBSP_PCR_CLKXM_INPUT Transmit clock sync is generated by the master CODEC MCBSP_PCR_CLKRM_INPUT Receive clock sync is generated by the master CODEC MCBSP_PCR_CLKSSTAT_0 Does not matter (used in GPIO) MCBSP_PCR_DXSTAT_0 Does not matter (used in GPIO) MCBSP_PCR_FSXP_ACTIVEHIGH Transmit frame sync is active high for AIC24 MCBSP_PCR_FSRP_ACTIVEHIGH Receive frame sync is active high for AIC24 MCBSP_PCR_CLKXP_RISING Transmit data driven on rising edge MCBSP_PCR_CLKRP_FALLING Receive data sampled on falling edge MCR 0 Unused RCER 0 Unused XCER 0 Unused

## Footnotes

1. An additional board the DSP-CODEC Platform () is also needed. This board mainly interfaces between the TLV320AIC24EVM connector and the peripherals connector in the DSK6713.
2. We will use a single EVM board in this example.
3. The CODEC can operate in DATAMODE or PROGRAMMING mode. We’ll use DATAMODE only. For a detailed explanation, please refer to the TLV320AIC24 datasheet.
4. This is not mandatory. You may add the files from any directory.
5. The driver sets a default configuration. Those commands are needed if changes in the default configuration are required.
6. The EDMA and interrupts configurations are handled as in the original CCS driver.
7. The terminator dimension should match the value of the DATANUM constant in the aic24link.c file
9. The requirement for a threshold amount of wining rounds was set in order to prevent random noise or occasional “spikes” from interfering with the algorithms function. This threshold is configurable. In this example it was set to 10.
10. The algorithm is implemented for 4 channels, however we will use only three of them.
11. According to the table the connection is to J10, since we are working with 24K EVM and channel 0 is located at the master side.)
12. Other entries were reset ('0'), as they should not be connected to the channel's input.

## Content actions

PDF | EPUB (?)

### What is an EPUB file?

EPUB is an electronic book format that can be read on a variety of mobile devices.

My Favorites (?)

'My Favorites' is a special kind of lens which you can use to bookmark modules and collections. 'My Favorites' can only be seen by you, and collections saved in 'My Favorites' can remember the last module you were on. You need an account to use 'My Favorites'.

| A lens I own (?)

#### Definition of a lens

##### Lenses

A lens is a custom view of the content in the repository. You can think of it as a fancy kind of list that will let you see content through the eyes of organizations and people you trust.

##### What is in a lens?

Lens makers point to materials (modules and collections), creating a guide that includes their own comments and descriptive tags about the content.

##### Who can create a lens?

Any individual member, a community, or a respected organization.

##### What are tags?

Tags are descriptors added by lens makers to help label content, attaching a vocabulary that is meaningful in the context of the lens.

| External bookmarks