Search found 221 matches

by ESP_bignacio
Mon Nov 20, 2023 10:43 am
Forum: IDEs for ESP-IDF
Topic: Unable to start debugging. Unexpected GDB output from command "- interpreter-exec console "target remote:3333""
Replies: 14
Views: 168314

Re: Unable to start debugging. Unexpected GDB output from command "- interpreter-exec console "target remote:3333""

Have you followed our setup tutorial here: https://github.com/espressif/vscode-esp-idf-extension/blob/master/docs/tutorial/install.md And our debug tutorial: https://github.com/espressif/vscode-esp-idf-extension/blob/master/docs/tutorial/debugging.md If you have any problems share the troubleshootin...
by ESP_bignacio
Mon Nov 20, 2023 10:41 am
Forum: IDEs for ESP-IDF
Topic: Cannot install esp-idf V5.1.2 on VSCode
Replies: 1
Views: 19704

Re: Cannot install esp-idf V5.1.2 on VSCode

Have you followed our setup tutorial here: https://github.com/espressif/vscode-esp-idf-extension/blob/master/docs/tutorial/install.md If you have any problems share the troubleshooting information with us to understand better the problem: https://github.com/espressif/vscode-esp-idf-extension/blob/ma...
by ESP_bignacio
Wed Nov 01, 2023 11:19 am
Forum: IDEs for ESP-IDF
Topic: esp-idf + esp-matter + vsc not even compiling on examples
Replies: 5
Views: 21480

Re: esp-idf + esp-matter + vsc not even compiling on examples

Apologies for the bad experience with the vscode extension. Can you help us make it better for you ? First, check the Troubleshooting section of the vscode extension. This information help us to understand your setup. When you run the Install ESP-IDF Matter command, are you doing a full install or a...
by ESP_bignacio
Wed Oct 11, 2023 12:47 pm
Forum: IDEs for ESP-IDF
Topic: Can I display how long the build task takes in vscode extension?
Replies: 2
Views: 10425

Re: Can I display how long the build task takes in vscode extension?

Maybe you can try to use some additional option of ninja-build. In your <project-dir>/.vscode/settings.json add:

"idf.ninjaArgs": ["-d stats"]
by ESP_bignacio
Wed Oct 11, 2023 8:27 am
Forum: IDEs for ESP-IDF
Topic: Using extra components esp-protocols with vscode extension
Replies: 1
Views: 7517

Re: Using extra components esp-protocols with vscode extension

You can try to use the ESP-IDF: Show Component Registry command to open the IDF Component manager website inside vscode. Find the asp-protocols components you want like esp_modem. Click the install button. this will update your src/main/idf_component.yml file. Use the component in your project. When...
by ESP_bignacio
Tue Jul 04, 2023 5:14 am
Forum: IDEs for ESP-IDF
Topic: ESP IDF VSCode Extension Release v1.6.4
Replies: 0
Views: 3906

ESP IDF VSCode Extension Release v1.6.4

v1.6.4 ### Features and enhancements Add IDF Target to project configuration editor Add ESP-IDF Rainmaker download and build support Add IDF Monitor timestamps settings Add gitee mirrors for git cloning when using Espressif Download Server ### Bug Fixes Fix resolve task manager Increase input width...
by ESP_bignacio
Tue Apr 25, 2023 6:13 am
Forum: IDEs for ESP-IDF
Topic: Configuring the TWDT
Replies: 2
Views: 2250

Re: Configuring the TWDT

Take a look at the document in the [urlhttps://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/system/wdts.html#configuration]Interrupt watchdog documentation[/url] And find the Interrupt watchdog in the SDK Configuration editor (using the plugin UI) or in the terminal using idf.py...
by ESP_bignacio
Tue Apr 25, 2023 6:03 am
Forum: IDEs for ESP-IDF
Topic: esp-32 x enc28j60 tx_ready_sem expired
Replies: 1
Views: 1579

Re: esp-32 x enc28j60 tx_ready_sem expired

This is the wrong forum for this post.

You want to post in the ESP-IDF forum instead.
by ESP_bignacio
Tue Apr 25, 2023 6:02 am
Forum: IDEs for ESP-IDF
Topic: ESP32C3 VS Code Extension debugger not working
Replies: 1
Views: 1644

Re: ESP32C3 VS Code Extension debugger not working

Based on your output it seems you are having some timeout issues.

You can increase the timeout of the debug adapter with "tmoScaleFactor": 2, in your launch.json where 2 is the timeout scale factor (a multiplier) as described in debugging documentation