BLE on dedicated SoCs: a few µA in idle BLE on ESP32: ~35 mA base current For a battery powered product, that’s the difference between months and days 💡 Always do battery profiling before locking in hardware Want to estimate the battery life for your product? DMs are open.

Github is going to steal your code to make you job less, The policy change will take into effect from 24 April. If you want to save your code/data Just run off the stealing from the provacy settings. Attching a picture for reference.

Got it. Heads up GitHub is changing Copilot policy. From April 24, your chats, prompts, code suggestions, and context will be used by default to train their AI models (for Free, Pro, Pro users). If you don't want that, turn it off now. Go to: github.com/settings/copilot Under Privacy, set “Allow GitHub to use my data for AI model training" to Disabled. Do it quick before the change kicks in.

🛠️ Hardware debug help needed (I2C issue) ESP32 (ESP-IDF v5.2.5) I2C bus with 13 slaves. Works fine normally. But when ESP32 enters deep sleep: • SDA/SCL drop to ~1.2 V • After wake-up, lines never return to 3.3 V • I2C stays stuck until power cycle Pull-ups: 2.2k → 3.3 V Looks like a slave holding the bus or back-powering/leakage during sleep. Has anyone debugged this kind of behavior? What’s the right HW/FW fix with many slaves?

🛠️ Hardware debug help needed (I2C issue) ESP32 (ESP-IDF v5.2.5) I2C bus with 13 slaves. Works fine normally. But when ESP32 enters deep sleep: • SDA/SCL drop to ~1.2 V • After wake-up, lines never return to 3.3 V • I2C stays stuck until power cycle Pull-ups: 2.2k → 3.3 V Looks like a slave holding the bus or back-powering/leakage during sleep. Has anyone debugged this kind of behavior? What’s the right HW/FW fix with many slaves?

I asked GPT-5.1-Codex to hunt down a memory leak in my c based project. It confidently pointed at… nothing. A complete red herring. 😂 So I dug in myself, sprinkled debug logs, and found the real bug. Then I handed the exact fix back to GPT… and suddenly it “recognizes” it. Like bro, am I debugging my code or training you? 🤦‍♂️ AI is great, but nothing beats real engineering instincts. 🚀💻

Interrupts are powerful and dangerous. Used well: they make your firmware responsive. Used poorly: they create chaos. Golden rules: - Keep ISRs short - Avoid calling non-reentrant code - Never block or delay inside an ISR - Defer work to tasks or queues Fast ISR, stable system.

Firmware debugging tip: When the system “hangs,” it’s rarely truly stuck, it is waiting for something. Check for: • Blocked queues or semaphores • ISR missing a signal • Task starvation • Peripheral never ready Find what it is waiting for, and you will find your bug.

Horrible experience with @makemytrip and @IndiGo6E. Avoid booking flights through third-party apps. Here’s what happened: I booked a round trip AMD ↔ BLR. While returning, I missed my flight. Indigo rescheduled me to the next flight with an additional ₹3,000 fee — acceptable. But then the invoice mess started: • @makemytrip invoice: ₹12,385 • @IndiGo6E revised invoice: ₹13,936 (includes the extra ₹3,000 but shows reduced MMT commission) • My actual total expense: ₹15,385 • Correct invoice showing actual amount: NONE MMT says they cannot revise the invoice. Indigo’s invoice shows a different amount than what I actually paid. To make it worse, I even have call recordings with MMT customer care acknowledging the issue — still no resolution. Screenshots attached. Extremely disappointing experience. Final advice: If you value transparency, correct invoicing, and smooth issue resolution - always book flights directly from the airline website. Third-party apps may look convenient, but when something goes wrong, you’re stuck between two companies with no accountability.

Firmware design rule: If you can’t describe your system in events and actions, you don’t understand it yet. Every robust embedded application boils down to: When X happens → do Y. That’s event-driven design, the difference between a hobby project and a product

Good old days of through hole soldering. .

This was my first playground.😍

Bluetooth Low Energy (BLE): Nordic UART Service (NUS) Testing from Web Browser

This guy built a solar powered drone.. 100% Solar Powered Drone ☀️ youtube.com/shorts/nTpS9YVpn… via @YouTube

Today, I had a meeting with two talented founders, I am suprised by the product vision. Product is simple yet very useful and yet nothing like this in market. You don’t need to invent but observation can also generate great product ideas.

When you are building electronic products, the onlyperson who can decode your setup is you.

Palm-sized programmable USB-C PD power supply compatible with USB Power Delivery 3.0 PPS mode. cnx-software.com/2025/10/30/… Based on Raspberry Pi RP2040 MCU and AP33772 PD controller design, the PocketPD outputs 3.3V to 21V at up to 5A, supports adjustment in 20mV/50mA steps, features constant voltage/current modes, and includes a 0.96-inch OLED display for real-time monitoring.

ESP32-S3-based wireless JTAG and Logic Analyzer. cnx-software.com/2025/10/31/… EZ32's ESP32JTAG features a 16-channel 250 MHz logic analyzer with four configurable 4-wire ports that can also be used for JTAG, SWD, and UART interfaces. It is designed as an alternative to tools such as ST-Link or Saleae analyzers. A web interface is provided for configuration, and ESP32JTAG is compatible with tools such as OpenOCD, Blackmagic Probe, CMSIS-DAP, GDB Server, and openFPGALoader.

This has huge scope.

Agree! Mathematics is beautiful.

Fault-injection attack on the data/address bus: a new way to dump secret keys or break ARM TrustZone. 🩻🔗💣⌚🎰 More details on: LinkedIn: linkedin.com/posts/dlaskov_t… Substack: it4sec.substack.com/p/fault-…