This article has multiple issues. Please helpimprove it or discuss these issues on thetalk page.(Learn how and when to remove these messages) This articleneeds additional or more specificcategories. Pleasehelp out byadding categories to it so that it can be listed with similar articles.(June 2025) This articleneeds additional citations forverification. Please helpimprove this article byadding citations to reliable sources. Unsourced material may be challenged and removed. Find sources: "UNI/O" – news ·newspapers ·books ·scholar ·JSTOR(October 2009) (Learn how and when to remove this message) (Learn how and when to remove this message)

TheUNI/O bus/ˌjuːniˈoʊ/ is anasynchronousserialbus created byMicrochip Technology for low speed communication inembedded systems.^[1] The bus uses amaster/slave configuration, requiring onesignal to passdata between devices. The first devices supporting the UNI/O bus were released in May 2008.

The UNI/O bus requires one logic signal:

• SCIO — Serial Clock, Data Input/Output^[2]

Only one master device is allowed per bus, but multiple slave devices can be connected to a single UNI/O bus. Individual slaves are selected through an 8-bit to 12-bit address included in thecommand overhead.

Both master and slave devices use atri-stateable,push-pullI/O pin to connect to SCIO, with the pin being placed in ahigh impedance state when not driving the bus. Because push-pull outputs are used, the output driver on slave devices iscurrent-limited to prevent high systemcurrents from occurring during bus collisions.

The idle state of the UNI/O bus islogic high. A pull-up resistor can be used to ensure the bus remains idle when no device is driving SCIO, but is not required for operation.^[3]

Clock and data signals are combined and communicated on the bus throughManchester encoding. This means that eachdata bit is transmitted in a fixed amount of time (called the "bit period").

The UNI/O specification places certain rules on the bit period:

• It is determined by the master.
  • Slaves are required tosynchronize with the master torecover the bit period during thestart header.
• It can be within10 μs and 100 μs (corresponding to abit rate of 100 kbit/s to 10 kbit/s, respectively).
• It is only required to be fixed within a single bus operation (for new bus operations, the master can choose a different bit period).

In accordance with Manchester encoding, the bit value is defined by a signal transition in the middle of the bit period. UNI/O uses theIEEE 802.3 convention for defining0 and1 values:

• Ahigh-to-low transition signifies a0.
• Alow-to-high transition signifies a1.

Bit periods occur back-to-back, with no delay between bit periods allowed.

UNI/O uses 8-bitdata words for communication. Bytes are transmittedmsb first.

To facilitateerror detection, a 2-bit wide "acknowledge sequence" is appended to the end of every data byte transmitted. The first bit is called the "master acknowledge" (shortened to "MAK") and is always generated by the master. The second bit, called the "slave acknowledge" (shortened to "SAK"), is always generated by the slave.

The MAK bit is used in the following manner:

• The master transmits a1 bit (aMAK) to indicate to the slave that the bus operation will be continued.
• The master transmits a0 bit (aNoMAK) to indicate that the preceding byte was the last byte for that bus operation.

The SAK bit is used in the following manner:

• Once a full device address has been transmitted (and a valid slave has been selected), if the previous data byte and subsequent MAK bit were received correctly, the slave transmits a1 bit (aSAK).
• If an error occurs, the slave automatically shuts down and ignores further communication until a standby pulse is received. In this scenario, nothing will be transmitted during the SAK bit period. This missing transition can be detected by the master and is considered aNoSAK bit.

UNI/O defines a signal pulse, called the "standby pulse", that can be generated by the master to force slave devices into a reset state (referred to as "standby mode"). To generate a standby pulse, the master must drive the bus to a logic high for a minimum of 600 μs.

A standby pulse is required to be generated under certain conditions:

• Before initiating a command when selecting a new device (including after aPOR/BOR event)
• After an error is detected

If a command is completed without error, a new command to the same device can be initiated without generating a standby pulse.

The start header is a special byte sequence defined by the UNI/O specification, and is used to initiate a new command. The start header consists of the following elements:

• The master drives the bus low for a minimum of 5 μs.
• The master outputs a0x55 data byte.
  • Slave devices measure the time necessary to receive the0x55 byte by counting signal transitions. This time is then used by the slaves to determine the bit period and synchronize with the master.
• The master outputs a1 for the MAK bit.
• The slave devicesdo not respond during the SAK bit following the start header. This is to avoid bus collisions which would occur of all slave devices tried to respond at the same time.

After the start header has been transmitted, the master must transmit a device address to select the desired slave device for the current operation. Once the device address has been sent, any slave device with an address different from that specified is required to shut down and ignore all further communication until a standby pulse is received.

UNI/O allows for both 8-bit and 12-bit device addresses. 8-bit addressing offers better data throughput due to less command overhead, while 12-bit addressing allows for more slaves with a common family code to exist on a single bus. When a slave device is designed, the designer must choose which addressing scheme to use.

For 8-bit addressing, the entire device address is transmitted in a single byte. The most significant 4 bits indicate the "family code", which is defined by Microchip in the UNI/O bus specification. The least significant 4 bits indicate the device code. The device code allows multiple slave devices with a common family code to be used on the same bus. The device code can be fixed for a given slave or customizable by the user. Choosing a device code and how it can be customized (if necessary) are the responsibilities of the slave device designer.

The current family codes for 8-bit devices, as of November 22, 2009,^[1] are as follows:

For 12-bit addressing, the device address is sent in two bytes. The most significant 4 bits of the first byte (which would correspond to the family code in 8-bit addressing), are set to ′1111′. The next 4 bits are the family code for the 12-bit address, and the second byte of the address is an 8-bit wide device code. The device code follows the same guidelines for definition as with 8-bit addressing.

Because the specified slave device is not selected until both bytes of the device address have been received, a NoSAK will occur during the acknowledge sequence following the first device address byte.

The current family codes for 12-bit devices, as of November 22, 2009,^[1] are as follows:

After the master has transmitted the device address and selected an individual slave, the master must transmit the 8-bit value for the specific command to be executed by the slave. The available commands are determined by the designer of each slave device, and will vary from slave to slave, e.g. a serial EEPROM will likely have different commands than a temperature sensor. The slave device designer will also determine if and how many data bytes are necessary for the execution of a command. If any data bytes are necessary, they are transmitted by either the master or the slave (dictated by the command type) after the command byte.

Communication will continue until either the master transmits a0 (NoMAK) during the acknowledge sequence, or an error occurs. Assuming no errors occur, this means that commands can continue indefinitely if the master chooses.

Some UNI/O Parts can be powered from the bus, eliminating the need for a dedicated supply voltage/wire.^[4][5][6]

• UNI/O Bus Specification - Microchip

• Serial buses
• Microchip Technology hardware
• Embedded systems
• Data transmission

• Articles with short description
• Short description matches Wikidata
• Articles needing additional categories from June 2025
• Articles needing additional references from October 2009
• All articles needing additional references
• Articles with multiple maintenance issues