Easy Demo User Manual
Contents
1. 5 User Manual INSTRUMENTS SLAUG45 June 2015 Easy Demo User Manual Jorge Arbona Audio and Imaging Products ABSTRACT The Easy Demo platform is a combination of hardware and microcontroller software capable of self booting and performing A B comparisons The newest revision of the PurePath Console Motherboard Rev F has the hardware necessary to perform these functions This manual explains the operation of the available reference hardware and MSP430 code Contents 1 General CVE GW f 0 n n4 4X 3 2 The Easy Demo User Interface siciiccccccccscisscicascencccestenedseecescctscccscssenenentastsenssececianeacatuacnscncacaeenctaans 4 Dev lopment TOES icc cease bins eee eee 5 3 1 Hardware 5 3 2 SOOM WANS I DM eM LM I DE 5 4 Easy Demo Sample veceeestsaxeceasveceesaseeasieks 6 41 The Easy Demo Projet 8 4 2 The Application Layer 9 4 3 The Audio API Layer AUDIO_API 10 4 3 1 Audio Header File Generation 11 4 3 2 Loading a PurePath Studio Console2. 9 Figure 9 Audio API Folder 1 exceedances ee eine cece cee ee 10 Figure 10 Header Parser Folder Structure 11 Figure 11 PurePath Studio Header File 12 Figure 12 PurePath Console Header File 12 Figure 13 Audlo Signal FlOW entretenir tnnt omen cu a Sex nu su enean a eR ER 13 Figure 14 PPCMB AIC3262 Process 13 Figure 15 Set Volume Input and Mode 14 SLAU645 Table 1 Table 2 Tables Example Demo Layout Easy Demo Virtual Register Map Summary Easy Demo User Manual TEXAS INSTRUMENTS lu LM uM 4 cc PEE 15 TEXAS INSTRUMENTS SLAU645 1 General Overview The Easy Demo platform is a simple way to perform quick demos using its on board user interface The newest revision of the PurePath Console Motherboard PPCMB Rev adds self booting capabilities and this user interface to easily perform A B comparisons The PPCMB is already compatible with many of Tl s audio evaluation modules EVMs making it a great choice for the Easy Demo
3. 3 The Volume button VOL controls the volume level of the system The volume range can be defined by the user 4 The Input button selects between PPCMB input sources USB Optical and Analog The Easy Demo UI can also be controlled remotely via USB or an external interface by sending simple commands 4 Easy Demo User Manual IB TEXAS INSTRUMENTS SLAU645 3 Development Tools This section covers the recommended hardware and software tools for development 3 4 Hardware Tools A list of the recommended hardware collateral follows PurePath Console Motherboard PPCMB Can be obtained here http www ti com tool purepath cmbevm PPCMB compatible EVM is needed to perform demos eZ430 USB Debugging Interface Older versions are not compatible with the MSP430F5510 on board the PPCMB The eZ430 Chronos has the latest version and can be obtained here http www ti com tool EZ430 CHRONOS MSP FET Flash Emulation Tool optional Requires hand wiring Spy Bi Wire connections between the debugger and the PPCMB Can be obtained here http www ti com tool msp fet430uif 3 2 Software Tools A list of recommended tools to download before starting evaluation follows e Code Composer Studio for MSP430 firmware debugging and programming Download here http www ti com tool ccstudio e PurePath Studio GDE Portable Audio generates and downloads miniDSP code into the on bo
4. DO R W 0 Control DUT via USB 0 USB DUT control command has already been sent 1 Activate USB Control of the DUT self clearing A 2 1 2 Page 0 0x00 Register 2 0x02 Demo Increment Register This register controls Volume Input and Mode and Profile in the same way the on board push buttons control these READ RESET BIT WRITE VALUE DESCRIPTION D7 D5 R W 000 Reserved Write only reset values D4 R W 0 Increment Profile 0 Profile has been already incremented 1 Increment Profile self clearing D3 R W 0 Increment Vol 0 Vol has been already incremented 1 Increment Vol self clearing D2 R W 0 Increment Vol 0 Vol has been already incremented 1 Increment Vol self clearing D1 R W 0 Increment Audio Input Select 16 Easy Demo User Manual TEXAS INSTRUMENTS A 2 1 2 0 0x00 Register 2 0x02 Demo Increment Register This register controls Volume Input and Mode and Profile in the same way the on board push buttons control these READ RESET BIT WRITE VALUE DESCRIPTION 0 Audio Input has already been incremented 1 Increment Audio Input self clearing DO R W 0 Increment Mode 0 Mode has been already incremented 1 Increment Mode self clearing A 2 1 3 Page 0 0x00 Register 3 0x03 Active Profile Control Register This register directly controls the Active Profile READ RESET BIT WRITE VALUE DE
5. Header File into the Audio API 11 5 TLV320AIC3262 PurePath Studio Example Process Flow 13 Appendix A Easy Demo Virtual Register 14 A 1 Register Map SI TB y e miss uis asses du d PU d UTD 15 A 2 Virtual Register Map p 16 Dod Page Registers ose coat tfo dtp ee eee Nd AS DINEM IUE eee iude 16 A 2 2 Page GUIS RETTULIT 19 Figures Figure 1 PurePath Console Motherboard shown on the left 3 Figure 2 The Easy Demo User Interface 4 Figure 3 Software and Hardware Layer 6 Figure 4 Hardware Layer nnmnnn nenna 7 Figure 5 Easy Demo aiii too tapa n aka p EXER oup E n RR ARAS A RIAM RS AIRES 8 Figure 6 Project Configuration Selection 8 Figure 7 Project Configuration Selection 8 Figure 8 Event Handler State Machine
6. for details Rev F TLV320AIC3262 Target EVM Figure 13 Audio Signal Flow The PurePath Studio process flow shows such implementation For cases where it is desired to limit the main volume for example to protect a speaker based on power level the Limit 1 component can be adjusted relative to full scale Volume is controlled indirectly using the Main Vol 1 component 0 dB is obtained by writing 0x400000 PurePath Console Motherboard AIC3262 Process Flow Split 3 Multi Channe Digi AIC3262App8x4x 1 Split 1 Mux 2 Port 1 Out 1 PCM9211 Input 2 PCM3168A Input 3 MUTE Revision History v1 0 2015 06 16 E Initial Release Zero 1 One 1 Main Vol 1 ScaleOut 1 Limit D 1 Limit_1 Main Limits Volume Main Ad Vokes dCoef_i Figure 14 PPCMB AIC3262 Process Flow Easy Demo User Manual 13 14 TEXAS SLAU645 INSTRUMENTS Appendix A Easy Demo Virtual Register Map The Easy Demo Virtual Register Map VRM contains 128 pages of 8 bit registers Each register corresponds to an on board 64kB 512kbit EEPROM memory location The external I2C master sends 2 commands through USCI B1 to program these virtual registers The device can be controlled by writing to certain locations in Page 0 and Page 1 of the VRM Figure 15 is an example command that can be sent through 12C by the host 30 02 01 Increment Mode 500 30 02 02 Increment Audio Input Source 500 30 02 04 I
7. 5510 microcontroller to perform the self booting and user interface tasks It also has 4 methods to store data MSP430 flash on board IC EEPROM on board SPI flash and an SPI microSD card slot Currently the MSP430 flash and EEPROM are the only methods being used MSP430 Hardware Storage microSD Card USB AMbit Flash I2C Master 512kbit PurePath User Interface Console Buttons LEDs gt Motherboard Figure 4 Hardware Layer Stack up The Easy Demo code has a Virtual Hegister Map VRM that is controlled by the Application layer or the C Slave port The Slave port allows configuring the User Interface via USB or remotely without having to use the on board User Interface This is handled in Device vrm c Additional details can be found in Appendix A Note that the Virtual Register Map is stored in the first few registers of the EEPROM The DUT can be controlled via by the on board TAS1020B USB controller or the MSP430F5510 To prevent contention issues the bus is multiplexed and controlled by a GPIO pin see Figure 4 As mentioned in Chapter 2 the MSP430 waits for the user to push a UI button to begin initialization This will give the MSP430 control of the DUT bus DUT control can return to the TAS1020B or external interface by sending 0x01 to the VRM Register 1 Pushing the on board Reset button will also return DUT control back to the TAS1020B or external interfac
8. SCRIPTION D7 R W 0 Reserved Write only reset values D6 DO R W 000 0000 Active Profile 0 Profile A 1 Profile B 2 Profile 2 127 Profile 127 Maximum A 2 1 4 Page 0 0x00 Register 4 0x04 Active Mode Control Register This register directly controls the Active Mode READ RESET BIT WRITE VALUE DESCRIPTION D7 RAN 0 Reserved Write only reset values D6 DO R W 000 0000 Active Mode 0 Mode A 1 Mode B 2 Mode 2 127 Mode 127 Maximum A 2 1 5 Page 0 0x00 Register 5 0x05 Volume Level Control Register This register directly controls the Volume Level READ RESET BIT WRITE VALUE DESCRIPTION D7 R W 0 Reserved Write only reset values D6 DO R W 000 1000 Volume Level Easy Demo User Manual SLAU645 TEXAS INSTRUMENTS A 2 1 5 Page 0 0x00 Register 5 0x05 Volume Level Control Register This register directly controls the Volume Level BIT READ WRITE RESET VALUE DESCRIPTION 000 0000 Mute 000 0001 Level 1 000 1000 Level 8 Default 000 1110 Level 14 000 1111 Level 15 Recommended maximum 001 0000 Custom 16 111 1111 Custom 127 Maximum A 2 1 6 Page 0 0x00 Register 6 0x06 Active Audio Input Control Register This register directly controls the Active Audio Input READ RESET BIT WRITE VALUE DESCRIPTION D7 R W 0 Reserved Write only reset val
9. ard TLV320AIC3262 Download here http www ti com tool aicpurepath studio PurePath Console generates and downloads miniDSP code to EVM boards connected to the PPCMB Download here http www ti com tool PUREPATHCONSOLE Easy Demo User Manual 5 TEXAS SLAU645 INSTRUMENTS 4 Easy Demo Sample Code The Easy Demo sample code handles the user interface and sends 5 commands to on board peripherals and EVM connected to the PurePath Console Motherboard The code is divided into 3 software layers 1 The Application layer contains the main event handler initialization code interrupt service routines ISRs for port interrupts and so forth 2 The API layer contains the Audio API which handles the configuration of the audio devices for each profile mode volume and input selection 3 The Driver layer translates the audio commands into and SPI commands It also implements low level functions such as delays and the slave interface Application Layer Application Code Device API Layer Audio API AUDIO i aic3262 c tas5766 c etc Driver Layer Drivers spi c 2 vrm c MSP430 Hardware Storage microSD ius USB A4Mbit Flash 12 Master 512kbit EEPROM DUT PurePath User Interface Console 0o o Ni Motherboard Figure 3 Software and Hardware Layer Stack up 6 Easy Demo User Manual TEXAS INSTRUMENTS SLAU645 The PPCMB has an MSP430F
10. ble for compliance with all legal and regulatory requirements in connection with such use TI has specifically designated certain components as meeting ISO TS16949 requirements mainly for automotive use In any case of use of non designated products TI will not be responsible for any failure to meet ISO TS16949 Products Applications Audio www ti com audio Automotive and Transportation www ti com automotive Amplifiers amplifier ti com Communications and Telecom www ti com communications Data Converters DLP Products DSP Clocks and Timers Interface Logic Power Mgmt Microcontrollers RFID OMAP Applications Processors Wireless Connectivity dataconverter ti com www dlp com www ti com clocks interface ti com logic ti com microcontroller ti com www ti rfid com www ti com omap Computers and Peripherals Consumer Electronics Energy and Lighting Industrial Medical Security Space Avionics and Defense Video and Imaging TI E2E Community www ti com wirelessconnectivity www ti com computers www ti com consumer apps www ti com energy www ti com industrial www ti com medical www ti com security www ti com space avionics defense www ti com video Mailing Address Texas Instruments Post Office Box 655303 Dallas Texas 75265 Copyright 2015 Texas Instruments Incorporated IMPORTANT NOTICE FOR TI REFERENCE DESIGNS Texas Instruments Incorporated TI reference designs are s
11. cing orders and should verify that such information is current and complete All semiconductor products are sold subject to Tl s terms and conditions of sale supplied at the time of order acknowledgment TI warrants performance of its components to the specifications applicable at the time of sale in accordance with the warranty Tl s terms and conditions of sale of semiconductor products Testing and other quality control techniques for components are used to the extent TI deems necessary to support this warranty Except where mandated by applicable law testing of all parameters of each component is not necessarily performed TI assumes no liability for applications assistance or the design of Buyers products Buyers are responsible for their products and applications using Tl components To minimize the risks associated with Buyers products and applications Buyers should provide adequate design and operating safeguards Reproduction of significant portions of TI information in TI data books data sheets or reference designs is permissible only if reproduction is without alteration and is accompanied by all associated warranties conditions limitations and notices is not responsible or liable for such altered documentation Information of third parties may be subject to additional restrictions Buyer acknowledges and agrees that it is solely responsible for compliance with all legal regulatory and safety related requirements concer
12. ct It does not need to be modified The PurePath Studio process flow that was used to generate that code is explained in Chapter 5 4 3 2 Loading a PurePath Studio Console Header File into the Audio API The AUDIO AP header folder of the MSP430 code contains custom miniDSP header files Once the code is compiled the header file data should be pasted in xxxxx x code h This header file usually contains the default configuration that is loaded when a Profile is selected 2 header 5 aic3262 1 3262 1 app c aic3262 1 app h aic3262 1 code h aic3262 1 configs h aic3262 1 54 2 tas5766m 1 c tas5766m 1 tas5766m 1 app h 8 tas5766m 1 code h n tas5766m 1 configs h tas5766m 1 txt tas5766m 2 8 header parser c h header parser h Figure 10 Header Parser Folder Structure The x configs h files contain configurations such as coefficients for comparison sleep wake and other commands This header file usually contains the configurations loaded when a Mode is selected Small changes need to be done to the PurePath Studio Console output header file when integrating into the MSP430 code 1 Header guards should be added 2 The header parser h file should be included 3 The cfg reg reg value name should be re defined to be const so it is loaded into the MSP430 ROM and not RAM Easy Demo User Manual 11 SLAU645 12 A PurePath Studio example is
13. e Easy Demo User Manual 7 1B TEXAS SLAU645 INSTRUMENTS 4 1 The Easy Demo Project The folder structure is quite simple The execution begins in main c The 3 software layers are organized in folders Device AUDIO_API and Drivers The changelog txt file provides a list of changes from previous revisions The rest of the files and folders are automatically generated by the Code Composer Studio compiler Easy Demo Active PPCMB 7 Binaries in Includes z AUDIO Device amp Drivers 2 PPCMB 2 targetConfigs d Ink msp430f5510 cmd 8 main c changelog txt gf Ink msp430f5528 cmd Figure 5 Easy Demo Project For the PPCMB select PPCMB REVXx under Properties gt CCS General This selects the MSP430F5510 as the MCU CCS General Configuration Manage Configurations Figure 6 Project Configuration Selection The PPCMB_REVx also sets the PPCMB REVF flag under Properties gt C C General gt Paths and Symbols This symbol is used throughout the project to identify the configuration Paths and Symbols Configuration PPCMB REVF Active Includes Symbols m Libraries Library Paths Languages Symbol Assembly _PPCMB_REVF_ Figure 7 Project Configuration Selection Easy Demo User Manual IB TEXAS INSTRUMENTS 4 2 The Application Layer Device SLAU645 The Application code uses an event driven archit
14. e The second parameter passes the address of a volume variable Note that the second parameter is of type void therefore any type is compatible with the Audio function The advantage of this approach is that the Audio API can change the volume at the Application Layer in case the value exceeds the maximum level specified in the Audio API The Application Layer should only have access to AUDIO APl Audio h The AUDIO API is structured to support any parser type for example EEPROM header and so forth However loading scripts from a header file is the only method that has been implemented at this moment 2 AUDIO 2 common 4 2 parsers eeprom 2 header gt aic3262 1 aic3262 1 app c B aic3262 1 app h 8 3262 1 code h aic3262 1 configs h aic3262_1 b 4 2 tas5766m 1 tas5766m 1 app c B tas5766m 1 app h tas5766m 1 code h n tas5766m 1 configs h tas5766m 1 txt 2 tas5766m 2 c header parser c h header parser h sdcard 8 Audio c Audio h Figure 9 Audio API Folder Structure 10 Easy Demo User Manual TEXAS INSTRUMENTS SLAU645 4 3 1 Audio Header File Generation The Audio API currently parses header files that originate from PurePath Studio GDE and PurePath Console software Refer to the documentation of each software tool for details The miniDSP code for the on board TLV320AIC3262 chip is already included as part of the proje
15. ect Register 0 0x00 1 0x01 USB DUT Control Register 0 0x00 2 0x02 Demo Increment Register 0 0x00 3 0x03 Active Profile Control Register 0 0x00 4 0x04 Active Mode Control Register 0 0x00 5 0x05 Volume Level Control Register 0 0x00 6 0x06 Active Audio Input Control Register 0 0x00 7 0x07 Reserved 0 0x00 at 0 0x00 127 Ox7F VRM Options 1 0x01 0 0x00 Page Select Register 1 0x01 1 0x01 Reserved 1 0x01 T m 1 0x01 127 Ox7F Reserved Easy Demo User Manual 15 1B TEXAS SLAU645 INSTRUMENTS A 2 Virtual Register Map A 2 1 Page 0 Registers A 2 1 0 Page 0 0x00 Register 0 0x00 Page Select Register Selects active VRM Page BIT READ WRITE RESET VALUE DESCRIPTION D7 DO R W 0000 0000 Page Select Register 0 Selects Page 0 of the Register Map 1 Selects Page 1 of the Register Map 2 Selects Page 2 of the Register Map 254 Selects Page 254 of the Register Map 255 Selects Page 255 of the Register Map A 2 1 1 0 0x00 Register 1 0x01 USB DUT Control Register By default the TAS1020B USB Controller has control of the DUT When a User Interface button is pressed the DUT control is given to the MSP430 To give control back to the TAS1020B write a 1 to DO READ RESET BIT WRITE VALUE DESCRIPTION D7 D1 R W 0000 000 Reserved Write only reset values
16. ecture The event handler can be found in Device Device_eventHandler c Its state machine is shown in Figure 8 Text in capital letters indicates states Each state will call an output function upon entry Before exiting the state flags in blue will be set for other states to perform actions reset 0 reset 1 RESET out reset reset_chg PPCMB_INIT out ppcmb init profile chg input chg profile chg PROFILE out profile local chg mode chg mode chg MODE out mode local chg vol chg Service Priority Figure 8 pre service out service START LPM3 INIT out init vrm_chg IDLE out idle Active POST SERVICE out post_service PRE SERVICE out USB_ACTIVE usb_active_chg out usb_active local_chg UPDATE LEDS SERVICE out update leds vol chg input 6 VOLUME out volume local chg INPUT out input local chg vol chg Event Handler State Machine Easy Demo User Manual 9 TEXAS SLAU645 INSTRUMENTS 4 3 The Audio API Layer AUDIO The Audio API makes loading audio device configurations easy The Application Layer simply needs to call a function with a parameter and value For example if it is desired to change the volume simply send the following command Audio AUDIO VOLUME amp Device status volum
17. eset values Easy Demo User Manual 19 IMPORTANT NOTICE Texas Instruments Incorporated and its subsidiaries reserve the right to make corrections enhancements improvements and other changes to its semiconductor products and services per JESD46 latest issue and to discontinue any product or service per JESD48 latest issue Buyers should obtain the latest relevant information before placing orders and should verify that such information is current and complete All semiconductor products also referred to herein as 5 are sold subject to Tl s terms and conditions of sale supplied at the time of order acknowledgment TI warrants performance of its components to the specifications applicable at the time of sale in accordance with the warranty Tl s terms and conditions of sale of semiconductor products Testing and other quality control techniques are used to the extent deems necessary to support this warranty Except where mandated by applicable law testing of all parameters of each component is not necessarily performed TI assumes no liability for applications assistance or the design of Buyers products Buyers are responsible for their products and applications using Tl components To minimize the risks associated with Buyers products and applications Buyers should provide adequate design and operating safeguards TI does not warrant or represent that any license either e
18. ncrement Volume 500 30 02 08 Increment Volume 500 30 02 10 Increment Profile 500 30 02 1F Increment All 500 30 03 01 Set Profile to 1 500 30 00 Set Profile to Figure 15 Set Volume Input and Mode Example The Write Protocol S I2C Slave Address W ACK Register Offset ACK Data ACK Data n ACK P The I2C master must perform ACK polling to allow the MSP430 time to process its data after each write To perform ACK polling send the 12C slave address along with a write command If a NACK is returned as in the following then issue a stop command P S I2C Slave Address W NACK P If an ACK is received issue a stop and then proceed with the full command S I2C Slave Address W ACK P The I C Read Protocol A read is performed using repeated starts Sr by first writing the register offset and then issuing a read command S I2C Slave Address W ACK Register Offset ACK Sr I2C Slave Address R ACK Data 0 Data n NACK P A page is selected similar to an AIC device by writing Register O of any page Easy Demo User Manual TEXAS INSTRUMENTS A 1 Register Map Summary Table 2 summarizes the VRM SLAU645 Table 2 Easy Demo Virtual Register Map Summary PAGE NO REG NO DESCRIPTION ANY 240 OxFO Device Select Register 0 0x00 0 0 00 Page Sel
19. ning its products and any use of TI components in its applications notwithstanding any applications related information or support that may be provided by TI Buyer represents and agrees that it has all the necessary expertise to create and implement safeguards that anticipate dangerous failures monitor failures and their consequences lessen the likelihood of dangerous failures and take appropriate remedial actions Buyer will fully indemnify TI and its representatives against any damages arising out of the use of any TI components in Buyer s safety critical applications In some cases components may be promoted specifically to facilitate safety related applications With such components Tl s goal is to help enable customers to design and create their own end product solutions that meet applicable functional safety standards and requirements Nonetheless such components are subject to these terms No TI components are authorized for use FDA Class III or similar life critical medical equipment unless authorized officers of the parties have executed an agreement specifically governing such use Only those TI components that TI has specifically designated as military grade or enhanced plastic are designed and intended for use in military aerospace applications or environments Buyer acknowledges and agrees that any military or aerospace use of TI components that have not been so designated is solely at Buyer s risk and Buyer is solely
20. nts in its applications notwithstanding any applications related information or support that may be provided by TI Buyer represents and agrees that it has all the necessary expertise to create and implement safeguards which anticipate dangerous consequences of failures monitor failures and their consequences lessen the likelihood of failures that might cause harm and take appropriate remedial actions Buyer will fully indemnify TI and its representatives against any damages arising out of the use of any TI components in safety critical applications In some cases components may be promoted specifically to facilitate safety related applications With such components goal is to help enable customers to design and create their own end product solutions that meet applicable functional safety standards and requirements Nonetheless such components are subject to these terms No TI components are authorized for use in FDA Class III or similar life critical medical equipment unless authorized officers of the parties have executed a special agreement specifically governing such use Only those TI components which TI has specifically designated as military grade or enhanced plastic are designed and intended for use in military aerospace applications or environments Buyer acknowledges and agrees that any military or aerospace use of Tl components which have not been so designated is solely at the Buyer s risk and that Buyer is solely responsi
21. olely intended to assist designers Buyers who are developing systems that incorporate semiconductor products also referred to herein as components Buyer understands and agrees that Buyer remains responsible for using its independent analysis evaluation and judgment in designing Buyer s systems and products TI reference designs have been created using standard laboratory conditions and engineering practices Tl has not conducted any testing other than that specifically described in the published documentation for a particular reference design may make corrections enhancements improvements and other changes to its reference designs Buyers are authorized to use TI reference designs with the TI component s identified in each particular reference design and to modify the reference design in the development of their end products HOWEVER NO OTHER LICENSE EXPRESS OR IMPLIED BY ESTOPPEL OR OTHERWISE TO ANY OTHER TI INTELLECTUAL PROPERTY RIGHT AND NO LICENSE TO ANY THIRD PARTY TECHNOLOGY OR INTELLECTUAL PROPERTY RIGHT IS GRANTED HEREIN including but not limited to any patent right copyright mask work right or other intellectual property right relating to any combination machine or process in which TI components or services are used Information published by TI regarding third party products or services does not constitute a license to use such products or services or a warranty or endorsement thereof Use of such information ma
22. platform The Easy Demo push button user interface is described in Chapter 2 au GoTO6E VM TASS Figure 1 The PurePath Console Motherboard Shown the Left Chapter 3 lists the hardware and software tools necessary for development Chapter 4 describes the Easy Demo sample code Chapter 5 describes the TLV320AIC3262 signal processing flow Easy Demo User Manual TEXAS SLAU645 INSTRUMENTS 2 Easy Demo User Interface The Easy Demo User Interface Ul has several push buttons and LEDs to easily perform A B comparisons To activate the User Interface and begin the self boot process simply push any UI button This will give the MSP430 control of the DUT I C bus USER INTERFACE USB cz 3 a A A OPTICAL mm T B VOL ANALOG PROFILE MODE INPUT Figure 2 The Easy Demo User Interface The User Interface consists of 1 A Profile is meant to hold different demos For example Profile A might be a stereo enhancement demo while Profile B might be a bass boost demo 2 Within each Profile there are Modes Each Mode is meant to change an option within a Profile For example if performing a stereo enhancement demo Mode A is bypass and Mode B enables the enhancement Table 1 Example Demo Layout Profile Profile Name Mode Mode Name A Disabled A Stereo Enhancement B Enabled A Disabled B Bass Boost B Enabled
23. responsible for compliance with all legal and regulatory requirements in connection with such use TI has specifically designated certain components as meeting ISO TS16949 requirements mainly for automotive use In any case of use of non designated products TI will not be responsible for any failure to meet ISO TS16949 Mailing Address Texas Instruments Post Office Box 655303 Dallas Texas 75265 Copyright O 2015 Texas Instruments Incorporated
24. shown in Figure 11 c 2015 by Texas Instruments Incorporated All Rights Reserved ifndef AIC3262 1 CODE H define AIC3262 1 CODE include header_parser h define cfg reg static const cfg reg define reg value cfg reg reg value REG Section program 6 0x0 eOx7F 0x00 121 0x01 1 0xe1 254 0x01 0x7F 0x78 n endif AIC3262 1 CODEH TEXAS INSTRUMENTS Figure 11 PurePath Studio Header File Example Figure 12 shows a PurePath Console Example c 2015 by Texas Instruments Incorporated All Rights Reserved ifndef TAS5766M 1 CODE define TAS5766M 1 CODE include header parser h define cfg reg static const cfg reg define reg value cfg reg Paste PurePath Console generated configuration here cfg reg registers Select Page 0x00 exeo Set the device into Powerdown 0x02 0x11 Reset Device 0x01 0x11 n endif TAS5766M 1 CODEH Figure 12 PurePath Console Header File Example Easy Demo User Manual TEXAS INSTRUMENTS SLAU645 5 TLV320AIC3262 PurePath Studio Example Process Flow In the PurePath Console Motherboard audio can be sourced from USB Optical or Analog This signal is then fed to the TLV320AIC3262 Audio Codec with miniDSP The codec then sends digital signal to the target EVM via 125 and an analog signal to the HP OUT audio jack Refer to the schematics
25. ues D6 DO R W 000 0000 Active Audio Input 0 USB 1 Optical 2 Analog 127 Custom 255 Maximum A 2 1 7 Page 0 0x00 Registers 7 126 0x05 0x7E Reserved Registers READ RESET BIT WRITE VALUE DESCRIPTION D7 DO R W 1111 1111 Reserved Write only reset values A 2 1 8 0 0x00 Register 127 0x7F VRM Options TBD READ RESET BIT WRITE VALUE DESCRIPTION D7 D1 R W 1111 111 Reserved Write only reset values DO R W 0 VRM Default Settings Control 0 Normal operation 1 VRM Page 0 and Page 1 registers will be reset to defaults upon RESET or power cycle 18 Easy Demo User Manual TEXAS INSTRUMENTS SLAU645 A 2 1 8 Page 0 0x00 Register 127 0x7F VRM Options TBD READ RESET BIT WRITE VALUE DESCRIPTION self clearing bit A 2 2 Page 1 Registers 2 2 1 Page 1 0x01 Register 0 0x00 Page Select Register Selects active VRM Page READ RESET BIT WRITE VALUE DESCRIPTION D7 DO R W 0000 0000 Page Select Register 0 Selects Page 0 of the Register Map 1 Selects Page 1 of the Register Map 2 Selects Page 2 of the Register Map 254 Selects Page 254 of the Register Map 255 Selects Page 255 of the Register Map A 2 2 2 Page 1 0x01 Registers 1 127 0x01 0x7F Reserved Registers READ RESET BIT WRITE VALUE DESCRIPTION D7 DO R W 1111 1111 Reserved Write only r
26. xpress or implied is granted under any patent right copyright mask work right or other intellectual property right relating to any combination machine or process in which TI components or services are used Information published by TI regarding third party products or services does not constitute a license to use such products or services or a warranty or endorsement thereof Use of such information may require a license from a third party under the patents or other intellectual property of the third party or a license from TI under the patents or other intellectual property of TI Reproduction of significant portions of TI information in TI data books or data sheets is permissible only if reproduction is without alteration and is accompanied by all associated warranties conditions limitations and notices is not responsible or liable for such altered documentation Information of third parties may be subject to additional restrictions Resale of components or services with statements different from or beyond the parameters stated by TI for that component or service voids all express and any implied warranties for the associated TI component or service and is an unfair and deceptive business practice Tl is not responsible or liable for any such statements Buyer acknowledges and agrees that it is solely responsible for compliance with all legal regulatory and safety related requirements concerning its products and any use of TI compone
27. y require a license from a third party under the patents or other intellectual property of the third party or a license from under the patents or other intellectual property of TI TI REFERENCE DESIGNS ARE PROVIDED AS IS TI MAKES NO WARRANTIES OR REPRESENTATIONS WITH REGARD TO THE REFERENCE DESIGNS OR USE OF THE REFERENCE DESIGNS EXPRESS IMPLIED OR STATUTORY INCLUDING ACCURACY OR COMPLETENESS TI DISCLAIMS ANY WARRANTY OF TITLE AND ANY IMPLIED WARRANTIES OF MERCHANTABILITY FITNESS FOR A PARTICULAR PURPOSE QUIET ENJOYMENT QUIET POSSESSION AND NON INFRINGEMENT OF ANY THIRD PARTY INTELLECTUAL PROPERTY RIGHTS WITH REGARD TO TI REFERENCE DESIGNS OR USE THEREOF TI SHALL NOT BE LIABLE FOR AND SHALL NOT DEFEND OR INDEMNIFY BUYERS AGAINST ANY THIRD PARTY INFRINGEMENT CLAIM THAT RELATES TO OR IS BASED ON A COMBINATION OF COMPONENTS PROVIDED IN A TI REFERENCE DESIGN IN NO EVENT SHALL TI BE LIABLE FOR ANY ACTUAL SPECIAL INCIDENTAL CONSEQUENTIAL OR INDIRECT DAMAGES HOWEVER CAUSED ON ANY THEORY OF LIABILITY AND WHETHER OR NOT TI HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES ARISING IN ANY WAY OUT OF TI REFERENCE DESIGNS OR BUYER S USE OF TI REFERENCE DESIGNS TI reserves the right to make corrections enhancements improvements and other changes to its semiconductor products and services per JESD46 latest issue and to discontinue any product or service per JESD48 latest issue Buyers should obtain the latest relevant information before pla
Download Pdf Manuals
Related Search