Forum Replies Created
-
Posts
-
Hi,
Sure, we could easily add something like this. Could you send us a sample project file with your rule layout so that we could test it?
BTW, if you are using your own build system and don’t need VisualGDB to update Makefiles, you can simply replace the build command with <VisualGDB.exe> /build <file.vgdbsettings>. This will eliminate the need to parse the .vcxproj files.
Hi,
The problem happens because VisualGDB needs to parse the .vcxproj file when building the project and it does not have the VS API available at that point, so it does not check included property sheets. Hence each project needs to specify the path to the settings file explicitly. Also due to the performance limitations of VS, the settings file name needs to be named exactly as <Project>-<Configuration>.vgdbsettings file, as otherwise some of the context menu GUI won’t be able to find it.
The easiest workaround would be to symlink the files via the mklink commands. We could also add a feature to allow linking property files, e.g. each of your project’s .vgdbsettings files could contain something like <LinkedFilePath>$(BUILD_ROOT_DIR)\…</LinkedFilePath> and then VisualGDB would load the linked file instead of the per-project files. Would that work for you?
OK, perhaps the “CPU did not halt” error is unrelated to the Default_Handler() problem.
Please try adding ‘DEBUG_DEFAULT_INTERRUPT_HANDLERS’ to the Preprocessor Macros field on the Makefile Settings page of VisualGDB Project Properties and build your project again. This should show which actual interrupt ends up being unhandled.
Hi,
Are you talking about the IntelliSense when editing the OpenCV sources, or when editing your application based on OpenCV?
Please ensure that the “Configure IntelliSense baesd on CFLAGS dumped by CMake” checkbox on the CMake Project Settings page is set. If it was not set, please set it and build your project again.
Hi,
This error happens when VisualGDB fails to update your system environment properly. Normally restarting your computer should help.
VisualGDB should normally fix this problem for you. Simply select your port in VisualGDB Project properties and it should get it to work.
Hi,
The CDC driver can be downloaded from ST: http://www.st.com/web/en/catalog/tools/PF257938
In order to create the HID examples, please download the ST cube software package for your board, locate the HID example for your board, copy the source and header files to your project directory and add them to your project.
Hi,
Yes, that should fix it. However if you define it in nrf5x.mak, it will get overwritten next time you change your device settings, so please define it in debug.mak/release.mak instead (can be done via VisualGDB Project Properties).
Hi,
You don’t need to reinstall VisualGDB itself; you can simply delete the Raspberry Pi toolchain and reinstall it. This should help.
Regarding the error, it looks strange. Can you confirm that the “file not found” line is shown BEFORE the “GNU Make 3.82” line? Do you see the same when you try running make.exe in the project directory from Command Prompt manually?
Regarding formatting, we have fixed it, but next time you can just select “Preformatted” instead of “Heading 6” for the pasted text and the forum should display it properly.
Hi,
This looks like a connectivity problem. Please double-check your JTAG cable and your Reset signal. If it does not help, please try it on a different board.
Hi,
The problem is that NXP does not allow downloading the entire KSDK as one package, so we cannot make a BSP based on it similarly to what we did with KSDK 1.3.
As a workaround we would suggest generating an SDK for your device using their online tool and importing it to VisualGDB using the project import wizard.
Hi,
The “The system cannot find the path specified” message is most likely produced not by the Make itself, but by some command that Make launches. Please check the log file for statements like “running command xxx” just before the error message. Then try running the same command manually to see if you can pinpoint the one showing the error.
Hi,
No problem. Similarly looking things are always easy to confuse. Happens to everyone.
Regarding the priority, we are somewhat hesitant to change the code that comes from ST without testing it on the real hardware, so we’ll probably simply add a big warning in the sample or the tutorial about the interrupt priorities.
