How to update ESP32-S3 firmware (after install of platform 1.0.4)

Hardware UNO R4 UNO R4 WiFi
1

I had got the impression that this would be somehow automatic after platform update to 1.0.4.

For earlier versions this has been described in several topics. I could go searching. Still valid?

But I think an explanation for 1.0.4 would be helpful.

Of course I noticed this readme:
https://github.com/arduino/ArduinoCore-renesas/blob/main/bootloaders/UNO_R4/README.md

Do I really need to install the ESP32 IDF?

I am running Arduino IDE 1.8.19 on a Windows 10 notebook, and Arduino IDE 2.2.1 on a Windows 11 notebook.

Thank you!
-jz-

2
1 Like
3

Are you wanting to update to 0.2.1 or 0.3.0?
Or install your own firmware?

Using Tools > Firmware Updater from the Arduino IDE menu currently installs 0.2.1

They indicated 0.3.0 will be available in the next few days

1 Like
4

I highly appreciate the answers I got to my question. Will hopefully be of use to others, too.

I will wait for 0.3.0 to become available.

Thank you!

5

it is available, just not in the IDE

6

Firmware version 0.3.0 should now be available for installation via the "Firmware Updater" feature of Arduino IDE.

2 Likes
7

Hi @ptillisch, is there a way to determine which ESP revision is installed on a board?

It isn’t reported when you query the board info from the Tools menu.

Or is the only way to ensure a firmware version to install it?

Thanks

8

Hi @flynace. You can upload this sketch to your board and then open Serial Monitor:

#include <WiFiS3.h>
void setup() {
  Serial.begin(9600);
  while (!Serial) {
    ;  // wait for serial port to connect.
  }
  delay(2000);
  Serial.print("Firmware version: ");
  Serial.println(WiFi.firmwareVersion());
}
void loop() {}
1 Like
9

I had some issues with Firmware Updater. I add my findings here.

I received my first Arduino UNO R4 WiFi about a month ago. I don't know which firmware it had.
I purposely waited with updating its firmware (and using WiFi with this board) until a stable method became available. That is why I then created this topic to be sure.
I had an issue with the Firmware Updater on my first board, see
Arduino UNO R4 WIFI firmware updater - UNO R4 / UNO R4 WiFi - Arduino Forum

It consistently failed to install 0.3.0.
I then installed 0.2.1, success on the first attempt.
Then I tried to install 0.3.0 again, success at first attempt.

Now I received my second Arduino UNO R4 WiFi.
Its firmware came as 0.2.1, checked with method in post #8.
I tried to install firmware 0.3.0 with Firmware Updater, result installation failed.
I didn't observe the installation behavior, and didn't check the firmware version.
I then tried to install firmware 0.2.1 with Firmware Updater, result installation failed.
But the installation behavior looked ok, until some idle time at the end.
I then tried to install firmware 0.3.0 with Firmware Updater, result installation failed.
But the installation behavior again looked ok, until some idle time at the end.
Check of the firmware showed 0.3.0
Cycling between 0.2.1 and 0.3.0 always showed the same behavior.
Of course I had to disconnect / reconnect USB after every update.

Conclusion: for me the Firmware Updater method works, but seems to have some quirks.
-jz-

10

You can also check this Help Center article for firmware update.

11

@jojo, thank you.

I assume you agree that use of the Firmware Updater would be easier.

Therefore I hope that the quirks with the Firmware Updater can / will be solved sometime.

But maybe I am the only one affected?

12

Hi @ZinggJM. Unfortunately the IDE doesn't currently do a good job of making the information about the cause of a firmware update failure visible to the user. We might be able to get a better idea of what is going wrong by checking the output that is printed to the IDE's logs when the update process fails.

The basic procedure:

  1. Select File > Quit from the Arduino IDE menus if it is running.
  2. Start Arduino IDE from a command line terminal
  3. Perform firmware updates just as you did before until you experience the fault.
  4. Switch back to the terminal window.
  5. Copy the logs that are printed there.
  6. Paste the logs in a reply here.

I can provide more detailed instructions if you like; I would only need to know which operating system you are using on your computer (e.g., "Windows").

I have performed many firmware updates using the Arduino IDE Firmware Updater feature during the course of my beta testing work. There are some known conditions under which the update will fail (having Serial Monitor/Plotter open, not power cycling the board after a previous operation), but the failure occurs 100% consistently under those conditions. I haven't experienced an intermittent failure as you describe.

13

Hi @ptillisch.

It depends on the Arduino UNO R4 WiFi board. It works on my first one, but indicates failure on the second one. Follows the CMD output of the second one:

An error occurred: Body is limited to 120000 characters; you entered 196367.

going to add as ZIP-file.

Thank you; may help for future users.
-jz-

Windows PowerShell.zip (16.4 KB)

added:

I didn't pay attention to this. I am not yet used to Arduino IDE 2.2.1.
But still reports failed when Monitor is closed.

14

I can see that Serial Monitor was open during the session that generated the logs you shared. So I think that was the cause of the failure of the Firmware Updater operation.

15

Yes, I can confirm that. I just tried again, and it updated successfully.

I had tried again yesterday already, but then it failed.
The reason was, that the Monitor was (re-) started when I opened the project.
I had then closed the Monitor, but not restarted the IDE again.
Closing the Monitor seems not enough, the IDE needs to be restarted without automatic start of the Monitor.

Thank you for your support.
-jz-
CProgram FilesArduino IDE.zip (10.1 KB)

16

had the same issue. flashed the OTA.ino example to a new Arduino R4 WiFi. it passed through firmware checking but throws an error on ota.begin(). following similar steps @ZinggJM i downgraded the module firmware to 0.2.1 using Tools->Firmware Updater then upgrading back to 0.3.0 works for me. in my case during the update process i noticed the ide gets disconnected from the board and the com port (COM4) changes to a different number (COM5). i was able to catch the event and manually reconnect the ide to the new serial port asap then the update went smoothly. after the update i disconnect/reconnect the usb cable and the serial port returns to its original number (COM4) then the OTA.ino works fine