Forum Replies Created
-
Posts
-
Hi,
Yes, the libraries we provide (that come straight from the Espressif’s SDK) are compiled in a way that occupies most of the RAM. You can try hacking them (with extracting individual objects from .a files to .o files and renaming sections) to move some rarely functions from RAM to the IROM section.
We have also heard people disabling the instruction cache and successfully using another 32K block of RAM after the first 32K, but we have not tried it ourselves and are not aware of the potential performance or stability impact.
Hi,
The ESP8266 is not very reliable and often needs some experimenting to get it to work. It’s also very sensitive to the power supply quality. In our tests it generated random problems when powered from the same USB port as the JTAG debugger and started working more reliably when we connected it to a separate 5V 2A power supply.
As an alternative you can try the CC3200 microcontroller from TI. It is more expensive, but much more reliable.
Hi,
The easiest would be to create a copy of your configuration and configure different debugging settings there. Then you can simply switch between the Debug and Debug_JLink configurations in Visual Studio. You can modify the second configuration to have the same output folder name as the first one – then you will avoid the necessity to build everything twice.
Hi,
Cool. Thanks for the link. It currently looks like just a development build rather than an official release, so we are a bit hesitant to replace the previous RTOS libraries in the toolchain as it may introduce more bugs, especially given that it’s very easy to replace those manually after the installation. Once there is an official release from Espressif, we will gladly include it in our toolchain.
Hi,
Yes, this makes sense. Normally if you are using a newer gdb version, the -thread-select should be automatically replaced with the –thread argument passed to -stack-list-frames, so you’ll get 3 commands. If you disable the “show arguments” and other similar settings in the call stack window, you’ll get only 2 commands that is pretty much the absolute minimum.
Hi,
The toolchain is quite large, but it should normally download/install within minutes. Please try downloading it manually from http://gnutoolchains.com/.
OK, VisualGDB now fully supports the OTA mechanism. It will automatically generate the OTA binaries, program them, configure the bootloader and can even serve the binaries over HTTP to the ESP8266 device. Read this tutorial for more details: http://visualgdb.com/tutorials/esp8266/ota/
Hi,
Then you should be able to configure VisualGDB similarly to the Edison tutorial. Let us know if you encounter any problems.
Hi,
Yes, as long as you have a cross-toolchain for your distro. E.g. see the Intel Edison tutorial: http://visualgdb.com/tutorials/linux/edison/
You can also compile your code directly on the device or order a cross-toolchain from us if you don’t have one.
Hi,
Thanks for letting us know. We actually used the latest SDK from Espressif. Could you post a link to the update you have used so that we could include it in our toolchain as well?
As we mentioned before, there is not a lot of difference from turning on the compression. You can close the Threads and Call Stack windows in Visual Studio, then it will query less things and the overall performance should increase.
You can also try using a cross-toolchain with gdb running on the Windows side. This may improve the performance a bit more.
Hi,
The wizard layout depends on whether you are using a cross-compiler and where do you store the source files. Please provide us more details on the previous choices in the wizard so that we could check why it is disabled.
As an alternative solution you can import the project from folderA, select “Do not import files to Solution Explorer” and then add the root folder manually via Add->Import Folder Recursively. This way the main source directory from the VisualGDB’s point of view will be folderA, but the Solution Explorer contents will look like you have imported the parent folder. Let us know if that works.
Hi,
We are not aware of this problem. Where did you get that linker script? The ones shipped with VisualGDB should not contain any ‘mdata’ sections. Perhaps there is a newer version of the script available?
