-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request for ESP S3 chip #106
Comments
Hello @Kuba1606 , Thank you for your kind words. The problem with adding new chips is not the compilation but rather the testing on my part. I don't have all the chips and variations, so it will be difficult. I have attached the firmware for you to try. You can test whether you can flash it and check if it works in general. Then I can add the S3 to the next release. Kind Regards, |
同样希望添加esp32s3开发板支持,刚刚开始玩硬件开发,您的代码我还处于看不懂的阶段,只能希望您来开发了,感谢您的贡献 |
您解决了在esp32s3上的使用此程序的问题了吗,如果解决可否给我提供一下解决方案呢 |
Hi @dchristl , First of all, thank you for your work on this project. I have a S3 version, this one: https://www.aliexpress.com/item/1005006266375800.html I wrote the bin file you shared in your previous comment, but I didn't succeed in seeing the network the board should have created. I tried twice. In all cases, there were no errors shown in the console. I also tried the ESP Flash Tool, with no success. ==update: March, 15 == I forgot to mention I am starting to IoT, so most of what I did so far was to see lots of videos. Based on Platform IO, I added S3 as a new task. To do that I edited platformio.ini and added to the end of the file the following lines: [env:esp32-s3] The first compilation failed and I found the solution in a comment from the martin-ger project. It is at: martin-ger/esp32_nat_router#48 I successfully built and uploaded it. The wifi network "ESP32_NAT_Router" showed up and I connected to it, but I wasn't able to open the IP address. I will try again later. As I mentioned, I am new to this IoT word, and I don't know if it is normal, but touching the esp32 soc I noticed that it was hot, I mean, nothing that requires removing the thumb fast, but is it common to be hot in that way? Thanks and Regards! |
Hello @AlexNOliveira , the issue has become a bit unclear. Your development attempts on the S3 board look good; my implementation is also working almost exactly the same way, except more settings are changed. This is pushed in the dev branch, so you can simply compile this. Therefore, I don't quite understand why your self-compiled code works but the uploaded binary does not. How did you flash it? Did you use the full version or the individual bins (firmware, bootloader, partitions)? Does anyone other tried the firmware, too? If I have more imput I can add the chip. |
Hi @dchristl , Apologies for my previous comments. Let me try to explain differently. All my tests were done based on downloading the repo via a zip file, from the master. My first attempt do upload a bin file to S3 was based on the zip file you shared in your comments to Kudo1606. Since it was (I assume in that way) a fresh install, I tried to upload the full file (esp32-s3-nat_extended_full.bin). I tried to upload in 3 different ways, all following the readme file. The first time, I followed the First Install process: esptool.py write_flash 0x0 esp32nat_extended_full_vX.X.X.bin In all 3 cases above, no issues with uploading, I mean, there were no error messages after the upload processes. It is important to highlight that I have no background in ESP32 nor in the development tools required to work with it. I am someone who just started to study it and try to solve the issues by google them. :-) All these attempts resulted in not having the WiFi SSID "ESP32_NAT_Router" available for me, even removing and connecting the USB cable to power the S3. I decided to open into PlatformIO and try to build by myself. I researched on the internet and found out that I need to add a "task" to platformio.ini to build to S3. So I added the following code: [env:esp32-s3] After I added this code, I clicked on the build button on the footer of the VS Code. A few moments after the build had started, an error showed up. After a search for the error message, I found the solution at martin-ger/esp32_nat_router#48. The solution was to change a few configurations for the S3. To do so, I run the following command: Building the new task without doing the changes resulted in the following error: Changing the configuration per the mentioned URL, made it possible to build with no issues. After that, I choose to upload using PlatformIO. After following these steps, I was able to connect to the WiFi SSID "ESP32_NAT_Router". I was able to open the configuration page. It worked this time because I just observed that on my Android phone, it was necessary to agree to keep connected to the unsecured network, which I didn't notice the last time I tried to connect. |
Hello developer, I use esp32s3 n16r8 development board flash size 16M after brushing into the firmware or can not identify the wireless route, the source code needs to modify where to adapt? |
Can you post an output of the serial connection after flash? The attached bin should work for all S3 models |
this works for me! |
sptool.py v4.6.2 Leaving... |
Great, I will add it to the official releases when I have more time |
Hello, what is the possibility that you can compile a version for the esp32c3 super mini? The current version for the C3 has not worked for me, I thank you very much, excellent work, greetings. |
Hello @reyxv16 , If I understand the documentation correctly, the super mini version is also just a normal C3 on a different board. So the firmware should actually work (what does the og say when flashing, what does the serial console say). Unfortunately I can't support all chips in case it doesn't work. |
[974/976] Linking CXX executable esp32_nat_router_extended.elf |
I have a ESP32-S3 supermini and use Linux. I tried the version at martin-ger. It seemed to flash ok but constantly rebooted (watched output in Arduino IDE Serial Monitor). I rebuilt the version at martin-ger and it flashed but constantly rebooted. So I found the version here compiled for a S3. I erased the flash and then flashed the full version. It seemed to flash ok but the serial monitor shows it constantly outputting "invalid header 0xffffffff". |
I went back to the martin-ger code, ran menuconfig and changed the flash from 16MB to 4MB, recompiled and flashed. And now the martin-ger version works. I suspect there is the same problem here. The ESP32-S3 supermini only has 4MB flash. |
Hello, I am impressed with your work. This is exactly what I was looking for. Unfortunately, my module is based on the ESP32 S3 model (SpeedStudio Xiao S3), so your bin files for other models do not work. I'm not that advanced of a user to be able to compile my bin files for S3. Could you also compile your work for this chip? Thank you greetings.
The text was updated successfully, but these errors were encountered: