• State
  • Locked Locked
  • Replies 15 replies
  • Subscribers 30 subscribers
  • Views 258 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.

TAS2X63EVM: TAS2563

Riccardo Gennari
Prodigy 10 points
Part Number: TAS2X63EVM
Other Parts Discussed in Thread: TAS2563, PP-SALB2-EVM

Tool/software: 

I'm just getting started with the TAS2x63EVM, but I'm having more than one problem.
We've already built our custom board and integrated baremetal drivers for the minimal TAS2563 configuration. We've also played a short PCM trace, which has allowed us to establish that the hardware on our custom board is correct.
We now aim to characterize our speakers using the PurePath Console 3 tools, for which we've already obtained authorization.
However, we're immediately encountering two problems:

1. The EVM, connected and powered via USB, is recognized correctly, but except for a very brief period when the PC is restarted, it never emits any sound. To perform this test, we're using the speaker included in the kit with the default settings (JUMPER in the default position). We're only powering J31 with 5 volts, and the board is consuming 0.151A.
Do we have a driver issue? Our PC is a Dell Windows 11. The driver recognized and used for the audio device connected via USB 2 to the PC is listed as:
TI USB UAC2.0 Audio driver version 4.59.0.40491 dated March 27, 2019.
2- In the Purepath 3 console, we installed both the I2C master and speaker tuning apps, and we can connect to the device (the TAS2563 status shows connected), although when we start the console, it warns us that the EVM is not a supported type.
We downloaded Purepath today and the evaluation board about 3 months ago; we don't think any further updates are necessary.


How can we proceed? How can we perform a minimal tuning of our speakers?


We're awaiting feedback because all these issues are slowing down our development.
We think the documentation is somewhat confusing.
The software asks for a .cfg file, but from what we have downloaded from your portal, it doesn't appear to be available.
We urgently ask you to help us understand or provide updated guides that are aligned with the software tools currently available.
Thank you and keep up the good work.
  • 0
    TI__Guru** 111065 points

    Hi Ricardo,

    I'll have a look at your issue description and come back to you as soonn as possible.

    Best regards,
    -Ivan Salazar
    Applications Engineer

  • 0 in reply to Ivan Salazar
    TI__Guru** 111065 points

    Hi Ricardo,

    There are 2 versions of the PP3 app for TAS2563, one for WCSP and another for QFN package version of the device.
    I think you were granted access only for the WCSP, but you're using QFN EVM.

    Now you should have access to the QFN version, please install this new version and configure the device with it.

    The warning message you get about incorrect version of EVM can be ignored for now, this is something we'll fix on the software side.

    If you have speaker parameters from your speaker vendor you can copy into PPC3, otherwise you'll need PP-SALB2-EVM Evaluation board | TI.com connected to the EVM to run the characterization process.

    Best regards,
    -Ivan Salazar
    Applications Engineer

  • 0 in reply to Ivan Salazar
    Prodigy 10 points

    Now that I have access to the new version, does that mean I have to go to my personal section and download the new software?

    Thanks for that.

    Regarding my speaker, we're currently evaluating several vendors, and it shouldn't be difficult for me to get the speaker data they're offering. Given the cost of the PP-SALB2-EVM, we didn't think we'd need it.

    Regarding the I2C driver, I can best use and configure the device on our custom board. Will the new software help me create a configuration to pass via bare metal I2C to my device? I've already started with your bare metal driver, where I can find test cases 1, 2, and 3, but there's no information about the device's Music or Voice profiles. Only the Bypass profile is present. I've seen that the PPC software has a section dedicated to I2C master. How can I use it to create a complete driver for device configuration, volume control, and more? Thank you for your kind support.

  • 0 in reply to Ivan Salazar
    Prodigy 10 points

    I downloaded and familiarized myself with the tool, and now I can even hear the sound coming out of the demo speaker thanks to the integrated audio player.
    This allows me to create a precise configuration for my speaker.
    My system will be mono, even though the player only supports stereo tracks, as far as I can tell.
    However, I'm not entirely sure which output type is appropriate for the configuration I need to apply via I2C to the TAS2563. I saw that I can export two types of output to end system integration: ROM mode and Tuning Mode. I generate a PCM with I2S on my MCU and send it to the TAS2563, which is configured first. At this point, can you advise me which of the two outputs is best to use? I'm using your bare metal driver in C, which is what I started with and where I should use the header files generated by the end system integration procedure. Is my reasoning correct?
    Sorry but this is my first time approaching an intelligent audio device like your ppc3 system.

  • 0 in reply to Riccardo Gennari
    TI__Guru** 111065 points

    Hi Riccardo,

    Good to know you're making progress on your project.

    ROM mode is the simplest configuration for TAS2563, in this mode you can use the features included at the "Device Control" panel within PPC3.
    Tuning mode includes all the features, including those in "Tuning and Audio Processing" panel, this is EQ, DRC, speaker protection, etc. in addition to those from "Device Control".

    From end system integration you get a variety of configuration files, for bare metal driver you may use the .h files from "headers" directory.
    I'll make sure to add here our driver experts to address any driver specific questions.

    Best regards,
    -Ivan Salazar
    Applications Engineer

  • 0 in reply to Ivan Salazar
    Prodigy 10 points

    I finally generated and integrated the COEFF file for my speaker. I integrated three files:
    -1 for config_0
    -1 for config_1_calibration
    and -1 for register init.
    At this point, I integrated them into the three different calls of the bare metal driver, and the quality has improved slightly. But now I have a question for you.
    The bare metal driver I downloaded from your portal configures and characterizes the output to the speaker, but beyond the speaker on and off functions, I haven't found any reference to adjusting the volume. Can you give me some guidance or a C function that allows me to adjust it? From the datasheet, it looks like there's an AD adjustment register to manage the output power level. Is that it?
    Because now I think I always have the volume at maximum, and that's why my speaker crackles constantly when it plays voices or sounds.

    Thank you for your valuable support.

  • 0 in reply to Riccardo Gennari
    TI__Guru** 111065 points

    Hi

    I'll review your inputs and get back to you next week

    Best regards,
    -Ivan Salazar
    Applications Engineer

  • 0 in reply to Riccardo Gennari
    Prodigy 10 points 
    I'm also trying to find a workaround that allows me to configure the volume management registers for both DVC_RAMP and the AMP_LEVEL register.
AMP_LEVEL is listed in the documentation and corresponds to page 0 register 3.
But why can't I find the DVC_RAMP register? Can you help me with this issue?
  • 0 in reply to Riccardo Gennari
    TI__Guru** 111065 points

    You can refer to DVC_PCM registers for volume control: (+) [FAQ] TAS2563: Adjusting Digital Volume Control using I2C - Audio forum - Audio - TI E2E support forums

    It is recommended to keep AMP_LEVEL fixed after initialization, use only DVC_PCM for volume changes on the fly.

    Best regards,
    -Ivan Salazar
    Applications Engineer

  • 0 in reply to Ivan Salazar
    Prodigy 10 points


    From the bare metal driver downloaded from your portal, I don't see any way to access book 0 and page 2. Can you provide an example in C language? To write the individual registers, I use the function:
    tas256x_dev_write(pTAS256X, 0x00, 0x03, (level<<1)); for example. Is this correct?

    The address 0x0C for DVC_PCM isn't listed in the document's datasheet, right?
    Can I read and write that register without having to unlock it first? From testing with my speaker and the PurePath Console, I've learned that if I don't adjust the input gain (Digital Gain input), my speaker produces distorted sound. Will adjusting DVC_PCM be enough for this? Can you confirm this?

  • 0 in reply to Ivan Salazar
    Prodigy 10 points

    After several attempts, I was able to set and read registers 0x0c on page 2 of book 0.
    It wasn't easy, and now my device works as it should, but I have a question about PurePath console 3.
    It produces TuningMode.h files, which should contain everything set in the configuration section, right?
    That is, speaker impedance, impedances, etc.
    But how come I generated the ppc3 file attached here with a gain level of -13dB, and I don't find this setting in the register array in the TuningMode.h file? I'm attaching both the ppc3 and the files generated using the procedure.

    .File Attached

    And again, is there a way to work with mono files or is it necessary to work with stereo files? We saw that the ppc3 console does not accept mono files. Does the I2S we need to supply to the TAS2563's TDM input also have to be stereo? This is because on embedded systems like ours, this means having audio files that are double the size despite having only one speaker.

    Thank you for your support.

  • 0 in reply to Riccardo Gennari
    TI__Guru** 111065 points

    When using EVM, you can use Windows media player or other audio software to play, just select the EVM as your default playback device.

    Registers at other pages are not included in data sheet, usually these are only handled by PPC3, but we'll review and get more registers added in the next revision.

    TAS2563 has a stereo DAC which takes 2 slots of audio data configured by RX_SLOT_R and RX_SLOT_L in page 0 register 0x09. Either of these slots can then be selected or mixed together based on the setting of RX_SCFG in page 0 register 0x08.

    Your data stream to TAS2563 must be at least 2 channels, even if playing mono files in which case one of the channels would be 0's.

    If you have incorrect audio, you may also check RX_OFFSET and RX_EDGE at page 0 register 0x07 are properly set to match your audio source.

    Is it possible to share the configuration files attached directly to the forum? I can't reach online sharing platforms.

    Best regards,
    -Ivan Salazar
    Applications Engineer

  • 0 in reply to Riccardo Gennari
    Prodigy 10 points

    Here are my files. The gain level is the default one, rather than the one I set. The forum won't let me upload the basic ppc3 file for my work.  So, as I was saying, it's not possible to send a mono track to the device, but only stereo tracks with one of the two channels filled with zeros, which however increase the size of the track I have to store in memory. Is this correct, unfortunately?

  • 0 in reply to Riccardo Gennari
    TI__Guru** 111065 points
    Riccardo Gennari said:
    only stereo tracks with one of the two channels filled with zeros, which however increase the size of the track I have to store in memory. Is this correct, unfortunately?

    That is correct.

    The DVC_PCM registers are controlled by the "Volume Control" in "Device Control" panel.

    Perhaps you're actually using the tuning volume control in "Tuning and Audio Processing" panel?

    Best regards,
    -Ivan Salazar
    Applications Engineer