Re: ESP32-S3 (Beta2) MARLIN_9_1B on ESP32-S3-Addax-1 V1.0 Specs & Datasheet
Posted: Wed Jun 16, 2021 11:40 am
Which ones are you referring to?Soon there will be tiny low power SoCs that may replace many MCUs unless prices drop
ESP32 Official Forum
https://www.esp32.com/
Which ones are you referring to?Soon there will be tiny low power SoCs that may replace many MCUs unless prices drop
If you have working benchmarking code you want tested, I can do the test. I have wrover modules with ESP32 V3 chip, and S3 beta 3 modules.
You can find some Benchmark Code here:viewtopic.php?f=14&t=800&start=20#p73849.Vader_Mester wrote: ↑Tue Jul 06, 2021 12:32 pmIf you have working benchmarking code you want tested, I can do the test. I have wrover modules with ESP32 V3 chip, and S3 beta 3 modules.
OK.squonk11 wrote: ↑Tue Jul 06, 2021 10:15 pmYou can find some Benchmark Code here:viewtopic.php?f=14&t=800&start=20#p73849.Vader_Mester wrote: ↑Tue Jul 06, 2021 12:32 pmIf you have working benchmarking code you want tested, I can do the test. I have wrover modules with ESP32 V3 chip, and S3 beta 3 modules.
But it is mainly floatingpoint related, which is probably not the most important topic for this type of uC. Nevertheless it will give an indication. It would kind if you could run this test on both ESP32 versions.
Maybe I can provide you a larger code later in order to avoid having the whole program running in cache memory.
Rudi: I can not PM you, so if you would be so kind, to edit the first post with the following information:
Code: Select all
git reset --hard 3b60c2e131bc382f40d78095bde8af9e3518a6d3
Code: Select all
git reset --soft 3b60c2e131bc382f40d78095bde8af9e3518a6d3
Code: Select all
git checkout 3b60c2e131bc382f40d78095bde8af9e3518a6d3
git submodule update --init --recursive
Code: Select all
"win32": {
"sha256": "5711eb407ffe44adddbd1281b6b575a5645e7193ca78faefa27dc5bc5b662bec",
"size": 191266312,
"url": "https://github.com/espressif/crosstool-NG/releases/download/esp-2021r1/riscv32-esp-elf-gcc8_4_0-esp-2021r1-win32.zip"
},
"win64": {
"sha256": "be3c9ec364bd8e92924f922a4aec73136824f16e912e6a0b5cf5b30512f0ab96",
"size": 192799980,
"url": "https://github.com/espressif/crosstool-NG/releases/download/esp-2021r1/riscv32-esp-elf-gcc8_4_0-esp-2021r1-win64.zip"
}
Code: Select all
# riscv32-esp-elf-gcc8_4_0-esp-2021r1-patch1-win64.zip: 197027915 bytes
8e8e3e385833960762e9f007bc3f7785daf282deb0c8a4dfdd6340b2cce556b0 *riscv32-esp-elf-gcc8_4_0-esp-2021r1-patch1-win64.zip
Code: Select all
"win64": {
"sha256": "8e8e3e385833960762e9f007bc3f7785daf282deb0c8a4dfdd6340b2cce556b0",
"size": 197027915,
"url": "https://github.com/espressif/crosstool-NG/releases/download/esp-2021r1/riscv32-esp-elf-gcc8_4_0-esp-2021r1-patch1-win64.zip"
}
Code: Select all
NOTE: On my side it worked with the newest compile tool, but if you experience issues, you can revert back to the old one
Yes, that is exacly what I am also interested in. This micro probalbly is mostly used for communication purposes (WiFi, BT) and in this case memory reads and writes to the various memories and fetching code from flash etc. are more relevant that floatingpoint operations. In my use case I have an application running a webserver with websocket communication. The app today has a binary size of approx. 1,5MBytes - so most of the code will be executed from ext. flash and not from cache or iram. Since my app currently is too slow I am looking forward to test the ESP32-S3.Vader_Mester wrote: ↑Wed Jul 07, 2021 6:35 amOK.squonk11 wrote: ↑Tue Jul 06, 2021 10:15 pmYou can find some Benchmark Code here:viewtopic.php?f=14&t=800&start=20#p73849.Vader_Mester wrote: ↑Tue Jul 06, 2021 12:32 pm
If you have working benchmarking code you want tested, I can do the test. I have wrover modules with ESP32 V3 chip, and S3 beta 3 modules.
But it is mainly floatingpoint related, which is probably not the most important topic for this type of uC. Nevertheless it will give an indication. It would kind if you could run this test on both ESP32 versions.
Maybe I can provide you a larger code later in order to avoid having the whole program running in cache memory.
What interests me is the memory usage. I will try to write benchmarking code to test memory read and write speed both for internal RAM and external SPI-RAM as well. The S3 has an improved MMU.
Also, when it will be available, I want to test code execution speed from SPI-RAM.