I thought I'd check here before speaking to my supplier about a replacement board.
I've been using my UNO R4 WiFI for a couple of weeks, loading sketches etc. Every so often it would get in a bind ... usually "no device found" on the chosen COM port. It was annoying but after re-plugging the USB cable, or restarting the IDE, or even rebooting my computer it would come good.
But not anymore, now I can't upload a new sketch no matter what I try, and on two different computers :
Sketch uses 60480 bytes (23%) of program storage space. Maximum is 262144 bytes.
Global variables use 7020 bytes (21%) of dynamic memory, leaving 25748 bytes for local variables. Maximum is 32768 bytes.
No device found on COM12
Failed uploading: uploading error: exit status 1
I tried the double reset suggestion in this thread: failed uploading
The led pulses but no change in COM port list, or upload status.
What version of the ESP32 code are you running?
Or more specifically have you updated to version 0.3.0?
There are manual ways to do it, but with version 2.2.1 or the like, you can go to the tools menu and choose the firmware updater. The updated versions helped a lot with uploads.
Unfortunately I can't upload anything to R4 at present, and my Serial Monitor is almost completely silent. The LEDS on board just after reset indicate it's bascially working OK. Hence I suspect the Comms h/w has died.
As I mentioned, I went through some periods where I could not get a new program to upload and first the update to the ESP32 code to 0.2.2 helped and did not have any additional problems after I updated to 0.3.0.
The update of the ESP32 bridge code worked for the most part even when I could not upload programs. You needed to make sure that no Serial monitor was active.
As I mentioned in previous post, I experimented by slightly modifying the board. I soldered switch across the boot jumper, so that the RA4M1 processor is the one that talks directly to the USB, plus needed to build and install bootloader, plus a new variant to the IDE... More in the thread:
But before the updated ESP32 bridge code when I was in the state of nothing would upload. I would exit and then reopen IDE, usually with something real basic like blink.
And then would try to upload
If that failed, would click the reset button., then try double click. And then try two double clicks in a row... If all of those failed, would try turning the power off the board and try to time turning the power back on to just at the time the build was going to try to upload. Would try it several times. It felt like if you hit some timing window it would work.
@Dozie I'll keep that updater as a back pocket option (thanks). My R4 WiFi board was working fairly well under IDE 2.2.0 for some time, and only in last few days it doesn't. So I doubt updating the ESP firmware would fix it .
The comms started working long enough to upload a sketch. Lasted about an hour then started to fail with this new error report:
WARNING: library ArduinoGraphics claims to run on samd architecture(s) and may be incompatible with your current board which runs on renesas_uno architecture(s).
Sketch uses 64280 bytes (24%) of program storage space. Maximum is 262144 bytes.
Global variables use 8372 bytes (25%) of dynamic memory, leaving 24396 bytes for local variables. Maximum is 32768 bytes.
Cannot perform port reset: TOUCH: error during reset: opening port at 1200bps: The semaphore timeout period has expired.
No device found on COM3
Failed uploading: uploading error: exit status 1
At the start of the upload, Arduino IDE signals the UNO R4 WiFi board that it should go into the mode where it can accept an upload. The signal used is the IDE momentarily opening the serial port of the board at the special baud rate of 1200 bps.
@Dozie I have got my R4 comms working again. I also have a sketch to query my ESP F/W version and advise if any the later version is available. Apparently my ESP is 0.2.0 and there is a 0.3.0 available.
I went to the updater page on GitHub but for some reason I could not find the ZIP file to download. Can you point it out please ...
FYI it turns out my R4 WiFI board comms are not faulty after all, instead there is a known bug in the IDE that means the R4 WiFI board is not actually selected, even though it appears in the main pull-down. As a result the R4 WiFi packages weren't being loaded causing the USB comms to fail during upload.