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.

TAS2563: Register settings for 48kHz 24 bits - mono out, 2x stereo in (PDM)

Part Number: TAS2563
Other Parts Discussed in Thread: TAS2X63EVM

Hello,

we finally managed to integrate the driver (https://git.ti.com/cgit/tas2781-linux-drivers/tas2781-linux-driver/tree/) to our system including DSP settings from PPC3. Would you please provide us the .json file with the correct settings for the reg-bin tool as promised? Required settings:

i2s, 48kHz, 32 bits and 2x PDM mic. (3 MHz) including the rx reference (as you mentioned: slot 0 mic 1, slot 1 mic 2, slot 3 rx echo reference in 16 bits).

IC: TAS2563-QFN

Kind regards,

Christian (by proxy)

  • Hi Christian

    Long time no hear from your information. I will confirm with you following information.

    How many pieces of tas2563 on your system, one or two?

    As to rx reference, does it mean the signals from TX channel?

    As to dsp firmware, would you make it from PPC3 tool special for tas2563qfn? In that tool, have you selected PDM recording to make the bin file?

    One more important thing, have tas2563 can playback in your system in bypass mode, that means it can playback with only regbin file, without dsp fw?

    PDM recording need the correct dsp fw with pdm feature.

    I have involved our tas2563 expert together with me to support you.

    Looking forward to your feedback.

    BR

    Shenghao Ding

  • Hello Shenghao Ding,

    we have one tas2563 in our system (2x stereo was a mistake - we connect 2 PDM microphones to the device).

    I'm not totally sure of the RX reference - you mentioned it earlier and it seems to be required as an echo reference somehow. We require the TX signals of the PDM mircophones and maybe later some echo reference (for feedback suppression?) - what's your experience regarding that topic?

    Yes, we make the dsp firmware from PPC3 tool special for tas2563qfn. We activated the PDM mics with 3 MHz, and, of course, the setting to generally use PDM mics. We also set the TDM Transmitter settings to PDM Mic1 slot 0,1,2 and PDM Mic 2 slot 4,5,6 and the Mics work in Windows using the TAS2x63EVM board, the PPC3 software/drivers and Audacity.

    We have not tried if the playback is possible without the dsp firmware. Our current setting is using the dsp bin from PPC3 and the reg bin with the default settings from the driver (tas2563-1amp-reg.json). The bin files are in the /bin/firmware/ folder on the linux device. With this setup, playback works on the linux device. We did not try it with reg-bin file, but without the dsp-bin file - is that step important?

    Kind regards, 

    Christian

  • Hi Christian,

    If I understand correctly, you're able to create the device configuration files using PPC3, which you're already tested, and playback is working OK. Is that correct?

    You mentioned you're using EVM with PDM mics which also seems to work OK. Is this same PPC3 you're using to generate the configuration files?
    If so, when using the PPC3 config files on your system, and audio playback is OK, have you verified that PDMCK is coming out and it's the correct frequency?

    I can help with further details on how to generate the configuration files, just trying to understand what's the current status of the system implementation.

    Best regards,
    -Ivan Salazar
    Applications Engineer

  • Hello Ivan Salazar,

    yes, playback is working both on Windows PPC3 / Windows Drivers and the Linux system with the configuration file (tas2563-1amp-dsp.bin created with PPC3) - with 48kHz (24 Bits on Windows)

    Our PDM mics connected to the EVM are working too in Windows with the same PPC3 configuration with the correct PDMCK frequency. But on the Linux device connected to the same setup (EVN with external I2C and I2S i/o), the PDMCK does not come (from SW side, the driver seems to be set up correctly - arecord is working, but recording an empty file of course).

    If I've understood correctly, a correct tas2563-1amp-reg.bin file is required to set up the registers for enabling the PDM mics - is that correct? I already know the workflow of the reg-bin tool. Would you provide a .json file with the correct settings, or is it possible to create one with the PPC3 tool?

    Kind regards,

    Christian

  • Hi Herbert,

    .json files can't be created with PPC3. Unfortunately Ivan is out of office until Monday. Early next week he'll work with Shenghao to get you a .json file.

    Thank you for your patience,
    Jeff McPherson

  • Hi Herbert,

    Only Regbin tool need json file. PPC3 tool need ppc file. As far as I know, the latest PPC3 can set TX and RX in dsp bin file(you can set a new config for slot 0 mic 1, slot 1 mic 2, slot 3 rx echo reference in 16 bits in PPC3, for example, config 4, and generate the dsp bin file), so tas2563-1amp-reg.bin only set Book0page0reg2( poweron to 0x0, poweroff to 0xe, for example it is in profile id-8). Before recording, you can run following commands:

    tinymix set "Program" 0

    tinymix set "Configuration" 4

    tinymix set "TASDEVICE Profile id" 8

    arecord -t raw -c4 -fS16_LE -r48000 -v /usr/local/test.raw&
  • Hello,

    thank you for your explanation - I think I've got an idea of how the configuration process works somehow. Looking forward to a basic .json configuration file.

    Kind regards,

    Christian

  • Hi Christian

    New profile for pdm mic recording has been added into tas2563-1amp-reg.json(regbin « jsn - tas2781-linux-drivers/tas2781-linux-driver - Unnamed repository; edit this file 'description' to name the repository.)

    b0p0r0xc = 0x40 /*mic1 data set to channel 0*/

    b0p0r0xb = 0x42 /* mic 2 data to channel 1*/

    b0p0r0xd = 0x44 /* ref data to channel 2*/

    b0p0r0x41 = 0x06 /* set pdm clk 3.072MHz, enable both pdm mic*/

    b0p0r0x42 = 0x18 /* enable pull down*/

  • Thank you for your reply - we will test the settings next week.

    Kind regards, Christian

  • Looking forward to your feedback.