Search results for:

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.

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.

It seems like this might be a hardware issue with certain boards. Could you please indicate which boards work well or which ones don't, so that new users can avoid encountering this problem?

Thanks

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.

I've been looking into it, and you're referring to using gpio_config to configure the PIN correctly according to ESP-IDF, right?

Currently, gpio_set_level() is being used, but without prior configuration.

Is this what's causing the problems?

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,

And now I've tried connecting via Telnet, and so far, it's working fine.

I've now activated Wi-Fi and generated the firmware.

I've uploaded it to the board, and so far, it seems to be working fine. I've scanned the networks and successfully connected.

I'm using the following S3 board,ESP32-S3 N8R2, for testing, which has two USB connections: one that functions as a serial port like in the ESP32, and the other as USB-CDC.

https://es.aliexpress.com/item/1005004617322170.html

Now, I've started making some changes:

1. First, I modified it to download ESP-IDF 4.4.8, which will be the last in the 4.x branch.
   
2. I've added the parameters to enable the build for ESP32S3.
   
3. The first basic ESP32S3 test compiles without errors. Now, I'm moving on to Wi-Fi.
   
   

As soon as I have something useful for the community, I'll make a pull request.

I've posted in this forum, but it's not the right one.

Hi, I think there is a small misunderstanding. I've been preparing the firmware for ESP32 S3, and you asked me for the one for ESP32 C3. They are different CPUs from Espressif.

Anyway, I'll prepare the firmware for C3 later with my build system to see if it works well. And I'll share it on the forum.

And now I've tried connecting via Telnet, and so far, it's working fine.

I've now activated Wi-Fi and generated the firmware.

I've uploaded it to the board, and so far, it seems to be working fine. I've scanned the networks and successfully connected.

I'm using the following S3 board,ESP32-S3 N8R2, for testing, which has two USB connections: one that functions as a serial port like in the ESP32, and the other as USB-CDC.

https://es.aliexpress.com/item/1005004617322170.html

Now, I've started making some changes:

1. First, I modified it to download ESP-IDF 4.4.8, which will be the last in the 4.x branch.
   
2. I've added the parameters to enable the build for ESP32S3.
   
3. The first basic ESP32S3 test compiles without errors. Now, I'm moving on to Wi-Fi.
   
   

As soon as I have something useful for the community, I'll make a pull request.

I've just started getting back into the project. I already have the environment downloaded from GitHub and the ESP-IDF 4. Furthermore, I've tested both ESP32C3 and ESP32, and both generate the firmware without errors. I haven't tried uploading the firmware to the boards yet.

Hello everyone. I've been disconnected for the past three months. I wanted to make progress and help out, but I couldn't focus until the holidays.

I also follow the development. It's fantastic that there's finally a new line for the new boards and the new IDF. Honestly, I haven't had time yet, but my plan is to try the new system and focus on ESP32. I want to help with what I would have done for the ESP32-S3, which is still not implemented.

I hope to take a day off work soon and push the project forward.

Hello, sounds perfect, thank you very much for the work. I see that we can give it a boost.

Right now I am tied up with other projects, but I will make time to contribute.

We are betting on version 5.x directly, which I think is excellent. I worked on 4.x because it wasn't difficult. I will retrieve all the notes from 5.x to remember.

We'll keep notifying about the tests and progress.

Yes, understood.

So what I'm going to do is clone the latest repository of Espruino 2v21. And upon this, I'll make the current changes with three conditional definitions, ESP32-IDF3, ESP32-IDF4, and ESP32-C3-IDF4

and I'll upload the changes to my branch... and this way it can be integrated into the original repository.

Hello Mark, I don't mean being able to build both versions on the same computer.

What I mean is that version 3.3.6 is very stable, with all the hardware adaptation and testing completed. As for versions 4.x and 5.x, the functionality of the hardware SDK is different (SPI, LEDC, DMA, FreeRTOS, ADC...) and it will take us some time to get it ready.

If, while we prepare versions 4.x and 5.x, version 3.3.6 remains valid through conditional defines, we can generate binaries for all three versions at any time with the latest versions of the source files.

The idea of transforming the current makefile system to the IDF system on the fly, is a good one.
For me i find the current system confusing ,to carry out this task myself. Especially since it's shared across many different hardware configurations.

On the other hand, performing a full build with IDF is easy and fast. I don't see any drawbacks; you just need to have the entire SDK downloaded, but IDF takes care of everything.

The source files that need to be changed from the current Espruino, I've identified them very well, and there are very few things to modify. The main issue lies with the BUILD system; regarding the source files.

I also find it easy to maintain dual compatibility with 3.3.6 and 4.4.7 through defines in the source files. Although I've noticed a significant improvement in stability with the 4.x series compared to the 3.x series.