Most recent activity
-
Hello, the version you used is the initial one from about a year ago. Now, the latest version of Espruino for the ESP32-S3 is already integrated into the original repository.
Please check the README file to see how to generate the firmware and use this version instead of the one you used. Everything should work fine.
-
Yes, I think at the moment the use of #ifdefs is appropriate and balanced due to the different hardware boards.
But with 'sdkconfig' files, is something I believe we should clean up and clarify a bit more. It should be clear which options are important for Espruino to function correctly. The rest of the options can remain as defaults since they don't impact proper functionality.
-
-
I see that more or less we are all on the same path.
However, it's true that for the rest of the community, it's important to have a version of ESP32 IDF 3.x with the latest version of Espruino available. This way, specific apps can continue to progress without new errors.
I believe that once we have a fairly functional ESP32XX with ESP-IDF 4.4.8, we can start cleaning up and trying to rebuild the build process in a more modular and simpler way.
But we still have many things to test. I’m focused on the ESP32S3, and I’ve put the ESP32 aside for now. I don’t use the C3. We need users for each of the three versions to compare the results.
-
Hello @Gordon,
I’ve prepared the firmware for the S3 and C3 and uploaded it to this forum. @user158605 requested it because they wanted to test it.I’ve only tested the S3 myself, and it seems to work fine at first glance. Let's see if another user can give us feedback on the C3 firmware, and if not, I'll test it myself when I have the chance.
-
Hello,
that's a lot of information, and let's wait to hear what the others have to say about it. As for me, I wasn't aware of --sdkconfig-defaults. It seems like a good idea.
Currently, the important configurations for Espruino in sdkconfig are not well managed with this type of file. We have three files, and it's not easy to see what's important in them.
The --sdkconfig-defaults could make things easier.
Not to mention that with ESP-IDF v5.x and the new P4 chip (which I'm waiting for), more sdkconfig files will be generated.
-
-
Hi @SimonGAndrews , to be honest, I haven't touched this part for the S3. It compiled directly for me. I'll take a look at what you're mentioning to see if I can find anything.
-
Hello @user158605 , I'm uploading the two firmware of the latest version of Espruino, both with Bluetooth, Wi-Fi, and Telnet. Let's see if you can test them and if they work correctly for you.
Best regards,
Hello, it seems like this might be a configuration issue. I'm not sure if it could be specific to your board.
I checked the board you are using, and I noticed that it has connectors for the RX0 and TX0 pins. You could connect a USB-to-serial chip directly there in case you don’t find another solution.
Also, try using a different version of the IDE, for example, an offline version, as it might be an initialization issue with the IDE protocol that is causing miscommunication. You can also test with any other serial terminal program.