SWRA446 February   2015 CC1310 , CC1310 , CC2620 , CC2620 , CC2630 , CC2630 , CC2640 , CC2640 , CC2640R2F , CC2640R2F , CC2640R2F-Q1 , CC2640R2F-Q1 , CC2650 , CC2650 , CC2650MODA , CC2650MODA

 

  1.   Using GCC/GDB With SimpleLink CC26xx/CC13xx
    1.     Trademarks
    2. 1 Introduction
    3. 2 Prerequisites
      1. 2.1 Platforms
      2. 2.2 Hardware
      3. 2.3 Software
    4. 3 Hardware Setup
    5. 4 Software Installation Instructions
      1. 4.1 Java Runtime Environment
      2. 4.2 Eclipse IDE (Windows)
      3. 4.3 Eclipse IDE (Linux)
      4. 4.4 GNU Toolchain (Windows)
      5. 4.5 GNU Toolchain (Linux)
      6. 4.6 Build Tools for Windows
      7. 4.7 TI Emupack and GDB Server (Windows)
      8. 4.8 Flash Programmer (Windows)
      9. 4.9 Flash Programmer (Linux)
    6. 5 Build the Software Example
      1. 5.1 Import Example Project Into the IDE
      2. 5.2 Build the Software Example
    7. 6 Load Binary Image to Target
      1. 6.1 Configure Flash Programmer Tool (Windows)
      2. 6.2 Configure Flash Programmer Tool (Linux)
      3. 6.3 Load the Image to Target (Windows)
      4. 6.4 Load the Image to Target (Linux)
    8. 7 Debug the Software Example
      1. 7.1 Launch the GDB Server (Windows)
      2. 7.2 Launch the GDB Server (Linux)
      3. 7.3 Configure Eclipse Debugger
      4. 7.4 Running the Software Example From Debugger
    9. 8 References
  2. AMakefile
    1. A.1 Makedefs
    2. A.2 Makefile
  3. BLinker and Startup Files
    1. B.1 Linker File
    2. B.2 Startup Files

Build the Software Example

  1. On Windows, specify the make tool you are using. Navigate to Project → Properties → C/C++ build. Under the tab 'Builder Settings', uncheck 'Use default build command' and type in the build command you are using. If you are using the MinGW tools, the command will be mingw32-make.
  2. If you have a device that is different from the CC2650F128RGZ device, open the file called 'makedefs' in the project directory and change the variable called CHIP_ID to the ID that suits your device.
  3. Right click the project and select 'Build Project'. This will create the binary files blink_led.bin and blink_led.elf.
  4. On Windows, the console output from the build command should be as shown in Figure 12.

    build_project_swra446.gifFigure 12. Build Project

    NOTE

    On Linux, if the build fails and arm-none-eabi-gcc is not found, you must edit the file called makedefs. Modify the CC and OBJCOPY variables by adding the full path to arm-none-eabi-gcc and to arm-none-eabi-objcopy. These tools are both found in the bin folder under where GNU Tools for ARM Embedded Processors was installed.

  5. Right click blink_led and select 'Clean Project' if you want to clean the project. On Windows, the console output from the build command should be as shown in Figure 13.
  6. clean_project_swra446.gifFigure 13. Clean Project