Forum Replies Created
-
Posts
-
Hi,
Good to know it works now. It’s hard to say what could be causing the wifi_set_opmode() bug, can be that a simple rebuild just fixed it. If you encounter it again, feel free to let us know.
Hi,
You can do it by defining a custom pre-debug action (upload a file). Note that this works on Custom and Ultimate editions only.
Hi,
We have added a workaround to the “Command line too long” problem in this build: http://sysprogs.com/files/tmp/VisualGDB-5.1.0.617.msi
Let us know if this works.
Hi,
Thanks for reporting this. We have fixed it in this build: http://sysprogs.com/files/tmp/VisualGDB-5.1.0.613.msi
Thanks for verifying this. We have updated our ESP8266 toolchain to include the fix.
Please try the r5 build from here: http://gnutoolchains.com/esp8266/
Hi,
We have fixed this in the updated nRF5x BSP. Please download the new version via Tools->Embedded Tools Manager.
Hi,
Strange. If you are sure that the output window did not contain any other text or error messages, please feel free to send us the project causing this so that we could fix that. If VisualGDB skips some relevant error messages, we would rather fix it.
Can you share the toolchain test log? Alternatively you can ignore the toolchain testing error, create your project and try to build it. Do you get a meaningful error message that way?
Yes, but that would involve editing the BSP XML files.
We don’t have much documentation on that, so you can either try experimenting with the BSP.XML file in %LOCALAPPDATA%\VisualGDB\EmbeddedBSPs\<ID> or look through our open-source BSP generators: https://github.com/sysprogs/BSPTools/
Hi,
If you are compiling the code on Raspberry Pi, please open VisualGDB Project Properties, go to the IntelliSense Settings page and reload all include directories. If you are using a cross-compiler, simply resynchronize the sysroot from the Build Settings page of VisualGDB Project Properties.
Hi,
Please check the Output window for further details on the error. If this does not help, please share the contents of the Output window here so that we could help you.
Hi,
Yes, please change the function declaration as follows:
static inline void __attribute__((__optimize__(0, "omit-frame-pointer"))) bootloader_util_reset(uint32_t start_addr)
