[support]

Hi,

Texane ST-Link is separate from OpenOCD, however it’s also buggier. You can try using it, however you may need to unplug and replug your ST-Link if it starts behaving strangely.

Can you verify the lost variables problem with the following program?

int g_Global = 123;
int main()
{
    if (g_Global != 123)
        asm("bkpt 255"); 
}

Does it trigger the breakpoint? What is the address of g_Global?

[support]

Hi,

Are you using the latest VisualGDB 5.0 and the latest STM32 BSP? Does the normal LEDBlink (HAL) project build correctly?

[support]

Hi,

OpenOCD usually takes a few months to support the latest ST devices. Once it supports it, we will update our package.

Regarding the problem with the variables, could you please provide an example? Could you also verify that the variable address is within the RAM region according to the datasheet and that the value is actually lost, not just seems to be lost via the debugger (e.g. output it to a COM port from your firmware).

[support]

Hi,

Yes, simply contact our support with your license key and they will reset your activation.

[support]

Hi,

Good to know you got it to work. Let us know if you encounter further problems.

[support]

Hi,

The “propagate to the environment” flag is only supported for the per-user variables, not for variables set from commands. In the case you mentioned, specifying GitRevision=$(GitRevision) explicitly is the recommended way to go.

[support]

Please double-check that your custom variable has the “propagate to the environment” flag. This can be also caused by a bug in the .Net framework that changes all environment variables to lowercase. You can try $(git_revision) instead. If this does not help, you can explicitly specify it in GNU Make arguments: GIT_REVISION=$(GIT_REVISION). Then VisualGDB will expand $(GIT_REVISION) and pass the actual value to the Make command line.

[support]

Hi,

You could select the “custom mode” as the debug method and specify “gdb –interpreter mi $(TargetPath)” as your command and “target remote :<port>” as the target selection command.

Then VisualGDB won’t take any extra steps like trying to run a GDB stub.

[support]

Hi,

Please open VisualGDB Project Properties and check the build command there. If you are not sure, please send us your .vgdbsettings file so that we could help you locate the command.

[support]

Hi,

No problem. If you encounter further problems, feel free to contact us.

[support]

Hi,

Good to know you got it to work. If you encounter further problems, feel free to let us know.

[support]

Hi,

According to the STM32F7-Discovery schematics, an LED is connected to GPIOI1. Please select it in the wizard, or adjust the code afterwards.

[support]

Hi,

The extensibility interfaces are not documented as they are used by a fairly small amount of our users. If you have specific questions about those, feel free to ask here or direct them to our support.

[support]

This is a known bug in 4.3 that has been fixed in 5.0.

[support]

Hi,

Thanks for the link, we will investigate it and see if we can add similar functionality to VisualGDB.

[Author]

Posts