[support]

Hi,

This looks like a potential problem in the CMake file. Which version of VisualGDB did you use to create the project?

[support]

Hi,

The fast semihosting framework is designed to be used under debugger, but if your program does not call printf() or similar functions, it should not trigger. If you want to build a release executable that will discard the printf() output instead of trying to communicate to the debugger, please follow the steps below:

1. In VisualGDB Project Properties -> Embedded Frameworks please uncheck the “Redirect printf() to fast semihosting” flag
2. On the Makefile settings page for the Debug configuration add ‘FAST_SEMIHOSTING_STDIO_DRIVER’ to the list of preprocessor macros to enable this feature for Debug configuration only
3. In your code provide the default implementations for _isatty() and _write() that will just return the correct values and not send anything.

This should eliminate any references to the semihosting functionality in the release build and make it run with no debugger attached.

[support]

Hi,

Looks like your support period has expired. Please renew your license and we will be happy to help you.

[support]

Hi,

You can try using the per-user variables (or environment variables). Simply replace the host name and user name in .vgdbsettings files with something like $(VariableName) or do the same via GUI. Let us know if  you need more details.

[support]

Hi,

Perhaps the extra initizliation commands did not get imported properly. Could you attach your .vgdbsettings file and the <mcu>.xml file so that we could check that?

[support]

Hi,

Thanks for the project, we have reproduced the problem. It happens because the original ARM toolchain has a bug that does not set the FPU type correctly for Cortex-M4 devices.

The toolchain that comes with VisualGDB fixes this; the original ARM one does not. You can work around this by adding -mfpu=fpv4-sp-d16 to your LDFLAGS, however the standard libraries that come with the toolchain are still compiled with the wrong FPU setting, so they may cause random crashes if your program is using hardware FP.

We would recommend switching to the toolchain shipped with VisualGDB to avoid this problem in the first place.

[support]

Hi,

It usually requires understanding which files belong to which component and including only the relevant ones. That’s why it takes us some time to make usable wrappers around the SDK that include the necessary files automatically, sorry.

The only alternative to thoroughly looking through the sources and figuring out which ones are needed for what would be to wait a few months until we release an updated BSP.

[support]

Hi,

The latest BSP for the NXP LPC devices supports the LPC1769 MCU, however it does not come with any Smoothieboard-specific drivers or samples.

You should be able to build and debug a basic project though and then you can add any Smoothieboard-specific code manually. If you encounter any problems, feel free to let us know.

[support]

Hi,

Looks like your toolchain might not support hardware floating point properly. Please try using the ARM toolchain that comes with VisualGDB.

[support]

Hi,

You can easily add custom pre-build actions that will transfer any header files (or whole directories) to Raspberry Pi (see the Build Customization page of VisualGDB Project Properties). Then simply ensure that the relative paths to the directories where the headers end up are specified on your Build Settings page and you should be able to build the project successfully.

[support]

Hi,

VisualGDB actually recognizes and substitutes the normal environment variables with the $(Variable) syntax. Hence you can simply use the $(USERNAME) syntax to refer to the built-in Windows variable containing the current user name.

[support]

OK, we’ve fixed this. Please update your Segger debug package to version 3.3. We have added a new more reliable live memory engine based on the feedback from Segger.

Note that it’s somewhat slower than the old one, so we have also added an option that allows switching between the old and the new one. Let us know if this solves the problem.

[support]

Hi,

VisualGDB does not automatically configure the Python IntelliSense to match your Raspberry Pi. However you can configure it fairly easily:

1. Open Tools->Python Tools->Python Environments
2. Find the default environment there
3. Create a copy of your Python directory used by the default environment and copy the packages from Raspberry Pi to that copy so that they don’t interfere with your regular Python installation
4. Edit the Python environment settings in VS to use the new Python directory

This should get IntelliSense to display the libraries copied from Raspberry Pi.

[support]

We are looking into that and will publish a tutorial on this once we get it to work reliably.

[support]

Hi,

Yes, it sometimes causes Make to simply hang. VisualGDB 5.2 will come with a separate MSBuild platform that will integrate the existing toolchains directly into the Visual Studio build system, so the multi-threaded build will be automatic and it won’t trigger the Make bug.

[Author]

Posts