• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 34 subscribers
  • Views 199 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.

DS280MB810: Enabling of MUXSEL Pin Control via I2C Slave

Chris Davis
Prodigy 10 points
Part Number: DS280MB810

Tool/software:

Hi,

Our design uses two DS280MB810 devices with the need to use the MUXSEL pin control interface.

We are having difficulty enabling the pin control feature in SW.  We are able to successfully configure the MUX as desired using register 0x06, but we cannot enable pin control via register 0x05.

After reviewing the user guide and datasheet, it appears the MUX_CONFIG_PIN_CTRL register bit is READ ONLY?  We need to enable this feature, what steps are required to successfully configure this bit? 

Does it require the use of an external EEPROM?  The datasheet and programming guide make no mention of such a limitation, there must be a method to enable this via I2C slave.

Thanks,

Chris

  • 0
    Prodigy 10 points

    Schematic IO nets if interested - again, we are using I2C slave, there is no EEPROM connected, nor do we have the hooks to support one.

  • +1 in reply to Chris Davis
    TI__Mastermind 36793 points

    Hi Chris,

    Thanks for sharing details on this issue you're observing and for sharing your schematic.

    I have a couple thoughts on this issue:

    • MUX_CONFIG_PIN_CTRL is not read only, this is an error in our programming guide.  It is actually not possible to enable MUX pin control on this device with just EEPROM since this bit is not included in EEPROM (EEPROM = N).
    • From programming guide: "Note that shared register 0x05[1] of both quads must be set to 1 to enable pin-control crosspoint mode. Each quad can be selected through Reg_0xFF[5:4]"  Can you confirm that you're setting MUX_CONFIG_PIN_ CTRL = 1 in both quads?
    • Can you share your configuration sequence?

    Thanks,

    Drew

  • 0 in reply to Drew Miller1
    Prodigy 10 points

    Drew,

    Thanks for the reply - good to know we don't need the EEPROM and this is simply a configuration/setup issue.  Let me sync with SW to try again, we must be missing a config setting.

    Thanks again,

    Chris

  • 0 in reply to Chris Davis
    TI__Mastermind 36793 points

    Hi Chris,

    Thanks for the update.  Let us know if you need additional support.  We'd be interested to hear the resolution to the issue if you identify it.

    Thanks,

    Drew

  • 0 in reply to Drew Miller1
    Prodigy 10 points

    Drew - we got it working successfully via I2C writes. Just a config/SW issue.  All good now - thanks.

    Quick follow up question. We have a second design on the go where only half the redriver is used (CH0-CH3).  The datasheet states: By default, each channel’s output
    is muted and the channel is powered down when there is no signal present at the input.  If we were to re-use the SW configuration where all 8 channels are used on the design where only 4 channels are used (the unused nets are unconnected), we shouldn't have to manually power down the unused channels as they unconnected, correct?

  • 0 in reply to Chris Davis
    TI__Mastermind 20901 points

    Hi Chris,

    I'm glad to hear that you were able to successfully enable MUXSEL through I2C mode.

    Its a bit difficult to say based on the details shared in this thread (I'm not sure if you've shared your SW configuration with Drew directly). By default, the lack of any input signal will signal the device to automatically put the unused channels into a muted condition.

    Please let Drew and I confirm tomorrow on this item and get back to you. If you have any further details on your SW configuration for the DS280MB810, this would be helpful as well.

    Best,
    David