Firmware upload failed

[dac2020]

What can I do when I cannot even upload the minimal firmware to a device?
I get upload failed, not enough space which explains what the problem is but what can I do about it?

I thought the minimal build would fit on pretty much anything?
In this case, it's the ESP32R4 V2, RocketController relay.

Is there some way of clearing some space? Are logs kept on the device perhaps that I could delete?

[sfromis]

If you try uploading minimal, you are doing something very wrong. That is not relevant for ESP32. What exact upgrade are you trying to do, and exactly how?

[sfromis]

I asked for exact details, not a general abstract description of what you want to do. Details like name/size of the binary, how specifically you try to upload it, and what log messages you get when you try to do it.

[dac2020]

Wow, you don't have to scold me, I'm not a child playing games with you.
You know I'm just learning here and you also know I've been making progress so please be a little more patient.

I didn't know about the settings remaining. I would have thought and did that when you write new firmware, it overwrites everything.

I do have the template, the device is working fine. There is nothing wrong with it.

No general abstract, I also explained why. I wanted to write a basic firmware to it to see if those rules would change.
I removed them using the command suggested but as mentioned, continued to see three rules so wondered why.

As I said, I think the file was generated when I used the compiler.
The file is called tasmota-minimal.bin and is 376016 in size. I might have renamed it to minimal, I'm not sure.
I could run the compiler again and see if it generates it again.

As I said I used the firmware update page so not sure what else to add on that.

I had not looked at the log so I'll do it now. Web log is set to 3.

00:13:19.591 HTP: Firmware Upgrade
00:13:25.729 UPP: Multicast disabled
00:13:25.968 CFG: Saved, Count 219, Bytes 4096
00:13:25.970 UPL: File tasmota-minimal.bin
00:13:25.994 UPL: freespace=1900544 filesize=376016
00:13:25.000 UPL: File type 1
00:13:27.742 UPL: Progress 100 KB
00:13:29.464 UPL: Progress 200 KB
00:13:31.001 UPL: Progress 300 KB
00:13:32.098 UPP: Multicast (re)joined
00:13:32.118 HTP: Upload done
00:13:38.248 HTP: Main Menu

00:13:43.995 HTP: Consoles
00:13:45.973 HTP: Console

[sfromis]

Well, once more, using tasmota-minimal.bin is not relevant for ESP32. Do not do that.

I was assuming (hoping) that you only started to try with tasmota-minimal.bin after having problems uploading the binary you want to upgrade to, and that problem was what I was asking about. If you had not gotten to that state, it was because you should never have used tasmota-minimal.bin for ESP32.

If that tasmota-minimal.bin was generated when trying to build for ESP32, you were not successful in building for ESP32 instead of ESP8266. All standard build binary names for ESP32 start with tasmota32, when it is only tasmota, it is for ESP8266.

[dac2020]

I have a thousand notes since starting this and I do recall someone mentioning there is a difference between the chips but I didn't remember that the firmware files are specific, like openwrt for example.

So this seems to be where I'm at.
I have an ESP32 build which means I have to rename that so I don't forget and I need to now generate a new build for the ESP8266.

[barbudor]

An ESP32 build should always start by "tasmota32-someting.bin"
For more specifics with ESP32 variants, ESP32-C3 should be named tasmota32c3-something.bin, ESP32-S3 would be tasmota32s2-something.bin etc ...
And there is no .gz for ESP32 and its variants

ESP32 variants are very different one from the others. Some are even using a totally different CPU core. So each should be considered as a totally different processor

tasmota-something.bin(.gz) is reserved of ESP8266/ESP8285 (the later being en ESP8266 with a build-in 1MB flash)