Skip to main content

TinyCLR Config

TinyCLR Config

TinyCLR Config is a stand-alone tool for managing SITCore devices — firmware installation, encrypted application deployment, device configuration, and inspection. Get it from the Downloads page.

Connecting to a device​

When TinyCLR Config opens, the Device section is near the top of the window. Plug your device into USB, click the Select a device dropdown, pick your device from the list, then click Connect.

Updating firmware​

  1. Put the device in bootloader mode (hold LDR low while resetting — see Special Pins).
  2. Connect TinyCLR Config to the device.
  3. Click the ... button next to Update Firmware, then select a .ghi or .glb firmware file.
  4. Click Update Firmware.

The Erase → Erase All option erases both the firmware and the application. This isn't required for a firmware update, but it can help when a device is misbehaving.

Deploying encrypted applications​

TinyCLR Config can package your compiled application as an encrypted deployment file (.tca) that requires a key to install. This is the path for production deployments — the application code is not readable on the device without the key.

Creating a deployment file​

  1. Install the application on the device first, then connect TinyCLR Config to that device.
  2. Provide a key — either type one into the key box (hexadecimal pairs separated by hyphens) or click Generate Key to create a random one.
  3. Optionally, enter a version number in Version of created app.
  4. Click ... next to Create App and choose where to save the file.
  5. Click Create App. TinyCLR Config writes the encrypted deployment file (.tca) and a text file containing the key to the directory you chose.

Installing a deployment file​

  1. Connect TinyCLR Config to the target device.
  2. Click ... next to Update App and select the .tca file.
  3. Enter the matching key in the key box.
  4. Click Update App. If the key matches the file, the application is deployed to the device.

Device configuration​

The device configuration window (Utilities → Update Configuration) has options with important security implications. There are two regions: Firmware Config and Application Config.

Firmware Config​

Stored in flash. Changes only take effect after re-flashing the firmware or running Erase All.

  • Extend heap — uses external RAM for the system heap. Reduces security. See External Memory for the implications.
  • Persist slow clock — runs the system clock at half speed, saving about 40% power. See Power Management.
  • Disable APP pin, Debug Mode, Device Name — change or disable APP and MOD pin behavior. See Device Info.

Application Config​

Stored in flash. Persisted across firmware updates — only Erase All resets it.

For added security, the debug interface can be disabled here. Secure production designs typically disable the debug interface and rely on In-Field Update for firmware updates after deployment.

You can also disable the debug interface from within your application code — see IP Protection for the full security pattern.

Utilities​

The Utilities and Assemblies menus provide tools for inspecting and managing a connected device.

  • Assemblies → Assemblies Listing — lists all assemblies installed on the device along with their version numbers.
  • Utilities → Ping — verifies the device is responding.
  • Utilities → Reboot — restarts the device.
  • Utilities → Deployment Map — see below.

Deployment map​

Deployment Map

The Deployment Map shows how the device's flash is used by your application. Beyond resource accounting, it confirms that your assemblies are stored in secure internal flash rather than external flash — important for protecting application code on shipped devices. See IP Protection for the security implications.