Receiving Master with firmware 1.2?

Hi Ton,

I have the same problem, that the bi-directional demo only has one channel from Slave to Master.

I only hope that this is not a deficiency of the design, and that a new bi-directional demo is on its way.  This would be useful at this stage, even though we plan to use host controlled operation which I hope is possible to have stereo from Master to Slave and stereo Slave to Master.

Cheers,

Geoff Pickford

Ton, Geoff,

It seems that a few are asking the same question. I too require at least two channels from the slave to the master (whilst maintaining two from the master to the slave). The functionality was detailed in the spec from TI (not sure if it was 1.2).

Awaiting any info from TI eagerly.

Michael.

Dear TI,

I am a colleague of Ton. Yesterday there was a solution to the above problem in this blog which we have tried out on the demo board. I created the attached project, corrected all errors, but when I tried to program the configuration the wireless configurator reported an error. The application generator reports an unspecified error.

Can you take a look at the attached project, tell me what is wrong or correct the error. We need the slave inputs for our project.

With kind regards,

Adrie

2821.sb.zip

Adrie,

Would you be so kind as to point me to the solution you refer to in your above post?

Best regards,

Michael.

Michael,

Ti posted a solution on this BLOG yesterday which they removed overnight. We used the solution to create an application role that fits our application. Our application  is a stereo wireless microphone using a CC8520 link. The master is in control of the sample rate, the slave is connected to the stereo microphone.

I think it is best to wait for an answer from ti on both these scenarios, they must have removed the solution for a reason.

Regards,

Adrie

Adrie,

Thanks for the reply. My apologies, I misread Blog as Forum and assumed that I could not locate the thread/post in question. I will await an official reply from TI.

No doubt if they posted then removed a potential solution from the blog then there must be issues. I sincerely hope that these are bug related and not an unforseen limitation of the platform/technology. There is always an inherent risk for any engineering team in adopting new technology based on promised future feature sets / capability. A risk I was fully aware of before deciding to base a substantial portion of our current project on PurePath.

Michael.

Guys,

We are working on these features i.e., more than one slave producing a audio channel and a slave  producing more than one audio channel and release that in a 1.2.x release. We wanted to get a release out before the summer vacation (rev 1.2.0) and had to reduce the scope a lite. Hence, this is why we limited it to one audio channel from the slave to the master. Hopefully the next release supporting the above features will not be to far out in time.

Stay tuned!

-Per 

Dear Per!

Now we have PurePath Wireless Configurator 1.2.2.35659, but in list of Application role dont have variant with 2 channel from slave to master.

When can you make Configurator with this feature?

Best Regards,

Alexander.

Hi Alexander,

The release of this application role is right around the corner. The application role will be called stereo microphone (no audio from master to slave, 2 channels from slave to master). Is this what you want? Or do you want 2 channels in both directions? Because this is feasible with 1.2.2. Simply make an application role that supports it.

NB!! THE PERFORMANCE OF APPLICATION ROLES THAT IS NOT PART OF THE "OUT-OF-THE-BOX" PUREPATH WIRELESS CONFIGURATOR COULD BE POOR. TEXAS INSTRUMENTS HAVE ONLY TESTED AND OPTIMIZED THE PERFOMANCE ON THE APPLICATION ROLES THAT IS INCLUDED IN THE APPLICATION ROLE LIST IN THE OUT-OF-THE-BOX VERSION. ALSO SEE THE DISCLAIMER AT THE BOTTOM OF THIS POST.

I suggest copying the "m_headset_base_station.ppward" located in the "application_roles" folder in the install folder. Give this copy a suitful name e.g. "m_2up2down_base_station.ppward" and change the content to look like this:

<application_role>
    <name>Master/2up2down base station</name>
    <desc>To slave: 2 audio channels. From slave: 2 audio channel</desc>
    <aif_input_count>2</aif_input_count>
    <aif_output_count>2</aif_output_count>
    <hardware_platform_list>PurePath Wireless EB,CC85XX Headset,Custom design</hardware_platform_list>
    <operation_list>Autonomous,Host control,Host control without data side-channel</operation_list>
    <streaming_format_encoders>PCM16,SLAC</streaming_format_encoders>
    <streaming_format_decoders>SLAC</streaming_format_decoders>
    <max_slave_count>1</max_slave_count>
</application_role>

It's necessary to do similarily for the slave. Copy the "s_headset.ppward", give it a new name, and change the content to this:

<application_role>
    <name>Slave/Headset_2up2down</name>
    <desc>From master: 2 audio channels. To master: 2 audio channel</desc>
    <aif_input_count>2</aif_input_count>
    <aif_output_count>2</aif_output_count>
    <hardware_platform_list>PurePath Wireless EB,CC85XX Headset,Custom design</hardware_platform_list>
    <operation_list>Autonomous,Host control</operation_list>
    <streaming_format_encoders>SLAC</streaming_format_encoders>
    <streaming_format_decoders>PCM16,SLAC</streaming_format_decoders>
</application_role>

Pay attention to the disclaimer on top of all the application role files:

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE application_role SYSTEM "application_role_definition.dtd"[]>
<!--
By editing and changing this file the PurePath Wireless Configurator is to be regarded as Alpha Software.
Limited testing has been performed and the use of this is expected to exhibit problems,
which can range from mild to severe. The software is not fully qualified to Texas Instrument specifications
and is intended for evaluation purpose only and is not approved for production usage.

By editing or changing the content of this file, the user agrees to the following:
THE SOFTWARE ORDERED HEREUNDER IS NOT FULLY QUALIFIED TO TI SPECIFICATIONS.
NOTWITHSTANDING ANY PROVISION TO THE CONTRARY, TI MAKES NO WARRANTY, EXPRESSED, IMPLIED OR STATUTORY,
INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY OR FITNESS FOR A SPECIFIC PURPOSE, OF THIS SOFTWARE.
-->

-Kristoffer

Hi Kristoffer,

Can something similar be done to allow a system with two bidirectional slaves? Stereo from a master to two slaves, and a mono channel from each slave back to the master?

-- Ryan

Hello Kristoffer,

It is reassuring that some progress is being made in this difficult project.  

In reference to your reply of 12-15-2011 8:20 AM, I note that several other forum members also want '2 channels in both directions', (in other words, stereo from M to S and Stereo from S to M), and whilst you have shown a way of modifying the PPWARD files to achieve this, you give a substantial warning that the performance may not be good.  This is understandable because underlying proprietary software is out of a user's control.

QUESTION 1: Do you plan on formally developing the '2 channels in both directions' configuration, so that the performance is more or less guaranteed?

QUESTION 2: I know that the *.PPPRJ files call on *.PPCFG files, but what file types are called upon, or call *.PPWARD files"?  I cannot see the link.

Kind Regards,

Geoff Pickford

Hi Ryan,

The dual bidirectional slave system you mention is supported in FW1.3 which is on the web now. Configure the master as a "Dual headset base station" and each slave as "Headset". Remember to configure one slave to use "Microphone 0" and the other to use "Microphone 1".

Enjoy!

-Kristoffer