Forum Replies Created
-
Posts
-
No problem, please try this build: VisualGDB-5.5.4.3559.msi
It will automatically detect the old Windows 10 builds and will revert to using the old bash.exe syntax when targeting WSL.
Sorry, this looks like a generic C++ question and is outside of the VisualGDB support scope. For generic programming questions please consider sites like StackOverflow.
No problem. Please try updating to VisualGDB 5.5 Preview 4. If the problem persists, please share the updated exception log and we will investigate it further.
Generally, network configuration is outside of VisualGDB’s control and hence the help we can provide here is very limited.
If you are comfortable configuring the VPN, we would advise setting up OpenVPN on one of the machines, and joining the other one to it. If not, please consider using one of the cloud-based VPN services, and connecting both computers to that VPN. This would have the same effect as physically putting them on the same network.
It might theoretically work, however this is not something we have explicitly tested (or can officially support). When the control passes from the bootloader to the main application, the variable would get rewritten by the initialization code, and that may trigger weird bugs.
Either way, it could be worth trying. The variable name is s_FastSemihostingState in FastSemihosting.cpp. If it doesn’t work, making some sort of a syscall mechanism between the bootloader and the main application could be a better option.
Hi,
No problem, we have published a detailed tutorial here: https://visualgdb.com/tutorials/arm/remote/
According to our records, your support period has expired. Hence, we are not able to offer any further technical support, sorry.
Thanks for sending the logs to our support email. It looks like you are trying to debug a static library:
C:\Program Files (x86)\Sysprogs\VisualGDB\Keil\arm-eabi-gdb.exe --interpreter mi "C:\Users\amali\Documents\VS_prosject\VisualDGB_5\Test_VGDB_5_IAR_nr2\VisualGDB\Debug\Test_VGDB_5_IAR_nr2.a"
Please note that static libraries cannot be debugged directly. They must be linked with the executable projects, that can be actually debugged. Please double-check that the project you are importing is an executable project, not a static library.
You can check the project type for a VisualGDB project via Configuration Properties -> General page of VS Project Properties (see this page).
No worries. BTW, we have officially released Analyzer2Go 2.1 that includes this fix, adds support for 5 more STM32 boards, and introduces a few more features.
You can read more about it here: https://sysprogs.com/w/analyzer2go-2-1-is-out/
You can find an overview of various VisualGDB editions and their features at the following page: https://visualgdb.com/buy/
VisualGDB is licensed per seat i.e. computer/user combination. As a special exception to this rule, we allow the usage of two seats for personal i.e. non-company licenses.
No problem. We have fixed the issue in the following build: Analyzer2Go-2.1.0.28.msi
Hi,
It looks like your project might not be generating debug symbols. Please first try creating a new project from scratch for the same device (using the same compiler) and verify that you can debug it. You can use the following dummy main() function to try out breakpoints/stepping:
int main() { asm("nop"); asm("nop"); asm("nop"); return 0; }If it doesn’t help locate the problem, please describe what happens when you try the dummy project, and also share the .vcxproj file and the gdb log file for the broken project and we will help you get it to work.
Sorry, trying to assume the new value instead of verifying a stable value would break the current I2C parsing logic. We might be able to add an option for this in one of the future releases, but we wouldn’t promise it currently.
As a quick-and-dirty workaround, please try selecting a several clock cycles in the SCL signal and clicking the clock pulse icon. This will print the stable values of the SDA signal, making it easier to read.
Thanks for the detailed explanation. Unfortunately, it still doesn’t make full sense. Pressing backspace in the context of the “tab-not-working-1.png” screenshot would delete the ‘/’ character at the end of the /* USER CODE END Includes */ comment. This should not be affected by the tabs settings.
Generally, if you have generated a .c/.cpp file using STM32CubeMX, it will contain the tabs or spaces depending on the STM32CubeMX settings, not VisualGDB settings.
The VisualGDB settings for tabs and spaces will apply when adding new lines to the files, but it will not automatically replace them in existing files, to avoid unnecessary changes.
You can somewhat override it by removing all indentation (Ctrl-A to select the entire file, then press Shift-Tab several times) and reformatting the document using VisualGDB (Ctrl-K, Ctrl-D).
