![]() ![]() Note that although the build and debug has succeeded, the IntelliSense will not be able to find the include files.You can set a breakpoint somewhere in the mouse.c file if you want to step through its code: Once Windows recognizes the virtual mouse emulated by the example, the mouse pointer will begin to move. Once the project is programmed and started, connect the second USB connector of the board.When VisualGDB asks for the location of the ELF file, point it to the ELF file built by the KSDK build system: Now you can build the project by pressing Ctrl-Shift-B:.Then copy the make.exe in the Sysprogs ARM toolchain directory to mingw32-make.exe:.First of all replace “arm-none-eabi” in the \tools\cmake_toolchain_files\armgcc.cmake file with “arm-eabi”: Before you can build it, however, you would need to make some adjustments to the KSDK. Press “Finish” to generate the project.Finally select the debug method that works with your project for FRDM-KL25Z we will use Segger J-Link as the on-board OpenSDA programmer can run the Segger firmware:.For the Kinetis USB mouse example specify “cmd /c build_all.bat” as the build command, run it in the “bm\armgcc” subdirectory (containing the baremetal build files for GCC), add the CMake directory to PATH and create an environment variable called ARMGCC_DIR pointing to the ARM toolchain: On the next page specify the command line used to build the project.Even if the project uses files from other directories, they will still participate in build (as VisualGDB will be reusing your build system) an the debugger will be able to open them (as the ELF file records all the built source files): Note that it will only affect the contents of Solution Explorer. On the “Import Source” page specify the location of the source files of the project.In this example we will select MKL25Z128VLH4: On the next page select the ARM toolchain and pick device that the project is targeting.Select “Import a project built with command-line tools -> Specify a build command line manually”:. ![]() ![]() Start Visual Studio and launch the VisualGDB Embedded Project Wizard:.Before you begin, install VisualGDB 5.0 or later and download/unpack Kinetis KSDK. In this example we will show how to import the USB Mouse example from the Kinetis KSDK 1.3 that is built with CMake. This approach has the advantage of fully reusing the build system used to build the project, however is requires manually synchronizing the list of include directories and preprocessor macros between the build and IntelliSense, as VisualGDB won’t be able to automatically detect those settings for the build systems that are out of its control. This tutorial shows how to import an embedded project build with a third-party command-line to VisualGDB. ![]()
0 Comments
Leave a Reply. |