The Problem occurs on the Uno r4 WiFi and an ESP32 dev board. Connected via USB-c cable (works otherwise).
Windows 11 latest version
Reinstalled latest Arduino IDE
Uno and ESP32 libraries installed
nothing connected to the boards
It has worked on this PC a month ago. Now i just wanted to get a temp sensor running and it always says ,,no device found" and something about data transmission not possible. I would be very gratefull for any tips or ideas what might be wrong. Thanks!
You seem to be using 3 different COM ports in those screen shots, like you are not sure which is the correct one to use.
It's easy to know which one to use. It's the one that appears when you plug the Arduino in and disappears when you unplug it.
If no new port appears when you plug in the Arduino, that is the real problem.
Please don't post any more screenshots of error messages. An image consumes 10,000x more data than is needed to share the error message. Just select the error message, copy it and paste it into your message, inside code tags.
Let's start by focusing exclusively on solving the problem for the UNO R4 WiFi. If we instead try to troubleshoot both boards at the same time, we are likely to get confused and waste time. Once we have achieved a resolution for the UNO R4 WiFi, we can switch our focus to getting your ESP32 dev board working.
Please try this:
Unplug the USB cable of the UNO R4 WiFi board from your computer.
Connect the UNO R4 WiFi board to your computer with the USB cable.
Press and release the button marked "RESET" on your UNO R4 WiFi board quickly twice.
You should now see the on-board LED that is marked "L" start pulsing.
Select the port of the UNO R4 WiFi board from Arduino IDE's Tools > Port menu. The double reset you performed in step (3) can cause the port number of the board to change, so don't assume you already have the correct port selected.
Select Sketch > Upload from the Arduino IDE menus (or click the "Upload" button).
Hopefully the upload will now complete successfully. Let us know how it goes.
Hmmm. This is a bad sign. It means that either the bootloader on the board's Renesas RA4M1 microcontroller has been erased, or that the RA4M1 is in a state that causes it to not run the bootloader.
Neither of these things will ever occur under normal operating conditions.
It is possible a short or external circuitry connected to the Arduino board could cause it to be in this bad state.
Make sure the board is not sitting on anything conductive that could short the contacts on the bottom of the board. Do a careful visual examination to make sure there isn't any conductive debris (e.g., loose beads of solder, strands of wire, or component leads) on the board or on the surface the board is sitting on.
If you have a shield or any external circuitry or components connected to your Arduino board, try this experiment:
Disconnect the USB cable of the Arduino board from your computer.
Disconnect any shields, modules, external circuitry, etc. from your board.
If you have any wires or jumpers connected to the 2x6 male header on the board, or to any of the other headers on the board, disconnect them.
Connect the Arduino board to your computer with a USB cable.
Connect the USB cable of the Arduino board to your computer.
Now check to see whether a port is shown for the board in Arduino IDE's Tools > Port menu. If not, close the Tools > Port, press the reset button on the board twice (as you did when following the instructions I provided in my previous post), then check for the pulsing "L" light and a port in the Tools > Port menu again.
If the board works as expected after removing the external circuitry, you will know the problem was caused by the external circuitry. You can then focus your attention on identifying the specific problem with the circuit and resolving it.
The problem might be caused by a damaged or defective USB cable. If you have another suitable USB cable on hand, try connecting the UNO R4 WiFi board to your computer with that cable, then check again to see if it is now working.
Make sure the cable is fully inserted into the USB sockets on the board and your computer.
Sadly, I suspect the UNO R4 WiFi board has suffered permanent physical damage. Maybe the other forum helpers will have an idea, but I think it is a lost cause.
I suggest we now switch our focus to trying to get your ESP32 board working.
I'm going to ask you to provide the full verbose output from an attempt to upload to the ESP32 board:
This procedure is not intended to solve the problem. The purpose is to gather more information.
Please do this:
Connect the ESP32 board to your computer with a USB cable.
Select File > Preferences... (or Arduino IDE > Settings... for macOS users) from the Arduino IDE menus.
The "Preferences" dialog will open.
Uncheck the box next to Show verbose output during: ☑ compile in the "Preferences" dialog.
Check the box next to Show verbose output during: ☐ upload.
Click the "OK" button.
The "Preferences" dialog will close.
Select File > New Sketch from the Arduino IDE menus.
A new sketch will open in an Arduino IDE window.
Select the appropriate board from Arduino IDE's Tools > Board menu.
Select the port of the board from Arduino IDE's Tools > Port menu.
Select Sketch > Upload from the Arduino IDE menus.
Wait for the upload to fail.
You will see an "Upload error: ..." notification at the bottom right corner of the Arduino IDE window. Click the "COPY ERROR MESSAGES" button on that notification.
Open a reply here on this forum topic by clicking the "Reply" button.
Click the <CODE/> icon on the post composer toolbar.
This will add the forum's code block markup (```) to your reply to make sure the error messages are correctly formatted.
Sketch uses 254936 bytes (19%) of program storage space. Maximum is 1310720 bytes.
Global variables use 22100 bytes (6%) of dynamic memory, leaving 305580 bytes for local variables. Maximum is 327680 bytes.
"C:\Users\Simon Ruhland\AppData\Local\Arduino15\packages\esp32\hardware\esp32\3.3.11\tools\flasher.exe" --esptool "C:\Users\Simon Ruhland\AppData\Local\Arduino15\packages\esp32\tools\esptool_py\5.3.1/esptool.exe" --build-dir "C:\Users\Simon Ruhland\AppData\Local\arduino\sketches\AB44B34BC6BFC52C0D13401C53977584" --chip esp32 --port "COM1" --baud 921600 --before default-reset --after hard-reset write-flash -z --flash-mode keep --flash-freq keep --flash-size keep 0x1000 "C:\Users\Simon Ruhland\AppData\Local\arduino\sketches\AB44B34BC6BFC52C0D13401C53977584/sketch_aug11a.ino.bootloader.bin" 0x8000 "C:\Users\Simon Ruhland\AppData\Local\arduino\sketches\AB44B34BC6BFC52C0D13401C53977584/sketch_aug11a.ino.partitions.bin" 0xe000 "C:\Users\Simon Ruhland\AppData\Local\Arduino15\packages\esp32\hardware\esp32\3.3.11/tools/partitions/boot_app0.bin" 0x10000 "C:\Users\Simon Ruhland\AppData\Local\arduino\sketches\AB44B34BC6BFC52C0D13401C53977584/sketch_aug11a.ino.bin"
esptool v5.3.1
Serial port COM1:
Connecting......................................
A fatal error occurred: Failed to connect to ESP32: No serial data received.
For troubleshooting steps visit: https://docs.espressif.com/projects/esptool/en/latest/troubleshooting.html
Failed uploading: uploading error: exit status 2
Ok, that's unfortunate, but thank you all for the diagnosis on the UNO.
@ptillisch I followed your steps for the ESP32 and on top is the Error Message. Hope that helps
Select View > Devices by type from the Device Manager menus.
Open the "View" menu.
If there is a ✓ to the left of the "Show hidden devices" menu item, click on "Show hidden devices" to disable it.
Take note of the contents of the "Other devices" and "Ports (COM & LPT)" sections of the Device Manager tree.
Connect the Arduino board to your computer with a USB cable.
Select Action > Scan for hardware changes" from the Device Manager menus.
Now please reply here on this forum topic with the answers to the following questions:
Did you see any new device appear in the Device Manager tree after following those instructions?
If you did see a new device, where is it located in the tree, and what is it named?
You can repeat the procedure multiple times if you are not sure.
ⓘ You can use USBDeview instead of Device Manager if you prefer. I chose Device Manager when writing the above instructions only because this is something all Windows users will have access to without installing additional software.
OK, you should be able to fix this by installing the driver provided by Silicon Labs, the manufacturer of the CP2102 USB chip on the board. You can download the driver from the manufacturer website here: