// the find
bonthasuryateja/EventBoard-RTC_Driven-message-Display-System
**Event Board** is an automated messaging system built on the **ARM7 LPC2148**. Using the internal RTC, it scrolls scheduled announcements on an LCD (with a green LED indicator); when idle, it displays real-time clock data and LM35 temperature readings (via ADC, with a red LED). Features a secure, password-protected keypad admin panel.
A bare-metal embedded C project for the ARM7 LPC2148 that drives a 16x2 LCD to show scheduled messages, falling back to a clock/temperature readout when idle, with keypad-based admin access. It's a single-board hobbyist/coursework project, not a library or reusable framework — useful mainly as a reference for someone wiring up RTC, ADC, and keypad peripherals on this specific chip.
The drivers are written directly against LPC2148 peripheral registers (RTC, ADC, LCD, keypad) with no HAL in between, so it's a decent read if you want to see what raw register-level peripheral setup looks like on this chip. The admin flow with a physical bypass switch plus keypad password is a sensible touch for a device that needs occasional reconfiguration without a full reflash. State separation between 'broadcasting a schedule' and 'idle dashboard' via LED indicators is a simple but workable way to signal device state without a status screen.
The README is dressed up with emoji headers and feature-list marketing copy that oversells what's a single-file main loop (Event_Board_Main.c) plus a handful of driver files — there's no architecture here beyond that. No schematic, pin-mapping table, or wiring diagram is included despite referencing specific GPIO/keypad/LED connections, so reproducing the hardware setup requires reverse-engineering the header files. LPC2148 is an end-of-life ARM7 part NXP has been phasing out for years, so this has limited value as a starting point for new hardware. Zero tests, no CI, and no license file, which matters less for a one-off board project but still means anyone forking it has no safety net and unclear reuse terms.