[support]

Hi,

Looks like you have a typo in the MCUDefinitionFile element:

 <MCUDefinitionFile>\device\nRF52.xml</MCUDefinitionFile>

According to Windows path syntax, this actually means X:\device\nRF52.xml, where X: is the drive letter of the project directory. Please try changing it to this:

 <MCUDefinitionFile>device\nRF52.xml</MCUDefinitionFile>

[support]

Hi,

We are planning to update our mbed package after we release VisualGDB 5.2 Beta 1. The current plan is to do this by the end of September.

[support]

Hi,

Yes, you can disable this, although it will require some minor XML editing. Please try removing the ‘DownloadableSourcePackage’ elements from the toolchain.xml file in your toolchain directory.

[support]

Yes, we got all the necessary information from Segger and are expecting to release an update next week.

[support]

First of all, could you try debugging your existing ELF file with the Quick Debug feature? If this does not work, could you please attach the contents of the Segger J-Link window and the GDB Session window (switch view to ‘All GDB interaction’ so that we could see the internally sent commands)? This should explain what is going on.

[support]

Hi,

Yes, it is possible to configure IntelliSense to show the imported code, however could you first clarify if you mean Python IntelliSense or C++ IntelliSense?

[support]

Hi,

Sorry about that. You should be able to click “ignore” to get past the error message and get the project created. Then you can send us the project and we should be able to tell you what is going wrong with it.

Regarding the “command not found”, most likely you have specified an incorrect path when importing the toolchain. We normally recommend using the toolchains that VisualGDB itself downloads installs as they are tested to work out-of-the-box.

[support]

Hi,

Yes, the settings on the “General, Scroll Bars and Tabs” pages do not get synchronized automatically due to the internal architecture of the VS language services. However all the advanced code formatting settings (from the Formatting pages) should get synchronized properly.

Regarding Makefile, the EXTERNAL_LIBS variable is meant to be automatically updated by VisualGDB based on the referenced projects. If you want to manually add libraries that are not otherwise references, please use the ADDITIONAL_LINKER_INPUTS variable.

[support]

Hi,

Wow, that would be quite complex actually. Delphi uses the Pascal programming language and the VCL library, while making GUI for Raspberry Pi typically involves C++ and the Qt library, that are completely different.

You would essentially need to develop the Raspberry Pi version from scratch and use the Delphi version as your reference. If you don’t have software development experience to do this yourself, we could offer you our consulting services to have this done for you. You can simply contact sales@sysprogs.com with a brief overview of your application so that we could get you a basic estimate.

[support]

Hi,

Good to know it works. BTW VisualGDB has a ‘breakpoint diagnostics’ button in the GDB Session window that should detect and fix problems like this automatically. If you ever run into this again, the breakpoint diagnostics can save you some time…

[support]

Hi,

The arm-eabi toolchain does not actually expect an operating system; it’s designed to work with barebone projects (or using RTOSes like FreeRTOS).

Thanks for clarifying that you have specified the FP option manually. Then the problem could be caused by incompatible settings entered somewhere. If you can reproduce this on a new project, could you archive it and send it to us? We should be able to locate the problem quickly for you.

The ‘get settings from Makefile’ button does a very basic scan of the Makefile for lines like “CFLAGS := xxx”. It is very basic and does not handle complex cases as there is no good way of importing those settings from large projects reliably.

[support]

Hi,

Normally VisualGDB tries to import all C++ formatting settings from regluar VS. Because those vary between different VS versions, the importing logic is quite complex and may have bugs. If you could give us an example of a specific setting that is not imported properly, we should be able to fix it.

[support]

Hi,

The 4.8.3 toolchain indeed looks quite old. Furthermore, the problem might be caused by an incompatible default VFP setting in your toolchain.

VisualGDB actually comes with a newer one (can be installed from the wizard of from here), so we would recommend using it instead.

[support]

Hi,

You can always upgrade to the Custom edition by following this link: http://sysprogs.com/splm/mykey

[support]

Hi,

We would recommend using the External Memories feature of VisualGDB 5.1 for that (required Custom edition or higher). It will manage the linker scripts for you automatically and should avoid such problems.

[Author]

Posts