[support]

Hi,

Sorry, GNU tools like GDB are often unreliable and some versions may simply be not compatible with certain OS versions. If the version 7.12 does not work, the only advice we can give is to revert back to v7.10. As long as you are using the new method to run gdb directly on the target, both 7.10 and 7.12 should work.

[support]

Hi,

Thanks for posting this, it looks like our bug. We could not reproduce it on our side though.

Could you please check if modifying our version of the linker script to align the fs_data contents also helps?

.data : AT(_sidata)
 {
 . = ALIGN(4);
 _sdata = .;

PROVIDE(__data_start__ = _sdata);
 *(.data)
 *(.data*)

. = ALIGN(4);  #<=================== Insert this line
PROVIDE(__start_fs_data = .);
KEEP(*(.fs_data))</strong>
PROVIDE(__stop_fs_data = .);

. = ALIGN(4);
 _edata = .;

PROVIDE(__data_end__ = _edata);
 } > SRAM

If yes, we will release a hotfix for the BSP.

[support]

Hi,

Sorry, looks like the virtual terminal mechanism used by VisualGDB to redirect the program output is broken on your Linux distro:

&”/dev/pts/18: No such file or directory.\n”

The only workaround we could suggest is to explicitly forward the program output to a file:

1. Create an empty file on the Linux machine (e.g. /tmp/output) by running the following command on Linux via SmarTTY: echo > /tmp/output
2. Add the following command to the GDB commands after selecting a target (Additional GDB Commands page): tty /tmp/output

Note that you will not see the program output in real time then as it will be forwarded to a file.

[support]

Hi,

Please refer to the screenshot below (this corresponds to the Debug Settings page of VisualGDB Project Properties):

You only need to set those for the executable project.

[support]

Hi,

Sorry, looks like you are still using the gdbserver. Otherwise the ‘Remote communication error.’ message will not be shown.

Please try selecting the direct mode manually:

1. Start gdb in the following mode: Custom mode
2. GDB launch command: gdb –interpreter mi –args “$(TargetPath)”
3. Use a gdbserver: no
4. Target selection command: (empty)
5. Debugging start mode: use “run” command

[support]

Hi,

This define was added in one of the latest releases of the STM32 BSP and it supports controlling the HAL_LEGACY macro via the VisualGDB GUI.

Most likely you have created a project using the old BSP and then converted it to a stand-alone one using the new BSP, so VisualGDB did not find the new setting in the project configuration and did not substitute it properly. This can be safely ignored and should not happen for projects created with the new BSP.

[support]

Hi,

Please try manually running commands like ‘detach’ or ‘disconnect’ in the GDB session window and see if any of those ends debugging with resuming the target.

If it does, please configure VisualGDB to use that command on exit. If it does not work, please try enabling the GDB logging on the Advanced GDB Settings page of VisualGDB Project Properties. Then try ending debugging and check the last commands shown in the gdb log.

[support]

Hi,

Have you tried setting optimization to -Og like the tutorial suggests?

[support]

Hi,

Yes, you can download it manually from http://gnutoolchains.com/raspberry/

[support]

Hi,

Yes, we will fix this in the final BSP release.

[support]

Hi,

Thanks, we have managed to reproduce and fix this. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.2.14.1318.msi

 

[support]

Hi,

Thanks for confirming this. We have added background execution for custom shortcuts to v5.3 roadmap. We will post an update here once this feature is available.

[support]

Hi,

Yes, please check the ‘Allow choosing build/clean/debug command hosts independently’ checkbox on the Project Settings page of VisualGDB Project Properties.

[support]

Hi,

VisualGDB normally does exactly that – captures the #define-s reported by gcc and feeds them into the Clang IntelliSense. If you are using MSBuild projects, you can see a list of those via View->Clang IntelliSense Diagnostics Console ->View->ProjectStatus->CFLAGS (due to a bug in the Windows edit control, it may appear empty if CFLAGS is too long; copy-pasting it to notepad should help). If you are using non-MSBuild projects, the flags are dumped in gcc_<configuration name>.h and this file is forcibly included by the Clang engine.

If you believe this is not happening, please let us know the details (which macros are missing from the IntelliSense point of view) and we will help you troubleshoot this.

[support]

Hi,

Sorry about that, this is a bug of the new mbed BSP that is in the Beta stage.

To fix this, please copy the  %LOCALAPPDATA%\VisualGDB\EmbeddedBSPs\arm-eabi\com.sysprogs.arm.stm32\STM32F4xxxx\DeviceDefinitions\stm32f446xx.xml.gz file to %LOCALAPPDATA%\VisualGDB\EmbeddedBSPs\arm-eabi\com.sysprogs.arm.mbed\DeviceDefinitions\stm32f446xx.xml.gz and add the following line to the mbed.xml file in your project directory under the EmbeddedProfile element:

  <MCUDefinitionFile>DeviceDefinitions/stm32f446xx.xml</MCUDefinitionFile>

This will automatically pick the register definitions from the normal STM32 package.

[Author]

Posts