• State Resolved
  • Locked Locked
  • Replies 14 replies
  • Subscribers 32 subscribers
  • Views 1372 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.

Enable/disable DRC in PurePath Studio

Michel Dell'Oca
Prodigy 250 points

Other Parts Discussed in Thread: TAS3204

Hi,

I want to enable and bypass the DRC module like described in the help-file in th ePurePath Studio. It's written:

I2CAddress6 DspCoefBlockStart4 8 bytes DRC Enable/Disable 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x01 (Enable)

But when I send this, all the Output become disabled. I have to power off/on the device.

I also tried to disable(bypass) the DRC by sending 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 with the same effect.

Do I send something wrong? I know that I can send some coefficients that the DRC has no effect, but I want to try it the other way. I use a TAS3204.

Can someone explain it?

Thanks, Michael

 

 

 

  • 0
    TI__Mastermind 18320 points

    Michael,

    This questions seems to be specific to audio, not the BIOS RTOS.  I am going to move this thread to a different forum in hopes that you'll get a faster response there.

  • 0
    TI__Expert 3215 points

    Michael,

    If you want to enable/disable DRC, the simplest way would be to click on the component and view the properties window for this component.  In the run-time parameter list, you could toggle DRCEnable between bypass and inline.

    Let me know if this didn't work and we could figure out why.

    Susan

  • 0 in reply to susan xu
    Prodigy 250 points

    Susan,

    When I click the DRCEnable field in Runtime Properties, all that changes is Bypass / Inline. But what I need is the code which I must send through I2C to enable/disable it during runtime. It's described in the Help-window, but it doesn't work.

    Michael

  • 0 in reply to Michel Dell'Oca
    TI__Expert 3215 points

    Michael,

    When the GDE is connected to the target and running, changing the DRCEnable field will send the correponding I2C command to the DAP.

    Please describe in details how it didn't work for you?  When you toggle the field, the DRC doesn't seem to be enabled/disabled?  What board are you using, your board or our EVM?

    Susan

  • 0 in reply to susan xu
    Prodigy 250 points

    Susan

    First, I dont have the EVM, that's why I cant change the field during runtime...

    I work with my own board, and the command which is described in the help has a wrong effect. It disables the output instead of a bypass (I cant even enable it without a reset). Maybe I have to send an other command?

    Michael

  • 0 in reply to Michel Dell'Oca
    TI__Expert 3215 points

    Michael,

    Let me try to understand the situation: you can't connect the PPS with you board, but you could send I2C command using other tools?  Frankly, I've never done this before manually, but it should work. 

    First, you need to find out the I2C subaddress assigned for DRCEnable parameter.  When you build your .pfw using PPS, it's assigned by the tool, or you could manually change it.  Go to tools->I2C overview to find out. for example it's 0x32, then send 0x32 0x00 0x80 0x00 0x00 0x00 0x00 0x00 0x00 to enable and all 0's to disable.

    When you look at the I2C overview window, 0x00 I2C subaddress is reserved for clock and SAP control, no wonder it can crush your board when you send so many 0s to it.

    BTW, what tool do you use to send I2C command?

    Susan

  • 0 in reply to susan xu
    Prodigy 250 points

    Susan

    I have my own application board with the TAS and a microcontroller which controls the TAS through I2C. I can send a command to the microcontroler, it converts it to I2C and sends it to the TAS. I think thats "normal" usage.

    I know this part with the subaddress, my address for I2C interface 6 (DRC enable/disable) is 0x3C (see my first posting).

    You wrote, I have to send 0x00 0x80 0x00 0x00 0x00 0x00 0x00 0x00 to the address of the DRC to enable it, but in the help file it is 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x01.

    But when I send all 0x00, the output disables, but I can now reactive it by sending 0x00 0x80 0x00 ..... My communication seems to be ok, since I can change all fader and filter types.

    Maybe I'm wrong, but I dont think all 0s is the right command to bypass the DRC.

    If you have an EVM, please check the command for bypass the DRC.

    Michael

  • 0 in reply to Michel Dell'Oca
    TI__Expert 3215 points

    Michael,

    You're right, that's not the right value to bypass, I looked into the source code.

    try sending 0x00 0x00 0x00 0x00 0x00 0x80 0x00 0x00  to disable it.

    Susan

  • 0 in reply to susan xu
    Prodigy 250 points

    Susan,

    Thank you, that's what I have wanted. Please change the help-file too.

    Michael

  • 0 in reply to Michel Dell'Oca
    TI__Expert 3215 points

    Michael,

    I checked the help file of DRC in our latest release 1.88b5, it has the correct value in the table.  You must have got an older version.

    Please update your PPS to the latest when possible.

    Susan

  • 0 in reply to susan xu
    Prodigy 250 points

    Susan,

    I checked it and I have version 1.88b5, too (release date 25. jan. 2011):

    This is in the help file:

    I2C Sub-Address DSP Memory Address Size Description
    I2CAddress1 DspCoefBlockStart1 8 bytes Energy Calculation Window Parameters ae, 1-ae
    I2CAddress2 DspDataBlockStart1 16 bytes Theshold Boundary Regions T1, T2
    I2CAddress3 DspCoefBlockStart2 12 bytes Region Slope Paramters: k0, k1, and k2
    I2CAddress4 DspDataBlockStart2 16 bytes Boundary 1 Offset (O1) and Boundary 2 Offset (O2)
    I2CAddress5 DspCoefBlockStart3 16 bytes Attack Time Parameters:  aa, 1-aa,
    Decay Time Parameters: ad, 1-ad
    I2CAddress6 DspCoefBlockStart4 8 bytes DRC Enable/Disable
    Default Value
    0x 00 0x00 0x00 0xBE, 0x00 0x7F 0xFF 0x41
    0x00 0x00 0x00 0x00 0x08 0x8B 0x4A 0x08, 0x00 0x00 0x00 0x00 0x08 0xCB 0xF2 0x38
    0x00 0x00 0x00 0x00, 0x0F 0xC0 0x00 0x00, 0x0F 0x90 0x00 0x00
    0x00 0x00 0x00 0x00 0x01 0x33 0x35 0xF0, 0x00 0x00 0x00 0x00 0x01 0x95 0xB2 0xBD
    0x00 0x00 0x02 0xFB, 0x 00 0x7F 0xFD 0x07,
    0x00 0x00 0x00 0x5F, 0x00 0x7F 0xFF 0xA0
    0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x01 (Enable)

    Please tell me, where I can download a newer version.

    Michael

  • 0 in reply to Michel Dell'Oca
    TI__Expert 3215 points

    Michael,

    Sorry for the late reply, just came back from vacation.

    I just checked the help file of all three DRC components, since I don't know which one you used, but they all have the correct numbers.  It is really odd that you don't have the correct help file.

    Could that be that you didn't uninstall the old version of PPS which you install the PPS 1.88 b5?  Also, if you try to clear the cache, then reopen PPS GDE, can that make any difference?

    Susan

  • 0 in reply to Michel Dell'Oca
    TI__Expert 3215 points

    Michael,

    Sorry for the late reply, just came back from vacation.

    I just checked the help file of all three DRC components, since I don't know which one you used, but they all have the correct numbers.  It is really odd that you don't have the correct help file.

    Could that be that you didn't uninstall the old version of PPS when you install the PPS 1.88 b5?  Also, if you try to clear the cache, then reopen PPS GDE, can that make any difference?

    Susan

  • 0 in reply to susan xu
    Prodigy 250 points

    Susan,

    It's a bit strange. I'm sure I installed the latest version and there was no older version installed before. But a collegue installed the same PurePath software and he has the right help file. Looks that there is something wrong with my software, i'll re-install it.

    Thank you very much

    Michael