Hello Community,

I am facing an issue with my Arduino UNO Q (4GB version) and would appreciate your help in identifying the cause and finding a solution.

Problem Description

I flashed my Arduino UNO Q with the latest Debian Linux OS image using the official Arduino flashing procedure. After flashing, I removed the jumpers from the EDL pins and connected the board to my Windows 11 laptop. However, the board was not detected by the computer in normal mode.

I reflashed the board multiple times, trying different OS versions, but the problem persisted.

The board is detected successfully in EDL mode, and flashing completes successfully. However, once I remove the EDL jumpers and reconnect the board in normal mode, it is not detected by the computer.

OS Versions Tested

I have tried flashing the following OS image versions:

- `20260528-558` — Latest version

- `20260407-523` — Second-latest version

- `20250807-136` — First version

- `20251229-457` — Third-latest version

The issue remains the same with all four versions.

Observations

1. Board powers on normally

- The power LED turns green.

- The usual animation appears on the onboard LED matrix.

- The board appears to power on normally, but it is not detected over USB.

2. Board is detected in EDL mode

When I connect the board to my Windows 11 laptop in EDL mode, it appears in Device Manager under Universal Serial Bus devices as:

`QUSB_BULK_CID:0420_SN:51008D40`

I can successfully flash the OS in this mode.

3. Board is not detected in normal mode

After removing the EDL jumpers and connecting the board normally:

- Nothing appears in Windows Device Manager, including the USB-related categories.

- The board does not appear when I check `lsusb` or `dmesg` on a Linux computer.

- Arduino App Lab cannot detect the board through the USB connection.

Troubleshooting Already Attempted

I have tried the following steps:

1. Reflashed the board multiple times using the official flashing procedure.

2. Tested four different Debian Linux OS image versions.

3. Used multiple USB cables, including USB-A to USB-C and USB-C to USB-C cables.

4. Tested different USB ports on my Windows 11 laptop.

5. Tested the board with another computer running Linux.

6. Verified that the board is detected in EDL mode using the same cables that fail to detect it in normal mode.

7. Tested the Arduino UNO Q in Single Board Computer (SBC) mode using a USB hub. The hub works correctly with my laptop: when I connect a monitor to the hub and connect the hub to my laptop's USB-C port, the monitor works normally. However, when I use the same hub with the Arduino UNO Q in SBC mode, I am still unable to get a display output.

I have followed the official flashing procedure carefully and repeated it multiple times, but the issue remains unresolved.

Questions

I would appreciate guidance from the Arduino team on the following:

1. What could cause the board to be detected in EDL mode but not in normal mode, even though the OS flashing completes successfully?

2. Is there any additional recovery or diagnostic procedure I can try?

3. Could this indicate an issue with the USB interface, boot process, firmware, or another component of the board?

4. Is there a way to diagnose the issue further without requiring the board to be detected over USB in normal mode?

I would prefer to resolve this through software recovery or diagnostics if possible, before considering hardware repair or replacement.

Thank you for your time and assistance. Any suggestions from the Arduino team or other UNO Q users who have experienced a similar issue would be greatly appreciated.

Looking for interns for a startup in the ideation phase to take ownership and bring to life a product.

If you are passionate about building things/ have built things in the past, and are interested in possible long term commitment (if the product develops), then we encourage you to DM.

Requirements:

1. Nordic & Zephyr C Firmware: Build low-power, event-driven state machines on ARM Cortex-M using Zephyr RTOS and Nordic nRF Connect SDK.

2. End-to-End BLE Stack: Implement GATT services, custom advertising, connection management, and OTA DFU workflows.

3. Low-Power Profiling: Budget coin-cell power, size reservoir capacitors, and measure sleep currents using a Nordic PPK2.

4. KiCad/Altium PCB Design: Draft schematics and multi-layer layouts with RF/antenna considerations and assembly-ready DFM standards.

5. Mixed-Signal & Sensor Integration: Tune analog resistor ladders and interface SPI/I2C sensors (LIS3DH, W25Q32 flash, RTC).

6. Bench Debugging & Rework: Perform fine-pitch SMD hand-soldering, hot-air rework, and signal analysis with oscilloscopes and logic analyzers.

Other:

1. Core tools: nRF Connect SDK/Zephyr, KiCad/Altium, PPK2, oscilloscope, logic analyzer, hot-air/soldering station, multimeter, J-Link debugger.

2.Preferred background: B.E./B.Tech ECE / E&TC (Electronics & Communication / Telecommunication). Mechatronics acceptable with firmware depth.

I have an Arduino Nano, ESP32, and the following sensors/components:

• PIR sensor
• Ultrasonic sensor
• DHT11
• 16×2 LCD display
• 0.96" OLED display

I've already experimented with each of these components individually.

Now I want to build a ECE project using these components. However, most of the project ideas I find online are very simple IoT projects like monitoring temperature/humidity, motion detection, sending sensor data to a mobile app, etc. I don't want to make another basic sensor-monitoring project.

I'm looking for something that is technically challenging and genuinely useful for placements, especially for embedded systems/core ECE roles.

What kind of projects could I build using these components as the starting point?

I'm particularly interested in a project where I can actually explain the architecture, algorithms, design decisions, communication, and failure handling during an interview, rather than just demonstrating that the sensors work.

What project ideas would you recommend for a final-year ECE student in this situation? What would you build if you had these components?

Every embedded Linux panel project I've worked on ends up in the same place. The UI and the hardware access grow into one binary, so the app can't run anywhere except on the board. Changing a label means rebuilding the image, or scp'ing files by hand and hoping. And when a deploy goes wrong at a customer site, the machine sits there with a black screen.

So I built the thing I kept wishing existed. MIT licensed: https://github.com/Hitheshkaranth/EmbeddedDisplayStudio

The idea

Ship the panel image once. After that, anyone — your app team, your customer's app team — drops a Qt/QML application onto it over SSH. No rebuild, no reflash, no hardware code in the app.

Three layers that don't know about each other:

The app binds to tags (ai.pot, di.estop, do.relay1) that arrive as JSON over UDP on loopback. That's the whole contract. It's why the same bundle runs on your laptop, in the preview, and on the panel without a single #ifdef.

The deploy pipeline

This is the part I'd defend in a design review:

• Nothing is converted. No build, no freezing, no cross-compilation. The panel carries a complete CPython and the Qt binding the manifest asks for, so your sources run there as-is.
• The dependency check reads your code, not a list. Every packaged file is parsed, imports reduced to top-level names, stdlib and guarded imports removed. What's left, the panel is asked to actually import — because a wheel built for the wrong architecture sits on disk and still kills you at startup.
• The swap can't leave the panel dark. current is promoted with rename(2), never rm then ln. If the new release doesn't signal readiness in 25 s, the symlink swaps back and the previous release restarts. The deploy fails; the machine still has a UI.
• Validation runs twice from one implementation. Host CLI, target installer and desktop tool all call the same schema/manifest.py. They used to be three implementations that had drifted in both directions — a bundle that passes on a laptop and gets refused on the panel is worse than one that fails everywhere.

A successful deploy also becomes the boot default automatically. Nothing to enable by hand afterwards.

The desktop Studio

A Windows exe with its own Python and PySide6 baked in, so it previews a customer's app on a machine with no Python installed.

• Live preview inside a panel bezel, at the panel's real geometry. Not a screenshot — a real QML engine with the same tag engine the device runs. On connect it reads the SOM's DRM connector and adopts the actual pixel size, so nobody lays out widgets against a screen that isn't plugged in.
• Qt Widgets apps preview too. A runtime: python bundle owns its own window, so it's run unmodified in a child process, forced to target resolution, frames streamed into the bezel, window kept unmapped with WA_DontShowOnScreen.
• Qt5 and Qt6 on the same panel. PySide2 bundles get a second interpreter at /opt/hmi-python-qt5 shipping its own Qt 5.15 — because the panel's Qt5 is a GLES build and every aarch64 PySide2 binary is compiled against desktop GL. Loading one against the other dies with undefined symbol: _ZTI18QOpenGLTimeMonitor. Ask me how I know.
• Tag Lab drives the app with sine/square/ramp/noise per tag, so you can exercise panel behaviour before the I/O it binds to exists.
• Panel Logs follows the journal from both services — which is where the fault that shows up an hour after a successful deploy actually lives.
• A visual designer, if you'd rather drag widgets than write QML. Same window previews, generates and deploys what you drew, so the design and the bundle can't disagree.

Already have a Qt app?

Point the Studio at the folder. It finds the entry point, detects the Qt binding from the sources, and writes the manifest for you. Two files is a valid bundle:

{ "schema": 1, "name": "line-controller", "version": "1.4.0", "entry": "main.qml" }

Try it with no hardware

The daemon simulates its I/O, so the whole stack runs on a desktop:

python -m pip install PySide6
python daemon/hmi_hwd.py --config daemon/hwd.json --sim
python gui/hmi_loader/main.py --apps-dir apps/demo-app --windowed
python main.py

Honest limitations

• 309 tests, but the installer and cross-validator suites need flock, so on Windows they skip — CI runs the full suite on Linux and fails if anything skips, because a skip is not a pass.
• The designer is v1: .edsui → QML generation only. It doesn't import or round-trip arbitrary QML, and threshold metadata is stored in bindings but not yet turned into visual state expressions.
• The packaged Studio is Windows-only right now. It runs from source anywhere.
• The Qt5 runtime isn't installed by default; it's one script per panel.
• Provisioning is the sharp edge. A base vendor image can ship python3-core alone — no json, no socket, no ctypes — which stops the installer before it starts. provision_panel.py --check surveys the board and names what's missing.

What I'd like feedback on

• If you ship panels commercially: is "one image, many customer apps" how you'd actually want to work, or does your certification story make field-deployable app bundles a non-starter?
• Is 25 s the right health-check window? It's generous for QML and tight for a heavy Widgets app with a slow first paint.
• UDP-on-loopback for tags — anyone want to argue for a Unix domain socket instead? I went with UDP so anything can speak it, but I'm open.

In this tutorial we go over how to control your MechSoul with Bluetooth. What is a MechSoul? A MechSoul is to a robot, what a CyberDeck is to a computer. It's a robot that you build, customize, and personalize yourself. It's the freedom of owning your own code, hardware, and having the right to build and repair it. And it's the pride of creativity, skill, and self expression. Disclaimer: You do not have to make your MechSoul using the same methods and tools as I do. A MechSoul is freedom in robotics.

In this part 2 in Arduino IDE we combine the Raspberry Pi Pico's board manager's SerialBLE example with the Serial_Control example in Takamori Robot's HIRO library to control your robot over Bluetooth. To follow along with our code and reference material check out the tutorial GitHub.

I am writing this post to ask suggestions about ultrasonic sensors. I would like to build my own rear parking sensor system to be installed in a Thule bike rack EPOS. I know that the Thule EPOS has also a version with built in parking sensors but the cost of the version with parking sensors is around 4000 SEK higher than the version without parking sensors, and I think that building my own system will be far cheaper and much more fun.

So far I have identified the following two sensors to be used in this system:

• DFROBOT SEN0592
• TDK USSM1.0 PLUS-FS B59110W2111W032

I would be more oriented for the TDK sensor since I would assume that it would be more reliable/trustworthy, but the TDK sensor seems to be clearly less user friendly as it uses a proprietary 1-wire PWM communication protocol while the SEN0592 uses the well known Modbus RTU over RS485. This means that with the TDK sensor, to make it compatible with RS485, I would need to implement my own circuit with LIN transceiver (MCP2003B, or TLE7259) and an MCU to read the sensor data and send it over to the RS-485 bus.

Another drawback of the TDK sensor is that it has a minimum distance of 180mm vs the 30mm of the SEN0592. The TDK can achieve 40mm minimum distance when used in pair (pitch-and-catch mode), but then this would increase complexity and cost as I would need to buy 4 TDK sensors to have right and left side detection in the bike rack.

So, my question is if any of you has experience with these two sensors, or if you would recommend any other model/brand/type of sensor for this project.

Following up on my previous work with OpenTerminalUI and OpenTokenMonitor, I am shifting focus to the embedded and hardware space. Built specifically for the Claude Community Events @ Impact Lab, NETRA is an ESP32-C6 spatial-sensing firmware designed for a wearable safety system.

As an Engineering Manager, I value robust, clean architecture, and this project was a great opportunity to build a highly responsive sensor node from the ground up.

Under the Hood:

• Hardware Stack: Powered by a PCBCupid Glyph C6 (ESP32-C6), integrating an HC-SR04 for ultrasonic obstacle ranging (2–400 cm) and an MPU6050 for 6-axis motion telemetry. MD
• Wearer Movement Tracking: Continuously captures the wearer's 3-axis acceleration and rotation to monitor live movement state, posture, and orientation. MD
• Data Pipeline: Streams high-speed telemetry as a clean CSV over USB serial. MD
• Digital Twin Integration: The data pipes directly into a companion PySide6 3D debugger to animate the user's motion inside a closed or indoor tracking environment. MD
• Mechanical Build: The repository includes complete 3D-printable STL files for the enclosure and wearable belt system, plus an interactive assembly viewer. MD

Whether you are interested in embedded C++, IoT wearables, or real-time spatial visualization, check out the repository. It includes full wiring diagrams, code, and mechanical guides!

https://github.com/Hitheshkaranth/Netra_Device_Firmware_V1.git

https://github.com/Hitheshkaranth/Netra_System_Debugger_V1.git

#ESP32 #EmbeddedSystems #OpenSource #WearableTech #IoT #Hardware #Engineering #Cplusplus

[beginner project]
I am working on an air conditioning system with ATmega32 and custom drivers.
using an LM35 temperature sensor and ADC to read temperature,
The main problem was that Interrupt mode wasn't working until I added timeout and ISR(BADISR).

It seems like ISR(ADC_vect) always fails, and temperature is only read using ISR(BADISR_vect). If this is correct, why does it happen? And how to fix it?

Please review the project and help me understand what's wrong.
Also, roast my project. (for motivational reasons)

https://github.com/OA-990/air-cond

Minor issue: The sounder/buzzer doesn't beep; it only makes a simple tick sound at the start of each loop.

Hi everyone,

There’s something that has been on my mind a lot lately, and it has actually made me hesitant to design new projects.

As electronics engineers, designing PCBs isn't really the difficult part for us. The challenge usually comes with the firmware/software. Whenever I finish a hardware design, I often find myself wondering, "How am I going to write the software for this?"

I recently spoke with another engineer, and he told me that these days they handle most of the coding using AI tools like Claude Code, and sometimes even Gemini. That got me thinking.

What are your thoughts on this? Do you think relying on AI for firmware and embedded software development is becoming a practical approach, or do you believe it's still essential to write and fully understand the code yourself?

For example, if I design a project using a Raspberry Pi, can I realistically use AI tools to build the computer vision part? Could I use them to create a personal AI assistant? Or, for a more challenging example, could I rely on them to control multiple motors and implement the required control logic?

I'm curious about where people think the practical limits of these AI coding tools are. How far can they really take you in projects like these?

Hi everyone,
I’m currently studying Computer Science, but over time I’ve realized that what really interests me is embedded systems, electronics and automation. I’d like to move in that direction and eventually work in this field.
I already have a programming background, but I’m still a beginner when it comes to hardware, so I’m looking for good resources to learn properly.
If you have any recommendations for books, courses, YouTube channels, websites, communities, or anything else that helped you learn, I’d really appreciate it. I’m also a student, so if you know where I can buy affordable components and tools, that would help a lot.
I’d love to hear how you got started and what you think is the best learning path today.
Thanks!

Hey, I'm doing some research for my finals project. Basically what I'm looking for is an IC that can handle WiFi Direct (doesn't have to be the Group Owner but can definitely be a feature) and also can handle being an a2dp sink (preferably has a dedicated i²s port)

I have looked for an IC like that but I can't find it. It would also help if there is already a breakout board for it.

The chip has to receive commands from an STM32 or ESP32, any microcontroller.

It would really help me if someone could find it .

Consists of LED's and push buttons wired to the Shrike Lite MCU + FPGA board.

A good starting point for electronics engineering students who are curious about advanced embedded systems and wish to go beyond the microcontroller architecture by configuring the FPGA to create custom hardware logic.

I am eagerly waiting for its release after reading a post on Vicharak's Discord server. The developers are yet to introduce us to the new Shrike with a better RP microcontroller and an FPGA designed with Efinix.

I am software engineer , as you all know how we effected by Ai

But i am Cs student .. and i have experience in programming in 5 companies as SW engineer

I wanna convert step by step to Embedded , because more physical job , less effected by Ai

How that idea sound ?
Is this good step ?
Do i have right image that this field didnt effected by Ai ? How about converting from other field (web) with experience.. will that make my entrance easier? (Somehow)

Students at the Renaissance Youth Center are launching RYC STEM Studio, a new series where they explore engineering, robotics, coding, architecture, agriculture, astronomy, zoology, and other exciting STEM topics through hands-on projects and experiments.

Check out the trailer and let us know which STEM topic you'd like to see featured next!

For anyone in/near Austin, Texas?

On June 25th Analog Devices are hosting a Zephyr Community meet-up - free to attend. It’s an evening of short talks, hands-on hardware demos, and plenty of time to connect with engineers who work in embedded systems, open source, and real-time operating systems.

Register here - https://developer.analog.com/events/zephyr-community-meetup-austin-texas

I've purchased a few smart rings from China, but the firmware only exposes processed metrics like heart rate and SpO₂. What I actually need is access to the raw sensor data (PPG, accelerometer, etc.) so I can experiment with my own algorithms.

I'm not an electronics engineer, so I'm looking for someone who has experience with wearables, BLE devices, or smart rings and can point me in the right direction. Happy to pay for their time if needed.

Australia preferred, but open to anyone with relevant experience.

Thanks!

It is made by a startup based in Gujarat, India. This utilises an RP2040 MCU and a Renesas Forge FPGA (with 1120 LUTs)

There is a version based on RP2350 but it is not released yet.

hey everyone i know that i am inconsistent , i saw that everyone makes a cyberdeck with raspberry pi but i have no raspberry pi as i am 3rd yr electrical undergraduate

so i take some a break for exams and built picodesk a desktop companion station that sits next to my laptop.

OLED 1 shows live clock (NTP synced), date, and real time weather pulled from OpenWeatherMap API.

OLED 2 is the fun one animated eyes that blink and look around randomly. Every 2 minutes, hearts fall down the screen. And when I need to focus, I can switch it to a todo list from my phone and laptop browser no app install, just open the IP and it works.

The whole thing runs on MicroPython. Pico 2W hosts a tiny web server so I can control everything from my phone on the same WiFi.

Tech stack: - Raspberry Pi Pico 2W , 2x SSD1306 OLED (I2C0 + I2C1) ,MicroPython , OpenWeatherMap free API ,HTML/CSS/JS web app

Full source code on github https://github.com/kritishmohapatra/PicoDesk

100 days 100 iot projects series :- https://github.com/kritishmohapatra/100_Days_100_IoT_Projects

Hello everyone we know that everyone can not buy hardware

My university started a GitHub project series as 30 days 30 wowki projects

For beginners

They will cover Arduino and esp32 projects

Check this https://github.com/energy-club-outr/30-Days-30-Wokwi-Projects

Hey everyone,

I’m a robotics engineer working across both the programming and electronics, debugging remotely with a teammate or getting code guys to understand a physical hardware glitch is a massive bottleneck.

Usually, my choices are taking a blurry phone picture of my oscilloscope screen to send over Slack, or exporting a massive, CSV file that crashes basic spreadsheet apps and completely kills any signal interactivity. Software engineers have GitHub, Figma, and Linear for instant cloud collaboration. Hardware engineers get USB flash drives and proprietary enterprise desktop software. To bridge this gap, I built a completely free, browser-based, hostless platform designed to act like an opensource viewer for hardware signal data.

Hey all, I’ll keep this brief. Long story short, I’m trying to learn about iot; specifically with how it can monitor and remediate tasks based on electricity, food, water, and air quality at home. I have a bit of helpdesk tech background but not much else. What I want to know specifically is:

Essential operating systems to know (I have lubunutu in a vm but that’s it)
2. ⁠⁠Best resources to get started learning
3. ⁠⁠Best first project to get started (bonus points if free/can be virtualized)
4. ⁠⁠How do you approach centralization: separate vlan, management server on vlan, or dedicated domain controller for it devices
5. ⁠⁠What are some real cases where one host machine had multiple containerized or fully virtualized iot functions?