[arrow201]

Thank you for the support! 🙂

 

[arrow201]

Hi,

The popup only occurs once going into “Manage VisualGDB Packages” the first time after the VS update. I’ll try to summarize:
– updating to 17.2.? (sorry I don’t remember what sub version I had) never showed the popup
– 17.2.? to 17.3.0 popped the msg once, this was 2 days ago. I restarted VS and the popup went away, so I thought some weird glitch and didn’t report it. Subsequent selection of “Manage VisualGDB Packages” no longer popped up the msg
– 17.3.0 to 17.3.1 popped up once again, but subsequent selection of “Manage VisualGDB Packages” does not pop up the msg

Thanks

 

 

[arrow201]

Ok, I restarted my PC again, and going into “Manage VisualGDB Packages” no longer gives me the popup err. Appears something with the last two Visual Studio updates (v17.3.0 and v17.3.1) gives this error the first time going into “Manage VisualGDB Packages” but doesn’t appear after that.

 

[arrow201]

The manual update worked fine. Great product, great support.

Thank you!

[arrow201]

Thank you very much for the update! 🙂

[arrow201]

 

I would never build any sort of serious project with VGDB/STM32CubeMX. I use STM32CubeMX for configuring only. The code STM32CubeMX produces is messy, IMHO, and I can’t stand the /* USER CODE BEGIN /ENDs all over the place.

I use objects for maintainability where I can. I’ll first create a STM32CubeMX stand alone project(not VGDB) for just configuring the hardware. I then create my VGDB project and create a, ie. CHardware(.h/.cpp) class, where I’ll copy/paste the hardware configuration from STM32CubeMX into. Everything I need from STM32CubeMX, except the IRQ routines, will go in this class. I keep the handles global and pass a reference to my hardware methods, ie:
bool CHardware::InitUsart1(UART_HandleTypeDef &huart1)

True, a bit of pain if making many changes in STM32CubeMX to copy/paste into your project. Maybe there’s better way, but this seems to be a pretty good trade off to write clean/maintainable code while also using the advantages of STM32CubeMX.

 

[arrow201]

I think what you want is here:  https://visualgdb.com/tutorials/arm/mbed/mbed-cli/
Just before 3.,  click on “the official Git distribution” to start.

[arrow201]

I was going to ask this question at some point. I thought maybe the guide lines were left out purposely to avoid clutter, since there’s already much info already. If you really must see the guide lines: Project Properties | Intellisense Settings, change the Intellisense Engine to “Regular VC++”, but of course you lose all the Clang goodies.

[arrow201]

In q2-1.png, it shows “Minimal (no semihosting)”, shouldn’t “Support semihosting” instead be selected? There’s good info here: https://visualgdb.com/tutorials/arm/semihosting/

• This reply was modified 3 years, 9 months ago by arrow201.
• This reply was modified 3 years, 9 months ago by arrow201.

[arrow201]

This is a win for VisualGDB, as from what I’ve read, it’s currently a pain to setup the Pico for proper C/C++ development. I’m also looking to evaluate the Pico at some point and as expected, variants have already started to popup(i.e. “Tiny 2040”). Curious of the debug options that will be available (Seggear J-link?, Picoprobe?). Thanks.

[arrow201]

Hi,

I’m going to be evaluating this product soon and want to be clear with the licensing. So, if I’m reading the above correctly, if I purchase, for example, at version “VisualGDB-5.5.1.1111.msi” and there are updates during the year, I can use these updates for “free” during the year from the time of purchase. Just before the year is up, let’s say the version is now at “VisualGDB-5.5.2.2222.msi”. After the year is up, are you saying if I want to keep using it without renewing, I have to uninstall the updates and go back to version “VisualGDB-5.5.1.1111.msi”? If that’s the case, I can certainly see why the above users are confused, to me, reading the “Buy” page gives the impression that you can continue to use the product with the last update before the year was up.

[Author]

Posts