Forum Replies Created
-
Posts
-
Sorry, we do not have any plans to support QML on the VisualGDB side.
We can help you configure QML for Raspberry Pi as a part of our consulting services. Please feel free to reach out to our sales if you would like to get a quote.
Hi,
Sorry, QML (Qt Quick) is based on a completely different technology stack, compared to the regular Qt projects, and is hence not supported by VisualGDB.
Hi,
VisualGDB indeed uses its own settings to control every aspect for formatting. You can find out a searchable list of settings on the following page: https://visualgdb.com/settings/. It is automatically updated when VisualGDB settings are changed. E.g. try searching for “auto-format” for a detailed list of settings that control when VisualGDB would format code.
Hi,
Our regular Raspberry Pi toolchain is compatible with Raspberry Pi 4. That said, please make sure you are using a compatible SD card image (see this page for details).
Thanks, the problem might be caused by incorrect encoding of some of the QuickSync settings.
Please try this build: VisualGDB-5.5.5.3629.msi (you would need to re-enter the excluded subfolders via VisualGDB Project Properties).
If it still doesn’t help, please attach the updated .vgdbsettings file.
No problem, we have updated VisualGDB to use UTC times for folders, similar to files: VisualGDB-5.5.5.3628.msi
Thanks for clarifying everything. We have pinpointed and fixed the problem in the following build: VisualGDB-5.5.5.3626.msi
Hi,
Unfortunately, it’s hard to suggest anything specific based on the description you provided. We could help you find the correct settings if you could let us know the following:
- The .vgdbsettings (or .vgdbcmake) file with the transfer settings.
- The exact path on the Windows machine where the file is located.
- The exact paths on the Windows machine of files that et transferred despite being excluded.
Good to know it works. BTW, we have a detailed tutorial showing how to compare build command lines between VisualGDB and the Arduino IDE here: https://visualgdb.com/tutorials/arduino/diagnosing/
Thanks for confirming this. To narrow the problem further, please follow the steps below:
- Dump the build command line used by VisualGDB to a batch file as shown here. Make sure the build fails when running the batch file.
- Try modifying the batch file to use the arduino-builder.exe from the Arduino IDE directory instead of the VisualGDB’s one. Does it solve the problem?
- If not, please check the ESP32 Arduino core version used by the Arduino IDE and VisualGDB. If they are not the same, please try updating the core used by VisualGDB via Tools->VisualGDB->Manage VisualGDB Packages.
Hi,
Please try building the same project with the Arduino IDE. If the problem persists, the issue is with a specific library. If not, we can help you configure VisualGDB to match the behavior of the Arduino IDE.
No problem, we have updated VisualGDB to show an “empty project” template after the regular project samples in the embedded project wizard. Please try this build: VisualGDB-5.5.5.3622.msi
You can turn this feature on and off via the “Show Empty Project Template” setting (see this page for a list of all global settings).
Hi,
Please see this page for a detailed overview of supported targets.
Hi,
It’s hard to say why HAL_DeInit() would hang on a specific board, however it should be relatively easy to find out by terminating the OpenOCD instance and then attaching to the device as shown in this tutorial. It will show what exactly is happening on the device when it hangs.
