[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

US20160034416A1 - Peripheral device diagnostics and control over a two-wire communication bus - Google Patents

Peripheral device diagnostics and control over a two-wire communication bus Download PDF

Info

Publication number
US20160034416A1
US20160034416A1 US14/884,987 US201514884987A US2016034416A1 US 20160034416 A1 US20160034416 A1 US 20160034416A1 US 201514884987 A US201514884987 A US 201514884987A US 2016034416 A1 US2016034416 A1 US 2016034416A1
Authority
US
United States
Prior art keywords
audio
data
slave
node
slave node
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
US14/884,987
Other versions
US9946680B2 (en
Inventor
Miguel Chavez
Martin Kessler
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Analog Devices Inc
Original Assignee
Analog Devices Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US13/646,397 external-priority patent/US9417944B2/en
Priority claimed from US14/063,886 external-priority patent/US9448959B2/en
Application filed by Analog Devices Inc filed Critical Analog Devices Inc
Priority to US14/884,987 priority Critical patent/US9946680B2/en
Assigned to ANALOG DEVICES, INC. reassignment ANALOG DEVICES, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: CHAVEZ, MIGUEL, KESSLER, MARTIN
Publication of US20160034416A1 publication Critical patent/US20160034416A1/en
Application granted granted Critical
Publication of US9946680B2 publication Critical patent/US9946680B2/en
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38Information transfer, e.g. on bus
    • G06F13/42Bus transfer protocol, e.g. handshake; Synchronisation
    • G06F13/4247Bus transfer protocol, e.g. handshake; Synchronisation on a daisy chain bus
    • G06F13/426Bus transfer protocol, e.g. handshake; Synchronisation on a daisy chain bus using an embedded synchronisation, e.g. Firewire bus, Fibre Channel bus, SSA bus
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40Bus networks
    • H04L12/40169Flexible bus arrangements
    • H04L12/40176Flexible bus arrangements involving redundancy
    • H04L12/40182Flexible bus arrangements involving redundancy by using a plurality of communication lines
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38Information transfer, e.g. on bus
    • G06F13/42Bus transfer protocol, e.g. handshake; Synchronisation
    • G06F13/4282Bus transfer protocol, e.g. handshake; Synchronisation on a serial bus, e.g. I2C bus, SPI bus
    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00Programme-control systems
    • G05B19/02Programme-control systems electric
    • G05B19/04Programme control other than numerical control, i.e. in sequence controllers or logic controllers
    • G05B19/042Programme control other than numerical control, i.e. in sequence controllers or logic controllers using digital processors
    • G05B19/0421Multiprocessor system
    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00Programme-control systems
    • G05B19/02Programme-control systems electric
    • G05B19/04Programme control other than numerical control, i.e. in sequence controllers or logic controllers
    • G05B19/042Programme control other than numerical control, i.e. in sequence controllers or logic controllers using digital processors
    • G05B19/0423Input/output
    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00Programme-control systems
    • G05B19/02Programme-control systems electric
    • G05B19/418Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM]
    • G05B19/4185Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM] characterised by the network communication
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/26Power supply means, e.g. regulation thereof
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/26Power supply means, e.g. regulation thereof
    • G06F1/266Arrangements to supply power to external peripherals either directly from the computer or under computer control, e.g. supply of power through the communication port, computer controlled power-strips
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/14Handling requests for interconnection or transfer
    • G06F13/36Handling requests for interconnection or transfer for access to common bus or bus system
    • G06F13/362Handling requests for interconnection or transfer for access to common bus or bus system with centralised access control
    • G06F13/364Handling requests for interconnection or transfer for access to common bus or bus system with centralised access control using independent requests or grants, e.g. using separated request and grant lines
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38Information transfer, e.g. on bus
    • G06F13/42Bus transfer protocol, e.g. handshake; Synchronisation
    • G06F13/4282Bus transfer protocol, e.g. handshake; Synchronisation on a serial bus, e.g. I2C bus, SPI bus
    • G06F13/4291Bus transfer protocol, e.g. handshake; Synchronisation on a serial bus, e.g. I2C bus, SPI bus using a clocked protocol
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38Information transfer, e.g. on bus
    • G06F13/42Bus transfer protocol, e.g. handshake; Synchronisation
    • G06F13/4282Bus transfer protocol, e.g. handshake; Synchronisation on a serial bus, e.g. I2C bus, SPI bus
    • G06F13/4295Bus transfer protocol, e.g. handshake; Synchronisation on a serial bus, e.g. I2C bus, SPI bus using an embedded synchronisation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04BTRANSMISSION
    • H04B3/00Line transmission systems
    • H04B3/54Systems for transmission via power distribution lines
    • H04B3/542Systems for transmission via power distribution lines the information being in digital form
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04BTRANSMISSION
    • H04B3/00Line transmission systems
    • H04B3/54Systems for transmission via power distribution lines
    • H04B3/548Systems for transmission via power distribution lines the power on the line being DC
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40Bus networks
    • H04L12/40006Architecture of a communication node
    • H04L12/40019Details regarding a bus master
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40Bus networks
    • H04L12/40006Architecture of a communication node
    • H04L12/40045Details regarding the feeding of energy to the node from the bus
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40Bus networks
    • H04L12/403Bus networks with centralised control, e.g. polling
    • H04L12/4035Bus networks with centralised control, e.g. polling in which slots of a TDMA packet structure are assigned based on a contention resolution carried out at a master unit
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04RLOUDSPEAKERS, MICROPHONES, GRAMOPHONE PICK-UPS OR LIKE ACOUSTIC ELECTROMECHANICAL TRANSDUCERS; DEAF-AID SETS; PUBLIC ADDRESS SYSTEMS
    • H04R29/00Monitoring arrangements; Testing arrangements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04BTRANSMISSION
    • H04B2203/00Indexing scheme relating to line transmission systems
    • H04B2203/54Aspects of powerline communications not already covered by H04B3/54 and its subgroups
    • H04B2203/5462Systems for power line communications
    • H04B2203/547Systems for power line communications via DC power distribution
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04RLOUDSPEAKERS, MICROPHONES, GRAMOPHONE PICK-UPS OR LIKE ACOUSTIC ELECTROMECHANICAL TRANSDUCERS; DEAF-AID SETS; PUBLIC ADDRESS SYSTEMS
    • H04R29/00Monitoring arrangements; Testing arrangements
    • H04R29/007Monitoring arrangements; Testing arrangements for public address systems
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00Energy efficient computing, e.g. low power processors, power management or thermal management

Definitions

  • the present disclosure relates generally to communication systems and, more particularly, to peripheral device diagnostics and control over a two-wire communication bus.
  • the communication infrastructure used to exchange signals between these components has required thick and heavy bundles of cables.
  • FIG. 1 is a block diagram of an illustrative two-wire communication system, in accordance with various embodiments.
  • FIG. 2 is a block diagram of a node transceiver that may be included in a node of the system of FIG. 1 , in accordance with various embodiments.
  • FIG. 3 is a diagram of a portion of a synchronization control frame used for communication in the system of FIG. 1 , in accordance with various embodiments.
  • FIG. 4 is a diagram of a superframe used for communication in the system of FIG. 1 , in accordance with various embodiments.
  • FIG. 5 illustrates example formats for a synchronization control frame in different modes of operation of the system of FIG. 1 , in accordance with various embodiments.
  • FIG. 6 illustrates example formats for a synchronization response frame at different modes of operation of the system of FIG. 1 , in accordance with various embodiments.
  • FIG. 7 is a block diagram of various components of the bus protocol circuitry of FIG. 2 , in accordance with various embodiments.
  • FIGS. 8-11 illustrate examples of information exchange along a two-wire bus, in accordance with various embodiments of the bus protocols described herein.
  • FIG. 12 illustrates a ring topology for the two-wire bus and a uni-directional communication scheme thereon, in accordance with various embodiments.
  • FIG. 13 schematically illustrates a device that may serve as a node or host in the system of FIG. 1 , in accordance with various embodiments.
  • FIG. 14 is a block diagram of an example arrangement of audio components and sensors in a two-wire communication system, in accordance with various embodiments.
  • FIG. 15 is a block diagram of a particular example of the arrangement of FIG. 14 , in accordance with various embodiments.
  • FIG. 16 is a block diagram of a distributed amplifier embodiment of an example slave node, and its associated peripheral device, from the arrangement of FIG. 15 , in accordance with various embodiments.
  • FIG. 17 is a flow diagram of a method for communication of audio system diagnostic information by a slave node, in accordance with various embodiments.
  • FIG. 18 is a flow diagram of a method for communication of audio system diagnostic information and control by a host, in accordance with various embodiments.
  • FIG. 19 is a flow diagram of a method for audio system control by a slave node, in accordance with various embodiments.
  • Various embodiments of the systems and techniques may enable low-latency fault detection and control of peripheral devices (e.g., audio devices) coupled to the slave nodes daisy-chained along a two-wire bus.
  • peripheral devices e.g., audio devices
  • Described herein are communications systems that provide low latency, time division multiplexed (TDM) communications over a two-wire bus (e.g., a twisted wire pair).
  • TDM time division multiplexed
  • bi-directional synchronous data e.g., digital audio
  • clock e.g., a twisted wire pair
  • synchronization signals may be provided by the two-wire bus, supporting direct point-to-point connections between nodes on the bus and allowing multiple, daisy chained nodes at different locations to contribute, use or consume TDM slot content.
  • These communication systems enable downstream traffic (e.g., from a master node to a last slave node), upstream traffic (e.g., to a master node from a slave node), and power transmission over the same two-wire bus.
  • downstream and/or upstream slots along the two-wire bus may be used to transmit diagnostic information, such as information about operational characteristics of the peripheral devices.
  • the downstream and/or upstream slots may be used for slave nodes to communicate directly with each other, and/or to provide information upstream to a host that the host can then distribute downstream to the slave nodes.
  • the diagnostic information can include any relevant operational characteristic of the audio devices or their environment.
  • an “operational characteristic” of a peripheral device may refer to a particular property of the peripheral device (e.g., a numerical value of that property or an indicator of a range into which that property falls) or a property of the environment around the peripheral device that may affect operation of the peripheral device (e.g., a numerical value of that property or an indicator of a range into which that property falls).
  • Examples of operational characteristics include voice coil temperature, overcurrent, over-excursion, die temperature of chips (e.g., to prevent over-heating in an amplifier or to correlate to ambient temperature), local battery conditions (e.g., voltage of a battery), impedance, resonance frequency, acoustic box leakage, and noise near the audio device.
  • this diagnostic information may be used to control the peripheral devices and/or the associated slave nodes, trigger different modes for driving the peripheral devices and/or the associated slave nodes, detect faults or problems at the peripheral devices and/or the associated slave nodes, provide feedback to a control system (e.g., at the host or at another location in a communication system) for driving the peripheral devices and/or the associated slave nodes, or provide feedback to other peripheral devices and/or the associated slave nodes.
  • a control system e.g., at the host or at another location in a communication system
  • the diagnostic and control systems and techniques disclosed herein may be used to distribute amplification of speakers in a communication system among different slave nodes, thus providing “distributed amplification.”
  • the diagnostic and control systems and techniques disclosed herein may be used to control speaker output across different slave nodes to cancel noise and thus improve an overall audio system.
  • the upstream and/or downstream slots of the two-wire communication systems disclosed herein may be advantageously used for transmitting any suitable state information about a peripheral device (e.g., relevant currents, voltages, temperatures, or other conditions sensed by a sensor coupled to a slave node) back to the host or one or more other slave nodes.
  • a peripheral device e.g., relevant currents, voltages, temperatures, or other conditions sensed by a sensor coupled to a slave node
  • This information may not only be used for diagnostics but may also be used for improving the performance of the peripheral devices taken as a whole (e.g., an entire audio system).
  • feedback information provided to the two-wire bus from the slave nodes may improve the efficiency of the peripheral device system, and in some cases, may reduce the cost of the peripheral devices when the peripheral devices can be driven more efficiently and effectively.
  • a two-wire communication system may be used to connect sensors to a bus.
  • Sensor connectivity may provide a variety of monitoring functions, such as seat pressure sensing in a vehicle, proximity sensing, capacitive sensing, light sensing, moisture sensing, gesture sensing, acceleration sensing, temperature sensing, and direction sensing, among others.
  • Applications that may make use of the data provided by these sensors include identifying passenger location and providing voluntary and/or involuntary notifications to passengers.
  • sensor data may be used in combination with diagnostic information about other peripheral devices (e.g., operational characteristics of audio devices) to enhance the performance of the peripheral device system.
  • diagnostic information about other peripheral devices e.g., operational characteristics of audio devices
  • sensor data may be used to provide enhanced beam forming and noise cancellation.
  • sensors and other peripheral devices such as audio devices
  • sensors and other peripheral devices need not be wired separately to a controller but can leverage a common two-wire bus.
  • phrase “A and/or B” means (A), (B), or (A and B).
  • phrase “A, B, and/or C” means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C).
  • circuitry may refer to, be part of, or include an application-specific integrated circuit (ASIC), an electronic circuit, and optical circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware that provide the described functionality.
  • a master node may also be referred to as a master “device” herein; similarly, a slave node may be referred to as a slave “device” herein.
  • a “microphone” may include a microphone array.
  • any of the embodiments described herein may be performed in accordance with any suitable related embodiments disclosed in any of the prior patent filings to which the present application claims priority.
  • any of the embodiments of the Automotive Audio Bus (A2B) system disclosed in any of the priority filings may be implemented in any combination with the embodiments described herein.
  • power switching and diagnostics may be included in the two-wire communication systems described herein, as discussed in U.S. Provisional Application No. 61/845,542, filed Jul. 12, 2013.
  • decoders may be included in the two-wire communication systems described herein, as discussed in U.S. Provisional Application No. 61/843,902, filed Jul. 8, 2013.
  • digital phase detectors may be included in the two-wire communication systems described herein, as discussed in U.S. Provisional Application No. 61/843,896, filed Jul. 8, 2013.
  • the two-wire communication systems described herein may include the state machine functionality discussed in U.S. Provisional Application No. 61/843,891, filed Jul. 8, 2013.
  • FIG. 1 is a block diagram of an illustrative half-duplex two-wire communication system 100 , in accordance with various embodiments.
  • the system 100 includes a host 110 , a master node 102 and at least one slave node 104 .
  • three slave nodes ( 0 , 1 , and 2 ) are illustrated.
  • the depiction of three slave nodes 104 in FIG. 1 is simply illustrative, and the system 100 may include one, two, or more slave nodes 104 , as desired.
  • the master node 102 may communicate with the slave nodes 104 over a two-wire bus 106 .
  • the bus 106 may include different two-wire bus links between adjacent nodes along the bus 106 to connect the nodes along the bus 106 in a daisy-chain fashion.
  • the bus 106 may include a link coupling the master node 102 to the slave node 0 , a link coupling the slave node 0 to the slave node 1 , and a link coupling the slave node 1 to the slave node 2 .
  • the links of the bus 106 may each be formed of a single twisted wire pair (e.g., an unshielded twisted pair).
  • the host 110 may include a processor that programs the master node 102 , and acts as the originator and recipient of various payloads transmitted along the bus 106 .
  • the host 110 may be the master of Inter-Integrated Circuit Sound (I2S) communications that happen along the bus 106 .
  • the host 110 may communicate with the master node 102 via an I2S/Time Division Multiplex (TDM) bus and/or an Inter-Integrated Circuit (I2C) bus.
  • the master node 102 may be a transceiver (e.g., the node transceiver 120 discussed below with reference to FIG. 2 ) located within a housing of the host 110 .
  • the master node 102 may be programmable by the host 110 over the I2C bus for configuration and read-back, and may be configured to generate clock, synchronization, and framing for all of the slave nodes 104 .
  • an extension of the I2C control bus between the host 110 in the master node 102 may be embedded in the data streams transmitted over the bus 106 , allowing the host 110 direct access to registers and status information for the one or more slave nodes 104 , as well as enabling I2C-to-I2C communication over distance to allow the host 110 to control the peripherals 108 .
  • the master node 102 may generate “downstream” signals (e.g., data signals, power signals, etc., transmitted away from the master node 102 along the bus 106 ) and receive “upstream” signals (e.g., transmitted toward the master node 102 along the bus 106 ).
  • the master node 102 may provide a clock signal for synchronous data transmission over the bus 106 .
  • “synchronous data” may include data streamed continuously (e.g., audio signals) with a fixed time interval between two successive transmissions to/from the same node along the bus 106 .
  • the clock signal provided by the master node 102 may be derived from an I2S input provided to the master node 102 by the host 110 .
  • a slave node 104 may be an addressable network connection point that represents a possible destination for data frames transmitted downstream on the bus 106 or upstream on the bus 106 .
  • a slave node 104 may also represent a possible source of downstream or upstream data frames.
  • the system 100 may allow for control information and other data to be transmitted in both directions over the bus 106 from one node to the next.
  • One or more of the slave nodes 104 may also be powered by signals transmitted over the bus 106 .
  • each of the master node 102 and the slave nodes 104 may include a positive upstream terminal (denoted as “AP”), a negative upstream terminal (denoted as “AN”), a positive downstream terminal (denoted as “BP”), and a negative downstream terminal (denoted as “BN”).
  • the positive and negative downstream terminals of a node may be coupled to the positive and negative upstream terminals of the adjacent downstream node, respectively.
  • the master node 102 may include positive and negative upstream terminals, but these terminals may not be used; in other embodiments, the master node 102 may not include positive and negative upstream terminals.
  • the last slave node 104 along the bus 106 (the slave node 2 in FIG. 1 ) may include positive and negative downstream terminals, but these terminals may not be used; in other embodiments, the last slave node 104 along the bus may not include positive and negative downstream terminals.
  • the master node 102 may periodically send a synchronization control frame downstream, optionally along with data intended for one or more of the slave nodes 104 .
  • the master node 102 may transmit a synchronization control frame every 1024 bits (representing a superframe) at a frequency of 48 kHz, resulting in an effective bit rate on the bus 106 of 49.152 Mbps. Other rates may be supported, including, for example, 44.1 kHz.
  • the synchronization control frame may allow the slave nodes 104 to identify the beginning of each superframe and also, in combination with physical layer encoding/signaling, may allow each slave node 104 to derive its internal operational clock from the bus 106 .
  • the synchronization control frame may include a preamble for signaling the start of synchronization, as well as control fields that allow for various addressing modes (e.g., normal, broadcast, discovery), configuration information (e.g., writing to registers of the slave nodes 104 ), conveyance of I2C information, remote control of certain general-purpose input/output (GPIO) pins at the slave nodes 104 , and other services.
  • a portion of the synchronization control frame following the preamble and the payload data may be scrambled in order to reduce the likelihood that information in the synchronization control frame will be mistaken for a new preamble, and to flatten the spectrum of related electromagnetic emissions.
  • the synchronization control frame may get passed between slave node 104 (optionally along with other data, which may come from the master node 102 but additionally or alternatively may come from one or more upstream slave nodes 104 or from a slave node 104 itself) until it reaches the last slave node 104 (i.e., the slave node 2 in FIG. 1 ), which has been configured by the master node 102 as the last slave node 104 or has self-identified itself as the last slave node 104 .
  • the last slave node 104 may transmit a synchronization response frame followed by any data that it is permitted to transmit (e.g., a 24-bit audio sample in a designated time slot).
  • the synchronization response frame may be passed upstream between slave nodes 104 (optionally along with data from downstream slave nodes 104 ), and based on the synchronization response frame, each slave node 104 may be able to identify a time slot, if any, in which the slave node 104 is permitted to transmit.
  • one or more of the slave nodes 104 in the system 100 may be coupled to and communicate with a peripheral device 108 .
  • a slave node 104 may be configured to read data from and/or write data to the associated peripheral device 108 using I2S, pulse density modulation (PDM), TDM, and/or I2C protocols, as discussed below.
  • I2S pulse density modulation
  • PDM pulse density modulation
  • TDM time division multiple access
  • I2C protocols I2C protocols
  • peripheral devices may include a digital signal processor (DSP), a field programmable gate array (FPGA), an application-specific integrated circuit (ASIC), an analog to digital converter (ADC), a digital to analog converter (DAC), a codec, a microphone, a microphone array, a speaker, an audio amplifier, a protocol analyzer, an accelerometer or other motion sensor, an environmental condition sensor (e.g., a temperature, humidity, and/or gas sensor), a wired or wireless communication transceiver, a display device (e.g., a touchscreen display), a user interface component (e.g., a button, a dial, or other control), a camera (e.g., a video camera), a memory device, or any other suitable device that transmits and/or receives data.
  • DSP digital signal processor
  • FPGA field programmable gate array
  • ASIC application-specific integrated circuit
  • ADC analog to digital converter
  • DAC digital to analog converter
  • codec e.g., a microphone array, a
  • the peripheral device 108 may include any device configured for Inter-Integrated Circuit Sound (I2S) communication; the peripheral device 108 may communicate with the associated slave node 104 via the I2S protocol. In some embodiments, the peripheral device 108 may include any device configured for Inter-Integrated Circuit (I2C) communication; the peripheral device 108 may communicate with the associated slave node 104 via the I2C protocol. In some embodiments, a slave node 104 may not be coupled to any peripheral device 108 .
  • I2S Inter-Integrated Circuit Sound
  • I2C Inter-Integrated Circuit
  • a slave node 104 and its associated peripheral device 108 may be contained in separate housings and coupled through a wired or wireless communication connection or may be contained in a common housing.
  • a speaker connected as a peripheral device 108 may be packaged with the hardware for an associated slave node 104 (e.g., the node transceiver 120 discussed below with reference to FIG. 2 ), such that the hardware for the associated slave node 104 is contained within a housing that includes other speaker components. The same may be true for any type of peripheral device 108 .
  • the host 110 may communicate with and control the master node 102 using multi-channel I2S and I2C communication protocols.
  • the host 110 may transmit data via I2S to a frame buffer (not illustrated) in the master node 102 , and the master node 102 may read data from the frame buffer and transmit the data along the bus 106 .
  • the master node 102 may store data received via the bus 106 in the frame buffer, and then may transmit the data to the host 110 via I2S.
  • Each slave node 104 may have internal control registers that may be configured by communications from the master node 102 . A number of such registers are discussed in detail below. Each slave node 104 may receive downstream data and may retransmit the data further downstream. Each slave node 104 may receive and/or generate upstream data and/or retransmit data upstream and/or add data to and upstream transaction.
  • Communications along the bus 106 may occur in periodic superframes.
  • Each superframe may begin with a downstream synchronization control frame; be divided into periods of downstream transmission (also called “downstream portions”), upstream transmission (also called “upstream portions”), and no transmission (where the bus 106 is not driven); and end just prior to transmission of another downstream synchronization control frame.
  • the master node 102 may be programmed (by the host 110 ) with a number of downstream portions to transmit to one or more of the slave nodes 104 and a number of upstream portions to receive from one or more of the slave nodes 104 .
  • Each slave node 104 may be programmed (by the master node 102 ) with a number of downstream portions to retransmit down the bus 106 , a number of downstream portions to consume, a number of upstream portions to retransmit up the bus 106 , and a number of upstream portions in which the slave node 104 may transmit data received from the slave node 104 from the associated peripheral device 108 .
  • Communication along the bus 106 is discussed in further detail below with reference to FIGS. 2-12 .
  • Each of the master node 102 and the slave nodes 104 may include a transceiver to manage communication between components of the system 100 .
  • FIG. 2 is a block diagram of a node transceiver 120 that may be included in a node (e.g., the master node 102 or a slave node 104 ) of the system 100 of FIG. 1 , in accordance with various embodiments.
  • a node transceiver 120 may be included in each of the nodes of the system 100 , and a control signal may be provided to the node transceiver 120 via a master (MSTR) pin to indicate whether the node transceiver 120 is to act as a master (e.g., when the MSTR pin is high) or a slave (e.g., when the MSTR pin is low).
  • MSTR master
  • the node transceiver 120 may include an upstream differential signaling (DS) transceiver 122 and a downstream DS transceiver 124 .
  • the upstream DS transceiver 122 may be coupled to the positive and negative upstream terminals discussed above with reference to FIG. 1
  • the downstream DS transceiver 124 may be coupled to the positive and negative downstream terminals discussed above with reference to FIG. 1 .
  • the upstream DS transceiver 122 may be a low voltage DS (LVDS) transceiver
  • the downstream DS transceiver 124 may be an LVDS transceiver.
  • LVDS low voltage DS
  • Each node in the system 100 may be AC-coupled to the bus 106 , and data signals may be conveyed along the bus 106 (e.g., via the upstream DS transceiver 122 and/or the downstream DS transceiver 124 ) using a predetermined form of DS (e.g., LVDS or Multipoint LVDS (MLVDS) or similar signaling) with appropriate encoding to provide timing information over the bus 106 (e.g., differential Manchester coding, biphase mark coding, Manchester coding, Non-Return-to-Zero, Inverted (NRZI) coding with run-length limiting, or any other suitable encoding).
  • DS e.g., LVDS or Multipoint LVDS (MLVDS) or similar signaling
  • appropriate encoding e.g., differential Manchester coding, biphase mark coding, Manchester coding, Non-Return-to-Zero, Inverted (NRZI) coding with run-length limiting, or any
  • the upstream DS transceiver 122 and the downstream DS transceiver 124 may communicate with bus protocol circuitry 126 , and the bus protocol circuitry 126 may communicate with a phased locked loop (PLL) 128 and voltage regulator circuitry 130 , among other components.
  • PLL phased locked loop
  • the voltage regulator circuitry 130 may raise a “power good” signal that is used by the PLL 128 as a power-on reset.
  • one or more of the slave nodes 104 in the system 100 may receive power transmitted over the bus 106 concurrently with data.
  • the master node 102 may place a DC bias on the bus link between the master node 102 and the slave node 0 (e.g., by connecting one of the downstream terminals to a voltage source provided by a voltage regulator and the other downstream terminal to ground).
  • the DC bias may be a predetermined voltage, such as 5 V, 8 V, the voltage of a car battery, or a higher voltage.
  • Each successive slave node 104 can selectively tap its upstream bus link to recover power (e.g., using the voltage regulator circuitry 130 ).
  • This power may be used to power the slave node 104 itself (and optionally one or more peripheral device 108 coupled to the slave node 104 ).
  • a slave node 104 may also selectively bias the bus link downstream for the next-in-line slave node 104 with either the recovered power from the upstream bus link or from a local power supply.
  • the slave node 0 may use the DC bias on the upstream bus link 106 to recover power for the slave node 0 itself and/or for one or more associated peripheral device 108 , and/or the slave node 0 may recover power from its upstream bus link 106 to bias its downstream bus link 106 .
  • each node in the system 100 may provide power to the following downstream node over a downstream bus link.
  • the powering of nodes may be performed in a sequenced manner. For example, after discovering and configuring the slave node 0 via the bus 106 , the master node 102 may instruct the slave node 0 to provide power to its downstream bus link 106 in order to provide power to the slave node 1 ; after the slave node 1 is discovered and configured, the master node 102 may instruct the slave node 1 to provide power to its downstream bus link 106 in order to provide power to the slave node 2 (and so on for additional slave nodes 104 coupled to the bus 106 .
  • one or more of the slave nodes 104 may be locally powered, instead of or in addition to being powered from its upstream bus link.
  • the local power source for a given slave node 104 may be used to provide power to one or more downstream slave nodes.
  • upstream filtering circuitry 132 may be disposed between the upstream DS transceiver 122 and the voltage regulator circuitry 130
  • downstream filtering circuitry 131 may be disposed between the downstream DS transceiver 124 and the voltage regulator circuitry 130 . Since each link of the bus 106 may carry AC (signal) and DC (power) components, the upstream filtering circuitry 132 and the downstream filtering circuitry 131 may separate the AC and DC components, providing the AC components to the upstream DS transceiver 122 and the downstream DS transceiver 124 , and providing the DC components to the voltage regulator 130 .
  • AC couplings on the line side of the upstream DS transceiver 122 and downstream DS transceiver 124 substantially isolate the transceivers 122 and 124 from the DC component on the line to allow for high-speed bi-directional communications.
  • the DC component may be tapped for power, and the upstream filtering circuitry 132 and the downstream filtering circuitry 131 may include a ferrite, a common mode choke, or an inductor, for example, to reduce the AC component provided to the voltage regulator circuitry 130 .
  • the upstream filtering circuitry 132 may be included in the upstream DS transceiver 122 , and/or the downstream filtering circuitry 131 may be included in the downstream DS transceiver 124 ; in other embodiments, the filtering circuitry may be external to the transceivers 122 and 124 .
  • the node transceiver 120 may include a transceiver 127 for I2S, TDM, and PDM communication between the node transceiver 120 and an external device 155 .
  • the “external device 155 ” may be referred to in the singular herein, this is simply for ease of illustration, and multiple external devices may communicate with the node transceiver 120 via the I2S/TDM/PDM transceiver 127 .
  • the I2S protocol is for carrying pulse code modulated (PCM) information (e.g., between audio chips on a printed circuit board).
  • PCM pulse code modulated
  • I2S/TDM may refer to an extension of the I2S stereo (2-channel) content to multiple channels using TDM.
  • PDM may be used in sigma delta converters, and in particular, PDM format may represent an over-sampled 1-bit sigma delta ADC signal before decimation. PDM format is often used as the output format for digital microphones.
  • the I2S/TDM/PDM transceiver 127 may be in communication with the bus protocol circuitry 126 and pins for communication with the external device 155 . Six pins, BCLK, SYNC, DTX[1:0], and DRX[1:0], are illustrated in FIG.
  • the BCLK pin may be used for an I2S bit clock
  • the SYNC pin may be used for an I2S frame synchronization signal
  • the DTX[1:0] and DRX[1:0] pins are used for transmit and receive data channels, respectively.
  • two transmit pins (DTX[1:0]) and two receive pins (DRX[1:0]) are illustrated in FIG. 2 , any desired number of receive and/or transmit pins may be used.
  • the external device 155 may include the host 110 , and the I2S/TDM/PDM transceiver 127 may provide an I2S slave (in regards to BCLK and SYNC) that can receive data from the host 110 and send data to the host 110 synchronously with an I2S interface clock of the host 110 .
  • an I2S frame synchronization signal may be received at the SYNC pin as an input from the host 110 , and the PLL 128 may use that signal to generate clocks.
  • the external device 155 may include one or more peripheral devices 108 , and the I2S/TDM/PDM transceiver 127 may provide an I2S clock master (for BCLK and SYNC) that can control I2S communication with the peripheral device 108 .
  • the I2S/TDM/PDM transceiver 127 may provide an I2S frame synchronization signal at the SYNC pin as an output.
  • Registers in the node transceiver 120 may determine which and how many I2S/TDM channels are being transmitted as data slots over the bus 106 .
  • a TDM mode (TDMMODE) register in the node transceiver 120 may store a value of how many TDM channels fit between consecutive SYNC pulses on a TDM transmit or receive pin. Together with knowledge of the channel size, the node transceiver 120 may automatically set the BCLK rate to match the amount of bits within the sampling time (e.g., 48 kHz).
  • the node transceiver 120 may include a transceiver 129 for I2C communication between the node transceiver 120 and an external device 157 .
  • the “external device 157 ” may be referred to in the singular herein, this is simply for ease of illustration, and multiple external devices may communicate with the node transceiver 120 via the I2C transceiver 129 .
  • the I2C protocol uses clock (SCL) and data (SDA) lines to provide data transfer.
  • the I2C transceiver 129 may be in communication with the bus protocol circuitry 126 and pins for communication with the external device 157 . Four pins, ADR 1 , ADR 2 , SDA, and SCL are illustrated in FIG.
  • ADR 1 and ADR 2 may be used to modify the I2C addresses used by the node transceiver 120 when the node transceiver 120 acts as an I2C slave (e.g., when it is included in the master node 102 ), and SDA and SCL are used for the I2C serial data and serial clock signals, respectively.
  • the external device 157 may include the host 110
  • the I2C transceiver 129 may provide an I2C slave that can receive programming instructions from the host 110 .
  • an I2C serial clock signal may be received at the SCL pin as an input from the host 110 for register accesses.
  • the external device 157 may include a peripheral device 108 and the I2C transceiver 129 may provide an I2C master to allow the I2C transceiver to program one or more peripheral devices in accordance with instructions provided by the host 110 and transmitted to the node transceiver 120 via the bus 106 .
  • the I2C transceiver 129 may provide the I2C serial clock signal at the SCL pin as an output.
  • the node transceiver 120 may include an interrupt request (IRQ) pin in communication with the bus protocol circuitry 126 .
  • IRQ interrupt request
  • the bus protocol circuitry 126 may provide event-driven interrupt requests toward the host 110 via the IRQ pin.
  • the IRQ pin may serve as a GPIO pin with interrupt request capability.
  • the system 100 may operate in any of a number of different operational modes.
  • the nodes on the bus 106 may each have a register indicating which operational mode is currently enabled. Descriptions follow of examples of various operational modes that may be implemented.
  • bus activity is reduced to enable global power savings; the only traffic required is a minimal downstream preamble to keep the Pas of each node (e.g., the PLL 128 ) synchronized.
  • standby operational mode reads and writes across the bus 106 are not supported.
  • the master node 102 may send predetermined signals out along the bus 106 and wait for suitable responses to map out the topology of slave nodes 104 distributed along the bus 106 .
  • a normal operational mode full register access may be available to and from the slave nodes 104 as well as access to and from peripheral devices 108 over the bus 106 .
  • Normal mode may be globally configured by the host 110 with or without synchronous upstream data and with or without synchronous downstream data.
  • FIG. 3 is a diagram of a portion of a synchronization control frame 180 used for communication in the system 100 , in accordance with various embodiments.
  • the synchronization control frame 180 may be used for data clock recovery and PLL synchronization, as discussed below.
  • communications may be time-multiplexed into downstream portions and upstream portions.
  • a synchronization control frame and downstream data may be transmitted from the master node 102
  • a synchronization response frame, and upstream data may be transmitted to the master node 102 from each of the slave nodes 104 .
  • the synchronization control frame 180 may include a preamble 182 and control data 184 .
  • Each slave node 104 may be configured to use the preamble 182 of the received synchronization control frame 180 as a time base for feeding the PLL 128 . To facilitate this, a preamble 182 does not follow the “rules” of valid control data 184 , and thus can be readily distinguished from the control data 184 .
  • communication along the bus 106 may be encoded using a clock first, transition on zero differential Manchester coding scheme.
  • each bit time begins with a clock transition. If the data value is zero, the encoded signal transitions again in the middle of the bit time. If the data value is one, the encoded signal does not transition again.
  • the preamble 182 illustrated in FIG. 5 may violate the encoding protocol (e.g., by having clock transitions that do not occur at the beginning of bit times 5 , 7 , and 8 ), which means that the preamble 182 may not match any legal (e.g., correctly encoded) pattern for the control data 184 .
  • the preamble 182 cannot be reproduced by taking a legal pattern for the control data 184 and forcing the bus 106 high or low for a single bit time or for a multiple bit time period.
  • the preamble 182 illustrated in FIG. 5 is simply illustrative, and the synchronization control frame 180 may include different preambles 182 that may violate the encoding used by the control data 184 in any suitable manner.
  • the bus protocol circuitry 126 may include differential Manchester decoder circuitry that runs on a clock recovered from the bus 106 and that detects the synchronization control frame 180 to send a frame sync indicator to the PLL 128 . In this manner, the synchronization control frame 180 may be detected without using a system clock or a higher-speed oversampling clock. Consequently, the slave nodes 104 can receive a PLL synchronization signal from the bus 106 without requiring a crystal clock source at the slave nodes 104 .
  • FIG. 4 is a diagram of a superframe 190 , in accordance with various embodiments.
  • a superframe may begin with a synchronization control frame 180 .
  • the frequency at which superframes are communicated (“the superframe frequency”) may be the same as the synchronization signal frequency.
  • the superframe frequency may be the same as the audio sampling frequency used in the system 100 (e.g., either 48 kHz or 44.1 kHz), but any suitable superframe frequency may be used.
  • Each superframe 190 may be divided into periods of downstream transmission 192 , periods of upstream transmission 194 , and periods of no transmission 196 (e.g., when the bus 106 is not driven).
  • the superframe 190 is shown with an initial period of downstream transmission 192 and a later period of upstream transmission 194 .
  • the period of downstream transmission 192 may include a synchronization control frame 180 and X downstream data slots 198 , where X can be zero.
  • Substantially all signals on the bus 106 may be line-coded and a synchronization signal forwarded downstream from the master node 102 to the last slave node 104 (e.g., the slave node 104 C) in the form of the synchronization preamble 182 in the synchronization control frame 180 , as discussed above.
  • Downstream, TDM, synchronous data may be included in the X downstream data slots 198 after the synchronization control frame 180 .
  • the downstream data slots 198 may have equal width.
  • the PLL 128 may provide the clock that a node uses to time communications over the bus 106 .
  • the PLL 128 may operate at a multiple of the audio sampling frequency (e.g., 1024 times the audio sampling frequency, resulting in 1024-bit clocks in each superframe).
  • the period of upstream transmission 194 may include a synchronization response frame 197 and Y upstream data slots 199 , where Y can be zero.
  • each slave node 104 may consume a portion of the downstream data slots 198 .
  • the last slave node e.g., slave node 2 in FIG. 1
  • the last slave node may respond (after a predetermined response time stored in a register of the last slave node) with a synchronization response frame 197 .
  • Upstream, TDM, synchronous data may be added by each slave node 104 in the upstream data slots 199 directly after the synchronization response frame 197 .
  • the upstream data slots 199 may have equal width.
  • a slave node 104 that is not the last slave node may replace the received synchronization response frame 197 with its own upstream response if a read of one of its registers was requested in the synchronization control frame 180 of the superframe 190 or if a remote I2C read was requested in the synchronization control frame 180 of the superframe 190 .
  • the synchronization control frame 180 may begin each downstream transmission.
  • the synchronization control frame 180 may be 64 bits in length, but any other suitable length may be used.
  • the synchronization control frame 180 may begin with the preamble 182 , as noted above.
  • the preamble 182 may be generated by the transmitting slave node 104 , rather than being retransmitted.
  • the control data 184 of the synchronization control frame 180 may include fields that contain data used to control transactions over the bus 106 . Examples of these fields are discussed below, and some embodiments are illustrated in FIG. 5 .
  • FIG. 5 illustrates example formats for the synchronization control frame 180 in normal mode, I2C mode, and discovery mode, in accordance with various embodiments.
  • a different preamble 182 or synchronization control frame 180 entirely may be used in standby mode so that the slave nodes 104 do not need to receive all of the synchronization control frame 180 until a transition to normal mode is sent.
  • the synchronization control frame 180 may include a count (CNT) field.
  • the CNT field may have any suitable length (e.g., 2 bits) and may be incremented (modulo the length of the field) from the value used in the previous superframe.
  • a slave node 104 that receives a CNT value that is unexpected may be programmed to return an interrupt.
  • the synchronization control frame 180 may include a node addressing mode (NAM) field.
  • the NAM field may have any suitable length (e.g., 2 bits) and may be used to control access to registers of a slave node 104 over the bus 106 .
  • registers of a slave node 104 may be read from and/or written to based on the ID of the slave node 104 and the address of the register. Broadcast transactions are writes which should be taken by every slave node 104 .
  • the NAM field may provide for four node addressing modes, including “none” (e.g., data not addressed to any particular slave node 104 ), “normal” (e.g., data unicast to a specific slave node 104 specified in the address field discussed below), “broadcast” (e.g., addressed to all slave nodes 104 ), and “discovery.”
  • node addressing modes including “none” (e.g., data not addressed to any particular slave node 104 ), “normal” (e.g., data unicast to a specific slave node 104 specified in the address field discussed below), “broadcast” (e.g., addressed to all slave nodes 104 ), and “discovery.”
  • the synchronization control frame 180 may include an I2C field.
  • the I2C field may have any suitable length (e.g., 1 bit) and may be used to indicate that the period of downstream transmission 192 includes an I2C transaction.
  • the I2C field may indicate that the host 110 has provided instructions to remotely access a peripheral device 108 that acts as an I2C slave with respect to an associated slave node 104 .
  • the synchronization control frame 180 may include a node field.
  • the node field may have any suitable length (e.g., 4 bits) and may be used to indicate which slave node is being addressed for normal and I2C accesses. In discovery mode, this field may be used to program an identifier for a newly discovered slave node 104 in a node ID register of the slave node 104 .
  • Each slave node 104 in the system 100 may be assigned a unique ID when the slave node 104 is discovered by the master node 102 , as discussed below.
  • the master node 102 does not have a node ID, while in other embodiments, the master node 102 may have a node ID.
  • the slave node 104 attached to the master node 102 on the bus 106 (e.g., the slave node 0 in FIG. 1 ) will be slave node 0 , and each successive slave node 104 will have a number that is 1 higher than the previous slave node.
  • this is simply illustrative, and any suitable slave node identification system may be used.
  • the synchronization control frame 180 may include a read/write (RW) field.
  • the synchronization control frame 180 may include an address field.
  • the address field may have any suitable length (e.g., 8 bits) and may be used to address specific registers of a slave node 104 through the bus 106 .
  • the address field may be replaced with I2C control values, such as START/STOP, WAIT, RW, and DATA VLD.
  • the address field may have a predetermined value (e.g., as illustrated in FIG. 5 ).
  • the synchronization control frame 180 may include a data field.
  • the data field may have any suitable length (e.g., 8 bits) and may be used for normal, I2C, and broadcast writes.
  • the RESPCYCS value, multiplied by 4 may be used to determine how many cycles a newly discovered node should allow to elapse between the start of the synchronization control frame 180 being received and the start of the synchronization response frame 197 being transmitted.
  • the node address and data fields discussed below may be encoded as a RESPCYCS value that, when multiplied by a suitable optional multiplier (e.g., 4), indicates the time, in bits, from the end of the synchronization control frame 180 to the start of the synchronization response frame 197 . This allows a newly discovered slave node 104 to determine the appropriate time slot for upstream transmission.
  • a suitable optional multiplier e.g. 4
  • the synchronization control frame 180 may include a cyclic redundancy check (CRC) field.
  • the CRC field may have any suitable length (e.g., 16 bits) and may be used to transmit a CRC value for the control data 184 of the synchronization control frame 180 following the preamble 182 .
  • the CRC may be calculated in accordance with the CCITT-CRC error detection scheme.
  • At least a portion of the synchronization control frame 180 between the preamble 182 and the CRC field may be scrambled in order to reduce the likelihood that a sequence of bits in this interval will periodically match the preamble 182 (and thus may be misinterpreted by the slave node 104 as the start of a new superframe 190 ), as well as to reduce electromagnetic emissions as noted above.
  • the CNT field of the synchronization control frame 180 may be used by scrambling logic to ensure that the scrambled fields are scrambled differently from one superframe to the next.
  • Various embodiments of the system 100 described herein may omit scrambling.
  • synchronization control frame 180 may be used to ensure that the preamble 182 can be uniquely identified by the slave nodes 104 or to reduce the likelihood that the preamble 182 shows up elsewhere in the synchronization control frame 180 , in addition to or in lieu of techniques such as scrambling and/or error encoding as discussed above.
  • a longer synchronization sequence may be used so as to reduce the likelihood that a particular encoding of the remainder of the synchronization control frame 180 will match it.
  • the remainder of the synchronization control frame may be structured so that the synchronization sequence cannot occur, such as by placing fixed “0” or “1” values at appropriate bits.
  • the master node 102 may send read and write requests to the slave nodes 104 , including both requests specific to communication on the bus 106 and I2C requests.
  • the master node 102 may send read and write requests (indicated using the RW field) to one or more designated slave nodes 104 (using the NAM and node fields) and can indicate whether the request is a request for the slave node 104 specific to the bus 106 , an I2C request for the slave node 104 , or an I2C request to be passed along to an I2C-compatible peripheral device 108 coupled to the slave node 104 at one or more I2C ports of the slave node 104 .
  • the synchronization response frame 197 may begin each upstream transmission.
  • the synchronization response frame 197 may be 64 bits in length, but any other suitable length may be used.
  • the synchronization response frame 197 may also include a preamble, as discussed above with reference to the preamble 182 of the synchronization control frame 180 , followed by data portion.
  • the last slave node 104 on the bus 106 may wait until the RESPCYCS counter has expired and then begin transmitting a synchronization response frame 197 upstream. If an upstream slave node 104 has been targeted by a normal read or write transaction, a slave node 104 may generate its own synchronization response frame 197 and replace the one received from downstream. If any slave node 104 does not see a synchronization response frame 197 from a downstream slave node 104 at the expected time, the slave node 104 will generate its own synchronization response frame 197 and begin transmitting it upstream.
  • the data portion of the synchronization response frame 197 may include fields that contain data used to communicate response information back to the master node 102 . Examples of these fields are discussed below, and some embodiments are illustrated in FIG. 6 .
  • FIG. 6 illustrates example formats for the synchronization response frame 197 in normal mode, I2C mode, and discovery mode, in accordance with various embodiments.
  • the synchronization response frame 197 may include a count (CNT) field.
  • the CNT field may have any suitable length (e.g., 2 bits) and may be used to transmit the value of the CNT field in the previously received synchronization control frame 180 .
  • the synchronization response frame 197 may include an acknowledge (ACK) field.
  • the ACK field may have any suitable length (e.g., 2 bits), and may be inserted by a slave node 104 to acknowledge a command received in the previous synchronization control frame 180 when that slave node 104 generates the synchronization response frame 197 .
  • Example indicators that may be communicated in the ACK field include wait, acknowledge, not acknowledge (NACK), and retry.
  • the ACK field may be sized to transmit an acknowledgment by a slave node 104 that it has received and processed a broadcast message (e.g., by transmitting a broadcast acknowledgment to the master node 102 ).
  • a slave node 104 also may indicate whether the slave node 104 has data to transmit (which could be used, for example, for demand-based upstream transmissions, such as non-TDM inputs from a keypad or touchscreen, or for prioritized upstream transmission, such as when the slave node 104 wishes to report an error or emergency condition).
  • the synchronization response frame 197 may include an I2C field.
  • the I2C field may have any suitable length (e.g., 1 bit) and may be used to transmit the value of the I2C field in the previously received synchronization control frame 180 .
  • the synchronization response frame 197 may include a node field.
  • the node field may have any suitable length (e.g., 4 bits) and may be used to transmit the ID of the slave node 104 that generates the synchronization response frame 197 .
  • the synchronization response frame 197 may include a data field.
  • the data field may have any suitable length (e.g., 8 bits), and its value may depend on the type of transaction and the ACK response of the slave node 104 that generates the synchronization response frame 197 .
  • the data field may include the value of the RESPCYCS field in the previously received synchronization control frame 180 .
  • the data field may include a broadcast acknowledge (BA) indicator (in which the last slave node 104 may indicate if the broadcast write was received without error), a discovery error (DER) indicator (indicating whether a newly discovered slave node 104 in a discovery transaction matches an existing slave node 104 ), and a CRC error (CER) indicator (indicating whether a NACK was caused by a CRC error).
  • BA broadcast acknowledge
  • DER discovery error
  • CER CRC error
  • the synchronization response frame 197 may include a CRC field.
  • the CRC field may have any suitable length (e.g., 16 bits) and may be used to transmit a CRC value for the portion of the synchronization response frame 197 between the preamble and the CRC field.
  • the synchronization response frame 197 may include an interrupt request (IRQ) field.
  • the IRQ field may have any suitable length (e.g., 1 bit) and may be used to indicate that an interrupt has been signaled from a slave node 104 .
  • the synchronization response frame 197 may include an IRQ node (IRQNODE) field.
  • the IRQNODE field may have any suitable length (e.g., 4 bits) and may be used to transmit the ID of the slave node 104 that has signaled the interrupt presented by the IRQ field.
  • the slave node 104 for generating the IRQ field will insert its own ID into the IRQNODE field.
  • the synchronization response frame 197 may include a second CRC (CRC-4) field.
  • the CRC-4 field may have any suitable length (e.g., 4 bits) and may be used to transmit a CRC value for the IRQ and IRQNODE fields.
  • the synchronization response frame 197 may include an IRQ field, an IRQNODE field, and a CRC-4 field as the last bits of the synchronization response frame 197 (e.g., the last 10 bits). As discussed above, these interrupt-related fields may have their own CRC protection in the form of CRC-4 (and thus not protected by the preceding CRC field). Any slave node 104 that needs to signal an interrupt to the master node 102 will insert its interrupt information into these fields. In some embodiments, a slave node 104 with an interrupt pending may have higher priority than any slave node 104 further downstream that also has an interrupt pending. The last slave node 104 along the bus 106 (e.g., the slave node 2 in FIG.
  • interrupt frame may be referred to herein as an “interrupt frame.”
  • At least a portion of the synchronization response frame 197 between the preamble 182 and the CRC field may be scrambled in order to reduce emissions.
  • the CNT field of the synchronization response frame 197 may be used by scrambling logic to ensure that the scrambled fields are scrambled differently from one superframe to the next.
  • Various embodiments of the system 100 described herein may omit scrambling.
  • a longer synchronization sequence may be used so as to reduce the likelihood that a particular encoding of the remainder of the synchronization response frame 180 will match it.
  • the remainder of the synchronization response frame may be structured so that the synchronization sequence cannot occur, such as by placing fixed “0” or “1” values at appropriate bits.
  • FIG. 7 is a block diagram of the bus protocol circuitry 126 of FIG. 2 , in accordance with various embodiments.
  • the bus protocol circuitry 126 may include control circuitry 154 to control the operation of the node transceiver 120 in accordance with the protocol for the bus 106 described herein.
  • the control circuitry 154 may control the generation of synchronization frames for transmission (e.g., synchronization control frames or synchronization response frames, as discussed above), the processing of received synchronization frames, and the performance of control operations specified in received synchronization control frames.
  • the control circuitry 154 may include programmable registers, as discussed below.
  • the control circuitry 154 may create and receive synchronization control frames, react appropriately to received messages (e.g., associated with a synchronization control frame when the bus protocol circuitry 126 is included in a slave node 104 or from an I2C device when the bus protocol circuitry 126 is included in a master node 102 ), and adjust the framing to the different operational modes (e.g., normal, discovery, standby, etc.).
  • received messages e.g., associated with a synchronization control frame when the bus protocol circuitry 126 is included in a slave node 104 or from an I2C device when the bus protocol circuitry 126 is included in a master node 102
  • the framing e.g., normal, discovery, standby, etc.
  • preamble circuitry 156 may be configured to generate preambles for synchronization frames for transmission, and to receive preambles from received synchronization frames.
  • a downstream synchronization control frame preamble may be sent by the master node 102 every 1024 bits.
  • one or more slave nodes 104 may synchronize to the downstream synchronization control frame preamble and generate local, phase-aligned master clocks from the preamble.
  • Cyclic redundancy check (CRC) insert circuitry 158 may be configured to generate one or more CRCs for synchronization frames for transmission.
  • Frame/compress circuitry 160 may be configured to take incoming data from the I2S/TDM/PDM transceiver 127 (e.g., from a frame buffer associated with the transceiver 127 ) and/or the I2C transceiver 129 , optionally compress the data, and optionally generate parity check bits or error correction codes (ECC) for the data.
  • ECC error correction codes
  • a multiplexer (MUX) 162 may multiplex a preamble from the preamble circuitry 156 , synchronization frames, and data into a stream for transmission. In some embodiments, the transmit stream may be scrambled by scrambling circuitry 164 before transmission.
  • the frame/compress circuitry 160 may apply a floating point compression scheme.
  • the control circuitry 154 may transmit 3 bits to indicate how many repeated sign bits are in the number, followed by a sign bit and N ⁇ 4 bits of data, where N is the size of the data to be transmitted over the bus 106 .
  • the use of data compression may be configured by the master node 102 when desired.
  • the receive stream entering the node transceiver 120 may be descrambled by the descrambling circuitry 166 .
  • a demultiplexer (DEMUX) 168 may demultiplex the preamble, synchronization frames, and data from the receive stream.
  • CRC check circuitry 159 on the receive side may check received synchronization frames for the correct CRC. When the CRC check circuitry 159 identifies a CRC failure in an incoming synchronization control frame 180 , the control circuitry 154 may be notified of the failure and will not perform any control commands in the control data 184 of the synchronization control frame 180 .
  • Deframe/decompress circuitry 170 may accept receive data, optionally check its parity, optionally perform error detection and correction (e.g., single error correction—double error detection (SECDED)), optionally decompress the data, and may write the receive data to the I2S/TDM/PDM transceiver 127 (e.g., a frame buffer associated with the transceiver 127 ) and/or the I2C transceiver 129 .
  • SECDED single error correction—double error detection
  • upstream and downstream data may be transmitted along the bus 106 in TDM data slots within a superframe 190 .
  • the control circuitry 154 may include registers dedicated to managing these data slots on the bus 106 , a number of examples of which are discussed below.
  • the values in these registers may be programmed into the control circuitry 154 by the host 110 .
  • the values in these registers may be programmed into the control circuitry 154 by the master node 102 .
  • control circuitry 154 may include a downstream slots (DNSLOTS) register.
  • this register may hold the value of the total number of downstream data slots.
  • This register may also define the number of data slots that will be used for combined I2S/TDM/PDM receive by the I2S/TDM/PDM transceiver 127 in the master node 102 .
  • this register may define the number of data slots that are passed downstream to the next slave node 104 before or after the addition of locally generated downstream slots, as discussed in further detail below with reference to LDNSLOTS.
  • control circuitry 154 may include a local downstream slots (LDNSLOTS) register. This register may be unused in the master node 102 . In a slave node 104 , this register may define the number of data slots that the slave node 104 will use and not retransmit. Alternatively, this register may define the number of slots that the slave node 104 may contribute to the downstream data link 106 .
  • LNSLOTS local downstream slots
  • the control circuitry 154 may include an upstream slots (UPSLOTS) register.
  • this register may hold the value of the total number of upstream data slots.
  • This register may also define the number of slots that will be used for I2S/TDM transmit by the I2S/TDM/PDM transceiver 127 in the master node 102 .
  • this register may define the number of data slots that are passed upstream before the slave node 104 begins to add its own data.
  • control circuitry 154 may include a local upstream slots (LUPSLOTS) register. This register may be unused in the master node 102 . In a slave node 104 , this register may define the number of data slots that the slave node 104 will add to the data received from downstream before it is sent upstream. This register may also define the number of data slots that will be used for combined I2S/TDM/PDM receive by the I2S/TDM/PDM transceiver 127 in the slave node 104 .
  • LPSLOTS local upstream slots
  • control circuitry 154 may include a broadcast downstream slots (BCDNSLOTS) register. This register may be unused in the master node 102 . In a slave node 104 , this register may define the number of broadcast data slots. In some embodiments, broadcast data slots may always come at the beginning of the data field. The data in the broadcast data slots may be used by multiple slave nodes 104 and may be passed downstream by all slave nodes 104 whether or not they are used.
  • BCDNSLOTS broadcast downstream slots
  • control circuitry 154 may include a slot format (SLOTFMT) register.
  • This register may define the format of data for upstream and downstream transmissions.
  • the data size for the I2S/TDM/PDM transceiver 127 may also be determined by this register.
  • valid data sizes include 8, 12, 16, 20, 24, 28, and 32 bits.
  • This register may also include bits to enable floating point compression for downstream and upstream traffic. When floating point compression is enabled, the I2S/TDM data size may be 4 bits larger than the data size over the bus 106 . All nodes in the system 100 may have the same values for SLOTFMT when data slots are enabled, and the nodes may be programmed by a broadcast write so that all nodes will be updated with the same value.
  • FIGS. 8-11 illustrate examples of information exchange along the bus 106 , in accordance with various embodiments of the bus protocols described herein.
  • FIGS. 8-11 illustrate embodiments in which each slave node 104 is coupled to one or more speakers and/or one or more microphones as the peripheral device 108 .
  • FIG. 8 illustrates signaling and timing considerations for bi-directional communication on the bus 106 , in accordance with various embodiments.
  • the slave nodes 104 depicted in FIG. 8 have various numbers of sensor/actuator elements, and so different amounts of data may be sent to, or received from, the various slave nodes 104 .
  • slave node 1 has two elements
  • slave node 4 has four elements
  • slave node 5 has three elements
  • the data transmitted by the master node 102 includes two time slots for slave node 1 , four time slots for slave node 4 , and three time slots for slave node 5 .
  • slave node 0 has three elements
  • slave node 2 has three elements
  • slave node 3 has three elements
  • slave node 6 has one element
  • slave node 7 has four elements
  • the data transmitted upstream by those slave nodes 104 includes the corresponding number of time slots.
  • a microphone array, included in the peripheral device 108 having three microphones may include a digital signal processor that combines signals from the three microphones (and possibly also information received from the master node 102 or from other slave nodes 104 ) to produce a single data sample, which, depending on the type of processing, could correspond to a single time slot or multiple time slots.
  • the master node 102 transmits a synchronization control frame (SCF) followed by data for speakers coupled to specific slave nodes 104 (SD).
  • SCF synchronization control frame
  • SD specific slave nodes 104
  • Each successive slave node 104 forwards the synchronization control frame and also forwards at least any data destined for downstream slave nodes 104 .
  • a particular slave node 104 may forward all data or may remove data destined for that slave node 104 .
  • SRF synchronization response frame
  • Each successive slave node 104 forwards the synchronization response frame along with any data from downstream slave nodes 104 and optionally inserts data from one or more microphones coupled to the particular slave nodes 104 (MD).
  • the master node 102 sends data to slave nodes 1 , 4 , and 5 (depicted in FIG. 8 as active speakers) and receives data from slave nodes 7 , 6 , 3 , 2 , and 0 (depicted in FIG. 8 as microphone arrays).
  • FIG. 9 schematically illustrates the dynamic removal of data from a downstream transmission and insertion of data into an upstream transmission, from the perspective of the downstream DS transceiver 124 , in accordance with various embodiments.
  • the master node 102 transmits a synchronization control frame (SCF) followed by data for slave nodes 1 , 4 , and 5 (SD) in reverse order (e.g., data for slave node 5 is followed by data for slave node 4 , which is followed by data for slave node 1 , etc.) (see the row labeled MASTER).
  • SCF synchronization control frame
  • SD data for slave nodes 1 , 4 , and 5
  • slave node 1 When slave node 1 receives this transmission, slave node 1 removes its own data and forwards to slave node 2 only the synchronization control frame followed by the data for slave nodes 5 and 4 .
  • Slave nodes 2 and 3 forward the data unchanged (see the row labeled SLAVE 2 ), such that the data forwarded by slave node 1 is received by slave node 4 (see the row labeled SLAVE 3 ).
  • Slave node 4 removes its own data and forwards to slave node 5 only the synchronization control frame followed by the data for slave node 5
  • slave node 5 removes its own data and forwards to slave node 6 only the synchronization control frame.
  • Slave node 6 forwards the synchronization control frame to slave node 7 (see the row labeled SLAVE 6 ).
  • slave node 7 transmits to slave node 6 the synchronization response frame (SRF) followed by its data (see the row labeled SLAVE 6 ).
  • Slave node 6 forwards to slave node 5 the synchronization response frame along with the data from slave node 7 and its own data, and slave node 5 in turn forwards to slave node 4 the synchronization response frame along with the data from slave nodes 7 and 6 .
  • Slave node 4 has no data to add, so it simply forwards the data to slave node 3 (see the row labeled SLAVE 3 ), which forwards the data along with its own data to slave node 2 (see the row labeled SLAVE 2 ), which in turn forwards the data along with its own data to slave node 1 .
  • Slave node 1 has no data to add, so it forwards the data to slave node 0 , which forwards the data along with its own data.
  • the master node 102 receives the synchronization response frame followed by the data from slave nodes 7 , 6 , 3 , 2 , and 0 (see the row labeled MASTER).
  • FIG. 10 illustrates another example of the dynamic removal of data from a downstream transmission and insertion of data into an upstream transmission, from the perspective of the downstream DS transceiver 124 , as in FIG. 9 , although in FIG. 10 , the slave nodes 104 are coupled with both sensors and actuators as the peripheral device 108 such that the master node 102 sends data downstream to all of the slave nodes 104 and receives data back from all of the slave nodes 104 . Also, in FIG. 10 , the data is ordered based on the node address to which it is destined or from which it originates. The data slot labeled “Y” may be used for a data integrity check or data correction.
  • FIG. 11 illustrates another example of the dynamic removal of data from a downstream transmission and insertion of data into an upstream transmission, from the perspective of the downstream DS transceiver 124 , as in FIG. 9 , although in FIG. 11 , the data is conveyed downstream and upstream in sequential order rather than reverse order. Buffering at each slave node 104 allows for selectively adding, removing, and/or forwarding data.
  • each slave node 104 may remove data from downstream or upstream transmissions and/or may add data to downstream or upstream transmissions.
  • the master node 102 may transmit a separate sample of data to each of a number of slave nodes 104 , and each such slave node 104 may remove its data sample and forward only data intended for downstream slaves.
  • a slave node 104 may receive data from a downstream slave node 104 and forward the data along with additional data.
  • the system 100 may also support broadcast transmissions (and multicast transmissions) from the master node 102 to the slave nodes 104 , specifically through configuration of the downstream slot usage of the slave nodes 104 .
  • Each slave node 104 may process the broadcast transmission and pass it along to the next slave node 104 , although a particular slave node 104 may “consume” the broadcast message, (i.e., not pass the broadcast transmission along to the next slave node 104 ).
  • the system 100 may also support upstream transmissions (e.g., from a particular slave node 104 to one or more other slave nodes 104 ).
  • upstream transmissions can include unicast, multicast, and/or broadcast upstream transmissions.
  • a slave node 104 may determine whether or not to remove data from an upstream transmission and/or whether or not to pass an upstream transmission along to the next upstream slave node 104 based on configuration of the upstream slot usage of the slave nodes 104 .
  • data may be passed by a particular slave node 104 to one or more other slave nodes 104 in addition to, or in lieu of, passing the data to the master node 102 .
  • Such slave-slave relationships may be configured, for example, via the master node 102 .
  • the slave nodes 104 may operate as active/intelligent repeater nodes, with the ability to selectively forward, drop, and add information.
  • the slave nodes 104 may generally perform such functions without necessarily decoding/examining all of the data, since each slave node 104 knows the relevant time slot(s) within which it will receive/transmit data, and hence can remove data from or add data into a time slot. Notwithstanding that the slave nodes 104 may not need to decode/examine all data, the slave nodes 104 may typically re-clock the data that it transmits/forwards. This may improve the robustness of the system 100 .
  • the bus 106 may be configured for uni-directional communications in a ring topology.
  • FIG. 12 illustrates an arrangement 1200 of the master node 102 and four slave nodes 104 in a ring topology, and illustrates signaling and timing considerations for uni-directional communication in the arrangement 1200 , in accordance with various embodiments.
  • the transceivers 120 in the nodes may include a receive-only transceiver (MASTER IN) and a transmit-only transceiver (MASTER OUT), rather than two bi-directional transceivers for upstream and downstream communication.
  • MASTER IN receive-only transceiver
  • MASTER OUT transmit-only transceiver
  • the master node 102 transmits a synchronization control frame (SCF) 180 , optionally followed by “downstream” data 1202 for the three speakers coupled to various slave nodes 104 (the data for the different speakers may be arranged in any suitable order, as discussed above with reference to FIGS. 8-11 ), and each successive slave node 104 forwards the synchronization control frame 180 along with any “upstream” data from prior slave nodes 104 and “upstream” data of its own to provide “upstream” data 1204 (e.g., the data from the eight different microphones may be arranged in any suitable order, as discussed above with reference to FIGS. 8-11 ).
  • SCF synchronization control frame
  • data may be communicated between elements of the system 100 in any of a number of ways.
  • data may be sent as part of a set of synchronous data slots upstream (e.g., using the data slots 199 ) by a slave node 104 or downstream (e.g., using the data slots 198 ) by a slave node 104 or a master node 102 .
  • the volume of such data may be adjusted by changing the number of bits in a data slot, or including extra data slots.
  • Data may also be communicated in the system 100 by inclusion in a synchronization control frame 180 or a synchronization response frame 197 .
  • Data communicated this way may include I2C control data from the host 110 (with a response from a peripheral device 108 associated with a slave node 104 ); accesses to registers of the slave nodes 104 (e.g., for discovery and configuration of slots and interfaces) that may include write access from the host 110 /master node 102 to a slave node 104 and read access from a slave node 104 to the host 110 /master node 102 ; and event signaling via interrupts from a peripheral device 108 to the host 110 .
  • I2C control data from the host 110 (with a response from a peripheral device 108 associated with a slave node 104 ); accesses to registers of the slave nodes 104 (e.g., for discovery and configuration of slots and interfaces) that may include write access from the host 110 /master node 102 to a slave node 104 and read access from a slave node 104 to the host 110 /master node 102 ; and event signaling via interrupts
  • GPIO pins may be used to convey information from a slave node 104 to the master node 102 (e.g., by having the master node 102 poll the GPIO pins over I2C, or by having a node transceiver 120 of a slave node 104 generate an interrupt at an interrupt request pin).
  • a host 110 may send information to the master node 102 via I2C, and then the master node 102 may send that information to the slave via the GPIO pins.
  • Any of the types of data discussed herein as transmitted over the bus 106 may be transmitted using any one or more of these communication pathways. Other types of data and data communication techniques within the system 100 may be disclosed herein.
  • FIG. 13 schematically illustrates a device 1300 that may serve as a host or a node (e.g., a host 110 , a master node 102 , or a slave node 104 ) in the system 100 , in accordance with various embodiments.
  • a device 1300 may serve as a host or a node (e.g., a host 110 , a master node 102 , or a slave node 104 ) in the system 100 , in accordance with various embodiments.
  • a number of components are illustrated in FIG. 13 as included in the device 1300 , but any one or more of these components may be omitted or duplicated, as suitable for the application.
  • the device 1300 may not include one or more of the components illustrated in FIG. 13 , but the device 1300 may include interface circuitry for coupling to the one or more components.
  • the device 1300 may not include a display device 1306 , but may include display device interface circuitry (e.g., a connector and driver circuitry) to which a display device 1306 may be coupled.
  • the device 1300 may not include an audio input device 1324 or an audio output device 1308 , but may include audio input or output device interface circuitry (e.g., connectors and supporting circuitry) to which an audio input device 1324 or audio output device 1308 may be coupled.
  • the device 1300 may include the node transceiver 120 , in accordance with any of the embodiments disclosed herein, for managing communication along the bus 106 when the device 1300 is coupled to the bus 106 .
  • the device 1300 may include a processing device 1302 (e.g., one or more processing devices), which may be included in the node transceiver 120 or separate from the node transceiver 120 .
  • processing device may refer to any device or portion of a device that processes electronic data from registers and/or memory to transform that electronic data into other electronic data that may be stored in registers and/or memory.
  • the processing device 1302 may include one or more digital signal processors (DSPs), application-specific integrated circuits (ASICs), central processing units (CPUs), graphics processing units (GPUs), cryptoprocessors, or any other suitable processing devices.
  • DSPs digital signal processors
  • ASICs application-specific integrated circuits
  • CPUs central processing units
  • GPUs graphics processing units
  • cryptoprocessors or any other suitable processing devices.
  • the device 1300 may include a memory 1304 , which may itself include one or more memory devices such as volatile memory (e.g., dynamic random access memory (DRAM)), non-volatile memory (e.g., read-only memory (ROM)), flash memory, solid state memory, and/or a hard drive.
  • volatile memory e.g., dynamic random access memory (DRAM)
  • non-volatile memory e.g., read-only memory (ROM)
  • flash memory solid state memory
  • solid state memory solid state memory
  • the memory 1304 may be employed to store a working copy and a permanent copy of programming instructions to cause the device 1300 to perform any suitable ones of the techniques disclosed herein.
  • machine-accessible media including non-transitory computer-readable storage media
  • methods, systems, and devices for performing the above-described techniques are illustrative examples of embodiments disclosed herein for communication over a two-wire bus.
  • a computer-readable media e.g., the memory 1304
  • the device 1300 may include another communication chip 1312 (e.g., one or more other communication chips).
  • the communication chip 1312 may be configured for managing wireless communications for the transfer of data to and from the device 1300 .
  • wireless and its derivatives may be used to describe circuits, devices, systems, methods, techniques, communications channels, etc., that may communicate data through the use of modulated electromagnetic radiation through a non-solid medium. The term does not imply that the associated devices do not contain any wires, although in some embodiments they might not.
  • the communication chip 1312 may implement any of a number of wireless standards or protocols, including but not limited to Institute for Electrical and Electronic Engineers (IEEE) standards including Wi-Fi (IEEE 802.11 family), IEEE 802.16 standards (e.g., IEEE 802.16-2005 Amendment), Long-Term Evolution (LTE) project along with any amendments, updates, and/or revisions (e.g., advanced LTE project, ultra mobile broadband (UMB) project (also referred to as “3GPP2”), etc.).
  • IEEE 802.16 compatible Broadband Wireless Access (BWA) networks are generally referred to as WiMAX networks, an acronym that stands for Worldwide Interoperability for Microwave Access, which is a certification mark for products that pass conformity and interoperability tests for the IEEE 802.16 standards.
  • the one or more communication chips 1312 may operate in accordance with a Global System for Mobile Communication (GSM), General Packet Radio Service (GPRS), Universal Mobile Telecommunications System (UMTS), High Speed Packet Access (HSPA), Evolved HSPA (E-HSPA), or LTE network.
  • GSM Global System for Mobile Communication
  • GPRS General Packet Radio Service
  • UMTS Universal Mobile Telecommunications System
  • HSPA High Speed Packet Access
  • E-HSPA Evolved HSPA
  • LTE Long Term Evolution
  • EDGE Enhanced Data for GSM Evolution
  • GERAN GSM EDGE Radio Access Network
  • UTRAN Universal Terrestrial Radio Access Network
  • E-UTRAN Evolved UTRAN
  • the one or more communication chips 1312 may operate in accordance with Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Digital Enhanced Cordless Telecommunications (DECT), Evolution-Data Optimized (EV-DO), and derivatives thereof, as well as any other wireless protocols that are designated as 3G, 4G, 5G, and beyond.
  • the communication chip 1312 may operate in accordance with other wireless protocols in other embodiments.
  • the device 1300 may include an antenna 1322 to facilitate wireless communications and/or to receive other wireless communications (such as AM or FM radio transmissions).
  • the communication chip 1312 may manage wired communications using a protocol other than the protocol for the bus 106 described herein. Wired communications may include electrical, optical, or any other suitable communication protocols. Examples of wired communication protocols that may be enabled by the communication chip 1312 include Ethernet, controller area network (CAN), I2C, media-oriented systems transport (MOST), or any other suitable wired communication protocol.
  • Wired communications may include electrical, optical, or any other suitable communication protocols. Examples of wired communication protocols that may be enabled by the communication chip 1312 include Ethernet, controller area network (CAN), I2C, media-oriented systems transport (MOST), or any other suitable wired communication protocol.
  • CAN controller area network
  • I2C I2C
  • MOST media-oriented systems transport
  • the communication chip 1312 may include multiple communication chips. For instance, a first communication chip 1312 may be dedicated to shorter-range wireless communications such as Wi-Fi or Bluetooth, and a second communication chip 1312 may be dedicated to longer-range wireless communications such as GPS, EDGE, GPRS, CDMA, WiMAX, LTE, EV-DO, or others. In some embodiments, a first communication chip 1312 may be dedicated to wireless communications, and a second communication chip 1312 may be dedicated to wired communications.
  • a first communication chip 1312 may be dedicated to shorter-range wireless communications such as Wi-Fi or Bluetooth
  • a second communication chip 1312 may be dedicated to longer-range wireless communications such as GPS, EDGE, GPRS, CDMA, WiMAX, LTE, EV-DO, or others.
  • a first communication chip 1312 may be dedicated to wireless communications
  • a second communication chip 1312 may be dedicated to wired communications.
  • the device 1300 may include battery/power circuitry 1314 .
  • the battery/power circuitry 1314 may include one or more energy storage devices (e.g., batteries or capacitors) and/or circuitry for coupling components of the device 1300 to an energy source separate from the device 1300 (e.g., AC line power, voltage provided by a car battery, etc.).
  • the battery/power circuitry 1314 may include the upstream filtering circuitry 132 and the downstream filtering circuitry 131 discussed above with reference to FIG. 2 and could be charged by the bias on the bus 106 .
  • the device 1300 may include a display device 1306 (or corresponding interface circuitry, as discussed above).
  • the display device 1306 may include any visual indicators, such as a heads-up display, a computer monitor, a projector, a touchscreen display, a liquid crystal display (LCD), a light-emitting diode display, or a flat panel display, for example.
  • the device 1300 may include an audio output device 1308 (or corresponding interface circuitry, as discussed above).
  • the audio output device 1308 may include any device that generates an audible indicator, such as speakers, headsets, or earbuds, for example.
  • the device 1300 may include an audio input device 1324 (or corresponding interface circuitry, as discussed above).
  • the audio input device 1324 may include any device that generates a signal representative of a sound, such as microphones, microphone arrays, or digital instruments (e.g., instruments having a musical instrument digital interface (MIDI) output).
  • MIDI musical instrument digital interface
  • the device 1300 may include a global positioning system (GPS) device 1318 (or corresponding interface circuitry, as discussed above).
  • GPS global positioning system
  • the GPS device 1318 may be in communication with a satellite-based system and may receive a location of the device 1300 , as known in the art.
  • the device 1300 may include another output device 1310 (or corresponding interface circuitry, as discussed above).
  • Examples of the other output device 1310 may include an audio codec, a video codec, a printer, a wired or wireless transmitter for providing information to other devices, or an additional storage device. Additionally, any suitable ones of the peripheral devices 108 discussed herein may be included in the other output device 1310 .
  • the device 1300 may include another input device 1320 (or corresponding interface circuitry, as discussed above).
  • Examples of the other input device 1320 may include an accelerometer, a gyroscope, an image capture device, a keyboard, a cursor control device such as a mouse, a stylus, a touchpad, a bar code reader, a Quick Response (QR) code reader, or a radio frequency identification (RFID) reader.
  • any suitable ones of the sensors or peripheral devices 108 discussed herein may be included in the other input device 1320 .
  • any suitable ones of the display, input, output, communication, or memory devices described above with reference to the device 1300 may serve as the peripheral device 108 in the system 100 .
  • suitable ones of the display, input, output, communication, or memory devices described above with reference to the device 1300 may be included in a host (e.g., the host 110 ) or a node (e.g., a master node 102 or a slave node 104 ).
  • FIGS. 14-19 illustrate systems and techniques for providing diagnostic and control information within various embodiments of the system 100 .
  • FIGS. 14-19 illustrate audio systems to which the diagnostic and control techniques disclosed herein may be applied. Describing these techniques with respect to audio systems is simply illustrative, and the systems and techniques disclosed herein may be applied to diagnostics and control for any suitable peripheral devices.
  • FIG. 14 is a block diagram of an example arrangement of audio components and sensors in an embodiment of the system 100 , in accordance with various embodiments. Arrangements like that depicted in FIG. 14 may be particularly useful for managing audio in a vehicle or other enclosed space.
  • the host 110 and/or the master node 102 may be included in a head unit or vehicle function box, for example, and the links of the bus 106 may be routed through the walls, seats, floor, seatbelt, and other structures in the vehicle cabin.
  • the system 100 of FIG. 14 includes a number of slave nodes 104 (i.e., the slave nodes 0 - 7 ) daisy-chained along the bus 106 .
  • Each slave node 104 may be coupled to a peripheral device 108 .
  • the peripheral device 108 associated with the slave node 0 may include a sensor 0 .
  • the slave node 0 may be located within or behind a vehicle dashboard, and the sensor 0 may include an environmental sensor, such as a moisture or gas sensor, and/or a microphone.
  • the peripheral device 108 associated with the slave node 1 may include a sensor 1 , a speaker 11 , and a speaker 12 .
  • the slave node 1 and its peripheral device 108 may be located within or near a front passenger side door.
  • the peripheral device 108 associated with the slave node 2 may include a speaker 21 .
  • the slave node 2 and its peripheral device 108 may be located within or near a rear passenger side door.
  • the peripheral device 108 associated with the slave node 3 may include a sensor 3 .
  • the slave node 3 may be located behind a rear passenger seat, and the sensor 3 may include an environmental sensor and/or a microphone.
  • the peripheral device 108 associated with the slave node 4 may include a speaker 41 , a speaker 42 , and a speaker 43 .
  • the slave node 4 may be located at the center rear of the passenger compartment, and the speakers 41 - 43 may be arranged across the rear of the passenger compartment.
  • the peripheral device 108 associated with the slave node 5 may include a speaker 51 .
  • the slave node 5 and its peripheral device 108 may be located within or near a rear driver side door.
  • the peripheral device 108 associated with the slave node 6 may include a sensor 6 , a speaker 61 , and a speaker 62 .
  • the slave node 6 and its peripheral device 108 may be located within or near a front driver side door.
  • the peripheral device 108 associated with the slave node 7 may include a speaker 71 and a speaker 72 .
  • the slave node 7 and its associated peripheral device 108 may be located in a center console of the passenger compartment.
  • FIG. 15 is a block diagram of a particular example of the arrangement of FIG. 14 , in accordance with various embodiments.
  • some of the slave nodes 104 are shown as embodied in a distributed amplifier device.
  • slave nodes 1 , 2 , 4 , 5 , 6 , and 7 are shown as integrally attached to a speaker (i.e., the speakers 11 , 21 , 41 , 51 , 61 , and 71 , respectively).
  • the distributed amplifier device of slave nodes 1 , 4 , 6 , and 7 are also coupled to at least one additional speaker, as shown in FIG. 15 .
  • FIG. 16 is a block diagram of a distributed amplifier embodiment of the slave node 1 , and its associated peripheral device 108 , from the arrangement of FIG. 15 , in accordance with various embodiments.
  • the slave node 1 may include the node transceiver 120 ( FIG. 2 ), a processing device 1302 ( FIG. 13 ), a memory 1304 ( FIG. 13 ), battery/power circuitry 1314 ( FIG. 13 ), and an audio amplifier 1602 .
  • the audio amplifier 1602 may have multiple outputs, and thus may be able to provide amplified audio signals to multiple speakers (e.g., the speakers 11 and 12 ).
  • the components illustrated in the slave node 104 of FIG. 16 may be included in a common housing, and that housing may have connectors to couple the slave node 104 to the peripheral device 108 .
  • the slave node 1 may be coupled to the speaker 11 and to the speaker 12 via I2S/TDM/PDM connections (e.g., as discussed above with reference to the I2S/TDM/PDM transceiver 127 of the node transceiver 120 ), and to the sensor 1 via an I2C connection (e.g., as discussed above with reference to the I2C transceiver 129 of the node transceiver 120 ).
  • the audio amplifier 1602 may be a peripheral device 108 , regardless of whether or not it is included in a common housing with the node transceiver 120 .
  • FIG. 17 is a flow diagram of a method 1700 for communication of audio system diagnostic information by a slave node 104 , in accordance with various embodiments. While the operations of the method 1700 (and the other methods disclosed herein) are arranged in a particular order in the figures, and illustrated once each, in various embodiments, one or more of the operations may be repeated, omitted, or performed out of order. In particular, various operations of the method 1700 (and other methods disclosed herein), although illustrated as performed in a particular sequence for the sake of illustration, may be performed in parallel as suitable. In the discussion below, operations of the method 1700 (and the other methods disclosed herein) may be described as performed by the slave node 1 of the system 100 of FIG.
  • the operations of the method 1700 may be performed by any suitably configured device (e.g., any suitable ones of the other slave nodes 104 of FIG. 14 ) using the two-wire bus communication techniques disclosed herein.
  • any of the operations of the method 1700 may be performed in accordance with any of the embodiments of the system 100 disclosed herein.
  • a slave node 104 may receive a synchronization control frame 180 .
  • the synchronization control frame 180 may be provided to the slave node 104 over a two-wire bus link 106 from an upstream node (e.g., the master node 102 or an upstream slave node 104 ).
  • the slave node 104 may receive the synchronization control frame 180 via the upstream DS transceiver 122 of the node transceiver 120 .
  • the synchronization control frame 180 received at 1702 may be structured in accordance with any of the embodiments described herein.
  • the slave node 104 may receive audio data.
  • the audio data may be provided to the slave node 104 over the two-wire bus link 106 from the upstream node discussed above with reference to 1702 .
  • the slave node 104 may receive audio data at 1704 subsequent to receiving the synchronization control frame 180 at 1702 .
  • the slave node 104 may receive the audio data via the upstream DS transceiver 122 of the node transceiver 120 .
  • the audio data may be included in the downstream data slots 198 of a superframe 190 , as discussed above with reference to FIG. 4 .
  • the audio data may be encoded using any desired format (e.g., sampled at 44.1 or 48 kHz).
  • the audio data may originate at the host 110 and may be audio data streamed wirelessly to the host 110 or read from a computer readable medium, such as a CD or DVD.
  • the slave node 104 may derive timing information from the synchronization control frame 180 received at 1702 .
  • a preamble 182 may be used to recover a clock signal that can be locked by the PLL 128 of the node transceiver 120 .
  • the upstream DS transceiver 122 and/or the PLL 128 of the transceiver 120 may derive the timing information at 1706 .
  • the slave node 104 may provide the audio data received at 1704 to an audio device (e.g., the speaker 11 or the speaker 12 of FIG. 14 ).
  • the audio device may be coupled to the slave node 104 as a peripheral device 108 .
  • the I2S/TDM/PDM transceiver 127 may provide the audio data to the audio device at 1708 .
  • the audio device may output audio in response to receipt of the audio data.
  • the audio device may include an amplifier and/or a speaker.
  • the slave node 104 may be a distributed amplifier device (as illustrated in FIG. 16 ) and may include an audio amplifier 1602 and one or more speakers.
  • the operations discussed with reference to 1706 and 1708 may be performed at least partially in parallel.
  • the slave node 104 may receive first data representative of an operational characteristic of the audio device to which the audio data was provided at 1708 .
  • operational characteristic may be referred to in the singular
  • one or more operational characteristics may be received by the slave node 104 in the first data at 1710 .
  • the first data may be provided to the slave node 104 by a sensor (e.g., the sensor 1 of FIG. 14 ) coupled to the slave node 104 as a peripheral device 108 .
  • the I2C transceiver 129 may receive the first data at 1710 .
  • the sensor that provides the first data may be a standalone sensor, an integrated sensor (e.g., integrated fault detection circuitry), or any other suitable sensor for providing operational information about the audio device (e.g., using techniques known in the art).
  • the sensor may include a detection circuit that analyzes the output of the audio device for operational characteristics (e.g., clipping).
  • the first data may be received at 1710 in a synchronization control frame, a synchronization response frame, data following a synchronization control/response frame, via GPIO pins, or via any other suitable communication pathway in the system 100 .
  • the operational characteristic of 1710 may include an acoustic response indicative of a blocked speaker vent (when the audio device includes a vented speaker) or an acoustic response indicative of a blocked speaker (representative of a mechanical or acoustic blocking of the natural movement of the transducer of a speaker).
  • the sensor may be a mechanical or thermal sensor that detects the operational characteristic in any suitable manner.
  • the operational characteristic of 1710 may include a speaker surround failure (e.g., acoustic response indicative thereof), a speaker diaphragm failure (e.g., an acoustic response indicative thereof), a speaker enclosure failure (e.g., an acoustic response indicative thereof), a reversed speaker wire polarity (e.g., an acoustic response indicative thereof), a disconnected speaker wire (e.g., an acoustic response indicative thereof), or a speaker short.
  • the sensor may be a mechanical or electrical sensor that detects the operational characteristic in any suitable manner.
  • the operational characteristic of 1710 may include an audio amplifier clipping, an audio amplifier overheating, or an audio amplifier failure.
  • the sensor may be a mechanical, electrical, or thermal sensor that detects the operational characteristic in any suitable manner.
  • the operational characteristic of 1710 may include a power-related characteristic, such as a voltage of a battery supplying the audio device.
  • the sensor may be an electrical sensor that detects the operational characteristic in any suitable manner.
  • the operational characteristic may include an impedance, a resonant frequency, or an acoustic box leakage.
  • the sensor may be an electrical or mechanical sensor that detects the operational characteristic in any suitable manner.
  • the operational characteristic of 1710 may include a voice coil temperature, a speaker overcurrent, or a speaker over excursion.
  • the sensor may be an electrical, mechanical, or thermal sensor that detects the operational characteristic in any suitable manner.
  • the slave node 104 may provide a synchronization response frame 197 over the two-wire upstream bus link 106 toward an upstream node (e.g., the master node 102 or an upstream slave node 104 ).
  • the slave node 104 may provide the synchronization response frame 197 via the upstream DS transceiver 122 of the node transceiver 120 .
  • the timing of the provision of the synchronization response frame at 1712 may use the timing information derived at 1706 ; in particular, the slave node 104 may time the provision of the synchronization response frame at 1712 using a clock based on the timing information.
  • the synchronization response frame 197 provided at 1712 may be structured in accordance with any of the embodiments described herein.
  • the slave node 104 may provide second data representative of the operational characteristic of the audio device (discussed above with reference to 1710 ) over the two-wire upstream bus link 106 toward an upstream node (e.g., the master node 102 or an upstream slave node 104 ).
  • the slave node 104 may provide the second data via the upstream DS transceiver 122 of the node transceiver 120 .
  • the second data may be included in the upstream data slots 199 of a superframe 190 , as discussed above with reference to FIG. 4 .
  • the slave node 104 may provide the second data at 1714 subsequent to providing the synchronization response frame 197 at 1712 .
  • the second data may be transmitted through the system 100 to the host 110 ; in other embodiments, the second data to be received and processed by the master node 102 and/or another upstream slave node (e.g., the slave node 0 of FIG. 14 ) instead of or in addition to the host 110 .
  • the second data may be provided at 1714 in a synchronization response frame, data following a synchronization response frame, via GPIO pins, or via any other suitable communication pathway in the system 100 .
  • the first data of 1710 may encode the operational characteristic of the audio device using a first encoding scheme
  • the second data 1714 may encode the operational characteristic of the audio device using a second, different encoding scheme.
  • a sensor coupled to the slave node 104 may provide the first data using a sensor-specific format over an I2C bus, while the slave node 104 may provide the second data upstream on the bus 106 in accordance with the encoding techniques discussed herein and in any desired format (e.g., a format that is readily parsed by the host 110 upon receipt of the second data).
  • the first data of 1710 may be “raw” or minimally processed operational characteristic data from a sensor, while the second data of 1714 may represent the operational characteristic in a more processed form.
  • the second data may represent an averaged or otherwise filtered version of the first data.
  • the second data may represent the result of comparing the first data against a threshold; for example, the first data may include a voice coil temperature value, and the second data may include a binary indicator of whether the voice coil temperature value exceeds a predetermined threshold (e.g., an acceptable temperature threshold).
  • Processing performed on the first data of 1710 to generate the second data of 1714 may be performed by the processing device 1302 and/or the node transceiver 120 .
  • the first data of 1710 may be identical to the second data of 1714 .
  • the method 1700 is carried out by the slave node 1 of FIG. 14 .
  • the slave node 1 may receive a synchronization control frame 180 provided downstream on the bus 106 by the slave node 0 .
  • the synchronization control frame 180 may originate at the master node 102 and may be passed downstream from slave node 104 to slave node 104 .
  • the slave node 1 may receive audio data provided downstream on the bus 106 by the slave node 0 .
  • the audio data may originate at the host 110 and may be provided to the master node 102 via an I2S/TDM bus, for example.
  • the audio data may be provided to the slave node 0 from the master node 102 , and the slave node 0 may relay the audio data to the slave node 1 (e.g., in the downstream data slots 198 ). In some embodiments, the audio data may be consumed by the slave node 1 , while in other embodiments, the slave node 1 may provide the audio data further downstream along the bus 106 to the other slave nodes 104 .
  • the node transceiver 120 of the slave node 1 may derive timing information from the synchronization control frame 180 .
  • the PLL 128 may generate a local clock based on the preamble 182 of the synchronization control frame 180 . This local clock may be used to time further communications on the bus 106 (e.g., the provision of a synchronization response frame at 1712 , discussed below).
  • the slave node 1 may provide the audio data received at 1704 to the speaker 11 and/or the speaker 12 .
  • the slave node 1 may include an audio amplifier (e.g., the audio amplifier 1602 ) and may provide the audio data to the speaker 11 and/or the speaker 12 via the audio amplifier.
  • the processing device 1302 in the slave node 1 may selectively delay and/or amplify the audio data prior to provision to the speaker 11 and/or the speaker 12 in order to achieve a desired audio effect.
  • the inputs to the speakers 11 and 12 may be selected so that interference between the outputs of the speakers 11 , 12 , and other speakers in the system 100 causes an acoustic null at a desired location.
  • the inputs of the speakers 11 and 12 may be selected so that interference between the output of the speakers 11 , 12 , and other speakers in the system 100 causes additive interference at a desired location.
  • the selective delay and/or amplification of the inputs to a speaker included in the peripheral device 108 may be controlled by a control instruction from the host 110 or one or more processing devices 1302 distributed among the master node 102 and/or the slave nodes 104 of the system 100 , as discussed in further detail below.
  • the slave node 1 may receive first data representative of an operational characteristic of the speaker 11 and/or the speaker 12 from a sensor.
  • a sensor may be referred to herein in the singular
  • a slave node 104 may receive data at 1710 from one or more sensors.
  • the sensor may be coupled to the slave node 1 as a peripheral device 108 associated with the slave node 1 .
  • the sensor may be the sensor 1 , and may be configured to detect an electrical fault in the speaker 11 and/or the speaker 12 (e.g., a speaker short or a disconnected speaker wire).
  • the slave node 1 may receive the first data from the sensor 1 via an I2C bus managed by the I2C transceiver 129 ( FIG. 2 ).
  • the senor may be coupled to another slave node 104 in the system 100 (e.g., the sensor 3 or the sensor 6 ).
  • the sensor may be the sensor 3 and may be configured to detect acoustic box leakage from the speaker 11 and/or the speaker 12 .
  • the slave node 1 may receive the first data from the sensor 3 via an I2C bus connection between the sensor 3 and the slave node 3 , and upstream communication on the bus 106 between the slave node 3 and the slave node 1 .
  • the slave node 1 may provide a synchronization response frame 197 upstream on the bus 106 to the slave node 0 .
  • the synchronization response frame 197 may originate at a last slave node of the system 100 (e.g., the slave node 7 of FIG. 14 ).
  • the timing of the provision of the synchronization response frame 197 may be governed by the clock generated by the PLL 128 of the node transceiver 120 .
  • the slave node 1 may provide second data representative of the operational characteristic of the speaker 11 and/or the speaker 12 upstream on the bus 106 .
  • the second data may be based on the first data received at 1710 , as discussed above with reference to 1714 .
  • the second data may be provided in the upstream data slots 199 along with data originating at the slave nodes 2 - 7 and communicated upstream on the bus 106 .
  • the second data may be destined for the host 110 , while in other embodiments, the second data may be consumed by nodes upstream of the slave node 1 (e.g., the slave node 0 or the master node 102 ).
  • the second data representative of the operational characteristic of the speaker 11 and/or the speaker 12 may be used to generate control instructions to control the operation of the speaker 11 , the speaker 12 , and/or any of the other peripheral devices 108 in the system 100 .
  • FIG. 18 is a flow diagram of a method 1800 for communication of audio system diagnostic information and control by a host 110 , in accordance with various embodiments.
  • operations of the method 1800 may be described as performed by the host 110 of the system 100 of FIG. 14 for illustrative purposes, but the operations of the method 1800 , including individual operation of the method 1800 , may be performed by any suitably configured device (using the two-wire bus communication techniques disclosed herein). In particular, any of the operations of the method 1800 may be performed in accordance with any of the embodiments of the system 100 disclosed herein.
  • the host 110 may provide audio data to the master node 102 for provision along the bus 106 to a slave node 104 .
  • the audio data is to be output by an audio device coupled to the slave node 104 (e.g., as a peripheral device 108 ).
  • the host 110 may provide the audio data to the master node 102 at 1802 via an I2S/TDM bus (using an I2S/TDM transceiver included in the host 110 ), and the master node 102 may receive the audio data via the I2S/TDM/PDM transceiver 127 .
  • the master node 102 may provide the audio data to the bus 106 in the downstream data slots 198 of a superframe 190 , and the audio data may pass through any intervening slave nodes 104 between the master node 102 and the target slave node 104 .
  • the audio data may be encoded using any desired format (e.g., sampled at 44.1 or 48 kHz).
  • the audio data may be streamed wirelessly to the host 110 or read from a computer readable medium, such as a CD or DVD, prior to the host 110 providing the audio data to the master node 102 at 1802 .
  • the audio data provided by the host 110 at 1802 may be provided to multiple slave nodes 104 , each of which may include an audio device configured to output the audio data upon receipt.
  • the host 110 may receive, via the bus 106 and the master node 102 , data representative of an operational characteristic of the audio device of 1802 .
  • the host 110 may receive the data at 1804 using any suitable communication pathway(s) within the system 100 .
  • the host 110 may receive the data representative of the operational characteristic via an I2C bus between the host 110 and the master node 102 (e.g., using an I2C transceiver included in the host 110 ).
  • the master node 102 may provide the data representative of the operational characteristic to the host 110 using the I2C transceiver 129 .
  • the data representative of the operational characteristic of the audio device may be based on data generated by a sensor coupled to the slave node 104 of 1802 or any other slave node 104 .
  • the data representative of the operational characteristic of the audio device may take the form of any of the embodiments discussed above with reference to 1710 of FIG. 17 .
  • the data received at 1804 may be first data and may be based on second data representative of the operational characteristic of the audio device provided to the master node 102 over the bus 106 from a slave node 104 .
  • the slave node 104 may be associated with the audio device, or it may be a different audio device.
  • the second data may be generated by a sensor coupled to the slave node 104 associated with the audio device or a slave node 104 that is not coupled to the audio device.
  • the second data may be provided to the master node 102 along with a synchronization response frame 197 .
  • the synchronization response frame 197 may be generated by a last slave node 104 on the bus 106 (e.g., the slave node 7 of FIG. 14 ).
  • the second data may be provided to the master node 102 in the upstream data slots 199 of a superframe 190 , as discussed above with reference to FIG. 4 .
  • the relationship between the first and second data may take the form of any of the embodiments discussed above with reference to FIG. 17 .
  • the first and second data may be the same.
  • the host 110 may provide a control instruction for the audio device to the master node 102 for transmission downstream over the bus 106 .
  • the master node 102 may transmit data representative of the control instruction to the slave node 104 over the bus 106 (e.g., in a synchronization control frame, in data following a synchronization control frame, via GPIO pins, or using any other suitable communication pathway).
  • the host 110 may generate the control instruction based on the operational characteristic of the audio device received at 1804 , and, in some embodiments, execution of the control instruction by the audio device or its associated slave node 104 may change the operational characteristic of the audio device.
  • the control instruction may require the audio device to reduce its power consumption and thereby decrease its temperature.
  • the operations discussed above with reference to 1806 may not be performed; instead, the method may end with the operations discussed above with reference to 1804 .
  • the method 1800 may include further operations.
  • the host 110 may provide a control instruction for a first audio device based on an operational characteristic of a second, different audio device.
  • the second audio device may be coupled to a same slave node 104 as the first audio device or a different slave node 104 .
  • the host 110 may include display interface circuitry (e.g., as discussed above with reference to the display device 1306 of FIG. 13 ) that is configured to provide a visual indicator of the operational characteristic of the audio device to a display device 1306 in communication with the host 110 .
  • a visual indicator may be useful, for example, to alert a driver of a vehicle that a peripheral device 108 coupled to the bus 106 is experiencing a fault or is operating normally.
  • This visual indicator may include a text display, an icon, or any other suitable visual indicator.
  • the host 110 may include audio output device interface circuitry (e.g., as discussed above with reference to the audio output device 1308 of FIG. 13 ) that is configured to provide an audible indicator of the operational characteristic of the audio device.
  • the host 110 may receive, via the bus 106 and the master node 102 , data representative of a measurement made by a seat pressure sensor, a proximity sensor, a light sensor, a moisture sensor, a gesture sensor, or another environmental sensor coupled to a slave node 104 .
  • the host 110 may receive this measurement data along with the operational characteristic data received at 1804 (e.g., in the upstream data slots 199 ).
  • the host 110 may receive the measurement data via an I2C bus between the host 110 and the master node 102 (e.g., using an I2C transceiver included in the host 110 ).
  • the master node 102 may provide the measurement data to the host 110 using the I2C transceiver 129 .
  • the data representative of the operational characteristic of the audio device may be based on data generated by a sensor coupled to the slave node 104 of 1802 or any other slave node 104 .
  • the host 110 may then provide a control instruction to the audio device (e.g., as part of 1806 ) based at least in part on this measurement data.
  • the host 110 may use the measurement data from a seat pressure sensor to provide a control instruction to power down audio devices (e.g., speakers and/or microphones) proximate to an empty seat in order to conserve power.
  • the host 110 may use the measurement data from a seat pressure sensor to determine that no passenger is seated in a particular location in the vehicle and thus that audio interference that occurs at that location need not be carefully controlled when active noise cancellation control instructions are provided.
  • the host 110 when the host 110 is performing active noise cancellation within the passenger compartment of a vehicle, the host 110 may use the measurement data from a seat pressure sensor to determine that a passenger is seated in a particular location in the vehicle and, in response, to provide a control instruction to adjust and operating characteristics of a speaker (e.g., the speaker driving current) to achieve noise cancellation for that passenger.
  • a speaker e.g., the speaker driving current
  • the host 110 determines that a microphone coupled to a slave node 104 is generating little to no output
  • the measurement data generated by a seat pressure sensor in a seat proximate to the microphone may aid the host 110 in determining that the microphone is not failing (rather, there is simply no passenger proximate to the microphone and generating sound).
  • the host 110 may use measurement data from a proximity sensor (e.g., a capacitive sensor or infrared sensor) to determine how close a passenger in a vehicle is to an audio device (e.g., a speaker or microphone) and to provide a control instruction to that audio device to scale its output or amplification appropriately (e.g., to reduce the power output to a speaker very close to a passenger).
  • a proximity sensor e.g., a capacitive sensor or infrared sensor
  • the host 110 may use measurement data from a proximity sensor to track a position of a passenger within a vehicle in order to appropriately locate the noise cancellation nulls when active noise cancellation control instructions are provided.
  • the host 110 may use measurement data from a light sensor in the same manner as discussed above with reference to a seat pressure sensor when the light sensor is configured to indicate seat occupancy (e.g., when interruption of a light beam indicates the presence of a passenger in a seat).
  • the host 110 may use measurement data from a light sensor to adjust the brightness of a display (e.g., a display of an operational characteristic of an audio device).
  • the host 110 may use measurement data from a moisture sensor to determine when a defogger or other environmental control system should be turned on, and thus when to activate a noise cancellation system to cancel the noise generated by the environmental control system.
  • the host 110 may use measurement data from a gesture sensor (e.g., a video camera or other sensor for tracking the motion of a passenger's hands) for user interface purposes (e.g., to provide a control instruction to a slave node 104 to reduce the output volume of an associated speaker when a user performs a predetermined volume reduction gesture).
  • a gesture sensor e.g., a video camera or other sensor for tracking the motion of a passenger's hands
  • Microphones included as peripheral devices 108 may also be used to receive voice instructions, which may be processed and recognized by the host 110 .
  • the method 1800 is carried out by the host 110 of FIG. 14 .
  • the host 110 may provide audio data to the master node 102 for provision along the bus 106 to the slave node 4 for output at the speaker 41 .
  • the host 110 may receive, via the bus 106 and the master node 102 , data representative of an operational characteristic of the speaker 41 . That data may include a measurement by a microphone included in the sensor 6 (associated with the slave node 6 ) of a test tone generated by the speaker 41 .
  • the data may represent a maximum amplitude of an audio signal detected by the microphone in the sensor 6 in response to a test tone generated by the speaker 41 .
  • the sensor 6 may provide the microphone measurement to the slave node 6 as representative of an operational characteristic of the speaker 41 (e.g., via the I2C transceiver 129 of the node transceiver 120 in the slave node 6 ).
  • the slave node 6 may optionally process the measurement provided by the sensor 6 and may provide data representative of the operational characteristic of the speaker 41 over the bus 106 , through the intervening slave nodes 0 - 5 , to the master node 102 .
  • the master node 102 may provide the data to the host 110 (e.g., via the I2C transceiver 129 of the node transceiver 120 of the master node 102 ).
  • the host 110 may provide a power increase control instruction for the speaker 41 to the master node 102 (e.g., to increase the maximum amplitude of audio signals detected by the microphone and the sensor 6 for a distributed amplification application).
  • the master node 102 may provide the control instruction over the bus 106 through the intervening slave nodes 0 - 3 to the slave node 4 .
  • the slave node 4 may itself increase the power provided to the speaker 41 in response to the control instruction, or the slave node 4 may provide the control instruction to the speaker 41 to cause a power increase.
  • FIG. 19 is a flow diagram of a method 1900 for audio system control by a slave node 104 , in accordance with various embodiments.
  • operations of the method 1900 may be described as performed by the slave node 1 of the system 100 of FIG. 14 (and with reference to other particular slave nodes and peripheral devices) for illustrative purposes, but the operations of the method 1900 , including individual operation of the method 1900 , may be performed by any suitably configured device (using the two-wire bus communication techniques disclosed herein).
  • any of the operations of the method 1900 may be performed in accordance with any of the embodiments of the system 100 disclosed herein.
  • a slave node 104 may perform the method 1700 and the method 1900 in an integrated manner.
  • the slave node 104 may provide a synchronization response frame 197 upstream over the bus 106 .
  • the slave node 104 may be coupled to a first audio device (e.g., the speaker 11 or the speaker 12 of FIG. 14 ).
  • the synchronization response frame 197 of 1902 may take the form of any of the embodiments disclosed herein.
  • the slave node 104 may provide data upstream that is representative of an operational characteristic of a second audio device, wherein the second audio device is coupled to a downstream slave node 104 (e.g., the speaker 51 associated with the slave node 5 ).
  • the data representative of the operational characteristic of the second audio device may be provided subsequent to provision of the synchronization response frame 197 ( 1902 ); for example, the data representative of the operational characteristic of the second audio device may be provided in the upstream data slots 199 of the superframe 190 .
  • the slave node 104 may receive the data from a downstream slave node 104 (which may be a same slave node as associated with the second audio device, or a different slave node). For example, a sensor coupled to a slave node 104 may generate the data, and that slave node 104 may provide the data upstream via the bus 106 (e.g., in accordance with any of the embodiments discussed above with reference to 1710 of FIG. 17 ).
  • the data provided at 1904 may be provided using any suitable communication pathway in the system 100 (e.g., in a synchronization response frame, in data following a synchronization response frame, via GPIO pins, etc.).
  • the slave node 104 may receive a synchronization control frame 180 .
  • the slave node 104 may receive the synchronization control frame 180 from an upstream node (e.g., the master node 102 or and intervening slave node 104 ).
  • the operations associated with 1906 may be performed in accordance with any of the embodiments of the operations associated with 1702 of FIG. 17 .
  • the slave node 104 may recover a clock signal from the synchronization control frame 180 .
  • the PLL 128 may lock to the recovered clock signal, as discussed above with reference to FIG. 2 .
  • the operations associated with 1908 may be performed in accordance with any of the embodiments of the operations associated with 1706 of FIG. 17 .
  • the slave node 104 may receive, from an upstream node (e.g., the master node 102 or an upstream slave node 104 ), a control instruction for the first audio device.
  • the control instruction may be based on the operational characteristic of the second audio device (provided upstream at 1904 ).
  • the slave node 104 may receive the control instruction at 1910 subsequent to receiving the synchronization control frame at 1906 ; in some embodiments, the control instruction may be provided in the downstream data slots 198 after the synchronization control frame 180 .
  • the control instruction may originate from the host 110 , as discussed above with reference to FIG. 18 .
  • Execution of the control instruction by the slave node 104 may change an operational characteristic of the first audio device associated with the slave node 104 .
  • operational characteristics of one audio device coupled to the bus 106 may be used to generate control instructions for another audio device coupled to the bus 106 .
  • the first and second audio devices may be speakers
  • the operational characteristic of the second speaker may be a temperature of the second speaker
  • a control instruction may cause the first speaker to increase its speaker driving current (and thereby increase its temperature), with this control instruction possibly accompanied by a control instruction to the second speaker to decrease its speaker driving current (e.g., in a distributed amplification application).
  • the host 110 may use data representative of a first operational characteristic of a first audio device to generate a control instruction to affect a second, different operational characteristic of a second audio device.
  • the control instruction may be received at 1910 via any suitable ones of the communication pathways disclosed herein.
  • the method 1900 is carried out by the slave node 2 of FIG. 14 .
  • the slave node 2 may provide a synchronization response frame 197 upstream to the slave node 1 .
  • the slave node 2 may be coupled to a speaker 21 as a peripheral device 108 .
  • the slave node 2 may provide data upstream that is representative of an operational characteristic of the speaker 43 associated with the slave node 4 . This data may be, for example, an indication that the voice coil of the speaker 43 has exited its magnetic gap and thus has undergone an over-excursion.
  • the over-excursion may be detected by circuitry included in the speaker 43 (e.g., fault detection circuitry) and may be provided to the I2C transceiver 129 of the node transceiver 120 of the slave node 4 .
  • the slave node 4 may push this data onto the bus 106 (e.g., in the upstream data slots 199 ), the slave node 3 may provide the data to the slave node 2 , and the slave node 2 may provide the data upstream at 1904 .
  • the slave node 2 may receive a synchronization control frame 180 from the slave node 1 .
  • the slave node 2 may recover a clock signal from the synchronization control frame 180 received at 1906 (e.g., as discussed above with reference to FIG. 3 ).
  • the slave node 2 may receive, from the slave node 1 , a control instruction for the speaker 21 .
  • the control instruction may be generated by the host 110 or a node upstream of the slave node 2 (e.g., the master node 102 , the slave node 0 , or the slave node 1 ), and may be based on the operational characteristic of the speaker 43 .
  • the host 110 may determine that the speaker 43 should be taken “offline” and no longer used to generate audio output; to compensate for the loss of the speaker 43 , the host 110 may provide a control instruction to the slave node 2 to increase the power of the speaker 21 .
  • Example 1 is a slave device for two-wire low-latency communication of audio system diagnostic information, including: first circuitry to: receive a synchronization control frame provided over a two-wire bus link to the slave device from an upstream device, subsequent to receipt of the synchronization control frame, receive audio data communicated over the two-wire bus link to the slave device from the upstream device, provide a synchronization response frame over the two-wire bus link toward the upstream device, and subsequent to provision of the synchronization response frame, provide, over the two-wire bus link toward the upstream device, first data representative of an operational characteristic of an audio device coupled to the slave device; second circuitry to derive timing information from the synchronization control frame, wherein the timing information is used to time the provision of the synchronization response frame; and third circuitry to: provide the audio data to the audio device, and receive, from a sensor coupled to the slave device, second data representative of the operational characteristic of the audio device.
  • Example 2 may include the subject matter of Example 1, and may further specify that the first data encodes the operational characteristic of the audio device using a first encoding scheme, and the second data encodes the operational characteristic of the audio device using a second encoding scheme different from the first encoding scheme.
  • Example 3 may include the subject matter of any of Examples 1-2, and may further specify that the third circuitry is to receive the second data via an I2C bus.
  • Example 4 may include the subject matter of any of Examples 1-3, and may further specify that the operational characteristic of the audio device includes an acoustic response indicative of a blocked speaker vent or an acoustic response indicative of a blocked speaker.
  • Example 5 may include the subject matter of any of Examples 1-4, and may further specify that the operational characteristic of the audio device includes a speaker surround failure, a speaker diaphragm failure, a speaker enclosure failure, a reversed speaker wire polarity, a disconnected speaker wire, or a speaker short.
  • Example 6 may include the subject matter of any of Examples 1-5, and may further specify that the first circuitry is to receive a control instruction for the audio device, and wherein execution of the control instruction is to change the operational characteristic of the audio device.
  • Example 7 may include the subject matter of any of Examples 1-6, and may further specify that the audio device includes an amplifier and a speaker.
  • Example 8 may include the subject matter of any of Examples 1-7, and may further specify that the operational characteristic includes an audio amplifier clipping, an audio amplifier overheating, or an audio amplifier failure.
  • Example 9 may include the subject matter of any of Examples 1-8, and may further specify that the first, second, and third circuitry are included in a common housing with an audio amplifier.
  • Example 10 is a host device for two-wire low-latency communication of audio system diagnostic information, including: first circuitry to provide audio data to a master device, wherein the master device is a master of a half-duplex two-wire bus, wherein the audio data is to be provided over the two-wire bus to a slave device, and wherein the audio data is to be output by an audio device coupled to the slave device; and second circuitry to receive, from the master device, first data representative of an operational characteristic of the audio device, wherein second data representative of the operational characteristic of the audio device is provided to the master device over the two-wire bus along with a synchronization response frame generated by a last slave device on the two-wire bus.
  • Example 11 may include the subject matter of Example 10, and may further specify that the first data is the same as the second data.
  • Example 12 may include the subject matter of any of Examples 10-11, and may further specify that the operational characteristic of the audio device includes a battery voltage.
  • Example 13 may include the subject matter of any of Examples 10-12, and may further specify that the operational characteristic of the audio device includes an impedance, a resonant frequency, or an acoustic box leakage.
  • Example 14 may include the subject matter of any of Examples 10-13, and may further specify that the second circuitry is to provide, to the master device, a control instruction for the audio device, wherein the master device is to transmit data representative of the control instruction to the slave device along the two-wire bus, and the host device is to generate the control instruction based on the operational characteristic of the audio device.
  • Example 15 may include the subject matter of any of Examples 10-14, and may further specify that: the slave device is a first slave device; the audio device is a first audio device; the second circuitry is to provide current to the master device, a control instruction for a second audio device, wherein the second audio device is coupled to a second slave device along the two-wire bus; the master device is to transmit data representative of the control instruction to the second slave device along the two-wire bus; and the host device is to generate a control instruction based on the operational characteristic of the first slave device.
  • Example 16 may include the subject matter of Example 15, and may further specify that the control instruction is a distributed amplification control instruction.
  • Example 17 may include the subject matter of any of Examples 15-16, and may further include display interface circuitry to provide a visual indicator of the operational characteristic of the audio device to a display device.
  • Example 18 is one or more non-transitory computer readable media having instructions thereon that, in response to execution by one or more processing devices of a host device, cause the host device to: subsequent to provision by the host device of audio data to a master device on a two-wire bus, receive, from the master device, first data representative of an operational characteristic of an audio device, wherein the audio data is to be transmitted along the two-wire bus to a slave device, the audio device is coupled to the slave device, the audio data is to be output by the audio device, and second data representative of the operational characteristic of the audio device is provided to the master device along with a synchronization response frame generated by a last slave device on the two-wire bus; and in response to receipt of the first data representative of the operational characteristic of the audio device, provide a control instruction for the audio device to the master device, wherein the master device is to transmit data representative of the control instruction to the slave device along the two-wire bus, and wherein execution of the control instruction is to change the operational characteristic of the audio device.
  • Example 19 may include the subject matter of Example 18, and may further specify that the slave device is the last slave device.
  • Example 20 may include the subject matter of any of Examples 18-19, and may further specify that the operational characteristic of the audio device includes a voice coil temperature, a speaker overcurrent, or a speaker over-excursion.
  • Example 21 may include the subject matter of any of Examples 18-20, and may further specify that: the host device is included in a passenger vehicle; the slave device is a first slave device; the instructions, in response to execution by the one or more processing devices of the host device, cause the host device to receive, from the master device, third data representative of a measurement made by a sensor coupled to a second slave device on the two-wire bus, wherein the second slave device is different from the first slave device; the sensor includes a seat pressure sensor, a proximity sensor, a light sensor, a moisture sensor, or a gesture sensor; and the control instruction is based at least in part on the third data.
  • Example 22 may include the subject matter of Example 21, and may further specify that the operational characteristic of the audio device is a speaker driving current, the sensor includes a seat pressure sensor for a seat, and the control instruction is to adjust the speaker driving current to achieve noise cancellation for a passenger in the seat.
  • the operational characteristic of the audio device is a speaker driving current
  • the sensor includes a seat pressure sensor for a seat
  • the control instruction is to adjust the speaker driving current to achieve noise cancellation for a passenger in the seat.
  • Example 23 is a method for low-latency control of an audio system, including: providing, by a first slave device on a two-wire bus, a synchronization response frame over a link of the two-wire bus toward an upstream device, wherein the first slave device is coupled to a first audio device; subsequent to providing the synchronization response frame, providing, by the first slave device over the link of the two-wire bus toward the upstream device, data representative of an operational characteristic of a second audio device coupled to a second slave device on the two-wire bus, wherein the second slave device is downstream of the first slave device; receiving, by the first slave device, a synchronization control frame from the upstream device over the link of the two-wire bus; recovering, by the first slave device, a clock signal from the synchronization control frame; and subsequent to receiving the synchronization control frame, receiving, by the first slave device from the upstream device over the link of the two-wire bus, a control instruction for the first audio device, wherein execution of the control instruction is to change an operational characteristic of the first
  • Example 24 may include the subject matter of Example 23, and may further include locking a phase locked loop based on the recovered clock signal.
  • Example 25 may include the subject matter of any of Examples 23-24, and may further specify that the operational characteristic of the second audio device is a temperature of a second speaker, the first audio device includes a first speaker, and wherein the control instruction is to increase a speaker driving current to the first speaker.
  • Example 26 is a device including means for performing any of the methods disclosed herein.
  • Example 27 is one or more computer readable media having instructions thereon that, in response to execution by one or more processing devices of a device, cause the device to perform any of the methods disclosed herein.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Power Engineering (AREA)
  • Automation & Control Theory (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Manufacturing & Machinery (AREA)
  • Small-Scale Networks (AREA)
  • Dc Digital Transmission (AREA)
  • Information Transfer Systems (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Otolaryngology (AREA)
  • Acoustics & Sound (AREA)

Abstract

Disclosed herein are systems and techniques for peripheral device diagnostics and control over a two-wire communication bus. For example, in some embodiments, a slave device may include circuitry to receive a synchronization control frame from an upstream device, receive audio data from the upstream device subsequent to receipt of the synchronization control frame, provide a synchronization response frame toward the upstream device, and provide first data representative of an operational characteristic of an audio device coupled to the slave device subsequent to provision of the synchronization response frame; circuitry to derive timing information from the synchronization control frame; and circuitry to provide the audio data to the audio device, and receive, from a sensor coupled to the slave device, second data representative of the operational characteristic of the audio device.

Description

    CROSS-REFERENCE TO RELATED APPLICATIONS
  • This application claims priority to U.S. patent application Ser. No. 14/063,886, entitled “Two-Wire Communication Protocol Engine” and filed Oct. 25, 2013, which claims priority to U.S. Provisional Application Ser. No. 61/843,891, entitled “A2B Protocol Engine” and filed Jul. 8, 2013; U.S. Provisional Application Ser. No. 61/843,896, entitled “Digital Phase Detector” and filed Jul. 8, 2013; U.S. Provisional Application Ser. No. 61/843,902, entitled “Differential Decoder” and filed Jul. 8, 2013; U.S. Provisional Application Ser. No. 61/845,542, entitled “System and Method for Implementing A2B Protocol” and filed Jul. 12, 2013; U.S. patent application Ser. No. 13/646,397, entitled “Two-Wire Communication System for High-Speed Data and Power Distribution” and filed Oct. 5, 2012; U.S. patent application Ser. No. 13/646,382 (now U.S. Pat. No. 8,990,464), entitled “Methods for Discovery, Configuration, and Coordinating Data Communications Between Master and Slave Devices in a Communication System” and filed Oct. 5, 2012; U.S. Provisional Application No. 61/543,379, entitled “Two-Wire Communication System for High-Speed Data and Power Distribution” and filed Oct. 5, 2011; and U.S. Provisional Application No. 61/543,380, entitled “Two-Wire Communication System for High-Speed Data and Power Distribution” and filed Oct. 5, 2011. This application also claims priority to U.S. Provisional Application No. 62/065,724, entitled “Applications of a Low-Latency Two-Wire Communication System” and filed Oct. 19, 2014; U.S. Provisional Application No. 62/065,736, entitled “Applications of a Low-Latency Two-Wire Communication System” and filed Oct. 19, 2014; and U.S. Provisional Application No. 62/065,738, entitled “Applications of a Low-Latency Two-Wire Communication System” and filed Oct. 19, 2014. The entireties of the disclosures of the prior applications are considered part of and are incorporated by reference in the present disclosure.
  • TECHNICAL FIELD
  • The present disclosure relates generally to communication systems and, more particularly, to peripheral device diagnostics and control over a two-wire communication bus.
  • BACKGROUND
  • As electronic components decrease in size, and as performance expectations increase, more components are included in previously un-instrumented or less-instrumented devices. In some settings, the communication infrastructure used to exchange signals between these components (e.g., in a vehicle) has required thick and heavy bundles of cables.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • Embodiments will be readily understood by the following detailed description in conjunction with the accompanying drawings. To facilitate this description, like reference numerals designate like structural elements. Embodiments are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings.
  • FIG. 1 is a block diagram of an illustrative two-wire communication system, in accordance with various embodiments.
  • FIG. 2 is a block diagram of a node transceiver that may be included in a node of the system of FIG. 1, in accordance with various embodiments.
  • FIG. 3 is a diagram of a portion of a synchronization control frame used for communication in the system of FIG. 1, in accordance with various embodiments.
  • FIG. 4 is a diagram of a superframe used for communication in the system of FIG. 1, in accordance with various embodiments.
  • FIG. 5 illustrates example formats for a synchronization control frame in different modes of operation of the system of FIG. 1, in accordance with various embodiments.
  • FIG. 6 illustrates example formats for a synchronization response frame at different modes of operation of the system of FIG. 1, in accordance with various embodiments.
  • FIG. 7 is a block diagram of various components of the bus protocol circuitry of FIG. 2, in accordance with various embodiments.
  • FIGS. 8-11 illustrate examples of information exchange along a two-wire bus, in accordance with various embodiments of the bus protocols described herein.
  • FIG. 12 illustrates a ring topology for the two-wire bus and a uni-directional communication scheme thereon, in accordance with various embodiments.
  • FIG. 13 schematically illustrates a device that may serve as a node or host in the system of FIG. 1, in accordance with various embodiments.
  • FIG. 14 is a block diagram of an example arrangement of audio components and sensors in a two-wire communication system, in accordance with various embodiments.
  • FIG. 15 is a block diagram of a particular example of the arrangement of FIG. 14, in accordance with various embodiments.
  • FIG. 16 is a block diagram of a distributed amplifier embodiment of an example slave node, and its associated peripheral device, from the arrangement of FIG. 15, in accordance with various embodiments.
  • FIG. 17 is a flow diagram of a method for communication of audio system diagnostic information by a slave node, in accordance with various embodiments.
  • FIG. 18 is a flow diagram of a method for communication of audio system diagnostic information and control by a host, in accordance with various embodiments.
  • FIG. 19 is a flow diagram of a method for audio system control by a slave node, in accordance with various embodiments.
  • DETAILED DESCRIPTION
  • Disclosed herein are systems and techniques for peripheral device diagnostics and control over a two-wire communication bus. Various embodiments of the systems and techniques may enable low-latency fault detection and control of peripheral devices (e.g., audio devices) coupled to the slave nodes daisy-chained along a two-wire bus.
  • As noted above, as electronic components decrease in size, and as performance expectations increase, more components are included in previously un-instrumented or less-instrumented devices. This drive toward increased instrumentation has conventionally been limited by the communication infrastructure used to exchange signals between components. For example, the proliferation of sensors, such as microphones, cameras, etc., in automobiles (and other closed and/or mobile systems, such as robotic systems) has led to excessive amounts of wiring between components. This excessive wiring is attended by an increase in system complexity and weight, and a decrease in performance and reliability.
  • Described herein are communications systems that provide low latency, time division multiplexed (TDM) communications over a two-wire bus (e.g., a twisted wire pair). In these systems, bi-directional synchronous data (e.g., digital audio), clock, and synchronization signals may be provided by the two-wire bus, supporting direct point-to-point connections between nodes on the bus and allowing multiple, daisy chained nodes at different locations to contribute, use or consume TDM slot content. These communication systems enable downstream traffic (e.g., from a master node to a last slave node), upstream traffic (e.g., to a master node from a slave node), and power transmission over the same two-wire bus.
  • In some embodiments of the peripheral device diagnostics and control systems and techniques disclosed herein, downstream and/or upstream slots along the two-wire bus may be used to transmit diagnostic information, such as information about operational characteristics of the peripheral devices. The downstream and/or upstream slots may be used for slave nodes to communicate directly with each other, and/or to provide information upstream to a host that the host can then distribute downstream to the slave nodes.
  • When the peripheral devices are audio devices, the diagnostic information can include any relevant operational characteristic of the audio devices or their environment. As used herein, an “operational characteristic” of a peripheral device may refer to a particular property of the peripheral device (e.g., a numerical value of that property or an indicator of a range into which that property falls) or a property of the environment around the peripheral device that may affect operation of the peripheral device (e.g., a numerical value of that property or an indicator of a range into which that property falls). Examples of operational characteristics that may be discussed in further detail herein include voice coil temperature, overcurrent, over-excursion, die temperature of chips (e.g., to prevent over-heating in an amplifier or to correlate to ambient temperature), local battery conditions (e.g., voltage of a battery), impedance, resonance frequency, acoustic box leakage, and noise near the audio device. In some embodiments, this diagnostic information may be used to control the peripheral devices and/or the associated slave nodes, trigger different modes for driving the peripheral devices and/or the associated slave nodes, detect faults or problems at the peripheral devices and/or the associated slave nodes, provide feedback to a control system (e.g., at the host or at another location in a communication system) for driving the peripheral devices and/or the associated slave nodes, or provide feedback to other peripheral devices and/or the associated slave nodes. For example, in some embodiments, the diagnostic and control systems and techniques disclosed herein may be used to distribute amplification of speakers in a communication system among different slave nodes, thus providing “distributed amplification.” In another example, in some embodiments, the diagnostic and control systems and techniques disclosed herein may be used to control speaker output across different slave nodes to cancel noise and thus improve an overall audio system.
  • The upstream and/or downstream slots of the two-wire communication systems disclosed herein may be advantageously used for transmitting any suitable state information about a peripheral device (e.g., relevant currents, voltages, temperatures, or other conditions sensed by a sensor coupled to a slave node) back to the host or one or more other slave nodes. This information may not only be used for diagnostics but may also be used for improving the performance of the peripheral devices taken as a whole (e.g., an entire audio system). Generally speaking, feedback information provided to the two-wire bus from the slave nodes may improve the efficiency of the peripheral device system, and in some cases, may reduce the cost of the peripheral devices when the peripheral devices can be driven more efficiently and effectively.
  • As discussed herein, a two-wire communication system may be used to connect sensors to a bus. Sensor connectivity may provide a variety of monitoring functions, such as seat pressure sensing in a vehicle, proximity sensing, capacitive sensing, light sensing, moisture sensing, gesture sensing, acceleration sensing, temperature sensing, and direction sensing, among others. Applications that may make use of the data provided by these sensors include identifying passenger location and providing voluntary and/or involuntary notifications to passengers. In some embodiments, sensor data may be used in combination with diagnostic information about other peripheral devices (e.g., operational characteristics of audio devices) to enhance the performance of the peripheral device system. For example, in a system of audio devices, sensor data may be used to provide enhanced beam forming and noise cancellation. In contrast to conventional bus technologies, sensors and other peripheral devices (such as audio devices) need not be wired separately to a controller but can leverage a common two-wire bus.
  • In the following detailed description, reference is made to the accompanying drawings which form a part hereof wherein like numerals designate like parts throughout, and in which is shown by way of illustration embodiments that may be practiced. It is to be understood that other embodiments may be utilized and structural or logical changes may be made without departing from the scope of the present disclosure. Therefore, the following detailed description is not to be taken in a limiting sense.
  • Various operations may be described as multiple discrete actions or operations in turn, in a manner that is most helpful in understanding the claimed subject matter. However, the order of description should not be construed as to imply that these operations are necessarily order dependent. In particular, these operations may not be performed in the order of presentation. Operations described may be performed in a different order than the described embodiment. Various additional operations may be performed and/or described operations may be omitted in additional embodiments.
  • For the purposes of the present disclosure, the phrase “A and/or B” means (A), (B), or (A and B). For the purposes of the present disclosure, the phrase “A, B, and/or C” means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C).
  • Various components may be referred to or illustrated herein in the singular (e.g., a “processor,” a “peripheral device,” etc.), but this is simply for ease of discussion, and any element referred to in the singular may include multiple such elements in accordance with the teachings herein.
  • The description uses the phrases “in an embodiment” or “in embodiments,” which may each refer to one or more of the same or different embodiments. Furthermore, the terms “comprising,” “including,” “having,” and the like, as used with respect to embodiments of the present disclosure, are synonymous.
  • As used herein, the term “circuitry” may refer to, be part of, or include an application-specific integrated circuit (ASIC), an electronic circuit, and optical circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware that provide the described functionality. A master node may also be referred to as a master “device” herein; similarly, a slave node may be referred to as a slave “device” herein. As used herein, a “microphone” may include a microphone array.
  • Any of the embodiments described herein may be performed in accordance with any suitable related embodiments disclosed in any of the prior patent filings to which the present application claims priority. In particular, any of the embodiments of the Automotive Audio Bus (A2B) system disclosed in any of the priority filings may be implemented in any combination with the embodiments described herein. For example, power switching and diagnostics may be included in the two-wire communication systems described herein, as discussed in U.S. Provisional Application No. 61/845,542, filed Jul. 12, 2013. In another example, decoders may be included in the two-wire communication systems described herein, as discussed in U.S. Provisional Application No. 61/843,902, filed Jul. 8, 2013. In another example, digital phase detectors may be included in the two-wire communication systems described herein, as discussed in U.S. Provisional Application No. 61/843,896, filed Jul. 8, 2013. In another example, the two-wire communication systems described herein may include the state machine functionality discussed in U.S. Provisional Application No. 61/843,891, filed Jul. 8, 2013.
  • FIG. 1 is a block diagram of an illustrative half-duplex two-wire communication system 100, in accordance with various embodiments. The system 100 includes a host 110, a master node 102 and at least one slave node 104. In FIG. 1, three slave nodes (0, 1, and 2) are illustrated. The depiction of three slave nodes 104 in FIG. 1 is simply illustrative, and the system 100 may include one, two, or more slave nodes 104, as desired.
  • The master node 102 may communicate with the slave nodes 104 over a two-wire bus 106. The bus 106 may include different two-wire bus links between adjacent nodes along the bus 106 to connect the nodes along the bus 106 in a daisy-chain fashion. For example, as illustrated in FIG. 1, the bus 106 may include a link coupling the master node 102 to the slave node 0, a link coupling the slave node 0 to the slave node 1, and a link coupling the slave node 1 to the slave node 2. The links of the bus 106 may each be formed of a single twisted wire pair (e.g., an unshielded twisted pair).
  • The host 110 may include a processor that programs the master node 102, and acts as the originator and recipient of various payloads transmitted along the bus 106. In particular, the host 110 may be the master of Inter-Integrated Circuit Sound (I2S) communications that happen along the bus 106. The host 110 may communicate with the master node 102 via an I2S/Time Division Multiplex (TDM) bus and/or an Inter-Integrated Circuit (I2C) bus. In some embodiments, the master node 102 may be a transceiver (e.g., the node transceiver 120 discussed below with reference to FIG. 2) located within a housing of the host 110. The master node 102 may be programmable by the host 110 over the I2C bus for configuration and read-back, and may be configured to generate clock, synchronization, and framing for all of the slave nodes 104. In some embodiments, an extension of the I2C control bus between the host 110 in the master node 102 may be embedded in the data streams transmitted over the bus 106, allowing the host 110 direct access to registers and status information for the one or more slave nodes 104, as well as enabling I2C-to-I2C communication over distance to allow the host 110 to control the peripherals 108.
  • The master node 102 may generate “downstream” signals (e.g., data signals, power signals, etc., transmitted away from the master node 102 along the bus 106) and receive “upstream” signals (e.g., transmitted toward the master node 102 along the bus 106). The master node 102 may provide a clock signal for synchronous data transmission over the bus 106. As used herein, “synchronous data” may include data streamed continuously (e.g., audio signals) with a fixed time interval between two successive transmissions to/from the same node along the bus 106. In some embodiments, the clock signal provided by the master node 102 may be derived from an I2S input provided to the master node 102 by the host 110. A slave node 104 may be an addressable network connection point that represents a possible destination for data frames transmitted downstream on the bus 106 or upstream on the bus 106. A slave node 104 may also represent a possible source of downstream or upstream data frames. The system 100 may allow for control information and other data to be transmitted in both directions over the bus 106 from one node to the next. One or more of the slave nodes 104 may also be powered by signals transmitted over the bus 106.
  • In particular, each of the master node 102 and the slave nodes 104 may include a positive upstream terminal (denoted as “AP”), a negative upstream terminal (denoted as “AN”), a positive downstream terminal (denoted as “BP”), and a negative downstream terminal (denoted as “BN”). The positive and negative downstream terminals of a node may be coupled to the positive and negative upstream terminals of the adjacent downstream node, respectively. As shown in FIG. 1, the master node 102 may include positive and negative upstream terminals, but these terminals may not be used; in other embodiments, the master node 102 may not include positive and negative upstream terminals. The last slave node 104 along the bus 106 (the slave node 2 in FIG. 1) may include positive and negative downstream terminals, but these terminals may not be used; in other embodiments, the last slave node 104 along the bus may not include positive and negative downstream terminals.
  • As discussed in detail below, the master node 102 may periodically send a synchronization control frame downstream, optionally along with data intended for one or more of the slave nodes 104. For example, the master node 102 may transmit a synchronization control frame every 1024 bits (representing a superframe) at a frequency of 48 kHz, resulting in an effective bit rate on the bus 106 of 49.152 Mbps. Other rates may be supported, including, for example, 44.1 kHz. The synchronization control frame may allow the slave nodes 104 to identify the beginning of each superframe and also, in combination with physical layer encoding/signaling, may allow each slave node 104 to derive its internal operational clock from the bus 106. The synchronization control frame may include a preamble for signaling the start of synchronization, as well as control fields that allow for various addressing modes (e.g., normal, broadcast, discovery), configuration information (e.g., writing to registers of the slave nodes 104), conveyance of I2C information, remote control of certain general-purpose input/output (GPIO) pins at the slave nodes 104, and other services. A portion of the synchronization control frame following the preamble and the payload data may be scrambled in order to reduce the likelihood that information in the synchronization control frame will be mistaken for a new preamble, and to flatten the spectrum of related electromagnetic emissions.
  • The synchronization control frame may get passed between slave node 104 (optionally along with other data, which may come from the master node 102 but additionally or alternatively may come from one or more upstream slave nodes 104 or from a slave node 104 itself) until it reaches the last slave node 104 (i.e., the slave node 2 in FIG. 1), which has been configured by the master node 102 as the last slave node 104 or has self-identified itself as the last slave node 104. Upon receiving the synchronization control frame, the last slave node 104 may transmit a synchronization response frame followed by any data that it is permitted to transmit (e.g., a 24-bit audio sample in a designated time slot). The synchronization response frame may be passed upstream between slave nodes 104 (optionally along with data from downstream slave nodes 104), and based on the synchronization response frame, each slave node 104 may be able to identify a time slot, if any, in which the slave node 104 is permitted to transmit.
  • In some embodiments, one or more of the slave nodes 104 in the system 100 may be coupled to and communicate with a peripheral device 108. For example, a slave node 104 may be configured to read data from and/or write data to the associated peripheral device 108 using I2S, pulse density modulation (PDM), TDM, and/or I2C protocols, as discussed below. Although the “peripheral device 108” may be referred to in the singular herein, this is simply for ease of discussion, and a single slave node 104 may be coupled with zero, one, or more peripheral devices. Examples of peripheral devices that may be included in the peripheral device 108 may include a digital signal processor (DSP), a field programmable gate array (FPGA), an application-specific integrated circuit (ASIC), an analog to digital converter (ADC), a digital to analog converter (DAC), a codec, a microphone, a microphone array, a speaker, an audio amplifier, a protocol analyzer, an accelerometer or other motion sensor, an environmental condition sensor (e.g., a temperature, humidity, and/or gas sensor), a wired or wireless communication transceiver, a display device (e.g., a touchscreen display), a user interface component (e.g., a button, a dial, or other control), a camera (e.g., a video camera), a memory device, or any other suitable device that transmits and/or receives data. A number of examples of different peripheral device configurations are discussed in detail herein.
  • In some embodiments, the peripheral device 108 may include any device configured for Inter-Integrated Circuit Sound (I2S) communication; the peripheral device 108 may communicate with the associated slave node 104 via the I2S protocol. In some embodiments, the peripheral device 108 may include any device configured for Inter-Integrated Circuit (I2C) communication; the peripheral device 108 may communicate with the associated slave node 104 via the I2C protocol. In some embodiments, a slave node 104 may not be coupled to any peripheral device 108.
  • A slave node 104 and its associated peripheral device 108 may be contained in separate housings and coupled through a wired or wireless communication connection or may be contained in a common housing. For example, a speaker connected as a peripheral device 108 may be packaged with the hardware for an associated slave node 104 (e.g., the node transceiver 120 discussed below with reference to FIG. 2), such that the hardware for the associated slave node 104 is contained within a housing that includes other speaker components. The same may be true for any type of peripheral device 108.
  • As discussed above, the host 110 may communicate with and control the master node 102 using multi-channel I2S and I2C communication protocols. In particular, the host 110 may transmit data via I2S to a frame buffer (not illustrated) in the master node 102, and the master node 102 may read data from the frame buffer and transmit the data along the bus 106. Analogously, the master node 102 may store data received via the bus 106 in the frame buffer, and then may transmit the data to the host 110 via I2S.
  • Each slave node 104 may have internal control registers that may be configured by communications from the master node 102. A number of such registers are discussed in detail below. Each slave node 104 may receive downstream data and may retransmit the data further downstream. Each slave node 104 may receive and/or generate upstream data and/or retransmit data upstream and/or add data to and upstream transaction.
  • Communications along the bus 106 may occur in periodic superframes. Each superframe may begin with a downstream synchronization control frame; be divided into periods of downstream transmission (also called “downstream portions”), upstream transmission (also called “upstream portions”), and no transmission (where the bus 106 is not driven); and end just prior to transmission of another downstream synchronization control frame. The master node 102 may be programmed (by the host 110) with a number of downstream portions to transmit to one or more of the slave nodes 104 and a number of upstream portions to receive from one or more of the slave nodes 104. Each slave node 104 may be programmed (by the master node 102) with a number of downstream portions to retransmit down the bus 106, a number of downstream portions to consume, a number of upstream portions to retransmit up the bus 106, and a number of upstream portions in which the slave node 104 may transmit data received from the slave node 104 from the associated peripheral device 108. Communication along the bus 106 is discussed in further detail below with reference to FIGS. 2-12.
  • Each of the master node 102 and the slave nodes 104 may include a transceiver to manage communication between components of the system 100. FIG. 2 is a block diagram of a node transceiver 120 that may be included in a node (e.g., the master node 102 or a slave node 104) of the system 100 of FIG. 1, in accordance with various embodiments. In some embodiments, a node transceiver 120 may be included in each of the nodes of the system 100, and a control signal may be provided to the node transceiver 120 via a master (MSTR) pin to indicate whether the node transceiver 120 is to act as a master (e.g., when the MSTR pin is high) or a slave (e.g., when the MSTR pin is low).
  • The node transceiver 120 may include an upstream differential signaling (DS) transceiver 122 and a downstream DS transceiver 124. The upstream DS transceiver 122 may be coupled to the positive and negative upstream terminals discussed above with reference to FIG. 1, and the downstream DS transceiver 124 may be coupled to the positive and negative downstream terminals discussed above with reference to FIG. 1. In some embodiments, the upstream DS transceiver 122 may be a low voltage DS (LVDS) transceiver, and the downstream DS transceiver 124 may be an LVDS transceiver. Each node in the system 100 may be AC-coupled to the bus 106, and data signals may be conveyed along the bus 106 (e.g., via the upstream DS transceiver 122 and/or the downstream DS transceiver 124) using a predetermined form of DS (e.g., LVDS or Multipoint LVDS (MLVDS) or similar signaling) with appropriate encoding to provide timing information over the bus 106 (e.g., differential Manchester coding, biphase mark coding, Manchester coding, Non-Return-to-Zero, Inverted (NRZI) coding with run-length limiting, or any other suitable encoding).
  • The upstream DS transceiver 122 and the downstream DS transceiver 124 may communicate with bus protocol circuitry 126, and the bus protocol circuitry 126 may communicate with a phased locked loop (PLL) 128 and voltage regulator circuitry 130, among other components. When the node transceiver 120 is powered up, the voltage regulator circuitry 130 may raise a “power good” signal that is used by the PLL 128 as a power-on reset.
  • As noted above, one or more of the slave nodes 104 in the system 100 may receive power transmitted over the bus 106 concurrently with data. For power distribution (which is optional, as some of the slave nodes 104 may be configured to have exclusively local power provided to them), the master node 102 may place a DC bias on the bus link between the master node 102 and the slave node 0 (e.g., by connecting one of the downstream terminals to a voltage source provided by a voltage regulator and the other downstream terminal to ground). The DC bias may be a predetermined voltage, such as 5 V, 8 V, the voltage of a car battery, or a higher voltage. Each successive slave node 104 can selectively tap its upstream bus link to recover power (e.g., using the voltage regulator circuitry 130). This power may be used to power the slave node 104 itself (and optionally one or more peripheral device 108 coupled to the slave node 104). A slave node 104 may also selectively bias the bus link downstream for the next-in-line slave node 104 with either the recovered power from the upstream bus link or from a local power supply. For example, the slave node 0 may use the DC bias on the upstream bus link 106 to recover power for the slave node 0 itself and/or for one or more associated peripheral device 108, and/or the slave node 0 may recover power from its upstream bus link 106 to bias its downstream bus link 106.
  • Thus, in some embodiments, each node in the system 100 may provide power to the following downstream node over a downstream bus link. The powering of nodes may be performed in a sequenced manner. For example, after discovering and configuring the slave node 0 via the bus 106, the master node 102 may instruct the slave node 0 to provide power to its downstream bus link 106 in order to provide power to the slave node 1; after the slave node 1 is discovered and configured, the master node 102 may instruct the slave node 1 to provide power to its downstream bus link 106 in order to provide power to the slave node 2 (and so on for additional slave nodes 104 coupled to the bus 106. In some embodiments, one or more of the slave nodes 104 may be locally powered, instead of or in addition to being powered from its upstream bus link. In some such embodiments, the local power source for a given slave node 104 may be used to provide power to one or more downstream slave nodes.
  • In some embodiments, upstream filtering circuitry 132 may be disposed between the upstream DS transceiver 122 and the voltage regulator circuitry 130, and downstream filtering circuitry 131 may be disposed between the downstream DS transceiver 124 and the voltage regulator circuitry 130. Since each link of the bus 106 may carry AC (signal) and DC (power) components, the upstream filtering circuitry 132 and the downstream filtering circuitry 131 may separate the AC and DC components, providing the AC components to the upstream DS transceiver 122 and the downstream DS transceiver 124, and providing the DC components to the voltage regulator 130. AC couplings on the line side of the upstream DS transceiver 122 and downstream DS transceiver 124 substantially isolate the transceivers 122 and 124 from the DC component on the line to allow for high-speed bi-directional communications. As discussed above, the DC component may be tapped for power, and the upstream filtering circuitry 132 and the downstream filtering circuitry 131 may include a ferrite, a common mode choke, or an inductor, for example, to reduce the AC component provided to the voltage regulator circuitry 130. In some embodiments, the upstream filtering circuitry 132 may be included in the upstream DS transceiver 122, and/or the downstream filtering circuitry 131 may be included in the downstream DS transceiver 124; in other embodiments, the filtering circuitry may be external to the transceivers 122 and 124.
  • The node transceiver 120 may include a transceiver 127 for I2S, TDM, and PDM communication between the node transceiver 120 and an external device 155. Although the “external device 155” may be referred to in the singular herein, this is simply for ease of illustration, and multiple external devices may communicate with the node transceiver 120 via the I2S/TDM/PDM transceiver 127. As known in the art, the I2S protocol is for carrying pulse code modulated (PCM) information (e.g., between audio chips on a printed circuit board). As used herein, “I2S/TDM” may refer to an extension of the I2S stereo (2-channel) content to multiple channels using TDM. As known in the art, PDM may be used in sigma delta converters, and in particular, PDM format may represent an over-sampled 1-bit sigma delta ADC signal before decimation. PDM format is often used as the output format for digital microphones. The I2S/TDM/PDM transceiver 127 may be in communication with the bus protocol circuitry 126 and pins for communication with the external device 155. Six pins, BCLK, SYNC, DTX[1:0], and DRX[1:0], are illustrated in FIG. 2; the BCLK pin may be used for an I2S bit clock, the SYNC pin may be used for an I2S frame synchronization signal, and the DTX[1:0] and DRX[1:0] pins are used for transmit and receive data channels, respectively. Although two transmit pins (DTX[1:0]) and two receive pins (DRX[1:0]) are illustrated in FIG. 2, any desired number of receive and/or transmit pins may be used.
  • When the node transceiver 120 is included in the master node 102, the external device 155 may include the host 110, and the I2S/TDM/PDM transceiver 127 may provide an I2S slave (in regards to BCLK and SYNC) that can receive data from the host 110 and send data to the host 110 synchronously with an I2S interface clock of the host 110. In particular, an I2S frame synchronization signal may be received at the SYNC pin as an input from the host 110, and the PLL 128 may use that signal to generate clocks. When the node transceiver 120 is included in a slave node 104, the external device 155 may include one or more peripheral devices 108, and the I2S/TDM/PDM transceiver 127 may provide an I2S clock master (for BCLK and SYNC) that can control I2S communication with the peripheral device 108. In particular, the I2S/TDM/PDM transceiver 127 may provide an I2S frame synchronization signal at the SYNC pin as an output. Registers in the node transceiver 120 may determine which and how many I2S/TDM channels are being transmitted as data slots over the bus 106. A TDM mode (TDMMODE) register in the node transceiver 120 may store a value of how many TDM channels fit between consecutive SYNC pulses on a TDM transmit or receive pin. Together with knowledge of the channel size, the node transceiver 120 may automatically set the BCLK rate to match the amount of bits within the sampling time (e.g., 48 kHz).
  • The node transceiver 120 may include a transceiver 129 for I2C communication between the node transceiver 120 and an external device 157. Although the “external device 157” may be referred to in the singular herein, this is simply for ease of illustration, and multiple external devices may communicate with the node transceiver 120 via the I2C transceiver 129. As known in the art, the I2C protocol uses clock (SCL) and data (SDA) lines to provide data transfer. The I2C transceiver 129 may be in communication with the bus protocol circuitry 126 and pins for communication with the external device 157. Four pins, ADR1, ADR2, SDA, and SCL are illustrated in FIG. 2; ADR1 and ADR2 may be used to modify the I2C addresses used by the node transceiver 120 when the node transceiver 120 acts as an I2C slave (e.g., when it is included in the master node 102), and SDA and SCL are used for the I2C serial data and serial clock signals, respectively. When the node transceiver 120 is included in the master node 102, the external device 157 may include the host 110, and the I2C transceiver 129 may provide an I2C slave that can receive programming instructions from the host 110. In particular, an I2C serial clock signal may be received at the SCL pin as an input from the host 110 for register accesses. When the node transceiver 120 is included in a slave node 104, the external device 157 may include a peripheral device 108 and the I2C transceiver 129 may provide an I2C master to allow the I2C transceiver to program one or more peripheral devices in accordance with instructions provided by the host 110 and transmitted to the node transceiver 120 via the bus 106. In particular, the I2C transceiver 129 may provide the I2C serial clock signal at the SCL pin as an output.
  • The node transceiver 120 may include an interrupt request (IRQ) pin in communication with the bus protocol circuitry 126. When the node transceiver 120 is included in the master node 102 via the I2C transceiver 129, the bus protocol circuitry 126 may provide event-driven interrupt requests toward the host 110 via the IRQ pin. When the node transceiver 120 is included in a slave node 104 (e.g., when the MSTR pin is low), the IRQ pin may serve as a GPIO pin with interrupt request capability.
  • The system 100 may operate in any of a number of different operational modes. The nodes on the bus 106 may each have a register indicating which operational mode is currently enabled. Descriptions follow of examples of various operational modes that may be implemented. In a standby operational mode, bus activity is reduced to enable global power savings; the only traffic required is a minimal downstream preamble to keep the Pas of each node (e.g., the PLL 128) synchronized. In standby operational mode, reads and writes across the bus 106 are not supported. In a discovery operational mode, the master node 102 may send predetermined signals out along the bus 106 and wait for suitable responses to map out the topology of slave nodes 104 distributed along the bus 106. In a normal operational mode, full register access may be available to and from the slave nodes 104 as well as access to and from peripheral devices 108 over the bus 106. Normal mode may be globally configured by the host 110 with or without synchronous upstream data and with or without synchronous downstream data.
  • FIG. 3 is a diagram of a portion of a synchronization control frame 180 used for communication in the system 100, in accordance with various embodiments. In particular, the synchronization control frame 180 may be used for data clock recovery and PLL synchronization, as discussed below. As noted above, because communications over the bus 106 may occur in both directions, communications may be time-multiplexed into downstream portions and upstream portions. In a downstream portion, a synchronization control frame and downstream data may be transmitted from the master node 102, while in an upstream portion, a synchronization response frame, and upstream data may be transmitted to the master node 102 from each of the slave nodes 104. The synchronization control frame 180 may include a preamble 182 and control data 184. Each slave node 104 may be configured to use the preamble 182 of the received synchronization control frame 180 as a time base for feeding the PLL 128. To facilitate this, a preamble 182 does not follow the “rules” of valid control data 184, and thus can be readily distinguished from the control data 184.
  • For example, in some embodiments, communication along the bus 106 may be encoded using a clock first, transition on zero differential Manchester coding scheme. According to such an encoding scheme, each bit time begins with a clock transition. If the data value is zero, the encoded signal transitions again in the middle of the bit time. If the data value is one, the encoded signal does not transition again. The preamble 182 illustrated in FIG. 5 may violate the encoding protocol (e.g., by having clock transitions that do not occur at the beginning of bit times 5, 7, and 8), which means that the preamble 182 may not match any legal (e.g., correctly encoded) pattern for the control data 184. In addition, the preamble 182 cannot be reproduced by taking a legal pattern for the control data 184 and forcing the bus 106 high or low for a single bit time or for a multiple bit time period. The preamble 182 illustrated in FIG. 5 is simply illustrative, and the synchronization control frame 180 may include different preambles 182 that may violate the encoding used by the control data 184 in any suitable manner.
  • The bus protocol circuitry 126 may include differential Manchester decoder circuitry that runs on a clock recovered from the bus 106 and that detects the synchronization control frame 180 to send a frame sync indicator to the PLL 128. In this manner, the synchronization control frame 180 may be detected without using a system clock or a higher-speed oversampling clock. Consequently, the slave nodes 104 can receive a PLL synchronization signal from the bus 106 without requiring a crystal clock source at the slave nodes 104.
  • As noted above, communications along the bus 106 may occur in periodic superframes. FIG. 4 is a diagram of a superframe 190, in accordance with various embodiments. As shown in FIG. 6, a superframe may begin with a synchronization control frame 180. When the synchronization control frame 180 is used as a timing source for the PLL 128, the frequency at which superframes are communicated (“the superframe frequency”) may be the same as the synchronization signal frequency. In some embodiments in which audio data is transmitted along the bus 106, the superframe frequency may be the same as the audio sampling frequency used in the system 100 (e.g., either 48 kHz or 44.1 kHz), but any suitable superframe frequency may be used. Each superframe 190 may be divided into periods of downstream transmission 192, periods of upstream transmission 194, and periods of no transmission 196 (e.g., when the bus 106 is not driven).
  • In FIG. 4, the superframe 190 is shown with an initial period of downstream transmission 192 and a later period of upstream transmission 194. The period of downstream transmission 192 may include a synchronization control frame 180 and X downstream data slots 198, where X can be zero. Substantially all signals on the bus 106 may be line-coded and a synchronization signal forwarded downstream from the master node 102 to the last slave node 104 (e.g., the slave node 104C) in the form of the synchronization preamble 182 in the synchronization control frame 180, as discussed above. Downstream, TDM, synchronous data may be included in the X downstream data slots 198 after the synchronization control frame 180. The downstream data slots 198 may have equal width. As discussed above, the PLL 128 may provide the clock that a node uses to time communications over the bus 106. In some embodiments in which the bus 106 is used to transmit audio data, the PLL 128 may operate at a multiple of the audio sampling frequency (e.g., 1024 times the audio sampling frequency, resulting in 1024-bit clocks in each superframe).
  • The period of upstream transmission 194 may include a synchronization response frame 197 and Y upstream data slots 199, where Y can be zero. In some embodiments, each slave node 104 may consume a portion of the downstream data slots 198. The last slave node (e.g., slave node 2 in FIG. 1) may respond (after a predetermined response time stored in a register of the last slave node) with a synchronization response frame 197. Upstream, TDM, synchronous data may be added by each slave node 104 in the upstream data slots 199 directly after the synchronization response frame 197. The upstream data slots 199 may have equal width. A slave node 104 that is not the last slave node (e.g., the slave nodes 0 and 1 in FIG. 1) may replace the received synchronization response frame 197 with its own upstream response if a read of one of its registers was requested in the synchronization control frame 180 of the superframe 190 or if a remote I2C read was requested in the synchronization control frame 180 of the superframe 190.
  • As discussed above, the synchronization control frame 180 may begin each downstream transmission. In some embodiments, the synchronization control frame 180 may be 64 bits in length, but any other suitable length may be used. The synchronization control frame 180 may begin with the preamble 182, as noted above. In some embodiments, when the synchronization control frame 180 is retransmitted by a slave node 104 to a downstream slave node 104, the preamble 182 may be generated by the transmitting slave node 104, rather than being retransmitted.
  • The control data 184 of the synchronization control frame 180 may include fields that contain data used to control transactions over the bus 106. Examples of these fields are discussed below, and some embodiments are illustrated in FIG. 5. In particular, FIG. 5 illustrates example formats for the synchronization control frame 180 in normal mode, I2C mode, and discovery mode, in accordance with various embodiments. In some embodiments, a different preamble 182 or synchronization control frame 180 entirely may be used in standby mode so that the slave nodes 104 do not need to receive all of the synchronization control frame 180 until a transition to normal mode is sent.
  • In some embodiments, the synchronization control frame 180 may include a count (CNT) field. The CNT field may have any suitable length (e.g., 2 bits) and may be incremented (modulo the length of the field) from the value used in the previous superframe. A slave node 104 that receives a CNT value that is unexpected may be programmed to return an interrupt.
  • In some embodiments, the synchronization control frame 180 may include a node addressing mode (NAM) field. The NAM field may have any suitable length (e.g., 2 bits) and may be used to control access to registers of a slave node 104 over the bus 106. In normal mode, registers of a slave node 104 may be read from and/or written to based on the ID of the slave node 104 and the address of the register. Broadcast transactions are writes which should be taken by every slave node 104. In some embodiments, the NAM field may provide for four node addressing modes, including “none” (e.g., data not addressed to any particular slave node 104), “normal” (e.g., data unicast to a specific slave node 104 specified in the address field discussed below), “broadcast” (e.g., addressed to all slave nodes 104), and “discovery.”
  • In some embodiments, the synchronization control frame 180 may include an I2C field. The I2C field may have any suitable length (e.g., 1 bit) and may be used to indicate that the period of downstream transmission 192 includes an I2C transaction. The I2C field may indicate that the host 110 has provided instructions to remotely access a peripheral device 108 that acts as an I2C slave with respect to an associated slave node 104.
  • In some embodiments, the synchronization control frame 180 may include a node field. The node field may have any suitable length (e.g., 4 bits) and may be used to indicate which slave node is being addressed for normal and I2C accesses. In discovery mode, this field may be used to program an identifier for a newly discovered slave node 104 in a node ID register of the slave node 104. Each slave node 104 in the system 100 may be assigned a unique ID when the slave node 104 is discovered by the master node 102, as discussed below. In some embodiments, the master node 102 does not have a node ID, while in other embodiments, the master node 102 may have a node ID. In some embodiments, the slave node 104 attached to the master node 102 on the bus 106 (e.g., the slave node 0 in FIG. 1) will be slave node 0, and each successive slave node 104 will have a number that is 1 higher than the previous slave node. However, this is simply illustrative, and any suitable slave node identification system may be used.
  • In some embodiments, the synchronization control frame 180 may include a read/write (RW) field. The RW field may have any suitable length (e.g., 1 bit) and may be used to control whether normal accesses are reads (e.g., RW==1) or writes (e.g., RW==0).
  • In some embodiments, the synchronization control frame 180 may include an address field. The address field may have any suitable length (e.g., 8 bits) and may be used to address specific registers of a slave node 104 through the bus 106. For I2C transactions, the address field may be replaced with I2C control values, such as START/STOP, WAIT, RW, and DATA VLD. For discovery transactions, the address field may have a predetermined value (e.g., as illustrated in FIG. 5).
  • In some embodiments, the synchronization control frame 180 may include a data field. The data field may have any suitable length (e.g., 8 bits) and may be used for normal, I2C, and broadcast writes. The RESPCYCS value, multiplied by 4, may be used to determine how many cycles a newly discovered node should allow to elapse between the start of the synchronization control frame 180 being received and the start of the synchronization response frame 197 being transmitted. When the NAM field indicates discovery mode, the node address and data fields discussed below may be encoded as a RESPCYCS value that, when multiplied by a suitable optional multiplier (e.g., 4), indicates the time, in bits, from the end of the synchronization control frame 180 to the start of the synchronization response frame 197. This allows a newly discovered slave node 104 to determine the appropriate time slot for upstream transmission.
  • In some embodiments, the synchronization control frame 180 may include a cyclic redundancy check (CRC) field. The CRC field may have any suitable length (e.g., 16 bits) and may be used to transmit a CRC value for the control data 184 of the synchronization control frame 180 following the preamble 182. In some embodiments, the CRC may be calculated in accordance with the CCITT-CRC error detection scheme.
  • In some embodiments, at least a portion of the synchronization control frame 180 between the preamble 182 and the CRC field may be scrambled in order to reduce the likelihood that a sequence of bits in this interval will periodically match the preamble 182 (and thus may be misinterpreted by the slave node 104 as the start of a new superframe 190), as well as to reduce electromagnetic emissions as noted above. In some such embodiments, the CNT field of the synchronization control frame 180 may be used by scrambling logic to ensure that the scrambled fields are scrambled differently from one superframe to the next. Various embodiments of the system 100 described herein may omit scrambling.
  • Other techniques may be used to ensure that the preamble 182 can be uniquely identified by the slave nodes 104 or to reduce the likelihood that the preamble 182 shows up elsewhere in the synchronization control frame 180, in addition to or in lieu of techniques such as scrambling and/or error encoding as discussed above. For example, a longer synchronization sequence may be used so as to reduce the likelihood that a particular encoding of the remainder of the synchronization control frame 180 will match it. Additionally or alternatively, the remainder of the synchronization control frame may be structured so that the synchronization sequence cannot occur, such as by placing fixed “0” or “1” values at appropriate bits.
  • The master node 102 may send read and write requests to the slave nodes 104, including both requests specific to communication on the bus 106 and I2C requests. For example, the master node 102 may send read and write requests (indicated using the RW field) to one or more designated slave nodes 104 (using the NAM and node fields) and can indicate whether the request is a request for the slave node 104 specific to the bus 106, an I2C request for the slave node 104, or an I2C request to be passed along to an I2C-compatible peripheral device 108 coupled to the slave node 104 at one or more I2C ports of the slave node 104.
  • Turning to upstream communication, the synchronization response frame 197 may begin each upstream transmission. In some embodiments, the synchronization response frame 197 may be 64 bits in length, but any other suitable length may be used. The synchronization response frame 197 may also include a preamble, as discussed above with reference to the preamble 182 of the synchronization control frame 180, followed by data portion. At the end of a downstream transmission, the last slave node 104 on the bus 106 may wait until the RESPCYCS counter has expired and then begin transmitting a synchronization response frame 197 upstream. If an upstream slave node 104 has been targeted by a normal read or write transaction, a slave node 104 may generate its own synchronization response frame 197 and replace the one received from downstream. If any slave node 104 does not see a synchronization response frame 197 from a downstream slave node 104 at the expected time, the slave node 104 will generate its own synchronization response frame 197 and begin transmitting it upstream.
  • The data portion of the synchronization response frame 197 may include fields that contain data used to communicate response information back to the master node 102. Examples of these fields are discussed below, and some embodiments are illustrated in FIG. 6. In particular, FIG. 6 illustrates example formats for the synchronization response frame 197 in normal mode, I2C mode, and discovery mode, in accordance with various embodiments.
  • In some embodiments, the synchronization response frame 197 may include a count (CNT) field. The CNT field may have any suitable length (e.g., 2 bits) and may be used to transmit the value of the CNT field in the previously received synchronization control frame 180.
  • In some embodiments, the synchronization response frame 197 may include an acknowledge (ACK) field. The ACK field may have any suitable length (e.g., 2 bits), and may be inserted by a slave node 104 to acknowledge a command received in the previous synchronization control frame 180 when that slave node 104 generates the synchronization response frame 197. Example indicators that may be communicated in the ACK field include wait, acknowledge, not acknowledge (NACK), and retry. In some embodiments, the ACK field may be sized to transmit an acknowledgment by a slave node 104 that it has received and processed a broadcast message (e.g., by transmitting a broadcast acknowledgment to the master node 102). In some such embodiments, a slave node 104 also may indicate whether the slave node 104 has data to transmit (which could be used, for example, for demand-based upstream transmissions, such as non-TDM inputs from a keypad or touchscreen, or for prioritized upstream transmission, such as when the slave node 104 wishes to report an error or emergency condition).
  • In some embodiments, the synchronization response frame 197 may include an I2C field. The I2C field may have any suitable length (e.g., 1 bit) and may be used to transmit the value of the I2C field in the previously received synchronization control frame 180.
  • In some embodiments, the synchronization response frame 197 may include a node field. The node field may have any suitable length (e.g., 4 bits) and may be used to transmit the ID of the slave node 104 that generates the synchronization response frame 197.
  • In some embodiments, the synchronization response frame 197 may include a data field. The data field may have any suitable length (e.g., 8 bits), and its value may depend on the type of transaction and the ACK response of the slave node 104 that generates the synchronization response frame 197. For discovery transactions, the data field may include the value of the RESPCYCS field in the previously received synchronization control frame 180. When the ACK field indicates a NACK, or when the synchronization response frame 197 is responding to a broadcast transaction, the data field may include a broadcast acknowledge (BA) indicator (in which the last slave node 104 may indicate if the broadcast write was received without error), a discovery error (DER) indicator (indicating whether a newly discovered slave node 104 in a discovery transaction matches an existing slave node 104), and a CRC error (CER) indicator (indicating whether a NACK was caused by a CRC error).
  • In some embodiments, the synchronization response frame 197 may include a CRC field. The CRC field may have any suitable length (e.g., 16 bits) and may be used to transmit a CRC value for the portion of the synchronization response frame 197 between the preamble and the CRC field.
  • In some embodiments, the synchronization response frame 197 may include an interrupt request (IRQ) field. The IRQ field may have any suitable length (e.g., 1 bit) and may be used to indicate that an interrupt has been signaled from a slave node 104.
  • In some embodiments, the synchronization response frame 197 may include an IRQ node (IRQNODE) field. The IRQNODE field may have any suitable length (e.g., 4 bits) and may be used to transmit the ID of the slave node 104 that has signaled the interrupt presented by the IRQ field. In some embodiments, the slave node 104 for generating the IRQ field will insert its own ID into the IRQNODE field.
  • In some embodiments, the synchronization response frame 197 may include a second CRC (CRC-4) field. The CRC-4 field may have any suitable length (e.g., 4 bits) and may be used to transmit a CRC value for the IRQ and IRQNODE fields.
  • In some embodiments, the synchronization response frame 197 may include an IRQ field, an IRQNODE field, and a CRC-4 field as the last bits of the synchronization response frame 197 (e.g., the last 10 bits). As discussed above, these interrupt-related fields may have their own CRC protection in the form of CRC-4 (and thus not protected by the preceding CRC field). Any slave node 104 that needs to signal an interrupt to the master node 102 will insert its interrupt information into these fields. In some embodiments, a slave node 104 with an interrupt pending may have higher priority than any slave node 104 further downstream that also has an interrupt pending. The last slave node 104 along the bus 106 (e.g., the slave node 2 in FIG. 1) may always populate these interrupt fields. If the last slave node 104 has no interrupt pending, the last slave node 104 may set the IRQ bit to 0, the IRQNODE field to its node ID, and provide the correct CRC-4 value. For convenience, a synchronization response frame 197 that conveys an interrupt may be referred to herein as an “interrupt frame.”
  • In some embodiments, at least a portion of the synchronization response frame 197 between the preamble 182 and the CRC field may be scrambled in order to reduce emissions. In some such embodiments, the CNT field of the synchronization response frame 197 may be used by scrambling logic to ensure that the scrambled fields are scrambled differently from one superframe to the next. Various embodiments of the system 100 described herein may omit scrambling.
  • Other techniques may be used to ensure that the preamble 182 can be uniquely identified by the slave nodes 104 or to reduce the likelihood that the preamble 182 shows up elsewhere in the synchronization response frame 197, in addition to or in lieu of techniques such as scrambling and/or error encoding as discussed above. For example, a longer synchronization sequence may be used so as to reduce the likelihood that a particular encoding of the remainder of the synchronization response frame 180 will match it. Additionally or alternatively, the remainder of the synchronization response frame may be structured so that the synchronization sequence cannot occur, such as by placing fixed “0” or “1” values at appropriate bits.
  • FIG. 7 is a block diagram of the bus protocol circuitry 126 of FIG. 2, in accordance with various embodiments. The bus protocol circuitry 126 may include control circuitry 154 to control the operation of the node transceiver 120 in accordance with the protocol for the bus 106 described herein. In particular, the control circuitry 154 may control the generation of synchronization frames for transmission (e.g., synchronization control frames or synchronization response frames, as discussed above), the processing of received synchronization frames, and the performance of control operations specified in received synchronization control frames. The control circuitry 154 may include programmable registers, as discussed below. The control circuitry 154 may create and receive synchronization control frames, react appropriately to received messages (e.g., associated with a synchronization control frame when the bus protocol circuitry 126 is included in a slave node 104 or from an I2C device when the bus protocol circuitry 126 is included in a master node 102), and adjust the framing to the different operational modes (e.g., normal, discovery, standby, etc.).
  • When the node transceiver 120 is preparing data for transmission along the bus 106, preamble circuitry 156 may be configured to generate preambles for synchronization frames for transmission, and to receive preambles from received synchronization frames. In some embodiments, a downstream synchronization control frame preamble may be sent by the master node 102 every 1024 bits. As discussed above, one or more slave nodes 104 may synchronize to the downstream synchronization control frame preamble and generate local, phase-aligned master clocks from the preamble.
  • Cyclic redundancy check (CRC) insert circuitry 158 may be configured to generate one or more CRCs for synchronization frames for transmission. Frame/compress circuitry 160 may be configured to take incoming data from the I2S/TDM/PDM transceiver 127 (e.g., from a frame buffer associated with the transceiver 127) and/or the I2C transceiver 129, optionally compress the data, and optionally generate parity check bits or error correction codes (ECC) for the data. A multiplexer (MUX) 162 may multiplex a preamble from the preamble circuitry 156, synchronization frames, and data into a stream for transmission. In some embodiments, the transmit stream may be scrambled by scrambling circuitry 164 before transmission.
  • For example, in some embodiments, the frame/compress circuitry 160 may apply a floating point compression scheme. In such an embodiment, the control circuitry 154 may transmit 3 bits to indicate how many repeated sign bits are in the number, followed by a sign bit and N−4 bits of data, where N is the size of the data to be transmitted over the bus 106. The use of data compression may be configured by the master node 102 when desired.
  • In some embodiments, the receive stream entering the node transceiver 120 may be descrambled by the descrambling circuitry 166. A demultiplexer (DEMUX) 168 may demultiplex the preamble, synchronization frames, and data from the receive stream. CRC check circuitry 159 on the receive side may check received synchronization frames for the correct CRC. When the CRC check circuitry 159 identifies a CRC failure in an incoming synchronization control frame 180, the control circuitry 154 may be notified of the failure and will not perform any control commands in the control data 184 of the synchronization control frame 180. When the CRC check circuitry 159 identifies a CRC failure in an incoming synchronization response frame 197, the control circuitry 154 may be notified of the failure and may generate an interrupt for transmission to the host 110 in an interrupt frame. Deframe/decompress circuitry 170 may accept receive data, optionally check its parity, optionally perform error detection and correction (e.g., single error correction—double error detection (SECDED)), optionally decompress the data, and may write the receive data to the I2S/TDM/PDM transceiver 127 (e.g., a frame buffer associated with the transceiver 127) and/or the I2C transceiver 129.
  • As discussed above, upstream and downstream data may be transmitted along the bus 106 in TDM data slots within a superframe 190. The control circuitry 154 may include registers dedicated to managing these data slots on the bus 106, a number of examples of which are discussed below. When the control circuitry 154 is included in a master node 102, the values in these registers may be programmed into the control circuitry 154 by the host 110. When the control circuitry 154 is included in a slave node 104, the values in these registers may be programmed into the control circuitry 154 by the master node 102.
  • In some embodiments, the control circuitry 154 may include a downstream slots (DNSLOTS) register. When the node transceiver 120 is included in the master node 102, this register may hold the value of the total number of downstream data slots. This register may also define the number of data slots that will be used for combined I2S/TDM/PDM receive by the I2S/TDM/PDM transceiver 127 in the master node 102. In a slave node 104, this register may define the number of data slots that are passed downstream to the next slave node 104 before or after the addition of locally generated downstream slots, as discussed in further detail below with reference to LDNSLOTS.
  • In some embodiments, the control circuitry 154 may include a local downstream slots (LDNSLOTS) register. This register may be unused in the master node 102. In a slave node 104, this register may define the number of data slots that the slave node 104 will use and not retransmit. Alternatively, this register may define the number of slots that the slave node 104 may contribute to the downstream data link 106.
  • In some embodiments, the control circuitry 154 may include an upstream slots (UPSLOTS) register. In the master node 102, this register may hold the value of the total number of upstream data slots. This register may also define the number of slots that will be used for I2S/TDM transmit by the I2S/TDM/PDM transceiver 127 in the master node 102. In a slave node 104, this register may define the number of data slots that are passed upstream before the slave node 104 begins to add its own data.
  • In some embodiments, the control circuitry 154 may include a local upstream slots (LUPSLOTS) register. This register may be unused in the master node 102. In a slave node 104, this register may define the number of data slots that the slave node 104 will add to the data received from downstream before it is sent upstream. This register may also define the number of data slots that will be used for combined I2S/TDM/PDM receive by the I2S/TDM/PDM transceiver 127 in the slave node 104.
  • In some embodiments, the control circuitry 154 may include a broadcast downstream slots (BCDNSLOTS) register. This register may be unused in the master node 102. In a slave node 104, this register may define the number of broadcast data slots. In some embodiments, broadcast data slots may always come at the beginning of the data field. The data in the broadcast data slots may be used by multiple slave nodes 104 and may be passed downstream by all slave nodes 104 whether or not they are used.
  • In some embodiments, the control circuitry 154 may include a slot format (SLOTFMT) register. This register may define the format of data for upstream and downstream transmissions. The data size for the I2S/TDM/PDM transceiver 127 may also be determined by this register. In some embodiments, valid data sizes include 8, 12, 16, 20, 24, 28, and 32 bits. This register may also include bits to enable floating point compression for downstream and upstream traffic. When floating point compression is enabled, the I2S/TDM data size may be 4 bits larger than the data size over the bus 106. All nodes in the system 100 may have the same values for SLOTFMT when data slots are enabled, and the nodes may be programmed by a broadcast write so that all nodes will be updated with the same value.
  • FIGS. 8-11 illustrate examples of information exchange along the bus 106, in accordance with various embodiments of the bus protocols described herein. In particular, FIGS. 8-11 illustrate embodiments in which each slave node 104 is coupled to one or more speakers and/or one or more microphones as the peripheral device 108. This is simply illustrative, as any desired arrangement of peripheral device 108 may be coupled to any particular slave node 104 in accordance with the techniques described herein.
  • To begin, FIG. 8 illustrates signaling and timing considerations for bi-directional communication on the bus 106, in accordance with various embodiments. The slave nodes 104 depicted in FIG. 8 have various numbers of sensor/actuator elements, and so different amounts of data may be sent to, or received from, the various slave nodes 104. Specifically, slave node 1 has two elements, slave node 4 has four elements, and slave node 5 has three elements, so the data transmitted by the master node 102 includes two time slots for slave node 1, four time slots for slave node 4, and three time slots for slave node 5. Similarly, slave node 0 has three elements, slave node 2 has three elements, slave node 3 has three elements, slave node 6 has one element, and slave node 7 has four elements, so the data transmitted upstream by those slave nodes 104 includes the corresponding number of time slots. It should be noted that there need not have to be a one-to-one correlation between elements and time slots. For example, a microphone array, included in the peripheral device 108, having three microphones may include a digital signal processor that combines signals from the three microphones (and possibly also information received from the master node 102 or from other slave nodes 104) to produce a single data sample, which, depending on the type of processing, could correspond to a single time slot or multiple time slots.
  • In FIG. 8, the master node 102 transmits a synchronization control frame (SCF) followed by data for speakers coupled to specific slave nodes 104 (SD). Each successive slave node 104 forwards the synchronization control frame and also forwards at least any data destined for downstream slave nodes 104. A particular slave node 104 may forward all data or may remove data destined for that slave node 104. When the last slave node 104 receives the synchronization control frame, that slave node 104 transmits the synchronization response frame (SRF) optionally followed by any data that the slave node 104 is permitted to transmit. Each successive slave node 104 forwards the synchronization response frame along with any data from downstream slave nodes 104 and optionally inserts data from one or more microphones coupled to the particular slave nodes 104 (MD). In the example of FIG. 8, the master node 102 sends data to slave nodes 1, 4, and 5 (depicted in FIG. 8 as active speakers) and receives data from slave nodes 7, 6, 3, 2, and 0 (depicted in FIG. 8 as microphone arrays).
  • FIG. 9 schematically illustrates the dynamic removal of data from a downstream transmission and insertion of data into an upstream transmission, from the perspective of the downstream DS transceiver 124, in accordance with various embodiments. In FIG. 9, as in FIG. 8, the master node 102 transmits a synchronization control frame (SCF) followed by data for slave nodes 1, 4, and 5 (SD) in reverse order (e.g., data for slave node 5 is followed by data for slave node 4, which is followed by data for slave node 1, etc.) (see the row labeled MASTER). When slave node 1 receives this transmission, slave node 1 removes its own data and forwards to slave node 2 only the synchronization control frame followed by the data for slave nodes 5 and 4. Slave nodes 2 and 3 forward the data unchanged (see the row labeled SLAVE 2), such that the data forwarded by slave node 1 is received by slave node 4 (see the row labeled SLAVE 3). Slave node 4 removes its own data and forwards to slave node 5 only the synchronization control frame followed by the data for slave node 5, and, similarly, slave node 5 removes its own data and forwards to slave node 6 only the synchronization control frame. Slave node 6 forwards the synchronization control frame to slave node 7 (see the row labeled SLAVE 6).
  • At this point, slave node 7 transmits to slave node 6 the synchronization response frame (SRF) followed by its data (see the row labeled SLAVE 6). Slave node 6 forwards to slave node 5 the synchronization response frame along with the data from slave node 7 and its own data, and slave node 5 in turn forwards to slave node 4 the synchronization response frame along with the data from slave nodes 7 and 6. Slave node 4 has no data to add, so it simply forwards the data to slave node 3 (see the row labeled SLAVE 3), which forwards the data along with its own data to slave node 2 (see the row labeled SLAVE 2), which in turn forwards the data along with its own data to slave node 1. Slave node 1 has no data to add, so it forwards the data to slave node 0, which forwards the data along with its own data. As a result, the master node 102 receives the synchronization response frame followed by the data from slave nodes 7, 6, 3, 2, and 0 (see the row labeled MASTER).
  • FIG. 10 illustrates another example of the dynamic removal of data from a downstream transmission and insertion of data into an upstream transmission, from the perspective of the downstream DS transceiver 124, as in FIG. 9, although in FIG. 10, the slave nodes 104 are coupled with both sensors and actuators as the peripheral device 108 such that the master node 102 sends data downstream to all of the slave nodes 104 and receives data back from all of the slave nodes 104. Also, in FIG. 10, the data is ordered based on the node address to which it is destined or from which it originates. The data slot labeled “Y” may be used for a data integrity check or data correction.
  • FIG. 11 illustrates another example of the dynamic removal of data from a downstream transmission and insertion of data into an upstream transmission, from the perspective of the downstream DS transceiver 124, as in FIG. 9, although in FIG. 11, the data is conveyed downstream and upstream in sequential order rather than reverse order. Buffering at each slave node 104 allows for selectively adding, removing, and/or forwarding data.
  • As discussed above, each slave node 104 may remove data from downstream or upstream transmissions and/or may add data to downstream or upstream transmissions. Thus, for example, the master node 102 may transmit a separate sample of data to each of a number of slave nodes 104, and each such slave node 104 may remove its data sample and forward only data intended for downstream slaves. On the other hand, a slave node 104 may receive data from a downstream slave node 104 and forward the data along with additional data. One advantage of transmitting as little information as needed is to reduce the amount of power consumed collectively by the system 100.
  • The system 100 may also support broadcast transmissions (and multicast transmissions) from the master node 102 to the slave nodes 104, specifically through configuration of the downstream slot usage of the slave nodes 104. Each slave node 104 may process the broadcast transmission and pass it along to the next slave node 104, although a particular slave node 104 may “consume” the broadcast message, (i.e., not pass the broadcast transmission along to the next slave node 104).
  • The system 100 may also support upstream transmissions (e.g., from a particular slave node 104 to one or more other slave nodes 104). Such upstream transmissions can include unicast, multicast, and/or broadcast upstream transmissions. With upstream addressing, as discussed above with reference to downstream transmissions, a slave node 104 may determine whether or not to remove data from an upstream transmission and/or whether or not to pass an upstream transmission along to the next upstream slave node 104 based on configuration of the upstream slot usage of the slave nodes 104. Thus, for example, data may be passed by a particular slave node 104 to one or more other slave nodes 104 in addition to, or in lieu of, passing the data to the master node 102. Such slave-slave relationships may be configured, for example, via the master node 102.
  • Thus, in various embodiments, the slave nodes 104 may operate as active/intelligent repeater nodes, with the ability to selectively forward, drop, and add information. The slave nodes 104 may generally perform such functions without necessarily decoding/examining all of the data, since each slave node 104 knows the relevant time slot(s) within which it will receive/transmit data, and hence can remove data from or add data into a time slot. Notwithstanding that the slave nodes 104 may not need to decode/examine all data, the slave nodes 104 may typically re-clock the data that it transmits/forwards. This may improve the robustness of the system 100.
  • In some embodiments, the bus 106 may be configured for uni-directional communications in a ring topology. For example, FIG. 12 illustrates an arrangement 1200 of the master node 102 and four slave nodes 104 in a ring topology, and illustrates signaling and timing considerations for uni-directional communication in the arrangement 1200, in accordance with various embodiments. In such embodiments, the transceivers 120 in the nodes may include a receive-only transceiver (MASTER IN) and a transmit-only transceiver (MASTER OUT), rather than two bi-directional transceivers for upstream and downstream communication. In the link-layer synchronization scheme illustrated in FIG. 12, the master node 102 transmits a synchronization control frame (SCF) 180, optionally followed by “downstream” data 1202 for the three speakers coupled to various slave nodes 104 (the data for the different speakers may be arranged in any suitable order, as discussed above with reference to FIGS. 8-11), and each successive slave node 104 forwards the synchronization control frame 180 along with any “upstream” data from prior slave nodes 104 and “upstream” data of its own to provide “upstream” data 1204 (e.g., the data from the eight different microphones may be arranged in any suitable order, as discussed above with reference to FIGS. 8-11).
  • As described herein, data may be communicated between elements of the system 100 in any of a number of ways. In some embodiments, data may be sent as part of a set of synchronous data slots upstream (e.g., using the data slots 199) by a slave node 104 or downstream (e.g., using the data slots 198) by a slave node 104 or a master node 102. The volume of such data may be adjusted by changing the number of bits in a data slot, or including extra data slots. Data may also be communicated in the system 100 by inclusion in a synchronization control frame 180 or a synchronization response frame 197. Data communicated this way may include I2C control data from the host 110 (with a response from a peripheral device 108 associated with a slave node 104); accesses to registers of the slave nodes 104 (e.g., for discovery and configuration of slots and interfaces) that may include write access from the host 110/master node 102 to a slave node 104 and read access from a slave node 104 to the host 110/master node 102; and event signaling via interrupts from a peripheral device 108 to the host 110. In some embodiments, GPIO pins may be used to convey information from a slave node 104 to the master node 102 (e.g., by having the master node 102 poll the GPIO pins over I2C, or by having a node transceiver 120 of a slave node 104 generate an interrupt at an interrupt request pin). For example, in some such embodiments, a host 110 may send information to the master node 102 via I2C, and then the master node 102 may send that information to the slave via the GPIO pins. Any of the types of data discussed herein as transmitted over the bus 106 may be transmitted using any one or more of these communication pathways. Other types of data and data communication techniques within the system 100 may be disclosed herein.
  • Embodiments of the present disclosure may be implemented into a system using any suitable hardware and/or software to configure as desired. FIG. 13 schematically illustrates a device 1300 that may serve as a host or a node (e.g., a host 110, a master node 102, or a slave node 104) in the system 100, in accordance with various embodiments. A number of components are illustrated in FIG. 13 as included in the device 1300, but any one or more of these components may be omitted or duplicated, as suitable for the application.
  • Additionally, in various embodiments, the device 1300 may not include one or more of the components illustrated in FIG. 13, but the device 1300 may include interface circuitry for coupling to the one or more components. For example, the device 1300 may not include a display device 1306, but may include display device interface circuitry (e.g., a connector and driver circuitry) to which a display device 1306 may be coupled. In another set of examples, the device 1300 may not include an audio input device 1324 or an audio output device 1308, but may include audio input or output device interface circuitry (e.g., connectors and supporting circuitry) to which an audio input device 1324 or audio output device 1308 may be coupled.
  • The device 1300 may include the node transceiver 120, in accordance with any of the embodiments disclosed herein, for managing communication along the bus 106 when the device 1300 is coupled to the bus 106. The device 1300 may include a processing device 1302 (e.g., one or more processing devices), which may be included in the node transceiver 120 or separate from the node transceiver 120. As used herein, the term “processing device” may refer to any device or portion of a device that processes electronic data from registers and/or memory to transform that electronic data into other electronic data that may be stored in registers and/or memory. The processing device 1302 may include one or more digital signal processors (DSPs), application-specific integrated circuits (ASICs), central processing units (CPUs), graphics processing units (GPUs), cryptoprocessors, or any other suitable processing devices. The device 1300 may include a memory 1304, which may itself include one or more memory devices such as volatile memory (e.g., dynamic random access memory (DRAM)), non-volatile memory (e.g., read-only memory (ROM)), flash memory, solid state memory, and/or a hard drive.
  • In some embodiments, the memory 1304 may be employed to store a working copy and a permanent copy of programming instructions to cause the device 1300 to perform any suitable ones of the techniques disclosed herein. In some embodiments, machine-accessible media (including non-transitory computer-readable storage media), methods, systems, and devices for performing the above-described techniques are illustrative examples of embodiments disclosed herein for communication over a two-wire bus. For example, a computer-readable media (e.g., the memory 1304) may have stored thereon instructions that, when executed by one or more of the processing devices included in the processing device 1302, cause the device 1300 to perform any of the techniques disclosed herein.
  • In some embodiments, the device 1300 may include another communication chip 1312 (e.g., one or more other communication chips). For example, the communication chip 1312 may be configured for managing wireless communications for the transfer of data to and from the device 1300. The term “wireless” and its derivatives may be used to describe circuits, devices, systems, methods, techniques, communications channels, etc., that may communicate data through the use of modulated electromagnetic radiation through a non-solid medium. The term does not imply that the associated devices do not contain any wires, although in some embodiments they might not.
  • The communication chip 1312 may implement any of a number of wireless standards or protocols, including but not limited to Institute for Electrical and Electronic Engineers (IEEE) standards including Wi-Fi (IEEE 802.11 family), IEEE 802.16 standards (e.g., IEEE 802.16-2005 Amendment), Long-Term Evolution (LTE) project along with any amendments, updates, and/or revisions (e.g., advanced LTE project, ultra mobile broadband (UMB) project (also referred to as “3GPP2”), etc.). IEEE 802.16 compatible Broadband Wireless Access (BWA) networks are generally referred to as WiMAX networks, an acronym that stands for Worldwide Interoperability for Microwave Access, which is a certification mark for products that pass conformity and interoperability tests for the IEEE 802.16 standards. The one or more communication chips 1312 may operate in accordance with a Global System for Mobile Communication (GSM), General Packet Radio Service (GPRS), Universal Mobile Telecommunications System (UMTS), High Speed Packet Access (HSPA), Evolved HSPA (E-HSPA), or LTE network. The one or more communication chips 1312 may operate in accordance with Enhanced Data for GSM Evolution (EDGE), GSM EDGE Radio Access Network (GERAN), Universal Terrestrial Radio Access Network (UTRAN), or Evolved UTRAN (E-UTRAN). The one or more communication chips 1312 may operate in accordance with Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Digital Enhanced Cordless Telecommunications (DECT), Evolution-Data Optimized (EV-DO), and derivatives thereof, as well as any other wireless protocols that are designated as 3G, 4G, 5G, and beyond. The communication chip 1312 may operate in accordance with other wireless protocols in other embodiments. The device 1300 may include an antenna 1322 to facilitate wireless communications and/or to receive other wireless communications (such as AM or FM radio transmissions).
  • In some embodiments, the communication chip 1312 may manage wired communications using a protocol other than the protocol for the bus 106 described herein. Wired communications may include electrical, optical, or any other suitable communication protocols. Examples of wired communication protocols that may be enabled by the communication chip 1312 include Ethernet, controller area network (CAN), I2C, media-oriented systems transport (MOST), or any other suitable wired communication protocol.
  • As noted above, the communication chip 1312 may include multiple communication chips. For instance, a first communication chip 1312 may be dedicated to shorter-range wireless communications such as Wi-Fi or Bluetooth, and a second communication chip 1312 may be dedicated to longer-range wireless communications such as GPS, EDGE, GPRS, CDMA, WiMAX, LTE, EV-DO, or others. In some embodiments, a first communication chip 1312 may be dedicated to wireless communications, and a second communication chip 1312 may be dedicated to wired communications.
  • The device 1300 may include battery/power circuitry 1314. The battery/power circuitry 1314 may include one or more energy storage devices (e.g., batteries or capacitors) and/or circuitry for coupling components of the device 1300 to an energy source separate from the device 1300 (e.g., AC line power, voltage provided by a car battery, etc.). For example, the battery/power circuitry 1314 may include the upstream filtering circuitry 132 and the downstream filtering circuitry 131 discussed above with reference to FIG. 2 and could be charged by the bias on the bus 106.
  • The device 1300 may include a display device 1306 (or corresponding interface circuitry, as discussed above). The display device 1306 may include any visual indicators, such as a heads-up display, a computer monitor, a projector, a touchscreen display, a liquid crystal display (LCD), a light-emitting diode display, or a flat panel display, for example.
  • The device 1300 may include an audio output device 1308 (or corresponding interface circuitry, as discussed above). The audio output device 1308 may include any device that generates an audible indicator, such as speakers, headsets, or earbuds, for example.
  • The device 1300 may include an audio input device 1324 (or corresponding interface circuitry, as discussed above). The audio input device 1324 may include any device that generates a signal representative of a sound, such as microphones, microphone arrays, or digital instruments (e.g., instruments having a musical instrument digital interface (MIDI) output).
  • The device 1300 may include a global positioning system (GPS) device 1318 (or corresponding interface circuitry, as discussed above). The GPS device 1318 may be in communication with a satellite-based system and may receive a location of the device 1300, as known in the art.
  • The device 1300 may include another output device 1310 (or corresponding interface circuitry, as discussed above). Examples of the other output device 1310 may include an audio codec, a video codec, a printer, a wired or wireless transmitter for providing information to other devices, or an additional storage device. Additionally, any suitable ones of the peripheral devices 108 discussed herein may be included in the other output device 1310.
  • The device 1300 may include another input device 1320 (or corresponding interface circuitry, as discussed above). Examples of the other input device 1320 may include an accelerometer, a gyroscope, an image capture device, a keyboard, a cursor control device such as a mouse, a stylus, a touchpad, a bar code reader, a Quick Response (QR) code reader, or a radio frequency identification (RFID) reader. Additionally, any suitable ones of the sensors or peripheral devices 108 discussed herein may be included in the other input device 1320.
  • Any suitable ones of the display, input, output, communication, or memory devices described above with reference to the device 1300 may serve as the peripheral device 108 in the system 100. Alternatively or additionally, suitable ones of the display, input, output, communication, or memory devices described above with reference to the device 1300 may be included in a host (e.g., the host 110) or a node (e.g., a master node 102 or a slave node 104).
  • FIGS. 14-19 illustrate systems and techniques for providing diagnostic and control information within various embodiments of the system 100. In particular, FIGS. 14-19 illustrate audio systems to which the diagnostic and control techniques disclosed herein may be applied. Describing these techniques with respect to audio systems is simply illustrative, and the systems and techniques disclosed herein may be applied to diagnostics and control for any suitable peripheral devices.
  • FIG. 14 is a block diagram of an example arrangement of audio components and sensors in an embodiment of the system 100, in accordance with various embodiments. Arrangements like that depicted in FIG. 14 may be particularly useful for managing audio in a vehicle or other enclosed space. In a vehicle setting, the host 110 and/or the master node 102 may be included in a head unit or vehicle function box, for example, and the links of the bus 106 may be routed through the walls, seats, floor, seatbelt, and other structures in the vehicle cabin.
  • The system 100 of FIG. 14 includes a number of slave nodes 104 (i.e., the slave nodes 0-7) daisy-chained along the bus 106. Each slave node 104 may be coupled to a peripheral device 108. For example, the peripheral device 108 associated with the slave node 0 may include a sensor 0. In some embodiments, the slave node 0 may be located within or behind a vehicle dashboard, and the sensor 0 may include an environmental sensor, such as a moisture or gas sensor, and/or a microphone. The peripheral device 108 associated with the slave node 1 may include a sensor 1, a speaker 11, and a speaker 12. In some embodiments, the slave node 1 and its peripheral device 108 may be located within or near a front passenger side door. The peripheral device 108 associated with the slave node 2 may include a speaker 21. In some embodiments, the slave node 2 and its peripheral device 108 may be located within or near a rear passenger side door.
  • The peripheral device 108 associated with the slave node 3 may include a sensor 3. In some embodiments, the slave node 3 may be located behind a rear passenger seat, and the sensor 3 may include an environmental sensor and/or a microphone. The peripheral device 108 associated with the slave node 4 may include a speaker 41, a speaker 42, and a speaker 43. In some embodiments, the slave node 4 may be located at the center rear of the passenger compartment, and the speakers 41-43 may be arranged across the rear of the passenger compartment.
  • The peripheral device 108 associated with the slave node 5 may include a speaker 51. In some embodiments, the slave node 5 and its peripheral device 108 may be located within or near a rear driver side door. The peripheral device 108 associated with the slave node 6 may include a sensor 6, a speaker 61, and a speaker 62. In some embodiments, the slave node 6 and its peripheral device 108 may be located within or near a front driver side door. The peripheral device 108 associated with the slave node 7 may include a speaker 71 and a speaker 72. In some embodiments, the slave node 7 and its associated peripheral device 108 may be located in a center console of the passenger compartment.
  • FIG. 15 is a block diagram of a particular example of the arrangement of FIG. 14, in accordance with various embodiments. In FIG. 15, some of the slave nodes 104 are shown as embodied in a distributed amplifier device. In particular, slave nodes 1, 2, 4, 5, 6, and 7 are shown as integrally attached to a speaker (i.e., the speakers 11, 21, 41, 51, 61, and 71, respectively). The distributed amplifier device of slave nodes 1, 4, 6, and 7 are also coupled to at least one additional speaker, as shown in FIG. 15.
  • A block diagram of a distributed amplifier embodiment of a slave node 104 as illustrated in FIG. 16. In particular, FIG. 16 is a block diagram of a distributed amplifier embodiment of the slave node 1, and its associated peripheral device 108, from the arrangement of FIG. 15, in accordance with various embodiments. The slave node 1 may include the node transceiver 120 (FIG. 2), a processing device 1302 (FIG. 13), a memory 1304 (FIG. 13), battery/power circuitry 1314 (FIG. 13), and an audio amplifier 1602. In some embodiments, the audio amplifier 1602 may have multiple outputs, and thus may be able to provide amplified audio signals to multiple speakers (e.g., the speakers 11 and 12).
  • The components illustrated in the slave node 104 of FIG. 16 may be included in a common housing, and that housing may have connectors to couple the slave node 104 to the peripheral device 108. As illustrated in FIG. 16, the slave node 1 may be coupled to the speaker 11 and to the speaker 12 via I2S/TDM/PDM connections (e.g., as discussed above with reference to the I2S/TDM/PDM transceiver 127 of the node transceiver 120), and to the sensor 1 via an I2C connection (e.g., as discussed above with reference to the I2C transceiver 129 of the node transceiver 120). In some embodiments, the audio amplifier 1602 may be a peripheral device 108, regardless of whether or not it is included in a common housing with the node transceiver 120.
  • FIG. 17 is a flow diagram of a method 1700 for communication of audio system diagnostic information by a slave node 104, in accordance with various embodiments. While the operations of the method 1700 (and the other methods disclosed herein) are arranged in a particular order in the figures, and illustrated once each, in various embodiments, one or more of the operations may be repeated, omitted, or performed out of order. In particular, various operations of the method 1700 (and other methods disclosed herein), although illustrated as performed in a particular sequence for the sake of illustration, may be performed in parallel as suitable. In the discussion below, operations of the method 1700 (and the other methods disclosed herein) may be described as performed by the slave node 1 of the system 100 of FIG. 14 for illustrative purposes, but the operations of the method 1700 (and the other methods disclosed herein), including individual operation of the method 1700, may be performed by any suitably configured device (e.g., any suitable ones of the other slave nodes 104 of FIG. 14) using the two-wire bus communication techniques disclosed herein. In particular, any of the operations of the method 1700 (and the other methods disclosed herein) may be performed in accordance with any of the embodiments of the system 100 disclosed herein.
  • At 1702, a slave node 104 (e.g., the slave node 1 of FIG. 14) may receive a synchronization control frame 180. The synchronization control frame 180 may be provided to the slave node 104 over a two-wire bus link 106 from an upstream node (e.g., the master node 102 or an upstream slave node 104). In some embodiments, the slave node 104 may receive the synchronization control frame 180 via the upstream DS transceiver 122 of the node transceiver 120. The synchronization control frame 180 received at 1702 may be structured in accordance with any of the embodiments described herein.
  • At 1704, the slave node 104 (e.g., the slave node 1 of FIG. 14) may receive audio data. The audio data may be provided to the slave node 104 over the two-wire bus link 106 from the upstream node discussed above with reference to 1702. In some embodiments, the slave node 104 may receive audio data at 1704 subsequent to receiving the synchronization control frame 180 at 1702. In some embodiments, the slave node 104 may receive the audio data via the upstream DS transceiver 122 of the node transceiver 120. In particular, the audio data may be included in the downstream data slots 198 of a superframe 190, as discussed above with reference to FIG. 4. The audio data may be encoded using any desired format (e.g., sampled at 44.1 or 48 kHz). In some embodiments, the audio data may originate at the host 110 and may be audio data streamed wirelessly to the host 110 or read from a computer readable medium, such as a CD or DVD.
  • At 1706, the slave node 104 (e.g., the slave node 1 of FIG. 14) may derive timing information from the synchronization control frame 180 received at 1702. For example, as discussed above with reference to FIG. 3, a preamble 182 may be used to recover a clock signal that can be locked by the PLL 128 of the node transceiver 120. In some embodiments, the upstream DS transceiver 122 and/or the PLL 128 of the transceiver 120 may derive the timing information at 1706.
  • At 1708, the slave node 104 (e.g., the slave node 1 of FIG. 14) may provide the audio data received at 1704 to an audio device (e.g., the speaker 11 or the speaker 12 of FIG. 14). The audio device may be coupled to the slave node 104 as a peripheral device 108. In some embodiments, the I2S/TDM/PDM transceiver 127 may provide the audio data to the audio device at 1708. The audio device may output audio in response to receipt of the audio data. In some embodiments, the audio device may include an amplifier and/or a speaker. For example, the slave node 104 may be a distributed amplifier device (as illustrated in FIG. 16) and may include an audio amplifier 1602 and one or more speakers. In some embodiments, the operations discussed with reference to 1706 and 1708 may be performed at least partially in parallel.
  • At 1710, the slave node 104 (e.g., the slave node 1 of FIG. 14) may receive first data representative of an operational characteristic of the audio device to which the audio data was provided at 1708. Although the term “operational characteristic” may be referred to in the singular, one or more operational characteristics may be received by the slave node 104 in the first data at 1710. The first data may be provided to the slave node 104 by a sensor (e.g., the sensor 1 of FIG. 14) coupled to the slave node 104 as a peripheral device 108. In some embodiments, the I2C transceiver 129 may receive the first data at 1710. The sensor that provides the first data may be a standalone sensor, an integrated sensor (e.g., integrated fault detection circuitry), or any other suitable sensor for providing operational information about the audio device (e.g., using techniques known in the art). In some embodiments, the sensor may include a detection circuit that analyzes the output of the audio device for operational characteristics (e.g., clipping). The first data may be received at 1710 in a synchronization control frame, a synchronization response frame, data following a synchronization control/response frame, via GPIO pins, or via any other suitable communication pathway in the system 100.
  • In some embodiments, the operational characteristic of 1710 may include an acoustic response indicative of a blocked speaker vent (when the audio device includes a vented speaker) or an acoustic response indicative of a blocked speaker (representative of a mechanical or acoustic blocking of the natural movement of the transducer of a speaker). In such embodiments, the sensor may be a mechanical or thermal sensor that detects the operational characteristic in any suitable manner. In some embodiments, the operational characteristic of 1710 may include a speaker surround failure (e.g., acoustic response indicative thereof), a speaker diaphragm failure (e.g., an acoustic response indicative thereof), a speaker enclosure failure (e.g., an acoustic response indicative thereof), a reversed speaker wire polarity (e.g., an acoustic response indicative thereof), a disconnected speaker wire (e.g., an acoustic response indicative thereof), or a speaker short. In such embodiments, the sensor may be a mechanical or electrical sensor that detects the operational characteristic in any suitable manner. In some embodiments, the operational characteristic of 1710 may include an audio amplifier clipping, an audio amplifier overheating, or an audio amplifier failure. In such embodiments, the sensor may be a mechanical, electrical, or thermal sensor that detects the operational characteristic in any suitable manner.
  • In some embodiments, the operational characteristic of 1710 may include a power-related characteristic, such as a voltage of a battery supplying the audio device. In such embodiments, the sensor may be an electrical sensor that detects the operational characteristic in any suitable manner. In some embodiments, the operational characteristic may include an impedance, a resonant frequency, or an acoustic box leakage. In such embodiments, the sensor may be an electrical or mechanical sensor that detects the operational characteristic in any suitable manner. In some embodiments, the operational characteristic of 1710 may include a voice coil temperature, a speaker overcurrent, or a speaker over excursion. In such embodiments, the sensor may be an electrical, mechanical, or thermal sensor that detects the operational characteristic in any suitable manner.
  • At 1712, the slave node 104 (e.g., the slave node 1 of FIG. 14) may provide a synchronization response frame 197 over the two-wire upstream bus link 106 toward an upstream node (e.g., the master node 102 or an upstream slave node 104). In some embodiments, the slave node 104 may provide the synchronization response frame 197 via the upstream DS transceiver 122 of the node transceiver 120. The timing of the provision of the synchronization response frame at 1712 may use the timing information derived at 1706; in particular, the slave node 104 may time the provision of the synchronization response frame at 1712 using a clock based on the timing information. The synchronization response frame 197 provided at 1712 may be structured in accordance with any of the embodiments described herein.
  • At 1714, the slave node 104 (e.g., the slave node 1 of FIG. 14) may provide second data representative of the operational characteristic of the audio device (discussed above with reference to 1710) over the two-wire upstream bus link 106 toward an upstream node (e.g., the master node 102 or an upstream slave node 104). In some embodiments, the slave node 104 may provide the second data via the upstream DS transceiver 122 of the node transceiver 120. In particular, the second data may be included in the upstream data slots 199 of a superframe 190, as discussed above with reference to FIG. 4. The slave node 104 may provide the second data at 1714 subsequent to providing the synchronization response frame 197 at 1712. In some embodiments, the second data may be transmitted through the system 100 to the host 110; in other embodiments, the second data to be received and processed by the master node 102 and/or another upstream slave node (e.g., the slave node 0 of FIG. 14) instead of or in addition to the host 110. The second data may be provided at 1714 in a synchronization response frame, data following a synchronization response frame, via GPIO pins, or via any other suitable communication pathway in the system 100.
  • In some embodiments, the first data of 1710 may encode the operational characteristic of the audio device using a first encoding scheme, and the second data 1714 may encode the operational characteristic of the audio device using a second, different encoding scheme. For example, a sensor coupled to the slave node 104 may provide the first data using a sensor-specific format over an I2C bus, while the slave node 104 may provide the second data upstream on the bus 106 in accordance with the encoding techniques discussed herein and in any desired format (e.g., a format that is readily parsed by the host 110 upon receipt of the second data). In some embodiments, the first data of 1710 may be “raw” or minimally processed operational characteristic data from a sensor, while the second data of 1714 may represent the operational characteristic in a more processed form. For example, the second data may represent an averaged or otherwise filtered version of the first data. In some embodiments, the second data may represent the result of comparing the first data against a threshold; for example, the first data may include a voice coil temperature value, and the second data may include a binary indicator of whether the voice coil temperature value exceeds a predetermined threshold (e.g., an acceptable temperature threshold). Processing performed on the first data of 1710 to generate the second data of 1714 may be performed by the processing device 1302 and/or the node transceiver 120. In some embodiments, the first data of 1710 may be identical to the second data of 1714.
  • An example of an implementation of the method 1700 in the system 100 of FIG. 14 is now provided. In this example, the method 1700 is carried out by the slave node 1 of FIG. 14. At 1702, the slave node 1 may receive a synchronization control frame 180 provided downstream on the bus 106 by the slave node 0. As discussed above, the synchronization control frame 180 may originate at the master node 102 and may be passed downstream from slave node 104 to slave node 104. At 1704, the slave node 1 may receive audio data provided downstream on the bus 106 by the slave node 0. The audio data may originate at the host 110 and may be provided to the master node 102 via an I2S/TDM bus, for example. The audio data may be provided to the slave node 0 from the master node 102, and the slave node 0 may relay the audio data to the slave node 1 (e.g., in the downstream data slots 198). In some embodiments, the audio data may be consumed by the slave node 1, while in other embodiments, the slave node 1 may provide the audio data further downstream along the bus 106 to the other slave nodes 104.
  • At 1706, the node transceiver 120 of the slave node 1 may derive timing information from the synchronization control frame 180. For example, the PLL 128 may generate a local clock based on the preamble 182 of the synchronization control frame 180. This local clock may be used to time further communications on the bus 106 (e.g., the provision of a synchronization response frame at 1712, discussed below). At 1708, the slave node 1 may provide the audio data received at 1704 to the speaker 11 and/or the speaker 12. In some embodiments, the slave node 1 may include an audio amplifier (e.g., the audio amplifier 1602) and may provide the audio data to the speaker 11 and/or the speaker 12 via the audio amplifier.
  • In some embodiments, the processing device 1302 in the slave node 1 may selectively delay and/or amplify the audio data prior to provision to the speaker 11 and/or the speaker 12 in order to achieve a desired audio effect. For example, to achieve a noise cancellation effect, the inputs to the speakers 11 and 12 may be selected so that interference between the outputs of the speakers 11, 12, and other speakers in the system 100 causes an acoustic null at a desired location. To achieve a distributed amplification effect, the inputs of the speakers 11 and 12 may be selected so that interference between the output of the speakers 11, 12, and other speakers in the system 100 causes additive interference at a desired location. In some embodiments, the selective delay and/or amplification of the inputs to a speaker included in the peripheral device 108 may be controlled by a control instruction from the host 110 or one or more processing devices 1302 distributed among the master node 102 and/or the slave nodes 104 of the system 100, as discussed in further detail below.
  • At 1710, the slave node 1 may receive first data representative of an operational characteristic of the speaker 11 and/or the speaker 12 from a sensor. Although “a sensor” may be referred to herein in the singular, a slave node 104 may receive data at 1710 from one or more sensors. In some embodiments, the sensor may be coupled to the slave node 1 as a peripheral device 108 associated with the slave node 1. For example, the sensor may be the sensor 1, and may be configured to detect an electrical fault in the speaker 11 and/or the speaker 12 (e.g., a speaker short or a disconnected speaker wire). In such an embodiment, the slave node 1 may receive the first data from the sensor 1 via an I2C bus managed by the I2C transceiver 129 (FIG. 2). In some embodiments, the sensor may be coupled to another slave node 104 in the system 100 (e.g., the sensor 3 or the sensor 6). For example, the sensor may be the sensor 3 and may be configured to detect acoustic box leakage from the speaker 11 and/or the speaker 12. In such an embodiment, the slave node 1 may receive the first data from the sensor 3 via an I2C bus connection between the sensor 3 and the slave node 3, and upstream communication on the bus 106 between the slave node 3 and the slave node 1.
  • At 1712, the slave node 1 may provide a synchronization response frame 197 upstream on the bus 106 to the slave node 0. The synchronization response frame 197 may originate at a last slave node of the system 100 (e.g., the slave node 7 of FIG. 14). The timing of the provision of the synchronization response frame 197 may be governed by the clock generated by the PLL 128 of the node transceiver 120.
  • At 1714, the slave node 1 may provide second data representative of the operational characteristic of the speaker 11 and/or the speaker 12 upstream on the bus 106. The second data may be based on the first data received at 1710, as discussed above with reference to 1714. The second data may be provided in the upstream data slots 199 along with data originating at the slave nodes 2-7 and communicated upstream on the bus 106. In some embodiments, the second data may be destined for the host 110, while in other embodiments, the second data may be consumed by nodes upstream of the slave node 1 (e.g., the slave node 0 or the master node 102). As discussed in further detail herein, the second data representative of the operational characteristic of the speaker 11 and/or the speaker 12 may be used to generate control instructions to control the operation of the speaker 11, the speaker 12, and/or any of the other peripheral devices 108 in the system 100.
  • FIG. 18 is a flow diagram of a method 1800 for communication of audio system diagnostic information and control by a host 110, in accordance with various embodiments. In the discussion below, operations of the method 1800 may be described as performed by the host 110 of the system 100 of FIG. 14 for illustrative purposes, but the operations of the method 1800, including individual operation of the method 1800, may be performed by any suitably configured device (using the two-wire bus communication techniques disclosed herein). In particular, any of the operations of the method 1800 may be performed in accordance with any of the embodiments of the system 100 disclosed herein.
  • At 1802, the host 110 may provide audio data to the master node 102 for provision along the bus 106 to a slave node 104. Upon receipt by the slave node 104, the audio data is to be output by an audio device coupled to the slave node 104 (e.g., as a peripheral device 108). In some embodiments, the host 110 may provide the audio data to the master node 102 at 1802 via an I2S/TDM bus (using an I2S/TDM transceiver included in the host 110), and the master node 102 may receive the audio data via the I2S/TDM/PDM transceiver 127. The master node 102 may provide the audio data to the bus 106 in the downstream data slots 198 of a superframe 190, and the audio data may pass through any intervening slave nodes 104 between the master node 102 and the target slave node 104. The audio data may be encoded using any desired format (e.g., sampled at 44.1 or 48 kHz). In some embodiments, the audio data may be streamed wirelessly to the host 110 or read from a computer readable medium, such as a CD or DVD, prior to the host 110 providing the audio data to the master node 102 at 1802. The audio data provided by the host 110 at 1802 may be provided to multiple slave nodes 104, each of which may include an audio device configured to output the audio data upon receipt.
  • At 1804, the host 110 may receive, via the bus 106 and the master node 102, data representative of an operational characteristic of the audio device of 1802. The host 110 may receive the data at 1804 using any suitable communication pathway(s) within the system 100. In some embodiments, the host 110 may receive the data representative of the operational characteristic via an I2C bus between the host 110 and the master node 102 (e.g., using an I2C transceiver included in the host 110). For example, the master node 102 may provide the data representative of the operational characteristic to the host 110 using the I2C transceiver 129. The data representative of the operational characteristic of the audio device may be based on data generated by a sensor coupled to the slave node 104 of 1802 or any other slave node 104. The data representative of the operational characteristic of the audio device may take the form of any of the embodiments discussed above with reference to 1710 of FIG. 17. The data received at 1804 may be first data and may be based on second data representative of the operational characteristic of the audio device provided to the master node 102 over the bus 106 from a slave node 104. The slave node 104 may be associated with the audio device, or it may be a different audio device. For example, the second data may be generated by a sensor coupled to the slave node 104 associated with the audio device or a slave node 104 that is not coupled to the audio device. In some embodiments, the second data may be provided to the master node 102 along with a synchronization response frame 197. The synchronization response frame 197 may be generated by a last slave node 104 on the bus 106 (e.g., the slave node 7 of FIG. 14). For example, the second data may be provided to the master node 102 in the upstream data slots 199 of a superframe 190, as discussed above with reference to FIG. 4. The relationship between the first and second data may take the form of any of the embodiments discussed above with reference to FIG. 17. For example, in some embodiments, the first and second data may be the same.
  • At 1806, the host 110 may provide a control instruction for the audio device to the master node 102 for transmission downstream over the bus 106. In particular, the master node 102 may transmit data representative of the control instruction to the slave node 104 over the bus 106 (e.g., in a synchronization control frame, in data following a synchronization control frame, via GPIO pins, or using any other suitable communication pathway). The host 110 may generate the control instruction based on the operational characteristic of the audio device received at 1804, and, in some embodiments, execution of the control instruction by the audio device or its associated slave node 104 may change the operational characteristic of the audio device. For example, in embodiments in which the operational characteristic includes an indicator that the audio device (e.g., an amplifier) exceeds a threshold temperature, the control instruction may require the audio device to reduce its power consumption and thereby decrease its temperature. In some embodiments, the operations discussed above with reference to 1806 may not be performed; instead, the method may end with the operations discussed above with reference to 1804.
  • The method 1800 may include further operations. For example, as discussed in further detail below with reference to FIG. 19, the host 110 may provide a control instruction for a first audio device based on an operational characteristic of a second, different audio device. The second audio device may be coupled to a same slave node 104 as the first audio device or a different slave node 104.
  • In another example, the host 110 may include display interface circuitry (e.g., as discussed above with reference to the display device 1306 of FIG. 13) that is configured to provide a visual indicator of the operational characteristic of the audio device to a display device 1306 in communication with the host 110. Such a visual indicator may be useful, for example, to alert a driver of a vehicle that a peripheral device 108 coupled to the bus 106 is experiencing a fault or is operating normally. This visual indicator may include a text display, an icon, or any other suitable visual indicator. In some embodiments, the host 110 may include audio output device interface circuitry (e.g., as discussed above with reference to the audio output device 1308 of FIG. 13) that is configured to provide an audible indicator of the operational characteristic of the audio device.
  • In another example, the host 110 may receive, via the bus 106 and the master node 102, data representative of a measurement made by a seat pressure sensor, a proximity sensor, a light sensor, a moisture sensor, a gesture sensor, or another environmental sensor coupled to a slave node 104. In some embodiments, the host 110 may receive this measurement data along with the operational characteristic data received at 1804 (e.g., in the upstream data slots 199). In some embodiments, the host 110 may receive the measurement data via an I2C bus between the host 110 and the master node 102 (e.g., using an I2C transceiver included in the host 110). For example, the master node 102 may provide the measurement data to the host 110 using the I2C transceiver 129. The data representative of the operational characteristic of the audio device may be based on data generated by a sensor coupled to the slave node 104 of 1802 or any other slave node 104.
  • The host 110 may then provide a control instruction to the audio device (e.g., as part of 1806) based at least in part on this measurement data. For example, the host 110 may use the measurement data from a seat pressure sensor to provide a control instruction to power down audio devices (e.g., speakers and/or microphones) proximate to an empty seat in order to conserve power. In another example, when the host 110 is performing active noise cancellation within the passenger compartment of a vehicle, the host 110 may use the measurement data from a seat pressure sensor to determine that no passenger is seated in a particular location in the vehicle and thus that audio interference that occurs at that location need not be carefully controlled when active noise cancellation control instructions are provided. In another example, when the host 110 is performing active noise cancellation within the passenger compartment of a vehicle, the host 110 may use the measurement data from a seat pressure sensor to determine that a passenger is seated in a particular location in the vehicle and, in response, to provide a control instruction to adjust and operating characteristics of a speaker (e.g., the speaker driving current) to achieve noise cancellation for that passenger. In another example, when the host 110 determines that a microphone coupled to a slave node 104 is generating little to no output, the measurement data generated by a seat pressure sensor in a seat proximate to the microphone may aid the host 110 in determining that the microphone is not failing (rather, there is simply no passenger proximate to the microphone and generating sound).
  • The host 110 may use measurement data from a proximity sensor (e.g., a capacitive sensor or infrared sensor) to determine how close a passenger in a vehicle is to an audio device (e.g., a speaker or microphone) and to provide a control instruction to that audio device to scale its output or amplification appropriately (e.g., to reduce the power output to a speaker very close to a passenger). In an active noise cancellation application, the host 110 may use measurement data from a proximity sensor to track a position of a passenger within a vehicle in order to appropriately locate the noise cancellation nulls when active noise cancellation control instructions are provided.
  • The host 110 may use measurement data from a light sensor in the same manner as discussed above with reference to a seat pressure sensor when the light sensor is configured to indicate seat occupancy (e.g., when interruption of a light beam indicates the presence of a passenger in a seat). The host 110 may use measurement data from a light sensor to adjust the brightness of a display (e.g., a display of an operational characteristic of an audio device).
  • The host 110 may use measurement data from a moisture sensor to determine when a defogger or other environmental control system should be turned on, and thus when to activate a noise cancellation system to cancel the noise generated by the environmental control system. The host 110 may use measurement data from a gesture sensor (e.g., a video camera or other sensor for tracking the motion of a passenger's hands) for user interface purposes (e.g., to provide a control instruction to a slave node 104 to reduce the output volume of an associated speaker when a user performs a predetermined volume reduction gesture). Microphones included as peripheral devices 108 may also be used to receive voice instructions, which may be processed and recognized by the host 110.
  • An example of an implementation of the method 1800 in the system 100 of FIG. 14 is now provided. In this example, the method 1800 is carried out by the host 110 of FIG. 14. At 1802, the host 110 may provide audio data to the master node 102 for provision along the bus 106 to the slave node 4 for output at the speaker 41. At 1804, the host 110 may receive, via the bus 106 and the master node 102, data representative of an operational characteristic of the speaker 41. That data may include a measurement by a microphone included in the sensor 6 (associated with the slave node 6) of a test tone generated by the speaker 41. In particular, the data may represent a maximum amplitude of an audio signal detected by the microphone in the sensor 6 in response to a test tone generated by the speaker 41. The sensor 6 may provide the microphone measurement to the slave node 6 as representative of an operational characteristic of the speaker 41 (e.g., via the I2C transceiver 129 of the node transceiver 120 in the slave node 6). The slave node 6 may optionally process the measurement provided by the sensor 6 and may provide data representative of the operational characteristic of the speaker 41 over the bus 106, through the intervening slave nodes 0-5, to the master node 102. The master node 102 may provide the data to the host 110 (e.g., via the I2C transceiver 129 of the node transceiver 120 of the master node 102). At 1806, the host 110 may provide a power increase control instruction for the speaker 41 to the master node 102 (e.g., to increase the maximum amplitude of audio signals detected by the microphone and the sensor 6 for a distributed amplification application). The master node 102 may provide the control instruction over the bus 106 through the intervening slave nodes 0-3 to the slave node 4. The slave node 4 may itself increase the power provided to the speaker 41 in response to the control instruction, or the slave node 4 may provide the control instruction to the speaker 41 to cause a power increase.
  • FIG. 19 is a flow diagram of a method 1900 for audio system control by a slave node 104, in accordance with various embodiments. In the discussion below, operations of the method 1900 may be described as performed by the slave node 1 of the system 100 of FIG. 14 (and with reference to other particular slave nodes and peripheral devices) for illustrative purposes, but the operations of the method 1900, including individual operation of the method 1900, may be performed by any suitably configured device (using the two-wire bus communication techniques disclosed herein). In particular, any of the operations of the method 1900 may be performed in accordance with any of the embodiments of the system 100 disclosed herein. In some embodiments, a slave node 104 may perform the method 1700 and the method 1900 in an integrated manner.
  • At 1902, the slave node 104 (e.g., the slave node 1 of FIG. 14) may provide a synchronization response frame 197 upstream over the bus 106. The slave node 104 may be coupled to a first audio device (e.g., the speaker 11 or the speaker 12 of FIG. 14). The synchronization response frame 197 of 1902 may take the form of any of the embodiments disclosed herein.
  • At 1904, the slave node 104 (e.g., the slave node 1 of FIG. 14) may provide data upstream that is representative of an operational characteristic of a second audio device, wherein the second audio device is coupled to a downstream slave node 104 (e.g., the speaker 51 associated with the slave node 5). The data representative of the operational characteristic of the second audio device may be provided subsequent to provision of the synchronization response frame 197 (1902); for example, the data representative of the operational characteristic of the second audio device may be provided in the upstream data slots 199 of the superframe 190. Prior to providing the data upstream at 1904, the slave node 104 may receive the data from a downstream slave node 104 (which may be a same slave node as associated with the second audio device, or a different slave node). For example, a sensor coupled to a slave node 104 may generate the data, and that slave node 104 may provide the data upstream via the bus 106 (e.g., in accordance with any of the embodiments discussed above with reference to 1710 of FIG. 17). The data provided at 1904 may be provided using any suitable communication pathway in the system 100 (e.g., in a synchronization response frame, in data following a synchronization response frame, via GPIO pins, etc.).
  • At 1906, the slave node 104 (e.g., the slave node 1 of FIG. 14) may receive a synchronization control frame 180. The slave node 104 may receive the synchronization control frame 180 from an upstream node (e.g., the master node 102 or and intervening slave node 104). The operations associated with 1906 may be performed in accordance with any of the embodiments of the operations associated with 1702 of FIG. 17.
  • At 1908, the slave node 104 (e.g., the slave node 1 of FIG. 14) may recover a clock signal from the synchronization control frame 180. In some embodiments of 1908, the PLL 128 may lock to the recovered clock signal, as discussed above with reference to FIG. 2. The operations associated with 1908 may be performed in accordance with any of the embodiments of the operations associated with 1706 of FIG. 17.
  • At 1910, the slave node 104 may receive, from an upstream node (e.g., the master node 102 or an upstream slave node 104), a control instruction for the first audio device. The control instruction may be based on the operational characteristic of the second audio device (provided upstream at 1904). The slave node 104 may receive the control instruction at 1910 subsequent to receiving the synchronization control frame at 1906; in some embodiments, the control instruction may be provided in the downstream data slots 198 after the synchronization control frame 180. In some embodiments, the control instruction may originate from the host 110, as discussed above with reference to FIG. 18. Execution of the control instruction by the slave node 104 may change an operational characteristic of the first audio device associated with the slave node 104. In this manner, operational characteristics of one audio device coupled to the bus 106 may be used to generate control instructions for another audio device coupled to the bus 106. In one example, the first and second audio devices may be speakers, the operational characteristic of the second speaker may be a temperature of the second speaker, and a control instruction may cause the first speaker to increase its speaker driving current (and thereby increase its temperature), with this control instruction possibly accompanied by a control instruction to the second speaker to decrease its speaker driving current (e.g., in a distributed amplification application). Although a common “operational characteristic” as discussed above with reference to FIG. 19, the host 110 may use data representative of a first operational characteristic of a first audio device to generate a control instruction to affect a second, different operational characteristic of a second audio device. The control instruction may be received at 1910 via any suitable ones of the communication pathways disclosed herein.
  • An example of an implementation of the method 1900 in the system 100 of FIG. 14 is now provided. In this example, the method 1900 is carried out by the slave node 2 of FIG. 14. At 1902, the slave node 2 may provide a synchronization response frame 197 upstream to the slave node 1. The slave node 2 may be coupled to a speaker 21 as a peripheral device 108. At 1904, the slave node 2 may provide data upstream that is representative of an operational characteristic of the speaker 43 associated with the slave node 4. This data may be, for example, an indication that the voice coil of the speaker 43 has exited its magnetic gap and thus has undergone an over-excursion. The over-excursion may be detected by circuitry included in the speaker 43 (e.g., fault detection circuitry) and may be provided to the I2C transceiver 129 of the node transceiver 120 of the slave node 4. The slave node 4 may push this data onto the bus 106 (e.g., in the upstream data slots 199), the slave node 3 may provide the data to the slave node 2, and the slave node 2 may provide the data upstream at 1904.
  • At 1906, the slave node 2 may receive a synchronization control frame 180 from the slave node 1. At 1908, the slave node 2 may recover a clock signal from the synchronization control frame 180 received at 1906 (e.g., as discussed above with reference to FIG. 3). At 1910, the slave node 2 may receive, from the slave node 1, a control instruction for the speaker 21. The control instruction may be generated by the host 110 or a node upstream of the slave node 2 (e.g., the master node 102, the slave node 0, or the slave node 1), and may be based on the operational characteristic of the speaker 43. For example, in response to an over-excursion of the speaker 43, the host 110 may determine that the speaker 43 should be taken “offline” and no longer used to generate audio output; to compensate for the loss of the speaker 43, the host 110 may provide a control instruction to the slave node 2 to increase the power of the speaker 21.
  • The following paragraphs provide examples of various ones of the embodiments disclosed herein.
  • Example 1 is a slave device for two-wire low-latency communication of audio system diagnostic information, including: first circuitry to: receive a synchronization control frame provided over a two-wire bus link to the slave device from an upstream device, subsequent to receipt of the synchronization control frame, receive audio data communicated over the two-wire bus link to the slave device from the upstream device, provide a synchronization response frame over the two-wire bus link toward the upstream device, and subsequent to provision of the synchronization response frame, provide, over the two-wire bus link toward the upstream device, first data representative of an operational characteristic of an audio device coupled to the slave device; second circuitry to derive timing information from the synchronization control frame, wherein the timing information is used to time the provision of the synchronization response frame; and third circuitry to: provide the audio data to the audio device, and receive, from a sensor coupled to the slave device, second data representative of the operational characteristic of the audio device.
  • Example 2 may include the subject matter of Example 1, and may further specify that the first data encodes the operational characteristic of the audio device using a first encoding scheme, and the second data encodes the operational characteristic of the audio device using a second encoding scheme different from the first encoding scheme.
  • Example 3 may include the subject matter of any of Examples 1-2, and may further specify that the third circuitry is to receive the second data via an I2C bus.
  • Example 4 may include the subject matter of any of Examples 1-3, and may further specify that the operational characteristic of the audio device includes an acoustic response indicative of a blocked speaker vent or an acoustic response indicative of a blocked speaker.
  • Example 5 may include the subject matter of any of Examples 1-4, and may further specify that the operational characteristic of the audio device includes a speaker surround failure, a speaker diaphragm failure, a speaker enclosure failure, a reversed speaker wire polarity, a disconnected speaker wire, or a speaker short.
  • Example 6 may include the subject matter of any of Examples 1-5, and may further specify that the first circuitry is to receive a control instruction for the audio device, and wherein execution of the control instruction is to change the operational characteristic of the audio device.
  • Example 7 may include the subject matter of any of Examples 1-6, and may further specify that the audio device includes an amplifier and a speaker.
  • Example 8 may include the subject matter of any of Examples 1-7, and may further specify that the operational characteristic includes an audio amplifier clipping, an audio amplifier overheating, or an audio amplifier failure.
  • Example 9 may include the subject matter of any of Examples 1-8, and may further specify that the first, second, and third circuitry are included in a common housing with an audio amplifier.
  • Example 10 is a host device for two-wire low-latency communication of audio system diagnostic information, including: first circuitry to provide audio data to a master device, wherein the master device is a master of a half-duplex two-wire bus, wherein the audio data is to be provided over the two-wire bus to a slave device, and wherein the audio data is to be output by an audio device coupled to the slave device; and second circuitry to receive, from the master device, first data representative of an operational characteristic of the audio device, wherein second data representative of the operational characteristic of the audio device is provided to the master device over the two-wire bus along with a synchronization response frame generated by a last slave device on the two-wire bus.
  • Example 11 may include the subject matter of Example 10, and may further specify that the first data is the same as the second data.
  • Example 12 may include the subject matter of any of Examples 10-11, and may further specify that the operational characteristic of the audio device includes a battery voltage.
  • Example 13 may include the subject matter of any of Examples 10-12, and may further specify that the operational characteristic of the audio device includes an impedance, a resonant frequency, or an acoustic box leakage.
  • Example 14 may include the subject matter of any of Examples 10-13, and may further specify that the second circuitry is to provide, to the master device, a control instruction for the audio device, wherein the master device is to transmit data representative of the control instruction to the slave device along the two-wire bus, and the host device is to generate the control instruction based on the operational characteristic of the audio device.
  • Example 15 may include the subject matter of any of Examples 10-14, and may further specify that: the slave device is a first slave device; the audio device is a first audio device; the second circuitry is to provide current to the master device, a control instruction for a second audio device, wherein the second audio device is coupled to a second slave device along the two-wire bus; the master device is to transmit data representative of the control instruction to the second slave device along the two-wire bus; and the host device is to generate a control instruction based on the operational characteristic of the first slave device.
  • Example 16 may include the subject matter of Example 15, and may further specify that the control instruction is a distributed amplification control instruction.
  • Example 17 may include the subject matter of any of Examples 15-16, and may further include display interface circuitry to provide a visual indicator of the operational characteristic of the audio device to a display device.
  • Example 18 is one or more non-transitory computer readable media having instructions thereon that, in response to execution by one or more processing devices of a host device, cause the host device to: subsequent to provision by the host device of audio data to a master device on a two-wire bus, receive, from the master device, first data representative of an operational characteristic of an audio device, wherein the audio data is to be transmitted along the two-wire bus to a slave device, the audio device is coupled to the slave device, the audio data is to be output by the audio device, and second data representative of the operational characteristic of the audio device is provided to the master device along with a synchronization response frame generated by a last slave device on the two-wire bus; and in response to receipt of the first data representative of the operational characteristic of the audio device, provide a control instruction for the audio device to the master device, wherein the master device is to transmit data representative of the control instruction to the slave device along the two-wire bus, and wherein execution of the control instruction is to change the operational characteristic of the audio device.
  • Example 19 may include the subject matter of Example 18, and may further specify that the slave device is the last slave device.
  • Example 20 may include the subject matter of any of Examples 18-19, and may further specify that the operational characteristic of the audio device includes a voice coil temperature, a speaker overcurrent, or a speaker over-excursion.
  • Example 21 may include the subject matter of any of Examples 18-20, and may further specify that: the host device is included in a passenger vehicle; the slave device is a first slave device; the instructions, in response to execution by the one or more processing devices of the host device, cause the host device to receive, from the master device, third data representative of a measurement made by a sensor coupled to a second slave device on the two-wire bus, wherein the second slave device is different from the first slave device; the sensor includes a seat pressure sensor, a proximity sensor, a light sensor, a moisture sensor, or a gesture sensor; and the control instruction is based at least in part on the third data.
  • Example 22 may include the subject matter of Example 21, and may further specify that the operational characteristic of the audio device is a speaker driving current, the sensor includes a seat pressure sensor for a seat, and the control instruction is to adjust the speaker driving current to achieve noise cancellation for a passenger in the seat.
  • Example 23 is a method for low-latency control of an audio system, including: providing, by a first slave device on a two-wire bus, a synchronization response frame over a link of the two-wire bus toward an upstream device, wherein the first slave device is coupled to a first audio device; subsequent to providing the synchronization response frame, providing, by the first slave device over the link of the two-wire bus toward the upstream device, data representative of an operational characteristic of a second audio device coupled to a second slave device on the two-wire bus, wherein the second slave device is downstream of the first slave device; receiving, by the first slave device, a synchronization control frame from the upstream device over the link of the two-wire bus; recovering, by the first slave device, a clock signal from the synchronization control frame; and subsequent to receiving the synchronization control frame, receiving, by the first slave device from the upstream device over the link of the two-wire bus, a control instruction for the first audio device, wherein execution of the control instruction is to change an operational characteristic of the first audio device, and wherein the control instruction is based on the operational characteristic of the second audio device.
  • Example 24 may include the subject matter of Example 23, and may further include locking a phase locked loop based on the recovered clock signal.
  • Example 25 may include the subject matter of any of Examples 23-24, and may further specify that the operational characteristic of the second audio device is a temperature of a second speaker, the first audio device includes a first speaker, and wherein the control instruction is to increase a speaker driving current to the first speaker.
  • Example 26 is a device including means for performing any of the methods disclosed herein.
  • Example 27 is one or more computer readable media having instructions thereon that, in response to execution by one or more processing devices of a device, cause the device to perform any of the methods disclosed herein.

Claims (24)

What is claimed is:
1. A slave device for two-wire low-latency communication of audio system diagnostic information, comprising:
first circuitry to:
receive a synchronization control frame provided over a two-wire bus link to the slave device from an upstream device,
subsequent to receipt of the synchronization control frame, receive audio data communicated over the two-wire bus link to the slave device from the upstream device,
provide a synchronization response frame over the two-wire bus link toward the upstream device, and
subsequent to provision of the synchronization response frame, provide, over the two-wire bus link toward the upstream device, first data representative of an operational characteristic of an audio device coupled to the slave device;
second circuitry to derive timing information from the synchronization control frame, wherein the timing information is used to time the provision of the synchronization response frame; and
third circuitry to:
provide the audio data to the audio device, and
receive, from a sensor coupled to the slave device, second data representative of the operational characteristic of the audio device.
2. The slave device of claim 1, wherein the third circuitry includes an Inter-Integrated Circuit (I2C) transceiver.
3. The slave device of claim 1, wherein the operational characteristic of the audio device includes an acoustic response indicative of a blocked speaker vent or an acoustic response indicative of a blocked speaker.
4. The slave device of claim 1, wherein the operational characteristic of the audio device includes a speaker surround failure, a speaker diaphragm failure, a speaker enclosure failure, a reversed speaker wire polarity, a disconnected speaker wire, or a speaker short.
5. The slave device of claim 1, wherein the first circuitry is to receive a control instruction for the audio device, and wherein execution of the control instruction is to change the operational characteristic of the audio device.
6. The slave device of claim 1, wherein the audio device includes an amplifier and a speaker.
7. The slave device of claim 1, wherein the operational characteristic includes an audio amplifier clipping, an audio amplifier overheating, or an audio amplifier failure.
8. The slave device of claim 1, wherein the first, second, and third circuitry are included in a common housing with an audio amplifier.
9. A host device for two-wire low-latency communication of audio system diagnostic information, comprising:
first circuitry to provide audio data to a master device, wherein the master device is a master of a half-duplex two-wire bus, wherein the audio data is to be provided over the two-wire bus to a slave device, and wherein the audio data is to be output by an audio device coupled to the slave device; and
second circuitry to receive, from the master device, first data representative of an operational characteristic of the audio device, wherein second data representative of the operational characteristic of the audio device is provided to the master device over the two-wire bus along with a synchronization response frame generated by a last slave device on the two-wire bus.
10. The host device of claim 9, wherein the first data is the same as the second data.
11. The host device of claim 9, wherein the operational characteristic of the audio device includes a battery voltage.
12. The host device of claim 9, wherein the operational characteristic of the audio device includes an impedance, a resonant frequency, or an acoustic box leakage.
13. The host device of claim 9, wherein the second circuitry is to provide, to the master device, a control instruction for the audio device, wherein the master device is to transmit data representative of the control instruction to the slave device along the two-wire bus, and the host device is to generate the control instruction based on the operational characteristic of the audio device.
14. The host device of claim 9, wherein:
the slave device is a first slave device;
the audio device is a first audio device;
the second circuitry is to provide current to the master device, a control instruction for a second audio device, wherein the second audio device is coupled to a second slave device along the two-wire bus;
the master device is to transmit data representative of the control instruction to the second slave device along the two-wire bus; and
the host device is to generate a control instruction based on the operational characteristic of the first slave device.
15. The host device of claim 14, wherein the control instruction is a distributed amplification control instruction.
16. The host device of claim 14, further comprising display interface circuitry to provide a visual indicator of the operational characteristic of the audio device to a display device.
17. One or more non-transitory computer readable media having instructions thereon that, in response to execution by one or more processing devices of a host device, cause the host device to:
subsequent to provision by the host device of audio data to a master device on a two-wire bus, receive, from the master device, first data representative of an operational characteristic of an audio device, wherein the audio data is to be transmitted along the two-wire bus to a slave device, the audio device is coupled to the slave device, the audio data is to be output by the audio device, and second data representative of the operational characteristic of the audio device is provided to the master device along with a synchronization response frame generated by a last slave device on the two-wire bus; and
in response to receipt of the first data representative of the operational characteristic of the audio device, provide a control instruction for the audio device to the master device, wherein the master device is to transmit data representative of the control instruction to the slave device along the two-wire bus, and wherein execution of the control instruction is to change the operational characteristic of the audio device.
18. The one or more non-transitory computer readable media of claim 17, wherein the slave device is the last slave device.
19. The one or more non-transitory computer readable media of claim 17, wherein the operational characteristic of the audio device includes a voice coil temperature, a speaker overcurrent, or a speaker over-excursion.
20. The one or more non-transitory computer readable media of claim 17, wherein:
the host device is included in a passenger vehicle;
the slave device is a first slave device;
the instructions, in response to execution by the one or more processing devices of the host device, cause the host device to receive, from the master device, third data representative of a measurement made by a sensor coupled to a second slave device on the two-wire bus, wherein the second slave device is different from the first slave device;
the sensor includes a seat pressure sensor, a proximity sensor, a light sensor, a moisture sensor, or a gesture sensor; and
the control instruction is based at least in part on the third data.
21. The one or more non-transitory computer readable media of claim 20, wherein the operational characteristic of the audio device is a speaker driving current, the sensor includes a seat pressure sensor for a seat, and the control instruction is to adjust the speaker driving current to achieve noise cancellation for a passenger in the seat.
22. A method for low-latency control of an audio system, comprising:
providing, by a first slave device on a two-wire bus, a synchronization response frame over a link of the two-wire bus toward an upstream device, wherein the first slave device is coupled to a first audio device;
subsequent to providing the synchronization response frame, providing, by the first slave device over the link of the two-wire bus toward the upstream device, data representative of an operational characteristic of a second audio device coupled to a second slave device on the two-wire bus, wherein the second slave device is downstream of the first slave device;
receiving, by the first slave device, a synchronization control frame from the upstream device over the link of the two-wire bus;
recovering, by the first slave device, a clock signal from the synchronization control frame; and
subsequent to receiving the synchronization control frame, receiving, by the first slave device from the upstream device over the link of the two-wire bus, a control instruction for the first audio device, wherein execution of the control instruction is to change an operational characteristic of the first audio device, and wherein the control instruction is based on the operational characteristic of the second audio device.
23. The method of claim 22, further comprising locking a phase locked loop based on the recovered clock signal.
24. The method of claim 22, wherein the operational characteristic of the second audio device is a temperature of a second speaker, the first audio device includes a first speaker, and wherein the control instruction is to increase a speaker driving current to the first speaker.
US14/884,987 2012-10-05 2015-10-16 Peripheral device diagnostics and control over a two-wire communication bus Active 2033-05-24 US9946680B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US14/884,987 US9946680B2 (en) 2012-10-05 2015-10-16 Peripheral device diagnostics and control over a two-wire communication bus

Applications Claiming Priority (11)

Application Number Priority Date Filing Date Title
US13/646,397 US9417944B2 (en) 2011-10-05 2012-10-05 Two-wire communication system for high-speed data and power distribution
US13/646,382 US8990464B2 (en) 2011-10-05 2012-10-05 Methods for discovery, configuration, and coordinating data communications between master and slave devices in a communication system
US201361843896P 2013-07-08 2013-07-08
US201361843902P 2013-07-08 2013-07-08
US201361843891P 2013-07-08 2013-07-08
US201361845542P 2013-07-12 2013-07-12
US14/063,886 US9448959B2 (en) 2012-10-05 2013-10-25 Two-wire communication protocol engine
US201462065724P 2014-10-19 2014-10-19
US201462065738P 2014-10-19 2014-10-19
US201462065736P 2014-10-19 2014-10-19
US14/884,987 US9946680B2 (en) 2012-10-05 2015-10-16 Peripheral device diagnostics and control over a two-wire communication bus

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US14/063,886 Continuation US9448959B2 (en) 2011-10-05 2013-10-25 Two-wire communication protocol engine

Publications (2)

Publication Number Publication Date
US20160034416A1 true US20160034416A1 (en) 2016-02-04
US9946680B2 US9946680B2 (en) 2018-04-17

Family

ID=55180188

Family Applications (3)

Application Number Title Priority Date Filing Date
US14/884,947 Active 2033-05-27 US9946679B2 (en) 2011-10-05 2015-10-16 Distributed audio coordination over a two-wire communication bus
US14/884,900 Active 2033-06-10 US10311010B2 (en) 2011-10-05 2015-10-16 Two-wire communication systems and applications
US14/884,987 Active 2033-05-24 US9946680B2 (en) 2012-10-05 2015-10-16 Peripheral device diagnostics and control over a two-wire communication bus

Family Applications Before (2)

Application Number Title Priority Date Filing Date
US14/884,947 Active 2033-05-27 US9946679B2 (en) 2011-10-05 2015-10-16 Distributed audio coordination over a two-wire communication bus
US14/884,900 Active 2033-06-10 US10311010B2 (en) 2011-10-05 2015-10-16 Two-wire communication systems and applications

Country Status (2)

Country Link
US (3) US9946679B2 (en)
CN (1) CN106878125B (en)

Cited By (37)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140256440A1 (en) * 2011-10-21 2014-09-11 Novomatic Ag Gaming machine
US20160099817A1 (en) * 2007-03-02 2016-04-07 Qualcomm Incorporated N-phase phase and polarity encoded serial interface
US20160164973A1 (en) * 2014-12-04 2016-06-09 Apple Inc. Master device for using connection attribute of electronic accessories connections to facilitate locating an accessory
US20160337138A1 (en) * 2015-05-12 2016-11-17 Linear Technology Corporation System with sleep and wake up control over dc path
US20160371157A1 (en) * 2015-06-19 2016-12-22 Qualcomm Incorporated Serial interface with bit-level acknowledgement and error correction
US20170070195A1 (en) * 2015-09-04 2017-03-09 MUSIC Group IP Ltd. Method for controlling power consumption of a loudspeaker system
US20170195789A1 (en) * 2014-09-29 2017-07-06 Hitachi Kokusai Electric Inc. Loudspeaker device and wireless communication system
US9711041B2 (en) 2012-03-16 2017-07-18 Qualcomm Incorporated N-phase polarity data transfer
CN107182002A (en) * 2017-05-16 2017-09-19 苏州顺芯半导体有限公司 It is a kind of to recognize that modulus conversion chip audio output data format realizes device and implementation method
US20170315652A1 (en) * 2016-04-27 2017-11-02 Qualcomm Incorporated Variable rate display interfaces
US9948485B2 (en) 2007-03-02 2018-04-17 Qualcomm Incorporated Three phase and polarity encoded serial interface
CN107995080A (en) * 2017-12-14 2018-05-04 长沙玄米电子科技有限公司 Multi-host communication method based on two-wire bus
US10063968B1 (en) 2017-06-02 2018-08-28 Apple Inc. Dynamic master assignment in distributed wireless audio system for thermal and power mitigation
US10219073B1 (en) * 2017-11-20 2019-02-26 Ford Global Technologies, Llc Vehicle audio system
US10250376B2 (en) 2016-01-29 2019-04-02 Analog Devices, Inc. Clock sustain in the absence of a reference clock in a communication system
US20190139531A1 (en) * 2017-11-08 2019-05-09 Hyundai Motor Company Digital active road noise control method and system
EP3486794A1 (en) * 2017-11-15 2019-05-22 Sensata Technologies, Inc. A communication system configured for transmitting sensor values from n sensing sources to a control unit
WO2019112709A1 (en) * 2017-12-05 2019-06-13 Qualcomm Incorporated Super-speed uart with per-frame bit-rate and independent variable upstream and downstream rates
US10374583B1 (en) 2018-04-02 2019-08-06 Analog Devices, Inc. Dynamic hysteresis circuit
US10397021B2 (en) 2016-01-29 2019-08-27 Analog Devices, Inc. Synchronous slave-to-slave communications
US20190281398A1 (en) * 2018-03-12 2019-09-12 Panasonic Intellectual Property Management Co., Ltd. Noise reduction device, noise reduction system, and fault detection method for noise reduction device
US10649945B1 (en) 2018-12-10 2020-05-12 Analog Devices International Unlimited Company Non-native digital interface support over a two-wire communication bus
US10782714B2 (en) * 2017-01-06 2020-09-22 Sunland Information Technology Co., Ltd. Heat dissipation system and method for smart pianos
US10856199B2 (en) 2019-01-04 2020-12-01 Analog Devices, Inc. Communication systems with auxiliary master and auxiliary call support functionality
US10872049B2 (en) 2016-01-29 2020-12-22 Analog Devices, Inc. GPIO-to-GPIO communication on a multi-node daisy-chained network
US10884972B2 (en) 2019-05-08 2021-01-05 Analog Devices, Inc. Communication systems with serial peripheral interface functionality
US10931476B2 (en) 2018-10-29 2021-02-23 Analog Devices Global Unlimited Company Content protection over synchronous data networks
US11157235B2 (en) * 2020-03-10 2021-10-26 Aptiv Technologies Limited System and method for veryifying audible and/or visual notifications
US11175928B2 (en) * 2018-03-30 2021-11-16 Wuxi Ruiqin Technology Co., Ltd Master-slave configuration communication protocol, method for improving compatibility, and electronic device
US11234380B2 (en) * 2018-09-27 2022-02-01 Rain Bird Corporation Irrigation controller with relays
US11362750B2 (en) * 2019-03-11 2022-06-14 Marvell Asia Pte Ltd Synchronization of automotive sensors using communication-link TDM timing
US11388576B2 (en) 2019-12-16 2022-07-12 Huawei Technologies Co., Ltd. Emergency call method and apparatus, and system
US11411607B2 (en) 2020-01-07 2022-08-09 Analog Devices, Inc. Audio and lighting control via a communication bus
US20220335002A1 (en) * 2020-01-02 2022-10-20 Huawei Technologies Co., Ltd. Control Method and Apparatus
US11637546B2 (en) * 2018-12-14 2023-04-25 Synaptics Incorporated Pulse density modulation systems and methods
WO2023229877A1 (en) * 2022-05-23 2023-11-30 Panduit Corp. Systems, apparatuses, and methods for safe communication and data transmission in high voltage power systems
US11888498B2 (en) 2022-01-18 2024-01-30 Analog Devices International Unlimited Company Elimination of probability of bit errors in successive approximation register (SAR) analog-to-digital converter (ADC) logic

Families Citing this family (58)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9741398B1 (en) * 2009-05-08 2017-08-22 Micron Technology, Inc. Using out-of-band signaling to communicate with daisy chained nonvolatile memories
US9946679B2 (en) 2011-10-05 2018-04-17 Analog Devices, Inc. Distributed audio coordination over a two-wire communication bus
US10649948B2 (en) * 2011-10-05 2020-05-12 Analog Devices, Inc. Two-wire communication systems and applications
JP5856306B2 (en) 2011-10-05 2016-02-09 アナログ・デバイシズ・インコーポレーテッド Two-wire communication system for high-speed data and power distribution
US10303638B2 (en) * 2014-07-11 2019-05-28 Infineon Technologies Ag Method of data acquisition and apparatus for data acquisition
US10200794B2 (en) * 2014-12-31 2019-02-05 Invensense, Inc. Ultrasonic operation of a digital microphone
JP6652978B2 (en) * 2015-06-26 2020-02-26 ハーマン インターナショナル インダストリーズ インコーポレイテッド Sports headphones with situational awareness
AT517777A1 (en) * 2015-10-01 2017-04-15 Bernecker + Rainer Industrie-Elektronik Ges M B H A method of data communication with reduced overhead in a real-time capable Ethernet data network
AT517781B1 (en) * 2015-10-01 2021-10-15 B & R Ind Automation Gmbh Method for isochronous data communication in a real-time capable Ethernet data network
AT517782B1 (en) * 2015-10-01 2021-10-15 B & R Ind Automation Gmbh Method for asynchronous data communication in a real-time capable Ethernet data network
AT517778B1 (en) * 2015-10-01 2021-10-15 B & R Ind Automation Gmbh Method for data communication with reduced overhead in a real-time capable Ethernet data network
US20170199832A1 (en) * 2016-01-13 2017-07-13 Qualcomm Incorporated Signaling protocols for radio frequency front-end control interface (rffe) buses
US10123155B2 (en) * 2016-01-20 2018-11-06 Livio, Inc. Secondary-connected device companion application control of a primary-connected device
US10268614B2 (en) * 2016-04-19 2019-04-23 Nokia Of America Corporation Method and apparatus for a segmented on-chip digital interface block
US10067907B2 (en) 2016-05-05 2018-09-04 GM Global Technology Operations LLC Vehicle including noise management system having automotive audio bus (A2B) interface
US10499123B2 (en) * 2016-06-19 2019-12-03 Urban-Gro, Inc. Sensor bus architecture for modular sensor systems
US10176129B2 (en) * 2016-06-22 2019-01-08 Novatek Microelectronics Corp. Control method for I2C device of I2C system and I2C device using the same
KR102563779B1 (en) * 2016-06-30 2023-08-04 엘지디스플레이 주식회사 Organic light emitting diode display device
US10861939B2 (en) * 2016-09-30 2020-12-08 Intel Corporation Stiff quantum layers to slow and or stop defect propagation
US10212658B2 (en) * 2016-09-30 2019-02-19 Kinetic Technologies Systems and methods for managing communication between devices
US10719063B2 (en) * 2016-10-06 2020-07-21 Microsoft Technology Licensing, Llc Real-time equipment control
US10757484B2 (en) 2017-01-05 2020-08-25 Kinetic Technologies Systems and methods for pulse-based communication
DE102017107814B4 (en) * 2017-04-11 2022-01-05 Phoenix Contact Gmbh & Co. Kg Condition monitoring device for monitoring the condition of a mechanical machine component
US10756844B2 (en) * 2017-06-16 2020-08-25 Mediatek Inc. Devices and method for wirelessly broadcasting media packets
US20190005974A1 (en) * 2017-06-28 2019-01-03 Qualcomm Incorporated Alignment of bi-directional multi-stream multi-rate i2s audio transmitted between integrated circuits
JP6994329B2 (en) * 2017-09-11 2022-01-14 Koa株式会社 Multiple sensors
CN109859749A (en) * 2017-11-30 2019-06-07 阿里巴巴集团控股有限公司 A kind of voice signal recognition methods and device
CN108123862A (en) * 2017-12-18 2018-06-05 合肥华凌股份有限公司 Communication system, communication means and the household electrical appliance of household electrical appliance
CN108123863B (en) * 2017-12-18 2020-11-24 合肥华凌股份有限公司 Communication system and communication method of household appliance and household appliance
US20200356519A1 (en) * 2018-03-29 2020-11-12 Wayne Ballantyne Techniques for serial communication
CN108494517B (en) * 2018-05-04 2023-12-26 厦门亿联网络技术股份有限公司 Device and method for realizing synchronization of voice clocks of wireless microphone and built-in microphone
US10896106B2 (en) * 2018-05-10 2021-01-19 Teradyne, Inc. Bus synchronization system that aggregates status
CN110618960B (en) * 2018-06-19 2023-09-15 敦泰电子有限公司 Data stepped compression transmission method, device for realizing method and electronic equipment
CN111010881B (en) * 2018-08-06 2024-08-23 瑞萨设计(英国)有限公司 Serial communication protocol
CN109119053B (en) * 2018-08-08 2021-07-02 瓦纳卡(北京)科技有限公司 Signal transmission method and device, electronic equipment and computer readable storage medium
CN109086242B (en) * 2018-09-20 2021-09-17 郑州云海信息技术有限公司 Communication system and method
CN109120816B (en) * 2018-10-25 2021-03-30 丰泽智能装备股份有限公司 Pier-centered intelligent support synchronous data acquisition method and network system
TWI695313B (en) * 2019-02-15 2020-06-01 矽統科技股份有限公司 Device and method for detecting audio interface
US20210013929A1 (en) * 2019-07-10 2021-01-14 3M Innovative Properties Company Electrical node with monitoring feature
CN110445700B (en) * 2019-08-14 2021-12-17 深圳市优必选科技股份有限公司 Master-slave communication system and method and terminal equipment
US11507161B2 (en) 2020-01-09 2022-11-22 Simmonds Precision Products, Inc. Power and serial communication scheme
US11552676B2 (en) * 2020-02-11 2023-01-10 Samsung Electronics Co., Ltd. Mobile device for performing power line communication and operating method thereof
CN115336232B (en) * 2020-04-10 2023-08-22 株式会社富士 Communication system and working device
US11463491B2 (en) 2020-05-27 2022-10-04 H.M. Electronics, Inc. Systems and methods for DC power and data communication over a single pair of wires, for a quick-service restaurant
CN112038655B (en) * 2020-09-10 2021-07-27 广州云也科技有限公司 Fuel cell with bipolar plate sealing structure
CN112100112B (en) * 2020-09-18 2022-05-27 中车株洲电力机车研究所有限公司 Full duplex bus and train
CN112860622B (en) * 2021-02-08 2022-11-04 山东云海国创云计算装备产业创新中心有限公司 Processing system and system on chip
US11743024B2 (en) * 2021-02-10 2023-08-29 Sony Semiconductor Solutions Corporation Communication device and communication system
DE102021105919A1 (en) * 2021-03-11 2022-09-15 Ebm-Papst Mulfingen Gmbh & Co. Kg Addressable master-slave system and method for addressing slave units
CN114253896B (en) * 2021-12-07 2024-06-14 苏州上声电子股份有限公司 For I2Clock generation method and system for S audio bus
CN114167783B (en) * 2021-12-07 2024-06-11 宝星智能科技(上海)有限公司 Two-wire system sensor network system for analog signal transmission and measuring method thereof
US11960435B2 (en) * 2021-12-17 2024-04-16 Advanced Micro Devices, Inc. Skew matching in a die-to-die interface
TWI804163B (en) * 2022-01-18 2023-06-01 新唐科技股份有限公司 Microphone array
CN115314070B (en) * 2022-08-09 2024-02-09 浙江中控信息产业股份有限公司 Cascaded high-speed long-line transmission device
US12015412B1 (en) 2022-12-01 2024-06-18 Advanced Micro Devices, Inc. Dual phase clock distribution from a single source in a die-to-die interface
CN115840727A (en) * 2022-12-14 2023-03-24 浙江中控信息产业股份有限公司 Bus extension system and communication method
TWI822519B (en) * 2022-12-15 2023-11-11 明基電通股份有限公司 Display device
CN115862181B (en) * 2023-02-01 2023-06-02 钛能科技股份有限公司 Chain type communication display instrument group and chain type communication method thereof

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6611537B1 (en) * 1997-05-30 2003-08-26 Centillium Communications, Inc. Synchronous network for digital media streams
US7095860B1 (en) * 1998-11-11 2006-08-22 Michael Joseph Kemp Audio dynamic control effects synthesizer with or without analyzer
US8225207B1 (en) * 2007-09-14 2012-07-17 Adobe Systems Incorporated Compression threshold control
US9654869B2 (en) * 2012-05-08 2017-05-16 Landr Audio Inc. System and method for autonomous multi-track audio processing

Family Cites Families (207)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6825698B2 (en) * 2001-08-29 2004-11-30 Altera Corporation Programmable high speed I/O interface
US4317211A (en) 1980-06-02 1982-02-23 The United States Of America As Represented By The Secretary Of The Navy Manchester code decoding apparatus
DE3335932A1 (en) 1983-10-04 1985-04-18 Wabco Westinghouse Fahrzeugbremsen GmbH, 3000 Hannover DEVICE FOR INQUIRING AND CONTROLLING SEVERAL COMPONENTS OF A VEHICLE
US4542420A (en) 1984-01-24 1985-09-17 Honeywell Inc. Manchester decoder
JPS61154321A (en) 1984-12-27 1986-07-14 Hitachi Ltd Decoding circuit
US4860309A (en) 1986-09-17 1989-08-22 Costello John F Trinary bus communication system
FR2614110B1 (en) 1987-04-14 1989-07-21 Thiennot Jean OPTICAL FIBER TRANSMISSION DEVICE, PARTICULARLY IN AN UNDERWATER ENVIRONMENT
ZA883232B (en) 1987-05-06 1989-07-26 Dowd Research Pty Ltd O Packet switches,switching methods,protocols and networks
US5056114A (en) 1989-08-03 1991-10-08 Northern Telecom Limited Method and apparatus for decoding Manchester encoded data
US4965881A (en) 1989-09-07 1990-10-23 Northern Telecom Limited Linear feedback shift registers for data scrambling
JP2522413B2 (en) 1989-10-17 1996-08-07 日本電気株式会社 Phase frequency comparator
US5168511A (en) 1990-10-22 1992-12-01 Berkeley Varitronics Systems, Inc. Manchester data recorder with synchronously adjustable clock
US5805632A (en) 1992-11-19 1998-09-08 Cirrus Logic, Inc. Bit rate doubler for serial data transmission or storage
US5321372A (en) * 1993-01-08 1994-06-14 Synoptics Communications, Inc. Apparatus and method for terminating cables to minimize emissions and susceptibility
US5412652A (en) 1993-09-24 1995-05-02 Nec America, Inc. Sonet ring subnetwork management method
US5793993A (en) 1995-01-26 1998-08-11 General Magic, Inc. Method for transmitting bus commands and data over two wires of a serial bus
US5696800A (en) 1995-03-22 1997-12-09 Intel Corporation Dual tracking differential manchester decoder and clock recovery circuit
US5675811A (en) 1995-08-18 1997-10-07 General Magic, Inc. Method for transmitting information over an intelligent low power serial bus
JPH0958093A (en) * 1995-08-22 1997-03-04 Canon Inc Recording device
KR100461922B1 (en) 1995-11-13 2005-05-24 텍사스 인스트루먼츠 인코포레이티드 Method and apparatus for decoding noise, intermittent data such as Manchester coded data
US5819051A (en) 1995-12-29 1998-10-06 Compaq Computer Corporation Low speed serial bus protocol and circuitry
DE19611944C2 (en) 1996-03-26 2003-03-27 Daimler Chrysler Ag Integrated circuit for coupling a micro-controlled control unit to a two-wire bus
FR2746995B1 (en) 1996-03-28 1998-05-15 Sgs Thomson Microelectronics TRANSMISSION ENCODING METHOD AND DEVICE AND USE OF THE METHOD
US5841989A (en) 1996-04-08 1998-11-24 Apple Computer, Inc. System and method for efficiently routing data packets in a computer interconnect
US5872811A (en) * 1996-07-08 1999-02-16 Analog Devices, Inc. Differential line driver
US5790888A (en) 1996-08-12 1998-08-04 Seeq Technology, Inc. State machine for selectively performing an operation on a single or a plurality of registers depending upon the register address specified in a packet
US5929655A (en) * 1997-03-25 1999-07-27 Adaptec, Inc. Dual-purpose I/O circuit in a combined LINK/PHY integrated circuit
US5935229A (en) 1997-03-28 1999-08-10 Xerox Corporation Bidirectional sequential interaction designation scheme for a chained and bussed array of integrated circuits
US5974475A (en) 1997-06-24 1999-10-26 Microchip Technology Incorporated Method for flexible multiple access on a serial bus by a plurality of boards
JP3039466B2 (en) 1997-08-12 2000-05-08 日本電気株式会社 Clock recovery circuit
US5982297A (en) 1997-10-08 1999-11-09 The Aerospace Corporation Ultrasonic data communication system
US6285722B1 (en) 1997-12-05 2001-09-04 Telcordia Technologies, Inc. Method and apparatus for variable bit rate clock recovery
US6766950B2 (en) 1997-12-16 2004-07-27 Donald R. Hall Modular architecture sensing and computing platform
JP3347667B2 (en) 1998-05-20 2002-11-20 沖電気工業株式会社 Manchester encoded data decoding device
US6813777B1 (en) 1998-05-26 2004-11-02 Rockwell Collins Transaction dispatcher for a passenger entertainment system, method and article of manufacture
US6134698A (en) * 1998-06-17 2000-10-17 Advanced Micro Devices, Inc. Reduced pin count isochronous data bus
US6480510B1 (en) 1998-07-28 2002-11-12 Serconet Ltd. Local area network of serial intelligent cells
US6804304B1 (en) * 1998-10-30 2004-10-12 Broadcom Corporation Reduction of aggregate EMI emissions of multiple transmitters
US6240478B1 (en) 1998-10-30 2001-05-29 Eaton Corporation Apparatus and method for addressing electronic modules
JP3267569B2 (en) * 1998-11-27 2002-03-18 日本電気株式会社 Searcher control method, searcher control device, and wireless communication device
US6629172B1 (en) 1998-12-14 2003-09-30 Micron Technology, Inc. Multi-chip addressing for the I2C bus
US6363437B1 (en) 1999-01-07 2002-03-26 Telefonaktiebolaget Lm Ericsson (Publ) Plug and play I2C slave
US6609167B1 (en) 1999-03-17 2003-08-19 Adaptec, Inc. Host and device serial communication protocols and communication packet formats
US6956826B1 (en) 1999-07-07 2005-10-18 Serconet Ltd. Local area network for distributing data communication, sensing and control signals
WO2001008366A1 (en) 1999-07-23 2001-02-01 Centillium Communications, Inc. Apparatus and method for media access control
US6985503B1 (en) 1999-08-09 2006-01-10 Zarlink Semiconductor Inc. Inverse multiplexer
US7844687B1 (en) 1999-10-06 2010-11-30 Gelvin David C Method for internetworked hybrid wireless integrated network sensors (WINS)
US20020012401A1 (en) 2000-05-23 2002-01-31 Endevco Corporation Transducer network bus
US20020009089A1 (en) * 2000-05-25 2002-01-24 Mcwilliams Patrick Method and apparatus for establishing frame synchronization in a communication system using an UTOPIA-LVDS bridge
US7061926B2 (en) 2000-06-15 2006-06-13 Schneider Automation Inc. Method and apparatus for a network bus topology
US6326851B1 (en) 2000-06-26 2001-12-04 Texas Instruments Incorporated Digital phase-domain PLL frequency synthesizer
JP4467727B2 (en) * 2000-07-24 2010-05-26 キヤノン株式会社 Electronic device connection method, electronic device, and storage medium storing operation processing program thereof
US6987824B1 (en) 2000-09-21 2006-01-17 International Business Machines Corporation Method and system for clock/data recovery for self-clocked high speed interconnects
US6628212B1 (en) 2000-11-21 2003-09-30 Nortel Networks Limited State-driven over-sampling manchester decoder
US6745270B1 (en) 2001-01-31 2004-06-01 International Business Machines Corporation Dynamically allocating I2C addresses using self bus switching device
US6512403B2 (en) * 2001-02-14 2003-01-28 Samsung Electronics Co., Ltd. Phase-locked loop for reducing frequency lock time
KR100370243B1 (en) 2001-02-14 2003-02-05 삼성전자 주식회사 Phase locked loop circuit including fast frequency lock control circuit and method for reducing frequency lock time thereof
JP2002314552A (en) 2001-04-18 2002-10-25 Matsushita Electric Ind Co Ltd Data repeater and interphone system
US7818457B1 (en) 2001-05-22 2010-10-19 Rockwell Automation Technologies, Inc. Apparatus for multi-chassis configurable time synchronization
US6842806B2 (en) 2001-05-29 2005-01-11 Sun Microsystems, Inc. Method and apparatus for interconnecting wired-AND buses
SE0102162D0 (en) 2001-06-19 2001-06-19 Delaval Holding Ab System and method for milking animals
US7756917B2 (en) 2001-09-28 2010-07-13 Baseline, Llc Two wire communication apparatus and method
US6928501B2 (en) 2001-10-15 2005-08-09 Silicon Laboratories, Inc. Serial device daisy chaining method and apparatus
JP3844120B2 (en) 2001-10-19 2006-11-08 株式会社ルネサステクノロジ Semiconductor device
US7702293B2 (en) * 2001-11-02 2010-04-20 Nokia Corporation Multi-mode I/O circuitry supporting low interference signaling schemes for high speed digital interfaces
JP2003145456A (en) 2001-11-19 2003-05-20 Japan Science & Technology Corp Bipedal human-type robot
US7315551B2 (en) 2002-03-15 2008-01-01 Lockheed Martin Corporation Synchronous low voltage differential I/O buss
FR2837296B1 (en) 2002-03-15 2004-06-25 Airbus France DEVICE AND METHOD FOR ACQUIRING MEASUREMENTS USING A DIGITAL COMMUNICATION BUS, USED IN PARTICULAR DURING TESTS OF AN AIRCRAFT
JP2004001195A (en) 2002-03-27 2004-01-08 Sony Corp Robotic device
US7177661B2 (en) 2002-05-06 2007-02-13 Extricom Ltd. Communication between wireless access points over LAN cabling
GB2388501A (en) 2002-05-09 2003-11-12 Sony Uk Ltd Data packet and clock signal transmission via different paths
US8605623B2 (en) 2002-05-31 2013-12-10 Koninklijke Philips N.V. Determining and configuring a communication path in a network
KR100451374B1 (en) 2002-06-08 2004-10-06 엘지산전 주식회사 The improvement apparatus and method of the communication speed and reliability for backplane using a parallel bus
US6894505B2 (en) * 2002-08-01 2005-05-17 Teradyne, Inc. Flexible interface for universal bus test instrument
US7844690B1 (en) * 2003-01-24 2010-11-30 Douglas Durham Systems and methods for creation and use of a virtual protocol analyzer
US20060164266A1 (en) 2003-09-22 2006-07-27 Inova Semiconductors Gmbh Synthesizing a remote controlled clock for data transmission via a digital multimedia link
US7940877B1 (en) 2003-11-26 2011-05-10 Altera Corporation Signal edge detection circuitry and methods
US7500034B2 (en) * 2003-12-10 2009-03-03 Hewlett-Packard Development Company, L.P. Multiple integrated circuit control
US8667194B2 (en) 2003-12-15 2014-03-04 Finisar Corporation Two-wire interface in which a master component monitors the data line during the preamble generation phase for synchronization with one or more slave components
US7567642B2 (en) 2003-12-23 2009-07-28 Analog Devices, Inc. Phase detector with extended linear operating range
GB2409781A (en) 2004-01-02 2005-07-06 Adder Tech Ltd Transmission of colour video signals over a wire pair
US7475174B2 (en) 2004-03-17 2009-01-06 Super Talent Electronics, Inc. Flash / phase-change memory in multi-ring topology using serial-link packet interface
JP4575069B2 (en) 2004-07-30 2010-11-04 矢崎総業株式会社 Vehicle power superimposed telecommunications system
US8229301B2 (en) 2004-09-07 2012-07-24 Finisar Corporation Configuration of optical transceivers to perform custom features
US7664015B2 (en) 2004-10-20 2010-02-16 L-3 Communications Security & Detection Systems Inspection system with data acquisition system interconnect protocol
DE602004026195D1 (en) * 2004-10-21 2010-05-06 Hewlett Packard Development Co Serial bus system
TWI268423B (en) 2004-12-03 2006-12-11 Hon Hai Prec Ind Co Ltd System and method for configuring I2C address dynamically
US7656956B2 (en) 2005-01-14 2010-02-02 Motorola, Inc. Data, power and supervisory signaling over twisted pairs
US7706496B2 (en) 2005-01-31 2010-04-27 Skyworks Solutions, Inc. Digital phase detector for a phase locked loop
DE102005034652B4 (en) * 2005-03-02 2013-08-08 Rohde & Schwarz Gmbh & Co. Kg Bus system and method for operating the bus system
CN101138208B (en) * 2005-03-08 2016-06-08 皇家飞利浦电子股份有限公司 The method and apparatus that distribution media accesses time slot in the wireless network
US7398106B2 (en) 2005-03-31 2008-07-08 Adc Telecommunications, Inc. Dynamic readjustment of power
US7649912B2 (en) 2005-04-27 2010-01-19 Rockwell Automation Technologies, Inc. Time synchronization, deterministic data delivery and redundancy for cascaded nodes on full duplex ethernet networks
US7348803B2 (en) 2005-06-24 2008-03-25 Integrated Electronic Solutions Pty. Ltd. Bi-directional bus buffer
US7487331B2 (en) 2005-09-15 2009-02-03 Microchip Technology Incorprated Programming a digital processor with a single connection
JP4640126B2 (en) 2005-11-14 2011-03-02 富士通株式会社 Sideband bus setting circuit
TWI289386B (en) 2005-12-30 2007-11-01 Ind Tech Res Inst AC/DC power line communication modem
JP4791185B2 (en) 2006-01-04 2011-10-12 富士通セミコンダクター株式会社 Correction circuit
CN100573382C (en) 2006-01-26 2009-12-23 中控科技集团有限公司 Based on I 2The communication system of C and communication means
US7395362B2 (en) 2006-02-03 2008-07-01 Standard Microsystems Corporation Method for a slave device to convey an interrupt and interrupt source information to a master device
US8185680B2 (en) 2006-02-06 2012-05-22 Standard Microsystems Corporation Method for changing ownership of a bus between master/slave devices
US20080013640A1 (en) 2006-02-13 2008-01-17 Data Device Corporation Multi-dimensional burst link access streaming transmission (BLAST) architecture and algorithms for low latency real-time broadband burst data/video transmission
JP2007215102A (en) 2006-02-13 2007-08-23 Denso Corp Communication device
KR101429249B1 (en) * 2006-02-17 2014-08-14 스탠다드 마이크로시스템즈 코포레이션 System and method for transferring different types of streaming and packetized data across an ethernet transmission line using a frame and packet structure demarcated with ethernet coding violations
JP4918866B2 (en) 2006-03-13 2012-04-18 ミツミ電機株式会社 COMMUNICATION DEVICE, SEMICONDUCTOR INTEGRATED CIRCUIT DEVICE, AND COMMUNICATION SYSTEM
US7587539B2 (en) 2006-04-25 2009-09-08 Texas Instruments Incorporated Methods of inter-integrated circuit addressing and devices for performing the same
US7514962B2 (en) 2006-04-28 2009-04-07 Stmicroelectronics Pvt. Ltd. Configurable I2C interface
US7631110B2 (en) 2006-05-03 2009-12-08 Standard Microsystems Corporation Address assignment through device ID broadcast
JP4981494B2 (en) 2006-05-30 2012-07-18 株式会社日立国際電気 Wireless communication system and overhang station apparatus
US7702832B2 (en) 2006-06-07 2010-04-20 Standard Microsystems Corporation Low power and low pin count bi-directional dual data rate device interconnect interface
US20090322251A1 (en) 2006-06-27 2009-12-31 Koninklijke Philips Electronics N.V. Large area lighting
US20080031165A1 (en) * 2006-08-07 2008-02-07 Fenghua Shen RS-232 data through a half duplex differential link
DE102006036770A1 (en) 2006-08-07 2008-02-14 Siemens Ag Method for commissioning at least one field device
US20080046121A1 (en) 2006-08-17 2008-02-21 Innovati, Inc. Developing system of re-configurable modularized robot
US7890684B2 (en) 2006-08-31 2011-02-15 Standard Microsystems Corporation Two-cycle return path clocking
CN200944109Y (en) 2006-09-15 2007-09-05 吉林大学 Poisonous gas network intelligent sensor
CA2663797A1 (en) 2006-09-19 2008-03-27 The Trustees Of Columbia University In The City Of New York Systems, devices, and methods for surgery on a hollow anatomically suspended organ
US7953162B2 (en) * 2006-11-17 2011-05-31 Intersil Americas Inc. Use of differential pair as single-ended data paths to transport low speed data
US7802036B2 (en) 2007-02-06 2010-09-21 Seiko Epson Corporation Serial communication system using an I2C bus as a serial bus
US8565337B2 (en) 2007-02-07 2013-10-22 Valens Semiconductor Ltd. Devices for transmitting digital video and data over the same wires
US7673084B2 (en) 2007-02-20 2010-03-02 Infineon Technologies Ag Bus system and methods of operation using a combined data and synchronization line to communicate between bus master and slaves
US8488617B2 (en) 2007-03-20 2013-07-16 Mitsubishi Electric Corporation Railway-train communication apparatus
US20080246626A1 (en) 2007-04-03 2008-10-09 Vizionware, Inc. Data transaction direction detection in an adaptive two-wire bus
US20080250175A1 (en) 2007-04-03 2008-10-09 Vizionware, Inc. Cable assembly having an adaptive two-wire bus
US20080250184A1 (en) 2007-04-03 2008-10-09 Vizionware, Inc. Adaptive two-wire bus
DE102007017835A1 (en) 2007-04-16 2008-10-23 Beckhoff Automation Gmbh Packet switching device and local communication network with such a packet switching device
US8028176B2 (en) 2007-04-18 2011-09-27 Broadcom Corporation System and method for modeling a power over ethernet component in a computing device platform using a common information model
JP2008278179A (en) 2007-04-27 2008-11-13 Yaskawa Electric Corp Communication apparatus and address assigning method thereof
CN100551634C (en) 2007-04-29 2009-10-21 东北大学 A kind of control system for modular robot based on the CAN bus
US8806083B2 (en) 2007-05-15 2014-08-12 Texas Instruments Incorporated Identification address configuration circuit and method without use of dedicated address pins
US8400061B2 (en) 2007-07-17 2013-03-19 I/O Controls Corporation Control network for LED-based lighting system in a transit vehicle
AU2008221607A1 (en) 2007-09-25 2009-04-09 Acei Ab A gaming network
ES2339203B1 (en) 2007-09-26 2011-02-10 Universidad De Las Palmas De Gran Canaria DOMOTIC DEVICE COMPATIBLE WITH CELENEC STANDARDS IN 50090 AND ISO / IEC 14543 FOR THE CONTROL OF ROBOTIC CAMERAS.
US8700830B2 (en) 2007-11-20 2014-04-15 Spansion Llc Memory buffering system that improves read/write performance and provides low latency for mobile systems
KR100968865B1 (en) 2007-12-17 2010-07-09 주식회사 애트랩 Serial communication system and ID grant method thereof
US7707339B2 (en) 2007-12-18 2010-04-27 Freescale Semiconductor, Inc. Data arbitration on a bus to determine an extreme value
US8391180B2 (en) 2008-01-08 2013-03-05 Tejas Networks Limited Method to develop hierarchical ring based tree for unicast and/or multicast traffic
FR2927308B1 (en) 2008-02-08 2010-10-22 Airbus France DISTRIBUTED FLIGHT CONTROL SYSTEM.
CN201196834Y (en) 2008-04-03 2009-02-18 中国电力科学研究院 Industrial frequency communication system of power distribution network
TW201012130A (en) 2008-09-08 2010-03-16 Brainchild Electronic Co Ltd Remote communication method of a network and system thereof
JP2010065667A (en) 2008-09-12 2010-03-25 Suzuki Motor Corp Oil supply device of engine for motorcycle
JP4645717B2 (en) 2008-09-26 2011-03-09 ソニー株式会社 Interface circuit and video apparatus
US8485703B2 (en) 2008-10-30 2013-07-16 B/E Aerospace, Inc. Aircraft cabin lighting system and kit therefor
US8692487B2 (en) 2008-10-30 2014-04-08 B/E Aerospace, Inc. Aircraft cabin lighting system and kit therefor
US8185759B1 (en) 2008-11-06 2012-05-22 Smsc Holdings S.A.R.L. Methods and systems for interfacing bus powered devices with host devices providing limited power levels
US20100184575A1 (en) 2009-01-21 2010-07-22 Applied Robotics, Inc. Methods and systems for monitoring the operation of a robotic actuator
US8156274B2 (en) 2009-02-02 2012-04-10 Standard Microsystems Corporation Direct slave-to-slave data transfer on a master-slave bus
US8311085B2 (en) 2009-04-14 2012-11-13 Clear-Com Llc Digital intercom network over DC-powered microphone cable
US8219776B2 (en) * 2009-09-23 2012-07-10 Lsi Corporation Logical-to-physical address translation for solid state disks
US8621116B2 (en) 2011-08-26 2013-12-31 Lexmark International, Inc. Dynamic address change optimizations
CN101944750B (en) 2009-07-04 2013-04-10 李善伯 Implementation method of flexible intelligent direct current electric local area network electric power system
TW201141258A (en) 2009-08-03 2011-11-16 Htc Corp Method of updating management information and related communication device
JP2011050000A (en) 2009-08-28 2011-03-10 Sony Corp Communication centralized control system and communication centralized control method
US8260460B2 (en) 2009-09-22 2012-09-04 GM Global Technology Operations LLC Interactive robot control system and method of use
US8205017B2 (en) 2009-11-17 2012-06-19 Aptina Imaging Corporation Systems and methods for addressing and synchronizing multiple devices
DE102010005104B3 (en) 2010-01-20 2011-07-21 Texas Instruments Deutschland GmbH, 85356 Electronic device and method for a larger address range on an IIC or an IIC compatible bus
JP5430469B2 (en) 2010-03-31 2014-02-26 三菱電機株式会社 Master device, slave device, time synchronization method, and program
TWI532028B (en) 2010-05-06 2016-05-01 立錡科技股份有限公司 Flat panel display, light emitting module for use in flat panel display, and integrated circuit for use in light emitting module
JP5552132B2 (en) 2010-06-11 2014-07-16 本田技研工業株式会社 Communication network
CN201744997U (en) 2010-06-29 2011-02-16 上海中为智能机器人有限公司 Modularized portable mobile robot system
JP5097250B2 (en) 2010-08-25 2012-12-12 三菱電機株式会社 Network system
US9596738B2 (en) 2010-09-16 2017-03-14 Terralux, Inc. Communication with lighting units over a power bus
US8478917B2 (en) 2010-09-22 2013-07-02 Microsoft Corporation Automatic addressing protocol for a shared bus
US8615091B2 (en) 2010-09-23 2013-12-24 Bose Corporation System for accomplishing bi-directional audio data and control communications
DE102010041427A1 (en) 2010-09-27 2012-03-29 Robert Bosch Gmbh Method for transmitting data
US20120087503A1 (en) * 2010-10-07 2012-04-12 Passif Semiconductor Corp. Multi-channel audio over standard wireless protocol
EP2442587A1 (en) 2010-10-14 2012-04-18 Harman Becker Automotive Systems GmbH Microphone link system
US9064050B2 (en) 2010-10-20 2015-06-23 Qualcomm Incorporated Arbitrating bus transactions on a communications bus based on bus device health information and related power management
US20120116479A1 (en) 2010-11-08 2012-05-10 Werner Meskins Two-wire medical implant connection
KR20120068597A (en) 2010-12-17 2012-06-27 주식회사 이턴 Surgical robot system and adaptive control method thereof
JP5655562B2 (en) 2010-12-28 2015-01-21 ソニー株式会社 Electronic device, control method of electronic device, transmission device, and reception device
KR101750414B1 (en) 2011-01-13 2017-06-23 삼성전자주식회사 Digital phase frequency detector, digital phase locked loop including the same and method of detecting digital phase frequency
US8971470B2 (en) 2011-02-25 2015-03-03 Intel Corporation System, method, and device to distribute accurate synchronization timestamps in an expandable and timing critical system
TWI478560B (en) 2011-03-06 2015-03-21 Pcn Technology Inc Systems and methods of data transmission and management
GB2489724B (en) 2011-04-06 2017-08-02 Nexus Electronics Ltd Digital video transmission
US8908779B2 (en) 2011-04-29 2014-12-09 Linear Technology Corporation Isolated communications interface
CN202093392U (en) 2011-05-19 2011-12-28 苏州市职业大学 Hardware platform of AGV (automated guided vehicle) system
WO2013016534A1 (en) 2011-07-27 2013-01-31 Verified Energy, Llc Encapsulation of dali commands in wireless networks
US8384568B2 (en) 2011-07-27 2013-02-26 Xilinx, Inc. Decoder circuit for down-sampling a differential manchester encoding
US8718216B2 (en) 2011-09-23 2014-05-06 International Business Machines Corporation Digital phase detector with zero phase offset
US9946679B2 (en) 2011-10-05 2018-04-17 Analog Devices, Inc. Distributed audio coordination over a two-wire communication bus
US9448959B2 (en) * 2012-10-05 2016-09-20 Analog Devices, Inc. Two-wire communication protocol engine
JP5856306B2 (en) 2011-10-05 2016-02-09 アナログ・デバイシズ・インコーポレーテッド Two-wire communication system for high-speed data and power distribution
CN102367697A (en) 2011-11-04 2012-03-07 张琳 Bracket for high-altitude electric drill
US8400186B1 (en) * 2012-02-21 2013-03-19 Altera Corporation Techniques for buffering single-ended and differential signals
US9071360B2 (en) 2012-03-07 2015-06-30 Sumitomo Electric Industries, Ltd. Optical transceiver having improved functions to load control program
CN102615638B (en) 2012-04-01 2014-08-06 山东鲁能智能技术有限公司 Master-slave hydraulic mechanical arm system of high-voltage hot-line operation robot
US9274997B2 (en) 2012-05-02 2016-03-01 Smsc Holdings S.A.R.L. Point-to-point serial peripheral interface for data communication between devices configured in a daisy-chain
DE102012010851A1 (en) 2012-05-31 2013-12-05 Robert Bosch Gmbh Fieldbus network comprising two main participants and at least one secondary participant
CN103676797B (en) 2012-09-07 2016-09-21 南京理工大学 Modularity partition type multi-foot robot motion controller and control method thereof
CN202763839U (en) 2012-09-10 2013-03-06 王伟栋 Programmable automation controller (PAC) industrial robot control system based on field bus
FR2996322A1 (en) 2012-10-02 2014-04-04 St Microelectronics Rousset METHOD FOR MANAGING THE OPERATION OF A CIRCUIT CONNECTED ON A TWO-WIRE BUS, IN PARTICULAR AN I²C BUS, AND CORRESPONDING CIRCUIT
US9772665B2 (en) 2012-10-05 2017-09-26 Analog Devices, Inc. Power switching in a two-wire conductor system
CN102958062B (en) * 2012-10-19 2015-02-04 上海交通大学无锡研究院 Superframe-based low-energy-consumption media access control method in wireless body area network
KR102035005B1 (en) 2012-12-24 2019-10-22 엘지디스플레이 주식회사 Touch display device
US9160452B2 (en) 2012-12-29 2015-10-13 Zephyr Photonics Inc. Apparatus for modular implementation of multi-function active optical cables
DE102013001385A1 (en) * 2013-01-26 2014-07-31 Audi Ag Motor vehicle and microphone for a microphone assembly in the motor vehicle
CN203077287U (en) 2013-01-29 2013-07-24 山东电力集团公司电力科学研究院 Master-slave mode hydraulic pressure feedback mechanical arm controlling system of charged repair robot
WO2014133977A1 (en) 2013-03-01 2014-09-04 Robotex Inc. Low latency data link system and method
CN203225749U (en) 2013-03-04 2013-10-02 黄聪文 Master-slave two-way communication system
US9229889B2 (en) 2013-03-13 2016-01-05 Atieva, Inc. Dual voltage communication bus
US9946675B2 (en) 2013-03-13 2018-04-17 Atieva, Inc. Fault-tolerant loop for a communication bus
US9514086B2 (en) 2013-03-13 2016-12-06 Atieva, Inc. Configuration switch for a broadcast bus
RU2612359C1 (en) 2013-03-28 2017-03-07 ДжФЕ СТИЛ КОРПОРЕЙШН Method of inspecting forsterite, device for evaluation of forsterite and process line for production of steel sheet
US9197226B2 (en) 2013-07-08 2015-11-24 Analog Devices, Inc. Digital phase detector
DE102014109156A1 (en) 2013-07-08 2015-01-08 Analog Devices Inc. Digital phase detector
US9059724B2 (en) 2013-07-08 2015-06-16 Analog Devices, Inc. Differential decoder

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6611537B1 (en) * 1997-05-30 2003-08-26 Centillium Communications, Inc. Synchronous network for digital media streams
US7095860B1 (en) * 1998-11-11 2006-08-22 Michael Joseph Kemp Audio dynamic control effects synthesizer with or without analyzer
US8225207B1 (en) * 2007-09-14 2012-07-17 Adobe Systems Incorporated Compression threshold control
US9654869B2 (en) * 2012-05-08 2017-05-16 Landr Audio Inc. System and method for autonomous multi-track audio processing

Cited By (65)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160099817A1 (en) * 2007-03-02 2016-04-07 Qualcomm Incorporated N-phase phase and polarity encoded serial interface
US10033560B2 (en) 2007-03-02 2018-07-24 Qualcomm Incorporated Three phase and polarity encoded serial interface
US9998300B2 (en) * 2007-03-02 2018-06-12 Qualcomm Incorporated N-phase phase and polarity encoded serial interface
US9948485B2 (en) 2007-03-02 2018-04-17 Qualcomm Incorporated Three phase and polarity encoded serial interface
US20180006846A1 (en) * 2007-03-02 2018-01-04 Qualcomm Incorporated N-phase phase and polarity encoded serial interface
US9680666B2 (en) * 2007-03-02 2017-06-13 Qualcomm Incorporated N-phase phase and polarity encoded serial interface
US20140256440A1 (en) * 2011-10-21 2014-09-11 Novomatic Ag Gaming machine
US9711041B2 (en) 2012-03-16 2017-07-18 Qualcomm Incorporated N-phase polarity data transfer
US10134272B2 (en) 2012-03-16 2018-11-20 Qualcomm Incorporated N-phase polarity data transfer
US20170195789A1 (en) * 2014-09-29 2017-07-06 Hitachi Kokusai Electric Inc. Loudspeaker device and wireless communication system
US9826310B2 (en) * 2014-09-29 2017-11-21 Hitachi Kokusai Electric, Inc. Loudspeaker device and wireless communication system
US9565255B2 (en) 2014-12-04 2017-02-07 Apple Inc. Electronic accessory for detecting and communicating a connection attribute corresponding to another electronic accessory
US20160164973A1 (en) * 2014-12-04 2016-06-09 Apple Inc. Master device for using connection attribute of electronic accessories connections to facilitate locating an accessory
US9860932B2 (en) 2014-12-04 2018-01-02 Apple Inc. Master device for using connection attribute of electronic accessories connections to facilitate locating an accessory
US9641622B2 (en) * 2014-12-04 2017-05-02 Apple Inc. Master device for using connection attribute of electronic accessories connections to facilitate locating an accessory
US10015836B2 (en) 2014-12-04 2018-07-03 Apple Inc. Master device for using connection attribute of electronic accessories connections to facilitate locating an accessory
US20160337138A1 (en) * 2015-05-12 2016-11-17 Linear Technology Corporation System with sleep and wake up control over dc path
US9860072B2 (en) * 2015-05-12 2018-01-02 Linear Technology Corporation System with sleep and wake up control over DC path
US20160371157A1 (en) * 2015-06-19 2016-12-22 Qualcomm Incorporated Serial interface with bit-level acknowledgement and error correction
US9880895B2 (en) * 2015-06-19 2018-01-30 Qualcomm Incorporated Serial interface with bit-level acknowledgement and error correction
US20170070195A1 (en) * 2015-09-04 2017-03-09 MUSIC Group IP Ltd. Method for controlling power consumption of a loudspeaker system
US10397021B2 (en) 2016-01-29 2019-08-27 Analog Devices, Inc. Synchronous slave-to-slave communications
US10250376B2 (en) 2016-01-29 2019-04-02 Analog Devices, Inc. Clock sustain in the absence of a reference clock in a communication system
US10872049B2 (en) 2016-01-29 2020-12-22 Analog Devices, Inc. GPIO-to-GPIO communication on a multi-node daisy-chained network
US10698522B2 (en) * 2016-04-27 2020-06-30 Qualcomm Incorporated Variable rate display interfaces
US20170315652A1 (en) * 2016-04-27 2017-11-02 Qualcomm Incorporated Variable rate display interfaces
US10782714B2 (en) * 2017-01-06 2020-09-22 Sunland Information Technology Co., Ltd. Heat dissipation system and method for smart pianos
CN107182002A (en) * 2017-05-16 2017-09-19 苏州顺芯半导体有限公司 It is a kind of to recognize that modulus conversion chip audio output data format realizes device and implementation method
US10306363B2 (en) 2017-06-02 2019-05-28 Apple Inc. Dynamic master assignment in distributed wireless audio system for thermal and power mitigation
US10063968B1 (en) 2017-06-02 2018-08-28 Apple Inc. Dynamic master assignment in distributed wireless audio system for thermal and power mitigation
KR102515546B1 (en) * 2017-11-08 2023-03-29 현대자동차주식회사 Method and system for Controlling Digital Active Road Noise
KR20190052517A (en) * 2017-11-08 2019-05-16 현대자동차주식회사 Method and system for Controlling Digital Active Road Noise
US20190139531A1 (en) * 2017-11-08 2019-05-09 Hyundai Motor Company Digital active road noise control method and system
US10720140B2 (en) * 2017-11-08 2020-07-21 Hyundai Motor Company Digital active road noise control method and system
EP3486794A1 (en) * 2017-11-15 2019-05-22 Sensata Technologies, Inc. A communication system configured for transmitting sensor values from n sensing sources to a control unit
CN109819374A (en) * 2017-11-20 2019-05-28 福特全球技术公司 Vehicle audio frequency system
US10219073B1 (en) * 2017-11-20 2019-02-26 Ford Global Technologies, Llc Vehicle audio system
WO2019112709A1 (en) * 2017-12-05 2019-06-13 Qualcomm Incorporated Super-speed uart with per-frame bit-rate and independent variable upstream and downstream rates
US10447464B2 (en) 2017-12-05 2019-10-15 Qualcomm Incorporated Super-speed UART with pre-frame bit-rate and independent variable upstream and downstream rates
CN107995080A (en) * 2017-12-14 2018-05-04 长沙玄米电子科技有限公司 Multi-host communication method based on two-wire bus
US10687159B2 (en) * 2018-03-12 2020-06-16 Panasonic Intellectual Property Management Co., Ltd. Noise reduction device, noise reduction system, and fault detection method for noise reduction device
US20190281398A1 (en) * 2018-03-12 2019-09-12 Panasonic Intellectual Property Management Co., Ltd. Noise reduction device, noise reduction system, and fault detection method for noise reduction device
US11175928B2 (en) * 2018-03-30 2021-11-16 Wuxi Ruiqin Technology Co., Ltd Master-slave configuration communication protocol, method for improving compatibility, and electronic device
US10374583B1 (en) 2018-04-02 2019-08-06 Analog Devices, Inc. Dynamic hysteresis circuit
US11793129B2 (en) 2018-09-27 2023-10-24 Rain Bird Corporation Irrigation controller with relays
US11234380B2 (en) * 2018-09-27 2022-02-01 Rain Bird Corporation Irrigation controller with relays
US10931476B2 (en) 2018-10-29 2021-02-23 Analog Devices Global Unlimited Company Content protection over synchronous data networks
US10649945B1 (en) 2018-12-10 2020-05-12 Analog Devices International Unlimited Company Non-native digital interface support over a two-wire communication bus
US11637546B2 (en) * 2018-12-14 2023-04-25 Synaptics Incorporated Pulse density modulation systems and methods
US10856199B2 (en) 2019-01-04 2020-12-01 Analog Devices, Inc. Communication systems with auxiliary master and auxiliary call support functionality
US11362750B2 (en) * 2019-03-11 2022-06-14 Marvell Asia Pte Ltd Synchronization of automotive sensors using communication-link TDM timing
US11711157B2 (en) * 2019-03-11 2023-07-25 Marvell Asia Pte Ltd Full-duplex communication link using TDM
US20220329336A1 (en) * 2019-03-11 2022-10-13 Marvell Asia Pte Ltd Full-duplex communication link using TDM
US10884972B2 (en) 2019-05-08 2021-01-05 Analog Devices, Inc. Communication systems with serial peripheral interface functionality
US11388576B2 (en) 2019-12-16 2022-07-12 Huawei Technologies Co., Ltd. Emergency call method and apparatus, and system
JP2023505914A (en) * 2019-12-16 2023-02-13 華為技術有限公司 EMERGENCY CALL METHOD AND DEVICE, AND SYSTEM
EP4068696A4 (en) * 2019-12-16 2022-12-21 Huawei Technologies Co., Ltd. Emergency call method, apparatus and system
JP7430795B2 (en) 2019-12-16 2024-02-13 華為技術有限公司 Emergency call method, device, and system
EP4075736A4 (en) * 2020-01-02 2022-12-28 Huawei Technologies Co., Ltd. Control method and apparatus
US20220335002A1 (en) * 2020-01-02 2022-10-20 Huawei Technologies Co., Ltd. Control Method and Apparatus
US11411607B2 (en) 2020-01-07 2022-08-09 Analog Devices, Inc. Audio and lighting control via a communication bus
US11762626B2 (en) 2020-03-10 2023-09-19 Aptiv Technologies Limited System and method for verifying audible and/or visual notifications
US11157235B2 (en) * 2020-03-10 2021-10-26 Aptiv Technologies Limited System and method for veryifying audible and/or visual notifications
US11888498B2 (en) 2022-01-18 2024-01-30 Analog Devices International Unlimited Company Elimination of probability of bit errors in successive approximation register (SAR) analog-to-digital converter (ADC) logic
WO2023229877A1 (en) * 2022-05-23 2023-11-30 Panduit Corp. Systems, apparatuses, and methods for safe communication and data transmission in high voltage power systems

Also Published As

Publication number Publication date
US20160041941A1 (en) 2016-02-11
US10311010B2 (en) 2019-06-04
US20160034417A1 (en) 2016-02-04
CN106878125B (en) 2021-12-21
US9946680B2 (en) 2018-04-17
CN106878125A (en) 2017-06-20
US9946679B2 (en) 2018-04-17

Similar Documents

Publication Publication Date Title
US9946680B2 (en) Peripheral device diagnostics and control over a two-wire communication bus
KR102535076B1 (en) Systems and Techniques for Remote Bus Activation
US9851938B2 (en) Microphone arrays and communication systems for directional reception
US10649945B1 (en) Non-native digital interface support over a two-wire communication bus
US11874791B2 (en) Two-wire communication systems and applications
US10397021B2 (en) Synchronous slave-to-slave communications
CN107025200B (en) GPIO to GPIO communication over multi-node link networks
US10250376B2 (en) Clock sustain in the absence of a reference clock in a communication system
US10852799B2 (en) Adaptive use of multiple power supplies in communication systems
US10856199B2 (en) Communication systems with auxiliary master and auxiliary call support functionality
CN110347627B (en) Dynamic hysteresis circuit
CN109257260B (en) Adaptive application of multiple power supplies in a communication system
US20240004825A1 (en) Serial daisy-chained bus power for serial daisy-chained communication system
US20240378011A1 (en) Dynamic audio routing over a network bus
WO2022101407A1 (en) Systems and techniques for microphone array calibration

Legal Events

Date Code Title Description
AS Assignment

Owner name: ANALOG DEVICES, INC., MASSACHUSETTS

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:CHAVEZ, MIGUEL;KESSLER, MARTIN;SIGNING DATES FROM 20151015 TO 20151016;REEL/FRAME:036814/0540

STCF Information on status: patent grant

Free format text: PATENTED CASE

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 4