Forum Replies Created
-
Posts
-
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.
Hi,
Good to know it worked. Note that
((uint32_t)0x000F)does not refer to a floating-point value, it simply defines a priority of 15 (0x0F).Hi,
First of all, if you configure VisualGDB to build your code one one machine and deploy it to another one, it will configure gdbserver automatically.
If you don’t want to do that, you can specify the following settings:
- Select “custom mode”
- Enable the “use a gdbserver” checkbox and configure the following command:
- Command: gdbserver
- Arguments: :2000 <command line to launch your program>
- Target selection command: -target-select remote <gdbserver host>:2000
You can also replace 2000 with any other port number.
Let us know if you need more details.
Hi,
The easiest way to do that would be to directly include the files from it to the project via Add->Existing file and add its directory to the Include Directories in VisualGDB Project Properties.
Hi,
Looks like the latest version available on the Nordic website is v10.0: https://developer.nordicsemi.com/nRF5_SDK/
We normally update the SDKs quarterly and we only use the stable version. You can also try running our BSP generator on the pre-release SDK, however we cannot guarantee that it will work.
One of the possible workarounds is to rename the gdbserver to libgdbserver.so by patching the Android.mk file. VisualGDB will recognize libgdbserver.so as the alternative name for gdbserver and will launch it automatically.
Hi,
We normally recommend using Segger J-Link with the NXP devices, as it has much better support for them.
If you prefer using OpenOCD with the Olimex JTAG, you would need to locate a target script that matches your chip and select it manually in the ‘Target’ field. Normally if you click the ‘find’ button there, you should be able to quickly locate a matching script. For LPC1763 it should be lpc17xx.cfg.If this does not help, please let us know the error message you get when trying to use the lpc17xx script.
