PurePath™ Studio GDE Primer

Viewed the following video which was helpful: www.ti.com/.../slac323

Still could use more info.

For example, Int4xOut_1 appears to be an analog stereo output. How do we know this and is this the headphone output, line output, or record output?

Hi, Phil,

The video that you found is a great guide to get started on PurePath Studio.

It is necessary to understand that PurePath Studio generates algorithms to be used with the miniDSP. This means that the inputs and outputs on PPS refer to the miniDSP inputs and outputs.

Let's take your example of the Int4xOut_1. This output is actually the interpolation block output. It is marked in red on the following picture:

As you can see, this red path can be routed to any output. When the EVM is used with PurePath Studio, all the outputs are enabled and routed to the miniDSP output by default.

I hope this helps you. Please let me know if you have more questions or comments.

Best regards,
Luis Fernando Rodríguez S. 

Thank you, Luis.

With the EVM, the GDE example below works only with the HP out. Why am I not hearing anything on the Line Out (LOL/LOR) as well?

 

Thanks,

Phil

Hi, Phil,

I have been doing several tests. It seems that the generated code is not the same for all the codecs. The TLV320AIC3268 PPS default configuration uses only the headphone outputs. The generated code can be checked on the SystemSettingsCode Property:

So, to use the line outputs, it will be necessary to program it via I2C. You can configure the EVM with the I2C Memory Tool. It can be found on the Tools Menu.

Please let me know if you have more questions or comments.

Best regards,
Luis Fernando Rodríguez S.

Okay, understood. Not what I expected but I can live with that.

How about Line Input? I've tried to use a Dec4xIn_2 to iDSP_A_D_1 to Int4xOut to no avail. Shouldn't this allow us to route IN2 stereo input to the Headphone output?

Or, something like this to mix both inbound IS2 with line in IN2:

Hi, Phil,

I checked the SystemSettingsCode property with your configuration. It seems that PPS configure the codec to use IN1 instead IN2.

Could you try using IN1, please?

Best regards,
Luis Fernando Rodríguez S.

Luis,

Thank you. The office closed down for the holiday but I will try this on Monday when I get back to the office.

Normally, wouldn't the attributes of the input allow us to specify the input?

Thanks again!

Phil

Hi, Phil,

It would make the things easier, but actually the codec configuration (inputs, outputs, gains) is based on the SystemSettingsCode property.

I will be waiting for your results. If you have additional questions or comments, please let me know.

Best regards,
Luis Fernando Rodríguez S.

Hi, Phil,

Similar as the line outputs, the inputs are configured by the SystemSettingsCode property. It will be necessary to program the input routing via I2C.

Best regards,
Luis Fernando Rodríguez S.

Luis,
Can you elaborate on the I2C programming? Will GDE allow us to do this directly? For example, can we modify the .CFG file and upload that file?
Thanks,
Phil

Luis,
Also, what about having two (2) analog inputs? e.g. Using IN1 and IN2?
Phil

Hi, Phil,

The analog inputs configuration can be modified in two ways:

• The .CFG file can be modified manually on the SystemSettingCode Editor. You only need to select the SystemSettingCode property and open the .CFG file.

You may check the registers 52, 54 and 55 to configure IN2 (or both IN1 and IN2 if necessary).

• Another option is to use the I2C Memory Tool (in Tool Menu). It is used to configure the registers once the code has been downloaded and run. You only need to select the necessary registers and the data to be written.

I hope this helps you. Please let me know if you still have more questions or comments.

Best regards,
Luis Fernando Rodríguez S.