Forums

Hi Kristoffer.

Have tested the three configurations, and all come out really good, very similar to the test results I posted yesterday.  We will now study them to make sure we can create other successful configurations.

I tried reseting the 'audio device customisation' on your 3 examples, and found two of them to do exactly as you said in your last post.

However, your 'bi_directional_2slaves_micInputs' did not.  The two lists below show only those registers changed:

Before Reset:

OFF to SR-SWITCH
w 30 2A 60 # Pop reduction, output drivers delayed 100 ms
w 30 11 0F # Single-ended MIC2 in L, gain 0 db
w 30 12 F0 # Single-ended MIC2 in R, gain 0 db

INACTIVE to LOW-POWER
w 30 19 80 # Enable mic bias 2.5V
w 30 13 FC # Left ADC powered
w 30 16 FC # Right ADC powered

LOW-POWER to ACTIVE
OK

ACTIVE to LOW-POWER
OK

LOW-POWER to INACTIVE
w 30 0F 80 # Mute left ADC PGA
w 30 10 80 # Mute right ADC PGA
w 30 19 00 # Disable mic bias
w 30 13 F8 # Left ADC unpowered
w 30 16 F8 # Right ADC unpowered

After Reset:

OFF to SR-SWITCH
w 30 13 80 # Fully-differential line in L 1, gain 0 db, left ADC unpowered
w 30 16 80 # Fully-differential line in R 1, gain 0 db, right ADC unpowered
w 30 2A 60 # Pop reduction, output drivers delayed 100 ms

INACTIVE to LOW-POWER
w 30 00 00 # Select register page 0
w 30 13 84 # Fully-differential line in L 1, gain 0 db, left ADC powered
w 30 16 84 # Fully-differential line in R 1, gain 0 db, left ADC powered

LOW-POWER to ACTIVE
OK

ACTIVE to LOW-POWER
OK

LOW-POWER to INACTIVE
w 30 13 80 # Fully-differential line in L 1, gain 0 db, left ADC unpowered
w 30 16 80 # Fully-differential line in R 1, gain 0 db, right ADC unpowered

In other words, resetting changed the registers from mic inputs to RCA inputs, despite the fact that I had previously completely deleted all TI files and Configurator, and re-installed.

I tried another computer (both running VMWare Fusion on Macs running OS 10.7.4), and the same configuration did the same thing.  Further, 'bi_directional_mono_micInputs' changed, but only the order of several of the registers as they appeared on the page, but not the contents.

I deleted all TI files and Configurator on the second Mac, and it then behaved like the first Mac.

QUESTION: Could you please tell me how this may have occurred, because to me it is an unknown factor that is likely to cause problems in the future?

Regards,

Geoff Pickford

Hi Geoff,

Great that the configurations worked well!

The reason that the codec settings for "bi_directional_2slaves_micInputs" changes when you press "Reset all" is because I have modified the sequences inside the Audio device customization panel to match your requirements. Let me explain:

When custom setup of the audio device is disabled the settings in the ppwadd file is used. When custom setup is enabled the settings inside the Audio device customization panel have presidence over the ppwadd file. If you press "Reset all" the configurator will read from the ppwadd file and copy these settings into the sequences in the Audio device customization panel.

A rather confusing thing (which will be fixed in the next configurator release) is the fact that many of the example projects have old (non-ideal) saved settings that will apply if custom setup of the audio device is enabled. For example if you open the example project "CC85XXDK - Wireless Headset" you will see that custom setup of the audio device is disabled for both M and S. So-far everything is ok, and this example works as it should. The settings in the ppwadd file is now used. But if you enable custom setup for the master, and then click the Audio device customization panel you will see old saved settings. These saved settings are part of the device configuration ("cc85xxdk_demo_analog_input_bi_directional_master.ppwexcfg") and has nothing to do with the ppwadd file. They have now presidence over the ppwadd file. If you now press "Reset all" you will see that the settings change, because "Reset all" reads the ppwadd file and copy these settings into the Audio device customization panel.

In the following projects bi_directional_stereo_RCA_customSetupEnabled and bi_directional_mono_micInputs I have enabled custom setup and pressed "Reset all" (because you requested me to) so that you could see the configurations. I could have just disabled the custom setup and it would have been equivalent. So why you see changes in Mac OS is very strange!! Are you certain that you used the same configurator versions on your windows machine and your Mac?

Regards

Kristoffer

Hello Kristoffer,

Thanks for your helpful description in your Aug 2 Post.  This and other information TI has provided has assisted me in creating successful Projects, albeit a bit laborious, and I would like to list the detailed description of this creation to see if it can be improved;

1.  Create new project - File, New Project, enter File Name, save (eg Bidir-M&2xS)
2. Create 1st Device Configuration - Create New.
3. Enter Configuration Name, (eg M); Set, enter File Name (eg M), save
4. Network Role - Select Master
5. Application Role - Select Stereo Bi-Directional Base Station; Select - Create
6. Audio Streaming, Master to Slave - Change Streaming Format to SLAC
7. Audio Streaming, Slave to Master - Change Streaming Format to SLAC; Change Audio IO to AD1
8. Create Device Identification - Create New, Enter Manufacturer ID (eg 11111111);  Enter Manufacturer Name (eg PR); Create Manufacture ID
9. Use stored Name; Enter Product ID; Enter Product Name; add to Product List
10. IO Mapping - Choose Audio Device Reset Control (eg GIO2); Choose Network Pairing Button (e.g. GIO3), Choose Network Status LED (e.g. GIO3)
11. save
12. Create 2nd Device Configuration - Create New
13. Enter Configuration Name, (eg S1); Set, enter File Name (eg S1), save 
14. Network Role - Select Slave
15. Application Role - Select Mono Headset; Select - Create
16. Audio Streaming, Master to Slave - Change Audio IO to AD1
17. Audio Streaming, Slave to Master -  Change to Microphone0
18. Create Device Identification - use ID from M
19. IO Mapping - Choose Audio Device Reset Control (eg GIO2); Choose Network Pairing Button (e.g. GIO3), Choose Network Status LED (e.g. GIO3)
20. save
21. Repeat for S2

Hi Geoff,

Question 1: Your process looks fine.

Question 2: You are right. If you want to make changes to an allready existing audio device definition, and you want this change to apply every time you press the reset all button, you must do this change within the audio device definition file (.ppwadd). However, instead of making changes directly in the files that comes together with the download of the configurator, we recommend to make a copy of the device definition file you want to change and save this copy in the following folder:

C:\Documents and Settings\<user>\My Documents\Texas Instruments\PurePath Wireless Configurator\audio_devices\

If the name tag (inside the definition) is identical to a name tag in an allready existing audio device definition the user generated audio device definition overrides the installed (original) one, and this will be marked with a # in the audio device list. For more info see the" Audio Device Definition Files" chapter in the configurator help system under the sub chapter "File Handling".

Two features in the configurator that might be useful to you:

"Copy existing..." - This is a button in the Project panel that is handy if you want to create a device configuration that will be only slightly different than an allready exixting device configuration.

"Import settings from other device configuration" - This button is located next to the "Save" button. Pressing this button will copy the current sub panel of an allready existing device configurations.

Best regards

Kristoffer

Hi Kristoffer.

Will do all you have suggested.

However, what if you want different Codec settings for different configurations in the one project, eg Line Input for M and Microphone inputs for S, or even more so, very different audio paths through the Codec for each of the 3 configurations.  It appears to me that the .ppwadd changes are global.  Is it possible to define this in the ,ppward file - which to me seems magically to call on specific Application Roles, each of which can be different, but not sure how to use it for my question.

Also, I would value comments on Question 3 (re noise) of my post of Aug 5.

Finally, do you have any PCB layouts of the CC85XX using a chip antenna, or even third party sources of these?  if not, having no experience with RF design, is it possible to use the existing PCB layout (used in the CC85XX DK) and simply replace the inverted F antenna with a chip - both seem to need a 50 ohm feed.

Many thanks,

Geoff Pickford

Geoff, 

My comments to item 3 - there will be power-pulling with frequency = 1/timeslot. The higher RF output power on the board the bigger the pull. This has to do with the fact that a CC85xx will draw ╠~10mA with the radio off and ~30mA with the radio on (standalong at ~+5 dBm outputpower). With the CC2590 the difference between off and on can be twice as much. Proper care with regards to layout have to be taken to prevent this from being picked up by the audio paths. For your setup that has a ADC at the slave side and DAC at the master side (or visa versa) this pulling can be picked up at both sides. 

We spent a significant amount of effort on this on both our standard DK and the DK-HEADSET to minimize the effect, but amplify the signal enough (input volume offset for the slave/ADC and PC/Recorded input gain for the master/DAC) and you will be able to find traces of this. Remember that to be able to see this for the plot i posted I had to turn the input gain in my laptop to maximum. Without doing this I was not able to detect anything. 

Layout techniques to minimize power pulling includes:
- splitting of ground planes (Audio and RF)
- star-routing of power (GND and VCC)
- separate power regulators (Audio and RF) with good power supply rejection ratio
- good decoupling placed as close to circuits as possible

Best regards,
Kjetil 

Kjetil,

It certainly appears that your team achieved a really good result in respect to noise in terms of circuit and OCB design.

As indicated in my previous post, my colleague and I spent a fair part of today trying to put Kristoffer's suggestions into practice - without success due to two main problems.  We had previously duplicated the aic3101.ppwadd file and a stereo and mono version of the .ppward files, and stored them as instructed inside the appropriated sub-directories in the 'My Documents' Directory.  These files were modified by changing the internal names etc so as to be consistent with the .ppwcfg files.

It did not matter what we did, but the Configurator did not recognise the new .ppward files, because they did not cause the .ppwcfg files to even specify that they were M or S files etc.

We then changed the duplicate aic3101.ppwadd file and found this also was not effective in passing on its information to the .ppwdcfg files.  Even small 'comments' changes were not passed on.

Worse than this, when we Reset All, the original version of the aic3101 file showed in the Customization panel, EVEN WHEN we deleted both the original and modified files.  In other words, there was no aic3101.ppwadd file in any directory.

QUESTION 1.  Any thoughts on getting the project to recognise modified .ppward files? For example, can you please list essential parts of these files that have to be consistent with other files such as .ppwcfg and .ppward files?

QUESTION 2.  Any ideas where the Configurator is finding the deleted aic3101.ppwadd files?  Same thing happens when we insert Default.  It almost appears as if there is another aic3101.ppwadd file somewhere embedded in the Configurator.

QUESTION 3.  (already posted) Do you have any PCB layouts of the CC85XX using a chip antenna, or even third party sources of these?  if not, having no experience with RF design, is it possible to use the existing PCB layout (used in the CC85XX DK) and simply replace the inverted F antenna with a chip - both seem to need a 50 ohm feed.

Thanks again for being so patient - I am hoping the frequency of my questions will soon drop to just about nothing.

Geoff Pickford

Hi Geoff,

QUESTION1:

I'm not sure if I understand your question or problem. Could you please elaborate on what you are trying to do? If it helps I have attached a modified ppward file that should be recognized by the configurator. Place this in the "application_roles" folder under My Documents, and you should see it under "MASTER - Upstream audio" in the configurator. The name will be "MODIFIED Stereo output base station". An important part of the <name> tag is the Slave/ or Master/ prefix in the start of the name.

<name>Master/MODIFIED Stereo output base station</name>

QUESTION 2:

The only place the configurator looks for .ppwadd-files is in the "audio_devices" folder in the install folder and the "audio_devices" folder in My Documents. I tried to remove the aic3101.ppwadd file from the install folder (I don't have any in my My documents folder), and as a result the example project "CC85XXDK - Preloaded Demo" gives an error message in the Audio Interface panel because no audio device is selected. The drop down list doesn't have an option for selecting aic3101. The only possible explanations I can come up with to explain why you still see aic3101 in the list are:

- Maybe you have (by a mistake) modified the name tag inside some of the other ppwadd-files. For example if you open your aic3204.ppwadd file in an editor you could maybe see that the name tag is aic3101.

- Maybe you are looking too fast in the drop down list and that you are mistaking adc3101 to be aic3101. I have done this a few times...

- Maybe you have deleted your aic3101 files while the configurator is running and expecting to see the impact of this delete immediately. You have to close and reopen the configurator in order to see the effect of deleting ppwadd-files.

The magic you are referring to is something we have talked about earlier. There are several filters in the ppwadd-files in order to set up different i2c sequences depending on the application role selected. For examplein the aic3101.ppwadd you find:

On line 57:

    <cfg_sequence_filter_spec name="mic_input">
        <application_role_list>Master/Mono headset,Slave/Mono headset,Slave/Stereo headset,Slave/Mono microphone,Slave/Stereo microphone</application_role_list>
    </cfg_sequence_filter_spec>

These lines have the following meaning: If some of the listed application roles are selected we have what we have called "mic_input". Further down in the file on line 82 we see:

        -{mic_input
        w 30 13 80    # Fully-differential line in L 1, gain 0 db, left ADC unpowered
        w 30 16 80    # Fully-differential line in R 1, gain 0 db, right ADC unpowered
        -}
        +{mic_input
        w 30 11 0F    # Single-ended MIC2 in L, gain 0 db
        w 30 12 F0    # Single-ended MIC2 in R, gain 0 db
        +}

This means that if the application role selected is one of the following:

Master/Mono headset,  Slave/Mono headset,  Slave/Stereo headset,  Slave/Mono microphone,  Slave/Stereo microphone

we have mic_input and the i2c sequence that will be applied is

w 30 11 0F    # Single-ended MIC2 in L, gain 0 db
w 30 12 F0    # Single-ended MIC2 in R, gain 0 db

If any other appliaction role is selected we don't have mic_input and the i2c sequence that will be applied is

w 30 13 80    # Fully-differential line in L 1, gain 0 db, left ADC unpowered
w 30 16 80    # Fully-differential line in R 1, gain 0 db, right ADC unpowered

QUESTION 3:

Unfortunatelly we don't have any ref designs using chip antennas. But simply copy TI's ref design all the way to the PCB antenna (you can skip the zero ohm and the placeholder for the shunt component), and continue with the ref design for the chip antenna (they often come with some recommended external components). Just make sure the antenna is a 50 ohm antenna and designed to operate in the 2.4 GHz band.