Forum Replies Created
-
Posts
-
Hi,
The recent version of VisualGDB would use the clang-format engine to format the code (including the comments). Clang-format could be tuned in numerous of ways by editing the .clang-format files (VisualGDB provides a graphical editor for them). Please see this page for an explanation how clang-format is integrated into VisualGDB and this page for an overview of clang-format options.
No problem. If the project has no custom steps, the problem is likely happening on the MSBuild level. Please try enabling diagnostic MSBuild logging as shown here, reproduce the problem and share the diagnostic build log from a clean operation that triggered the error.
Thanks for the screenshot. This is the new STM32CubeMX-based project that is split into the STM32Cube-controlled part (under the blue STM32CubeMX icon) and the VisualGDB-controlled part (outside the STM32CubeMX part).
It looks like you are trying to add files to the STM32CubeMX-controlled part that is not editable because it will be overwritten by STM32CubeMX once the project is regenerated.
Please try adding files outside the STM32CubeMX Files node. See this tutorial for a detailed introduction in the new STM32CubeMX-based workflow.
No problem, we will clarify. You can use any version that was released within the “free update” year for free. In your example, you will be able to use the “VisualGDB-5.5.2.2222.msi” version (released just before the year was up) forever.
That said, VisualGDB always shows the update link to the latest available version, not the latest version compatible with the current license key. If you try activating that version with a key that is not compatible (i.e. had the “free update” year expired before the release date), it will direct you to the https://sysprogs.com/splm/mykey page where you can either renew your key, or download the latest version that works with it.
Update: We usually do not enforce expiry limits on early preview builds (e.g. VisualGDB 5.5 Preview X). I.e. they will often successfully activate even if the renewal period was already expired at the time of release. Once we switch from a Preview build to a stable build (5.5RCx or 5.5Ry), we start enforcing the expiry limits again, so updating from Preview X to a stable build may require renewing the license.
Hope this explains. Let us know if you have any further questions.
Hi,
Sorry, this looks like an issue with a specific board, or specific computer. Please try different a different computer or a different CYUSB3KIT-003 board.
Hi,
This should normally work. If not, please try attaching the screenshots showing what exactly you are trying to do and we will try to point out the possible cause of the problem.
Looks like you are setting a breakpoint in an inlined function that has multiple physical locations (one per each inlined instance). Setting a breakpoint there involves one physical breakpoint per each inlined instance, and based on the log, there are more than 10 of them (see line with the [ 3544 ms] tag). Running out of hardware breakpoints is completely expected in this scenario.
Hi,
Please try creating a gdb log and searching for the -break-insert commands (or any other command containing the “break” word). It will show the exact breakpoints set by VisualGDB.
If you can find a specific breakpoint that you believe should not be there, please let us know and we will help you understand what brings it in.
Please note that we are not able to review specific projects or code snippets for errors. Our support is limited to issues when VisualGDB itself is not working as expected. It does not cover the issues where the code itself is not working, or the target device is not behaving as expected. Having different clock dividers or different optimization levels will affect function timing and can trigger bugs in the code. This is to be expected and VisualGDB will not be able to fix those bugs automatically.
Please note the we only provide support in English.
We also have to prioritize the reported issues by the ease of reproducing/fixing it and the amount of affected users. Given the amount of resources already spent on the thread we will not be able to investigate it any further, or provide any further replies unless the issue starts affecting other users. Sorry.
Please note that VisualGDB is a productivity extension to Visual Studio. It makes building and debugging projects easier, however it does not replace an actual software engineer. It cannot automatically write code based on a verbal description, or fix the code that does not work as expected.
Fixing code that does not work as expected requires an engineer to review the code, its context, specific MCU datasheet and the related board design, and likely to debug it on the hardware. This would require non-trivial time and would cost much more than we charge per license, hence we are not able to provide it as a part of our product support. If you would like an engineer to review your project and help you resolve issues with it, please consider hiring a 3rd-party consultant.
We do our best to avoid confusion. We show the expiration date in the Help->About VisualGDB window and if VisualGDB fails to activate due to an old key, it directs to the MyKey page that lists renewal/upgrade options and also allows downloading the older VisualGDB versions.
Edit: the poster below pointed out the confusion here, so we will try to clarify. Any version released while the update period was active should be able to activate. Preview builds of VisualGDB may activate even beyond that, however updating to the next stable release will require active renewal period at the time of that release.
No problem. Also please note that as you have used the 50% renewal discount, your previous support/update expiration date has been extended by 1 year, placing it at 49 days from now. If this was not intended, you can instead use the 10% late renewal discount that will place it to 1 year from now (please contact our sales if you need a link to pay the difference). Or you could do another 50% renewal any time (before or after expiration) to add another year to the current expiration date.
Thank you for your feedback. As it takes continuous effort on our side to keep VisualGDB up-to-date, and test it with the new devices, tools and frameworks, we have to limit free updates to 1 year since the license purchase, and ask for license renewal afterwards.
We try to be very explicit about our renewal policy. Our buy page mentions the 1-year period and the renewal page provides a link to the latest version that can run with your key if you do not want to renew the license. Due to the way the installer framework works, it can only verify the license key after VisualGDB has been installed and you load it in Visual Studio.
That said, you can always uninstall the new VisualGDB version and install back the old one without losing any settings.
No problem, we have updated VisualGDB to remember the custom hardware register definitions selected for mbed projects. Please try this build: VisualGDB-5.5.101.3866.msi
Based on what you have described, it looks like a specific code snippet is not working as expected. It looks like an issue with a specific piece of code, rather than a VisualGDB bug. Also, unfortunately, you have not provided sufficient context for us to understand what is going on.
If the same project behaves differently when built with the Keil IDE vs. VisualGDB, please consider following this tutorial to track down the changes.
If it doesn’t help and you believe VisualGDB is not working as expected, please provide us the steps we could follow on our side to reproduce the problem per our problem reporting guidelines and we will try to investigate it further.
