Firmware
A pet wearable streams six-axis motion data at 100 Hz to a home hub over Bluetooth Low Energy. The dog walks into the next room. The wall absorbs more RF than the supervision timeout can tolerate, and the link drops. Twelve seconds later the dog walks back out and the
Hardware
In embedded systems, resets are often treated as normal behaviour. A watchdog expires. A brownout occurs. A PMIC toggles reset. Firmware crashes. Power sequencing fails. A peripheral hangs the bus. A rail collapses temporarily. The system resets and comes back online. From the outside, everything appears functional again. But the
Hardware
Modern embedded systems rarely “sleep” as a single unit anymore. A connected device today is usually a collection of semi-independent subsystems working together continuously. There may be an application processor running Linux, one or more microcontrollers handling real-time control, sensors operating in low-power modes, external transceivers, PMICs, retention domains, always-on
Hardware
Cables are one of the most underestimated variables in embedded systems design. On paper, they are treated as passive conductors — short, well-terminated, and electrically invisible. Schematics assume clean transitions, stable impedance, and perfect contact. But once a product leaves the lab, cables stop behaving like ideal interconnects and start behaving
Firmware
A double-bit error in the application flash of a deployed device is not a theoretical event. It is what happens when a stray neutron — or simply an aging storage cell — flips two bits in a single sixteen-byte ECC word at the wrong instant, in the wrong region, on a customer&
Software
Hardware setup flows are deceptively hard to build well. A Wi-Fi speaker or IoT device might need Bluetooth permissions, adapter readiness, a 10-second scan, device selection, GATT connection, and a service handshake - each of which can fail independently and silently. When you are building this in Flutter, you quickly
Hardware
UI elements are often treated as harmless. Buttons, LEDs, touch pads — they sit quietly on the board, interacting with the user, far removed from the “serious” parts of the system like high-speed interfaces, ADCs, or communication buses. But in reality, UI elements are some of the most uncontrolled electrical entry
Hardware
Rework is not an exception in hardware development. It is part of the process. Boards are probed, components are replaced, connectors are re-soldered, tracks are modified, and sometimes entire sections are rebuilt — all before the design reaches stability. Yet most boards are not designed with rework in mind. They are
Firmware
A time-of-flight proximity sensor's accuracy depends entirely on three calibrated numbers: an offset correction, a crosstalk coefficient, and a reference SPAD count. Without them, the sensor's distance readings carry systematic errors of tens of millimetres — enough to misfire a capture trigger or miss a detection event
Technology, Insights and Ideas.
Software
When users tell you "the chat feels slow," the first instinct is to blame the model. Bigger LLM, longer prompt, more retrieved context — those are the obvious suspects. But when we profiled our AI assistant's chat endpoint end-to-end, the model itself was already running about as
Firmware
A pet wearable streams six-axis motion data at 100 Hz to a home hub over Bluetooth Low Energy. The dog walks into the next room. The wall absorbs more RF than the supervision timeout can tolerate, and the link drops. Twelve seconds later the dog walks back out and the
Hardware
In embedded systems, resets are often treated as normal behaviour. A watchdog expires. A brownout occurs. A PMIC toggles reset. Firmware crashes. Power sequencing fails. A peripheral hangs the bus. A rail collapses temporarily. The system resets and comes back online. From the outside, everything appears functional again. But the
Hardware
Modern embedded systems rarely “sleep” as a single unit anymore. A connected device today is usually a collection of semi-independent subsystems working together continuously. There may be an application processor running Linux, one or more microcontrollers handling real-time control, sensors operating in low-power modes, external transceivers, PMICs, retention domains, always-on
Hardware
Cables are one of the most underestimated variables in embedded systems design. On paper, they are treated as passive conductors — short, well-terminated, and electrically invisible. Schematics assume clean transitions, stable impedance, and perfect contact. But once a product leaves the lab, cables stop behaving like ideal interconnects and start behaving
Firmware
A double-bit error in the application flash of a deployed device is not a theoretical event. It is what happens when a stray neutron — or simply an aging storage cell — flips two bits in a single sixteen-byte ECC word at the wrong instant, in the wrong region, on a customer&
Software
Hardware setup flows are deceptively hard to build well. A Wi-Fi speaker or IoT device might need Bluetooth permissions, adapter readiness, a 10-second scan, device selection, GATT connection, and a service handshake - each of which can fail independently and silently. When you are building this in Flutter, you quickly
Hardware
UI elements are often treated as harmless. Buttons, LEDs, touch pads — they sit quietly on the board, interacting with the user, far removed from the “serious” parts of the system like high-speed interfaces, ADCs, or communication buses. But in reality, UI elements are some of the most uncontrolled electrical entry
Hardware
Rework is not an exception in hardware development. It is part of the process. Boards are probed, components are replaced, connectors are re-soldered, tracks are modified, and sometimes entire sections are rebuilt — all before the design reaches stability. Yet most boards are not designed with rework in mind. They are
Firmware
A time-of-flight proximity sensor's accuracy depends entirely on three calibrated numbers: an offset correction, a crosstalk coefficient, and a reference SPAD count. Without them, the sensor's distance readings carry systematic errors of tens of millimetres — enough to misfire a capture trigger or miss a detection event