Wall switches commonly generate two signal types: level-hold and edge-triggered (quasi-sinusoidal "bun-shaped" pulses). In both cases, the system must detect power loss and subsequent restoration to toggle color temperature — but timing constraints are critical. Key hardware considerations: - VCC must remain stable for ≥100 ms after power interruption to retain state; shorter interruptions trigger mode switching.

• Upon detecting voltage drop, apply 30 ms debouncing before disabling output — this allows bulk capacitors to discharge gradually and avoids premature state reset.
• A re-power evant occurring within 100 ms of power loss triggers color-temperature cycling and EEPROM persistence; longer gaps suppress activation entirely.

Software implemantation should avoid ADC averaging for reliability. Instead, use direct GPIO level sampling with edge detection: ``` // Detect rising edge on power restoration void handle_power_rising_edge() { static uint8_t prev_state = 1; const uint8_t curr = READ_PIN(PWR_DETECT_PIN);

if (curr && !prev_state) {
    // Rising edge → power restored
    if (power_off_duration_ms < 100) {
        cycle_color_temperature();
        save_to_eeprom(current_mode);
    }
}
prev_state = curr;

}

// Track power-off duration in 1 ms tick ISR void tick_1ms_handler() { if (!READ_PIN(PWR_DETECT_PIN)) { power_off_duration_ms++; if (power_off_duration_ms == 30) { disable_output_drivers(); // Safe shutdown } else if (power_off_duration_ms == 100) { disable_switching_flag(); // Lock out mode change } } }

### 2. LED Matrix Brightness Control via Scan Timing

Brightness in multiplexed LED matrices is governed not by interrupt frequency alone, but by duty cycle distribution across active rows/columns. Best practices: - Place scanning logic inside a high-priority timer interrupt (e.g., 1–2 kHz), but modulate brightness by varying per-scan ON time — not interrupt rate.
- Minimize scan groups: For a 4×3 matrix, scanning 3 columns (instead of full 4-row sweeps) improves effective refresh rate and perceived brightness.
- Drive common terminals first (e.g., common cathode lines) — they typically support higher sink current and reduce driver overhead.
- Prefer shared-anode or shared-cathode layouts with minimal routing complexity during PCB design.

### 3. Battery Undervoltage Handling Logic

Robust low-voltage detection requires context-aware flag management: - **Primary cells:** Once under-voltage is detected (e.g., <3.0 V), the flag remains set until cold boot — no auto-clear on recovery.
- **Rechargeables:** Flag clears only when charging begins *and* cell voltage exceeds 3.3 V for ≥5 s.
- All implementations must enforce ≥3 s delay before asserting undervoltage — prevents false triggers from transient load spikes or incomplete discharge.

For validation, use constant-current electronic loads (CC mode) instead of resistive loads to simulate real-world battery sag. ### 4. Minimizing Standby Current

Excessive quiescent draw often stems from misconfigured I/O states: - Input pins with internal pull-ups/downs may form unintended current paths — verify schematic connectivity before enabling them.
- Open-drain interfaces (e.g., charger status pins) require pull-ups; always-on low signals (e.g., touch IC ready) suit pull-downs or floating inputs.
- Disable ADC modules before sleep — even idle analog inputs leak microamps through bias networks.
- Ensure PWM outputs default to low or high-Z in sleep mode; an active-high PWM line feeding a 120 kΩ resistor draws ~41 µA at 5 V.

Wake-up sources like external interrupts must be configured with analog input disabled — treat ADC channels as digital-only during deep sleep. ### 5. Single-Cell Li-ion Voltage Monitoring

Direct VDD-referenced ADC measurements are unreliable for single-cell monitoring because: - Li-ion range: 2.7–4.2 V; MCU supply (e.g., 3.3 V LDO) drops out below ~3.4 V.
- ADC reference collapses as VDD sags → measurement nonlinearity and offset errors.

Solution: Use an external voltage reference (e.g., TL431) or ratiometric divider with known precision resistors, referenced to a stable bandgap. ### 6. Smooth PWM Transition Implementation

Gradual duty-cycle ramping avoids visual flicker and mechanical stress on drivers: ```
void update_pwm_smoothly(uint16_t target_duty) {
    static uint16_t current_duty = 0;
    const uint16_t step = 8; // Adjustable step size

    if (current_duty < target_duty) {
        current_duty = MIN(current_duty + step, target_duty);
    } else if (current_duty > target_duty) {
        current_duty = MAX(current_duty - step, target_duty);
    }

    set_timer_compare_value(TIMER_PWM_CH, current_duty);
}

7. Memory Space Allocation in 8051-like Architectures

Understanding memory qualifiers prevents overflow and performance pitfalls: - data: Fastest (direct addressing), limited to first 128 B RAM.

• idata: Slower (indirect addressing), next 128 B RAM.
• xdata: External RAM accessed via DPTR — used for buffers, frame stores.
• code: Read-only program memory — store lookup tables, strings here.

Example declaration: uint8_t xdata frame_buffer[256]; allocates in external RAM. ### 8. MOSFET Driver Selection Guidelines

• NMOS: Preferred for low-side switching. Conducts when VGS > Vth (typically 2–4 V). Ideal for ground-referenced loads.
• PMOS: Used for high-side switching. Conducts when VGS < −Vth. Requires gate pulled below source — often driven by charge pump or level shifter.

Always include gate series resistors (10–100 Ω) and parallel 10 kΩ pull-downs/pull-ups for defined startup states. ### 9. Protection Diodes and Rectifier Bridges

• Zener diodes placed across MOSFET gates clamp transients to safe levels (4.7–6.8 V typical).
• Full-wave bridge rectifiers double AC input frequency — crucial for zero-crossing detection in AC-phase control.
• Post-rectification filtering requires bulk capacitance (e.g., 4.7 µF/440 V for 220 VAC) followed by LDO regulation (e.g., AMS1117-3.3) for clean logic supply.

10. Ambient Light Sensor Interference Mitigation

LED emission corrupts nearby photodiode readings. Solution: synchronize sampling to LED OFF periods using PWM timer interrupts — read sensor only during guaranteed dark intervals. ### 11. Debugging Runaway Code

Use GPIO toggling as execution markers: - Assert pin before entering critical loops.

• Clear pin up on successful exit.
• Oscilloscope observation reveals stuck states instantly.

Example UART transmit guard: ``` void uart_send_byte(uint8_t b) { PIN_DEBUG_SET(); SBUF = b; while (!TI); TI = 0; PIN_DEBUG_CLEAR(); }

### 12. J-Link Connection Troubleshooting

- Confirm J-Link driver installation via Device Manager.
- Verify SWD pin mapping: SWCLK ↔ CLK, SWDIO ↔ DIO, GND, and optional VREF (not VDD).
- Ensure target board receives stable power — many debuggers fail silently without proper VCC.
- In Keil µVision, select "SW" interface and reduce clock speed (≤1 MHz) for noisy or long-trace layouts.

</div>