[support]

Hi,

By default mbed provides its own implementation of the _write() function that is used when you call printf().

You can replace it by a VisualGDB-provided one that will print to the Visual Studio window in 2 steps:

1. Remove the retarget.cpp file from your project
2. On the Embedded Frameworks page add reference to the Fast Semihosting and Profiler framework

Let us know if you encounter any problems.

[support]

Hi,

Please try this syntax:

$(shell C:/date.exe +%s)

[support]

Hi,

Normally the live variable type is saved in the <Project>-<Configuration>.vgdbsettings.<username>.user file. We have just tried creating some variables and changing their type and the type was remembered correctly.

Perhaps something about your project is confusing the live variables logic? Could you share precise repro steps that could be reproduced on a basic “LEDBlink” project?

 

[support]

Hi,

Could you share a sample project that always causes the problem? We should be able to fix it easily then.

[support]

Hi,

We are considering it for the next update of our nRF52 BSP, but it’s not there yet. However we can easily help you get through the errors you are encountering if you share more details.

[support]

Hi,

USB serial port-based printing and Semihosting-based printing are actually using different mechanisms. Did they both stop working?

Can you also reproduce it on a new project? Perhaps the problem happens because the stdlib actually sends the printed text when it encounters a ‘\n’ character and your example above does not send it?

[support]

Hi,

Please feel free to summarize the advantages you see in -MMD -MP over -MD and we will consider using it instead.

[support]

If you are building on Windows, please install MinGW/msys to use the Unix-style commands like ‘date’ and then specify the absolute path to the ‘date.exe’ from the msys directory so that it’s not confused with the Windows ‘date’ command.

[support]

Yes, we are planning to look into it after releasing VisualGDB 5.2 at the end of summer.

[support]

Hi,

You can save those in a file in your project directory and then run it by adding one “source <file name>” command to GDB startup commands.

[support]

Yes, you can modify the EDP.XML as follows:

      <GDBStartupCommands>
        <string>target remote :2331</string>
        <string>$$com.example.extra_startup_commands$$</string>
        <string>$$com.sysprogs.jlink.resetcommand$$</string>
        <string>$$com.sysprogs.jlink.program$$</string>
        <string>$$com.sysprogs.jlink.resetafterload$$</string>
      </GDBStartupCommands>

Then edit your .vgdbsettings file as follows:

    <DebugMethodProperties>
      <Entries>
        <KeyValue>
          <Key>com.example.extra_startup_commands</Key>
          <Value>echo Hello!</Value>
        </KeyValue>

This will allow changing the exact command on a per-project basis.

Regarding the exception with large projects, we have managed to reproduce this and will fix it in the next preview build. For large projects VisualGDB unloads it, edits the project file directly and loads it back to make it faster than adding files one-by-one and it looks like this mechanism got broken in the new build.

[support]

Are you using the Segger J-Link software? Looks like the latest version breaks the semihosting support. We have not investigated this yet, but downgrading to an earlier one should solve the problem.

[support]

Hi,

Yes, please try this one: http://sysprogs.com/files/forum/mv.exe

[support]

Hi,

Yes, this should do.

[support]

Hi,

It’s a known bug. Please update your VisualGDB to 5.1r6 and re-download the OpenOCD package via Tools->Embedded Tools Manager. This should resolve the problem.

[Author]

Posts