• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 30 subscribers
  • Views 1572 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

PCM3070 / PurePath Studio - Mapping processing blocks and choosing framework

Benjamin Moore
Mastermind 30960 points

Other Parts Discussed in Thread: PCM3070

Hello Team,

I'm working with a PCM3070 EVM and the Control Software/PurePath Studio and I have a couple questions.

1) The signal processing blocks listed in the datasheet are tied to the output of PurePath studio, right? So when I setup a biquad in the GUI, it is mapped to a processing block with the appropriate biquad resources? 

2) I'm having trouble choosing between the different (2x1x), (4x2x), (8x4x) frameworks. I know this affects the interpolator for the DAC and the decimator for the ADC input, but does this just dictate the supported sample rates? How do I figure out what sample rates will be supported an what the effects will be of switching between frameworks?

Thank you in advance!

Best Regards,

Ben

  • 0
    TI__Guru* 84915 points

    Hi, Ben,

    1) The signal processing blocks are used when the miniDSP is not required. So, when the miniDSP is used (by PurePath Studio), the processing blocks are disabled. You may take a look at registers 60 and 61 (page 0). These registers must be configured as 0x00 in order to use the miniDSP.

    2) Please take a look at the help window of the frameworks on PurePath Studio. You may find all the information about the supported sample rates of each framework.

    Frameworks_PCM3070.pdf

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

    Best regards,
    Luis Fernando Rodríguez S.

  • 0 in reply to Luis Fernando Rodriguez S.
    TI__Mastermind 30960 points

    Thank you, Luis!

    If I want to include a volume control in my PurePath Studio design and expect the setting for this to be controlled by a UI in my end product, would that change be made via a command over the I2C interface? If so, how do I figure out the register address to use in that transaction? I see this in the 'help' menu for the part, but I'm not sure how I use it:

    The registers would not change with a different build, right? I'm also curious about how this might work with changing the EQ on the fly.

    Best Regards,

    Ben

  • 0 in reply to Benjamin Moore
    TI__Guru* 84915 points

    Hi, Ben,

    You may find all the information of the volume block on its properties. You must click on the volume block and then check the Component Interface section. This section contains all the registers related with the selected block (see the following picture for details).

    The component I2C address doesn't change unless you remove the block of the algorithm and place another one. The address assignation depends of which block is placed at first.

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

    Best regards,
    Luis Fernando Rodríguez S.

  • 0 in reply to Luis Fernando Rodriguez S.
    TI__Mastermind 30960 points
    Hello Luis,

    That makes sense.

    However, it seems strange that the addresses don't update as other controls are added/removed to optimize memory usage on the miniDSP. Is this the case or am I misunderstanding how the addresses are assigned and what they represent?

    Best Regards,
    Ben
  • 0 in reply to Benjamin Moore
    TI__Guru* 84915 points
    Hi, Benjamin,

    PurePath Studio assigns a memory address to each component block. In some kinds of blocks, there are specific memory addresses that cannot be used by other blocks. I mean, there are few blocks such interpolation/decimation block that have already assigned a group of memory locations and they cannot be changed. In cases where a value need to be stored, PPS assigns an address in order of appearance.

    Best regards,
    Luis Fernando Rodríguez S.