Gocator Development Kit
 All Classes Files Functions Variables Typedefs Friends Modules Pages
Getting Started

The Gocator Development Kit (GDK) provides a complete framework for the development, testing and deployment of custom Gocator firmware.

Using this kit, custom firmware upgrade packages containing custom tools can be generated and loaded onto sensors.

Build Pre-requisites

The GDK build system has the following pre-requisites:

  • Microsoft Visual Studio 2013
  • Python 3.4 or later
  • For Arm7 builds:
    • GCC ARM tools 4.9.3-p2
  • For C64x builds:
    • Texas Instruments C6000 Code Generation Tools 7.4.13
    • Texas Instruments BIOS 5.42.01.09

Visual Studio 2013

Microsoft Visual Studio 2013 is needed for development and debugging. Debugging is supported only for Desktop targets (i.e. Win32). No debugging support is provided for the embedded targets.

Python

The build steps for the GDK are automated using the Python programming language. The Python distribution can be downloaded for free. Use Python version 3.4 or later. After installation make sure the python.exe is in the %PATH% environment variable.

Link: https://www.python.org/downloads/

GCC ARM tools

The GCC ARM tools are currently distributed as a tarball for Win32 only. The tools need to be installed at C:\tools\GccArm-4.9.3-p2. Use the following Python command to extract the tarball into the correct destination directory:

1 python -m tarfile -e arm-unknown-elf_4.9.3-p2_win32.tar.bz2 C:\tools\GccArm-4.9.3-p2

Source code and patches to GCC can be obtained by sending a request to suppo.nosp@m.rt@l.nosp@m.mi3d..nosp@m.com. LMI Technologies will not provide support for rebuilding the GCC tools from source code.

TI C6000 Code Generation Tools

The Texas Instruments C6000 Code Generation Tools 7.4.13 need to be installed at C:\ti\cgtools_7.4.13.

Installer: ti_cgt_c6000_7.4.13_windows_installer.exe

TI BIOS

The Texas Instruments BIOS package needs to be installed at C:\ti\bios_5_42_01_09.

Installer: bios_setupwin32_5_42_01_09.exe

Sample

A sample project can be found under Gocator\GdkSampleApp. This project can be built and used directly. It can also serve as a template for new projects.

The supplied sample project will build either a win32 DLL (for use with the emulator) or a sensor firmware upgrade package.

Building a GDK application

  • Open the GDK Visual Studio solution, i.e. Gocator\Gdk.sln
  • Choose your target:
    • Select Win32 for debugging and emulation
    • Select Arm7 for current Gocator devices
    • Select C64x for Gocator legacy devices
  • Build the solution using <CTRL>+<Shift>+B

Running a GDK application

Debugging using the emulator

  1. Build virtual device using a Win32 target.
  2. Make sure the output file is built into bin\win32 or bin\win32d
  3. Set the UserAppName field in the GsGlobalCfg.xml file to match the output file name (without the ".dll" extension)
1 <?xml version="1.0" encoding="UTF-8"?>
2 <GsGlobalCfg version="1">
3  <UserAppName>GdkSampleApp</UserAppName>
4 </GsGlobalCfg>

The emulator will now use the custom GDK module when emulating scenarios. It is possible to attach a debugger to the kFramework.exe process at run time for debugging.

Using a Gocator sensor

Custom upgrade packages are built into the pkg directory. These upgrade packages can be loaded to a Gocator sensor using the firmware upgrade process.

Recover from bad firmware

Use the following steps to recover from bad firmware:

  • Power off the device
  • Make sure the device is directly connected to the PC – don't use a switch
  • Configure the PC as to use IP-address: 192.168.1.1 and netmask: 255.255.0.0
  • Start the kRescue application bin\win32\kRescue.exe
  • Power on the device
  • Close the kRescue application
  • Open a browser and point it to http://192.168.1.10
  • Apply an upgrade package that is known to work