Close

8.11.14 - programming and goal update

A project log for HQ Wireless Audio

I don't want to pay $200, when i can pay $250 and learn something. Wireless audio by someone who doesn't know anything about it.

zacnoteszacnotes 08/11/2014 at 23:230 Comments

Further reading has made me realize that I need something specific to do the programming of the wireless radio chip. The Pure Path Wireless Configurator calls for the CC Debugger, a TI product for SPI programming. Retails for $50, and I found a few clones for around $30-35. The configurator help file lists a couple of other programming methods, one of which still requires the CC Debugger. The other is direct access to the chip's bootloader through the SPI interface, using the command set defined in the user guide. This is the path I will attempt first, as I believe I can utilize stuff I have here to get it done, namely an Arduino Duemilanove. I have not delved into SPI yet, so this should be interesting.

I have learned that if I want to learn how to do something, there are at least 3 other things I will have to learn how to do, just to get to what I originally set out to learn.

Update to goals-

I believe I know the amount of latency that will be introduced by the wireless communication, which is somewhat configurable, depending on a number of programmable factors. On the low end, it looks like 16ms is achievable, and expandable up to 64ms. I am having trouble finding any reports online about how much latency is allowed before the human ear picks it up, I saw some reports that stated as low as 0.1ms, and others that ranged far above that. One of the most compelling pieces of info on this subject that I came across was a post by a TI customer in their forum, in which the customer was unhappy with a noticeable delay using a setting of around 42ms. The TI rep stated that for lip syncing purposes, latency around 20ms was desirable. The CC8520 chip trades wireless range and connection robustness for latency. Previous attempts at a project of this nature that I have done involved a bluetooth radio, which introduced a delay of about 150ms, and was unusable in a live environment, so at least the maximum is well below my previous attempt. This does not take into account the latency introduced by the CODEC, but I believe that is in the realm of 0.5-1.5ms.

Discussions