![]() SYSCONFIG_TOOL ?= /home/username/ti/ccs1030/ccs/utils/sysconfig_1.8.0/sysconfig_cli.sh +++ -18,14 +18,14 will build using each non-empty *_ARMCOMPILER cgtool. See the diff below as an example, and adapt for wherever you installed things. The only paths that need to be set here to build Sniffle are for GCC, XDC, and SysConfig. Within ~/ti/simplelink_cc13x2_26x2_sdk_5_10_00_48 (or wherever the SDK was installed) there is a makefile named imports.mak. Once the SDK has been extracted, you will need to edit one makefile to match your build environment. The same applies for the TI SysConfig tool. This works fine and my makefiles expect this path, so I suggest just going with the default here. On Linux and Mac, the default installation directory is inside ~/ti/. The TI SDK is provided as an executable binary that extracts a bunch of source code once you accept the license agreement. You can just download and extract the prebuilt executables. For minimal hassle, I suggest using the ARM GCC linked above. The arm-none-eabi-gcc provided through various Linux distributions’ package manager often lacks some header files or requires some changes to linker configuration. Note: it should be possible to compile Sniffle to run on CC1352P Launchpad boards with minimal modifications, but I have not yet tried this. When using prebuilt firmware, be sure to use the Python code corresponding to the release tag rather than master to avoid compatibility issues with firmware that is behind the master branch. Prebuilt firmware binaries are attached to releases on the GitHub releases tab of this project. If you don’t want to go through the effort of setting up a build environment for the firmware, you can just flash prebuilt firmware binaries using UniFlash/DSLite. TI DSLite Programmer Software: see below.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |