Forum Replies Created
-
Posts
-
Works well (once I understood how to create a reusable action list!) – Thanks a lot
Hopefully CMake is here to stay since this is our 3rd project migration!
As of now the problem has gone away (both home and work locations). I will apply your suggestions if the problem happens again. Thanks for the support.
I think I have useful information for you:
I went from the office to home, did a screenshot of the menu (attached) and then I clicked on the menu and realized that it was working!
A little bit later, I tried again and it was NOT working. Here is the punch line: at home it always works on the external screen but not always on the laptop screen. At work it works on neither one. It looks that with my setup at work (same laptop, different external screen), it is trying to show the property page on a non-existing display.
I also tried to uninstall VisualGDB / Reboot / Reinstall
That did not help and now I don’t have the properties on VS2010 (but project compile OK)
By the way, this is not a corruption in the project files because older version (from our SCC) have the same behavior.
1: New project has the same issue
2: Holding shift does not help
3: VS properties are working OK. I can build the project but that does not fix the issue.Exactly the same problem here. I have used VS2010 with Visual GDB for many years. I recently installed VS2019 community edition and renewed my Visual GDB support. After downloading the latest Visual GDB and installing it, I have the exact same behavior as the OP.
The Embedded Project page is now usable! The only comment I would have is that it does not use the same style as other pages (minor inconvenient). Normal style is to have headers in Bold letters on a light gray background. Fonts also look different.
I could not reproduce the “page too big” problem because it seems that the problem goes away after I rescale for the first time.
Hopefully that version is not too buggy because this is what I am going to use!
This is much improved. The “Makefile settings” is now showing correctly. This helps! I still see 3 issues:
- The fist time I click on “VisualGDB Project Properties” the page that is displayed is bigger than the screen. I see a few applications that do that. This is annoying as I need to grab the top of the page to shrink it.
- The “Embedded Project” page is still not showing correctly: too much spacing and no elevator on the right (see vgdb1.png)
- On the “Additional Memories” pages, the titles are truncated at the bottom (see vgdb2.png). If I add memory, the data is also truncated.
Problem closed (cockpit error).
The key was: “as long as you use the VisualGDB Project Properties dialog for it instead of the regular VS Configuration Manager.”
I was previously using the VS Configuration Manager and I had missed the “Add” button in the VisualGDB panel.
Thanks for the quick and accurate response.
I am building with this:
C:\SysGCC\arm-eabi\bin\make.exe”
I am pretty sure that if I create configurations other then Debug and Release, it does not really work.
I have seen that when I create new projects now I have an option to use MSBuild (Recommended). Is this what you are talking about? If yes, is there a way to convert my old project that builds with GNU make to MSBuild ?
Very useful post – thank you.
I understand that vendors update their framework all the time but the STM32 issue is very annoying. As of today, CubeMX generates code for version 1.6 of the STM32F0 framework but VisualGDB has V1.3.0 (released June 2015). As a result, the code generated by CubeMX does not compile with VisualGDB.
I also agree with the OP: it would be nice to be able to easily see the ST version of the individual frameworks.
All: thanks for the support.
In the process of trying everything, I removed VisualGDB, erased all the registry entries containing the magic word, erase all directories, etc
After yet another reboot, I got it back!
I am willing to forget the 2 days of work I lost, if I know how to quickly reverse this situation if it happens again!
Additional information: my setup works with the Texane debugger but not with OpenOCD. I have erased and downloaded Open OCD multiple times w/o success.
Thanks for the weekend support. I tried all the suggestions and it still does not work.
I tried to re-install everything on a virgin PC and it worked (used the trial version of VisualGDB).
Something is obviously corrupted on my PC but I don’t know what. I tried to transfer the working solution and it still fails.
What else should I try?
