Forum Replies Created
-
Posts
-
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.
Hi,
Yes, the “computer used for building and debugging” is the one running gdb. The “deployment machine” below is the one with gdbserver.
You can disable the actual deployment on the Debug Settings page, but the text on the Project page mentions it as it makes sense for most of the projects.
Hi,
The easiest way to limit the loaded symbols is to copy the symbols you need to a separate directory and ensure that it is added to gdb’s solib-search-path and that the original directory containing all of the symbols is actually not listed there.
Then GDB will only load the symbols you have copied.
Hi,
You can override the attach PID by adding a custom pre-debug action that will set the AttachPID variable (on the Custom Debug Steps page). Let us know if you need more details.
