[support]

Hi,

OK, please try the following Makefile from the command line:

test:
    gcc -DTIMESTAMP=$(shell C:/mingw/msys/1.0/bin/date.exe +%s) -E test.c -o test.E

You can use it with the following test.c file:

int timestamp = TIMESTAMP;

If this does not work, please let us know the error you get with this simple file. If it does, please compare the syntax here with your Makefile.

[support]

Hi,

VisualGDB does not normally *overwrite* the Makefile, it simply edits the SOURCEFILES line and a few other relevant lines, but only if it finds special tags in the file. Please let us know more details on what exactly is broken and we could suggest how to fix it.

[support]

Hi,

We would recommend exporting it as GccARM, unpacking the archive to any location within your source control system and then simply using the “Import Folder Recursively” command to import those files into your project.

If you run into problems with missing include files, you can try a daily build of VisualGDB 5.2 that has experimental support for repairing them automatically. Let us know if you want to try it out and we’ll post a link to it.

[support]

Hi,

This happens because the FreeRTOS port hardcodes the ISR vector table name variable name as ‘__isr_vector’ and the VisualGDB startup file uses a different name.

The easiest way to solve this is to replace this (in port.c):

    "   ldr r0, =__isr_vector     \n" /* Locate the stack using __isr_vector table. */
    "   ldr r0, [r0]              \n"

with that:

"   ldr r0, =_estack     \n"

Note that the “ldr ro, [r0]” line will be removed, as _estack already contains the end-of-stack address.

Let us know if you encounter further problems.

[support]

Hi,

Thanks for pointing this out, we will fix it in the next release of the Tiva BSP.

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

[Author]

Posts