• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 35 subscribers
  • Views 306 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.

General - coding of digital signals

May
Genius 9880 points

Hi Team,

Good day, we received inquiry from customer and want to confirm regarding the theoretical coding of digital signal. 

"

According to customer there are many coding schemes (e.g. PAM-5 for 1000BASE-T Ethernet; Biphase-Mark-Code for S/PDIF; 8b/10b for HDMI & DVI; 128b/130b for PCI Express 5.0; 8b/10b for SATA). They wonder why some standards do specify the coding while I²C doesn't. Document SLVA704 elaborate about the standard.

"

Thank you and looking forward for your kind response.

Regards,

Maynard

  • 0
    TI__Mastermind 45206 points

    Hi Maynard,

    The I2C standard is defined and managed by NXP Semiconductors (previously Philips Semiconductor). I2C modules in TI devices are designed to meet those defined specifications.

    Not certain if that answers your question. If not, please further explain the question.

    Best,

    Kevin

  • 0
    Guru 316940 points

    The I²C coding scheme is specified in section 3.1 of the specification. It could be described as "at the rising clock edge, high voltage = 1, low voltage = 0". This is so simple that it does not have a fancy name.

    (All the coding schemes mentioned above embed the clock into the signal. I²C uses a separate clock line.)

  • 0 in reply to Kevin Allen18
    TI__Genius 9880 points

    Hi Team,

    According to customer, they used the I²C-bus just as an example to an interface where the coding scheme is not specified.

    This is as opposed to other interfaces where the coding scheme is specified: e.g. 4B5B MLT-3 (100BASE-TX Ethernet).

    And the question is why?

    Regards,

    Maynard

  • 0 in reply to May
    TI__Mastermind 29111 points

    Maynard,

    Every interface is designed to serve a specific purpose. Hence every interface will be specified differently. I would encourage the customer to refer to existing academic literature on any interface they want to learn more about. A web search should yield plenty of literature on any specific interface.

    In order to further assist you, can you please clarify if there is a question regarding a specific TI product?

  • 0 in reply to May
    Guru 316940 points

    The I²C specification itself defines its own coding standard.

    Writing it as "I²C (I²C)" would be silly.