Forum Replies Created
-
Posts
-
Hi,
OK, this looks like the libcompactcpp.a is actually not being compiled in. Please check the verbose link log (if you are using MSBuild, simply check the .link.rsp file) for the linker command line and ensure it contains the “-lcompactcpp” argument. If you are not sure, please post the linker command line here and we will help you resolve this.
Hi,
Perhaps you were using semihosting instead? Basically, VisualGDB supports 3 ways of getting output from an Embedded target:
- Normal semihosting. It works similar to setting a breakpoint inside printf() and other functions, automatically reading the printed data and resuming the program. It’s fairly slow as the program is stopped on each event, but does not require any extra configuration (as long as you are using a C library that supports it).
- Fast semihosting. It uses our own implementation of the low-level _write() function that sends printed data to VisualGDB using an in-memory buffer without stopping the target (unless an overflow occurs). This mode can be enabled by referencing the “Fast Semihosting and Profiler” framework and is the recommended way.
- Using a COM port. The target physically outputs the data to a COM port and VisualGDB connects to it and shows the data. This requires manually configuring the COM port and the speed via VisualGDB Project Properties (Embedded Terminal page) and only works on the Custom edition and higher. If you have a lower edition, you can just run the free SmarTTY tool in the background to get the same effect.
The code shown in the previous post uses the mbed API for accessing serial ports, so it will only work in the 3rd mode (with either Embedded Terminal or a separate instance of SmarTTY or any other terminal program) and requires a physical connection, a driver for the USB-to-COM interface and a correct baud rate setting.
If your setup is not working, please double-check that:
- You are actually outputting the data to the correct UART interface on the board (step into the printf() method to see which one is used and then check the board schematic to ensure this UART is connected to the ST-Link COM-to-USB interface)
- You are opening the correct COM port from VisualGDB Project Properties (check which of the COM ports disappears in Device Manager when you unplug the board).
- The baud rate in VisualGDB Project Properties is explicitly set to 9600
Hope this helps.
Hi,
That does indeed look like our toolchain. Please try enabling the map file generation via Linker Properties and ensure that the _ZSt9terminatev (std::terminate) function is coming from the libcompactcpp.a:
.text 0x08000188 0xa4 e:/sysgcc/arm-eabi/bin/../lib/gcc/arm-eabi/6.2.0/thumb/cortex_m4/crtbegin.o .text 0x0800022c 0xc e:/sysgcc/arm-eabi/bin/../lib/gcc/arm-eabi/6.2.0/../../../../arm-eabi/lib/thumb/cortex_m4\libcompactcpp.a(libcompactcpp.o) 0x0800022c __cxa_pure_virtual 0x08000232 _ZSt9terminatev
Hi,
If you are using a 3rd-party toolchain, it may be configured slightly differently and the compactcpp library won’t override the necessary symbols. Please try switching to our ARM toolchain.
Hi,
Just to double-check, the serial port output of the board is connected to a USB-to-COM adapter, you are using a terminal program like SmarTTY to view the transmitted data and you can confirm that the adapter works properly with other boards, right?
Hi,
Please switch the GDB Session window to “All GDB interaction” and check if VisualGDB issues any gdb commands when you are trying to hover the mouse over a variable. If no, please check if this is broken for non-VisualGDB projects as well. If yes, please let us know if gdb reports any errors.
Hi,
It looks like your toolchain might be missing some libraries. Please try running C:\SysGCC\Beaglebone\arm-linux-gnueabihf\sysroot\usr\local\qt5\bin\uic.exe manually. Does it run successfully, or does it report that some DLL files are missing?
Hi,
You can do that, but the VisualGDB will treat the project as a black box. I.e. when you add new files to Solution Explorer, it won’t automatically update your Makefiles and if you want to change some settings like include directories, you will have to manually edit both the Makefiles and the IntelliSense settings in order to change them. You will also need to manually set the preprocessor macros and include directories generated by mbed-cli in the IntelliSense settings, as VisualGDB won’t detect them automatically.
You can try using our mbed BSP generator to build a first-class BSP that will be fully synchronized with Visual Studio, although it may need some adjustment due to changes to mbed codebase since the release it officially supports.
Hi,
This could be caused by some non-typical data types or rare combinations of settings. If you could describe how exactly you are using the Visual Watch, what do you expect and what actually happens, we should be able to suggest a way to get it to work.
Hi,
We will include it in v5.3 if it proves stable enough. The drawback of the new mechanism is that it unloads the VS project, edits it and then reloads it back, that might cause unforeseen side effects. We will definitely include this in either the first or the second v5.3 preview and decide whether to include it in the final build based on the feedback we get.
Hi,
Strange. Does the regular (non-JTAG) NodeMCU setup work as expected? If not, the module might simply be corrupt. If yes, what happens if you program the firmware via the gdb stub and then change the debug method to JTAG and select “do not program FLASH memory”?
Hi,
Yes, our Kinetis packages are less sophisticated than STM32 and Nordic ones, so the driver .c files need to be added to the project manually. The missing include paths should still be automatically discovered after you open any of the files that tries to include the missing headers.
Hi,
The files should still be generated (the extension is .ihex, not .hex). If not, please check the Embedded Project page of VS project properties (not VisualGDB project properties). The “generate .hex file” should be set to “yes”.
