Check the PATH environment variable in that case. If something goes wrong, it is usually due to tools not being found. Build the project CCS should now be able to build the. You can set those variables either in the Makefile or in the CCS environment just like PATH TARGET=srf06-cc26xx for CC13x0 and CC26x0 devices BOARD=launchpad/cc1310 for the CC1310 launchpad Add CFLAGS += -g to enable debug symbolsĩ 8. Add board and target variables, debug symbols It is sufficient, to build the executable (.elf) No need to do hex conversion which requires srecordĨ 7. XDCTools provides GNU make and the necessary shell tools Git Bash is git distribution for Windows Example: Append C:\ti\xdctools_3_50_04_43_core C:\ti\xdctools_3_50_04_43_core\bin C:\Program Files\Git\binĭo not let CCS generate makefiles For building an example, use the example’s source directory as build directory Note: When creating your own applications, put the application sources and the Makefile into your project directory, not in the Contiki directory. The Contiki build system needs git, make and some other shell tools to be in the PATH environment variable. cfg files in the Contiki source tree and asks whether it should build them with XDCTools. This allows to browse Contiki files whithout copying them into the project folder. Add Contiki sources Add a link to the Contiki source folder based on the CONTIKI_ROOT variable. Just for Convenience Allows us to refer to the Contiki source folder later Makes it possible to switch to another contiki folder without changing the projectĤ 3. Presentation on theme: "Contiki and Code Composer Studio"- Presentation transcript:Ĭonvenient step-debugging on all platformsĬreate a new workspace Create a bare-metal project and select the GCC toolchain
0 kommentar(er)
