LED Driver Circuit Using I2C Pins for Multi-Device Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing LED driver circuits require dedicated pins for synchronization, which increases the number of pins needed, making them less desirable for low-cost and small devices, and complicates the simultaneous start-up and synchronization of multiple LED driver devices in star or chain topologies.
Innovation Solution
The solution involves reconfiguring non-dedicated LED driver input-output pins to assign local I2C addresses, allowing for simultaneous start-up and synchronization of multiple LED driver devices without dedicated synchronization pins, using a microcontroller to manage a single clock signal and I2C bus for communication, enabling each device to be addressed individually for channel configuration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If dedicated synchronization pins are used in LED driver circuits, then simultaneous start-up and synchronization of multiple LED driver devices is achieved, but the number of pins required increases
Solution Approach 1:
The I2C bus pins (SDA and SCL) are made multi-functional by enabling them to serve both their original communication purpose and the new synchronization function. The existing pins are reconfigured through software control to act as synchronization pins, allowing one pin to perform multiple functions and thereby reducing the total pin count while maintaining synchronization capability
Solution Approach 2:
The synchronization function is merged with the existing I2C communication function by using the same physical pins (SDA and SCL) for both purposes. This combining of functions eliminates the need for separate dedicated synchronization pins, reducing device complexity while preserving the synchronization capability through shared resource utilization
2Reliability
If dedicated synchronization pins are used for each LED driver device, then reliable synchronization is achieved, but hardware costs increase
Solution Approach 1:
Existing I2C pins are made multi-functional to perform both communication and synchronization tasks, eliminating the need for additional dedicated synchronization pins. This reduces the bill of materials and manufacturing complexity while maintaining reliable synchronization through software-controlled pin reconfiguration
Solution Approach 2:
The synchronization function is merged into the existing I2C communication infrastructure, combining multiple functions into shared hardware resources. This consolidation reduces the number of components needed, lowering hardware costs while preserving synchronization reliability through the shared pin infrastructure
3Adaptability or versatility
If multiple LED driver devices are connected in star or chain topology, then system flexibility is improved, but synchronization coordination becomes more difficult
Solution Approach 1:
The pin configuration is made dynamic through software control, allowing pins to be reconfigured between communication and synchronization modes. This dynamic reconfiguration enables the system to adapt to different topology requirements (star or chain) while maintaining simple synchronization coordination through centralized microcontroller management
Solution Approach 2:
The microcontroller acts as an intermediary that manages the I2C bus and coordinates synchronization across multiple LED driver devices. This intermediary approach simplifies synchronization coordination in complex topologies by providing centralized control and management of the reconfigurable pin system
Data Source
AI summary
A circuit includes a set of LED driver devices and a controller including a set of nodes coupled to a first slave address pin and a second slave address pin in each LED driver devices in the set of LED driver devices. Each LED driver device includes a finite state machine (FSM) configured to generate LED drive PWM-modulated signal patterns, an oscillator configured to generate a clock signal for the FSM, a first signal path activatable between the first slave address pin and the FSM, and a second signal path activatable between the FSM and the second slave address pin.