I believe that a little explanation is required because the thing is much simpler than it seems.[Local Link Removed for Guests] wrote: [Local Link Removed for Guests]Wed Nov 23, 2022 9:18 amOh! ESP32-S2 use DFU (USB data to GPIO19 & 20)!!![Local Link Removed for Guests] wrote: [Local Link Removed for Guests]Wed Nov 23, 2022 8:50 amRobin,[Local Link Removed for Guests] wrote: [Local Link Removed for Guests]Tue Nov 22, 2022 10:44 pm I could not find any reference to hardware serial TX and RX on the S2, else I would have tried flashing the bin using the Toolkit and a UART... might that be a feasible solution ?
The ESP32-S2 cannot be flashed with the current AnnexToolkit as the flashing procedure is different.
To flash a module, you simply have to use a tool called ESPTOOL.
It is a tool that launches from the command line with associated files, such as boot, partition table, firmware and, optionally, OTA and FFAT partition.
Independently if the module is flashed by a serial port or by a USB emulation made by the chip itself, the tool does not change because, in the end, the tool only writes in a serial port.
Each module has, on the other hand, its specificities in terms of memory address which are also a function of the partition table.
The work done by AnnexToolkit is to automatically create a partition table and launch ESPTOOL with the right options.
This is very practical because everything is done automatically but you can do the same manually with the tools provided by IDF.
The actual toolkit still work for the ESP32 so you can simply put the latest ESP32 .bin inside and continue to use it.
It cannot just be used for the other versions but this do not seems a big issue as there is an alternative method, using the web flasher.
I plan to update the web flasher to handle several releases, including the download of the .bin for offline purposes.
Honestly the number of variants is a big problem for this project as I should publish, for each release, at least 4 variants for the ESP32 (full, noBLE, CAM and epaper) and at least 2 variants (USB / no USB) for the other 3 versions (-C3, -S2, -S3) (without including the associated 4 OTA bin applications that must just be developed once). The total is 10 versions !
If I include the variants NOBLE for the ESP32-S3 and the ESP32-C3 this gives 4 additional versions.
Consider that each version, even if shares the same baseline code, is specific and must be compiled and debugged individually.
I hope that you understand that is becoming a job and not a simple hobby.
The time I spend on the project does not seem to me in phase with its success and therefore I prefer to concentrate on the ESP32 and continue to play alone on the other chip versions without getting involved in a capillary distribution which does not interest anyone.
But again, this requires time and motivation, something that is starting to become more and more rare.