[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.

[support]

The Raw Terminal feature is only available in the Custom edition and higher. If you want to upgrade, please simply contact our sales.

[support]

Hi,

This is a known issue. Sometimes some gdb stubs report memory contents incorrectly. Please try enabling the “use ‘x’ command to read memory” checkbox in the VisualGDB Project properties (GDB Settings page). This should use a slightly slower but more reliable mechanism.

[support]

Hi,

We’ve actually just released the EFM32 package. You can now easily create a project like shown in this tutorial and VisualGDB will attach all necessary files automatically.

[support]

Hi,

We have fixed a few things in the engine since the latest 5.1 build, so please check if you can still reproduce the problem with this build: http://sysprogs.com/files/tmp/VisualGDB-5.2.4.821.msi

If yes, please upload an updated dump file and we will look into it.

[support]

Hi,

Please find the answers to your questions below:

1. We have added experimental support for changing embedded toolchains to this build: http://sysprogs.com/files/tmp/VisualGDB-5.2.4.821.msi. Let us know if it works.
2. The include directories are transferred to IntelliSense settings once VisualGDB performs toolchain testing. If you bypassed this stage, the directories won’t be added. Either way, the build above contains an experimental feature of automatically detecting and repairing missing include paths for both IntelliSense and project properties, so it should take care of this automatically. Feel free to let us know your feedback on this feature.
3. You can work around this by adding something like “$$custom_pre_load_command$$ to the startup commands in EDP.XML and then setting this variable per project by editing the .vgdbsettings files (inside the DebugMethodProperties element). Let us know if you need more details.

[Author]

Posts