Forum Replies Created
-
Posts
-
Hi,
If the problem only occurs on your board, but not on the reference board, it is likely caused by wiring issues (e.g. cross-talk, wrong reset connection, etc.). Generally if the problem cannot be reliably reproduced on any of the boards mentioned in our tutorials, we won’t be able to offer much help as a part of our regular product support. That said, feel free to attach the error log you are getting from OpenOCD. If this is something we have seen before, we might be able to at least suggest the direction for further investigation.
Hi,
Please try changing the following option:
Tools->Options->Text Editor->C/C++ (VisualGDB) -> Formatting -> Newline Insertion -> New functions.
Hi,
Sorry, we only provide support for our products on this forum. For general Qt-related questions please consider creating a thread at the Qt forum.
Hi,
Please try installing the experimental J-Link package from http://sysprogs.com/files/tmp/segger-dmsp-5.1preview1.vgdbxedp.
You can install it into VisualGDB via Tools->VisualGDB->Manage VisualGDB Packages.
Hi,
Yes, unless the pre-release testing reveals major unsolvable regressions caused by the new feature (highly unlikely in this case), all features added to daily builds will be included in the next upcoming release.
Hi,
It looks like some include directories from the CooCox project were not imported properly.
The easiest way to resolve this is to find the location of the missing files when compiling with CooCox. Most of the GCC-based projects use .dep files for dependency tracking – those files (generated by gcc) contain full paths of all header files included by a source file. Please try building the CooCox project and then search its build directory for .dep (or .d) files containing the names of the missing headers (e.g. hw_cmsis_core.h). If none are found, try searching in all files. Once you locate the directory of the missing files, please add them to your imported project (either via VisualGDB Project Properties or using header discovery).
If you run into further problems, feel free to post the details here and we will help you resolve them.
Hi,
No problem. We have just replied to your new inquiry. Let us know if you have any further questions.
Hi,
We have quickly rechecked the “blinking LED” project on the DISCO_V407VG target, but could not reproduce the crash. The linker scripts generally come directly from the mbed distro and are outside our control, so we are not able to offer any more backward compatibility than mbed itself does, sorry.
Please try checking whether a basic “blinking LED” project works with your device. If not, this could be a compatibility issue between the toolchain and the mbed BSP, so installing the latest ARM toolchain might fix this.
If the “Blinking LED” project works, please try comparing the initialization code of both projects to see if any of your code could be relying on the old linker script.
Another way to pinpoint this would be to try building your project with mbed-cli and then debugging it via Quick Debug (or by replacing the ELF file and not rebuilding the VisualGDB project). If the project built with mbed-cli works and the one built with VisualGDB doesn’t, this is likely our bug and we should be able to fix it if you could let us know more details (e.g. map files for both projects).
Hi,
No problem, please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.3.2348.msi
We have added a new command-line option for filtering tests: /testregex:<regex>.
If the filtering is not working as you expected, please set the VISUALGDB_VERBOSE_OUTPUT environment variable to 1. This will force VisualGDB to show the full test names it matches against the regex.
Hi,
Thanks for reporting this, looks like our bug. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.3.2348.msi
Hi,
Good to know it works. If you encounter any further problems, please do not hesitate to contact us again.
Hi,
The new advanced ESP-IDF project subsystem was added to VisualGDB 5.4 Preview. Most likely you have installed v5.3 that doesn’t have this feature yet (and won’t install the latest toolchain). Please ensure you install the v5.4 preview version. Also if the old toolchain cannot be removed from VisualGDB, please try closing all Visual Studio instances and simply deleting the toolchain directory from Windows Explorer.
Hi,
According to our records, your inquiry was answered on 06/20/2018 8:18 pm in less than 8 hours from the time we received it.
Please double-check your spam folder and let us know if you would like us to resend the reply.
Hi,
This might be caused by changes to some mbed components. Please try opening VisualGDB Project Properties on the first page and then either change the MCU forth and back, or click “Regenerate MCU-specific files”. This should automatically update all project properties and remove any deprecated settings.
Hi,
The sample projects like “LwIP_HTTP_Server_Netconn_RTOS” come from the ST examples, so if the original example is written in C, VisualGDB will not automatically change it to C++, as simply renaming files may introduce build errors.
There are quite a few things to watch for when converting Plain C code to C++ (the most notorious one is extern “C”), however as this is a generic C/C++ development question and is not specific to VisualGDB, we cannot provide step-by-step instructions for converting each sample. That said, such a conversion is a very commonly performed task, so searching resources like StackOverflow for the errors you encounter will most likely give you detailed answers from other users that performed a similar conversion.
