Forum Replies Created
-
Posts
-
Hi,
Thanks for sharing the details. The Wi-Fi driver is included in the ESP-IDF itself (the ESP32 SDK provided by Espressif, the chip vendor) and does not come from us. Hence please consider creating a topic on the ESP32 forum, or simply downgrade to an ESP-IDF version (and/or toolchain) that works.
Hi,
Thanks for clarifying this. For MSBuild projects you can use the regular Visual Studio property pages to configure various compiler/linker options. The easiest way to transfer them to the Release configuration would be as follows:
- Open VS project properties for the Debug Configuration.
- Locate the relevant setting and copy it to Clipboard.
- Switch the “Configuration” view in the Properties window to “Release”.
- Paste the setting value from the Clipboard.
BTW, you can switch the VS property window to “All Configurations” mode to simultaneously edit properties for both Debug and Release configurations.
Hi,
Sorry, we are not affiliated with Espressif and are only able to help with issues specific to our products. For general ESP32-related inquiries, please consider creating a post on the ESP32 forum. It is maintained by Espressif and they should be able to answer questions regarding the release schedules, plans and compatibility between SDKs.
Hi,
Sorry, looks like there is still some misunderstanding going on. We will try to clarify:
- VisualGDB builds the ESP32 projects using the ESP-IDF (official SDK from Espressif, the ESP32 chip vendor).
- The latest stable release of ESP-IDF is v3.1. It works out-of-the-box, but does not include the http_server example.
- The experimental ESP-IDF 3.2 (the master branch) includes http_server, but is currently broken (if try building it via command-line using the official toolchain from Espressif, you will run into the same problems).
Hope this explains. Let us know if you have further questions.
You should be able to copy the contents of the Output window by pressing Ctrl-A, Ctrl-C. If you want to share a long log, please consider attaching it as a text file instead of inserting it into the post.
Hi,
Sorry, it’s hard to give any advice without seeing the exact error messages. The easiest way to get it to work would be to:
- Install VisualGDB 5.4 Preview 6.
- Completely remove your ESP32 toolchain and install it from scratch via VisualGDB Package Manager.
- Create a new project using the v3.1 checkout that is included in the toolchain.
This is the scenario that we test as a part of our pre-release tests, so it should work out-of-the-box.
Hi,
Sorry, we don’t have any current plans for overriding the Visual Studio popup mechanism to support popups on the ‘(‘ symbol.
It also looks like your trial period has expired. Please feel free to get back to us once you purchase a license and we will be happy to discuss possible workarounds to display the information you would normally see with this popup.
Hi,
Nope, sorry. The CMake projects have a fundamentally different structure from the regular VC++ projects, so the regular VC++ IntelliSense won’t recognize them. Please consider filing a feature request with JetBrains. On our side we will be more than happy to provide a public interface for them to query the include paths and other compiler settings, but we need someone from them to modify Resharper to actually use this interface.
Hi,
Thanks for your suggestion, however this is something to ask from the Resharper developers. We don’t have access to the Resharper’s source code and cannot modify it to work with the Clang IntelliSense.
Hi,
Thanks, looks like VisualGDB was not properly recording some uses of the macros. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.6.2459.msi
Hi,
Thanks for the suggestion. We are actually experimenting with providing CodeLense-like interactive popups for visualizing and navigating relations between functions, classes and other entities. The functionality you are suggesting sounds like a good fit for that new mechanism, so we will likely add it there.
Hi,
It shouldn’t cause any extra problems, but it will trigger the same issue is you use the pre-packaged toolchain (as the problem is due to missing packages in the toolchain and not in VisualGDB). If you use a different toolchain (e.g. build one from scratch) and it works, you can easily use it with VisualGDB as well by copying the toolchain.xml file and esp32-bsp folder from our toolchain to it and importing it into VisualGDB.
Hi,
OK, thanks for clarifying this. The exact steps depend on your project type. Are you using MSBuild, GNU Make, QMake or CMake?
Hi,
We have just rested everything. The ESP-IDF v3.1 works as expected. Trying out the master branch indeed results in errors.
It looks like a known bug of the latest ESP-IDF and Espressif might be working on resolving it. As one of the comments on the bug thread mentions, you might be able to get it to work by rebuilding the toolchain from scratch (let us know if you need help getting VisualGDB to recognize the rebuilt toolchain), but if you don’t want to spend time diagnosing incompatibility between different components, we would simply advise waiting until Espressif fixes this (we will update our toolchain accordingly once they release a stable package compatible with the master branch).
Hi,
No worries. Sometimes the names in the SDKs can be indeed confusing and we are happy to point you to the right direction.
Hi,
This message itself does not indicate any error, it simply means that the target has stopped at a breakpoint. Please let us know what exactly you are doing, what are you observing/expecting and share the ENTIRE output of the OpenOCD window and the GDB Session window (after you switch it to the “All GDB Interaction” mode).
