Binho Customer Support
  • Customer Support Portal
  • User Guide
    • Binho Nova
    • Binho Supernova
    • Hardware Comparison Table
    • Safety Notice
    • Compliance & Legal
    • System Requirements
    • Updating Firmware
    • Protocols and Interfaces
      • I3C Common Command Codes
      • Bridge 1.1 API
        • Bridge 1.1 API - Basic I3C Commands
        • Bridge 1.1 API - I3C Common Command Codes
        • Bridge 1.1 API - I2C Commands
        • Bridge 1.1 API - SPI Commands
        • Bridge 1.1 API - UART Commands
        • Bridge 1.1 API - GPIO Commands
  • Getting Started
    • Hardware Setup
      • Binho Nova
      • Binho Supernova
    • Binho Mission Control
      • Overview
      • Download & Installation
      • Interactive Tour
        • App Layout
        • Protocol Activation
        • Command Panel
        • Transaction Log View
      • Updating Binho Mission Control Software
      • Simulators
      • Communication Protocols
        • SPI
        • UART
        • I2C
        • I3C
        • 1-WIRE
        • GPIO
      • Settings
    • Python SDKs
      • SupernovaController
      • Nova SDK
    • C++ SDK
      • Installation
      • Environment Setup
      • Building the C++ SDK Library
      • Building a Project Using the SDK
      • Example Applications
      • Using the Library
    • Software Releases
  • Examples
    • SupernovaController
    • Other Examples
  • Troubleshooting
    • Solving USB Connection Issues on Linux
  • FAQ
    • What is a host adapter?
    • What protocols are supported?
    • Can multiple devices be used at the same time?
    • Where can I find the product datasheet?
    • Is there a GUI available?
    • Is the ADC calibrated?
    • Is the DAC calibrated?
  • Returns & Warranty
    • 90-Day Return Policy
    • 2-Year Warranty
  • Dropping Legacy Terminology
  • Contact Us
  • Orders & Shipping
    • Place an Order
    • Requesting a Quotation
    • Placing a Purchase Order
    • Shipping Policy
    • International Shipping
    • Tax Exemption
    • Discounts
    • Distributors
Powered by GitBook
On this page
  • I2C Terminology
  • SPI Terminology
  • 1-Wire Terminology
  • Why did we change our documentation?

Dropping Legacy Terminology

The Binho support portal and product documentation have been updated to replace legacy industry terms with modern terminology.

I2C Terminology

The usage of I2C Master/Slave terminology is considered obsolete. Master and Slave are now Controller and Peripheral.

Regrettably as of yet, there has been very little consensus within the industry as to which terms to adopt for devices on the I2C bus. We're involved in this conversation taking place and plan to update our documentation once the industry has settled on a set new terms.

SPI Terminology

The usage of SPI Master/Slave terminology is considered obsolete. Master and Slave are now Controller and Peripheral. As such, the usage of MOSI/MISO/SS for pin and signal names has been replaced with SDI/SDO/CS.

New Signal Names:

  • SDO - Serial Data Out. An output pin on a device where data is sent out to another SPI device.

  • SDI - Serial Data In. An input pin on a device where data is received from another SPI device.

  • CS - Chip Select. Activated by the controller to initiate communication with a given peripheral. Often drawn C̅S̅ to indicate active low but not required.

Deprecated Signal Names:

  • MOSI - Master Out Slave In

  • MISO - Master In Slave Out

  • SS - Slave Select

Unchanged Signal Names:

  • SCK - Serial Clock. The clock for the bus generated by the controller.

While many microcontroller and processor manufacturers lag behind, the SDI/SDO/CS terminology is already widely adopted by several large semiconductor companies and can be found extensively used in the datasheets for their new devices.

1-Wire Terminology

The usage of 1-Wire Master/Slave terminology is considered obsolete. Master and Slave now Host and Device.

Maxim Integrated has already been using the terms Host and Device in their documentation for a while, and regret that we did not make this change to our documentation earlier. Thankfully this means there should be little confusion as a result of this change in our documentation.

Why did we change our documentation?

Previous2-Year WarrantyNextContact Us

Last updated 10 months ago

The electronics industry in particular has been using an embarrassingly outdated lexicon when it comes to discussing communication bus topology and the various roles and modes of operation of devices on the bus. It's unfortunate that this has gone on this long without acknowledging the need to leave these terms in the past. Thankfully, the industry is already making the shift, and many device manufacturers have already begun to adopt new terminology. Binho is proud to help push for the that is inclusive. Let's celebrate the ability to change and improve over time!

industry-wide adoption of modern terminology