Forum Replies Created
-
Posts
-
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.
No problem, please try this build: VisualGDB-5.5.5.3618.msi
It will display the currently used timestamp offset in the build log after the warning suggesting to use the Host-wide settings, e.g.:
Current timestamp offset for ubuntu19vm is -3600 (generation=0).
Please try the following steps to narrow down the problem:
- Build the project normally. Locate the current timestamp message and the “time stamp in the future” warning in the build log.
- Try adjusting the value in Host-wide settings (e.g. subtract 1000 from it).
- Build the project again and locate the updated messages.
Please share the messages from both builds and we should be able to track this down.
Hi,
Normally, when you create a new project with the Mbed Project Wizard, it will simply clone the official blinky sample and will use the mbed version that was referenced by it.
We have just rechecked it and as of 2020-05-16, the sample project references mbed 5.15.1 (you can double-check it by running “git describe” in the mbed-os subdirectory), so it works as expected.
Either way, you can change the referenced mbed version by right-clicking on Libraries->mbed-os in Solution Explorer and selecting “Change Library Version”.
