Skip to content

Enable Offline Capabilities

This guide covers enabling the ToloMEO offline stack, which lets a device keep working and buffering data while it is disconnected, both in the reference build and in your own integration project.

The stack pairs a local time-series database with ToloMEO Bridge (tlm-bridge), a local retention and cloud relay service. It is delivered by the meta-tolomeo-offline layer and is disabled by default.

Prerequisites

  • A ToloMEO Bridge access token. ToloMEO Bridge is fetched from a private repository, and offline capabilities are a licensed feature: request a token from DAVE Embedded Systems sales at sales@dave.eu.

Export the Access Token

Export the token, quoted, in the shell that runs kas:

export TLM_GITLAB_TOKEN="<access-token>"

The tlm-bridge recipe embeds the token in its fetch URL, authenticating as the TLM_GITLAB_USER user, which defaults to oauth2. Override TLM_GITLAB_USER only if DAVE instructs you to.

Enable Offline in the Reference Build

Append the kas/offline.yml fragment to the target configuration:

kas build kas/tolomeo-qemux86-64_tolomeo-prod_image-prod.yml:kas/offline.yml

kas/offline.yml enables the meta-tolomeo-offline layer and includes kas/gitlab-auth.yml, which forwards TLM_GITLAB_USER and TLM_GITLAB_TOKEN to BitBake. The other targets (image-devel, image-test-prod) opt in the same way. A build without the fragment needs no token.

Enable Offline in Your Own Project

When you integrate meta-tolomeo as a source layer (see Build Your Own BSP Layer), enable offline from your own kas configuration:

  1. Enable the layer — add meta-tolomeo-offline to the meta-tolomeo layer list in your kas configuration.
  2. Forward the credentials — include the shared credential fragment (see kas Configuration) so the token reaches BitBake:

    header:
      includes:
        - repo: meta-tolomeo
          file: kas/gitlab-auth.yml
    
  3. Supply the token — export TLM_GITLAB_TOKEN as shown above before building.

Reuse for other private repositories

kas/gitlab-auth.yml exposes a generic TLM_GITLAB_USER / TLM_GITLAB_TOKEN pair. Reuse the same pair for any other DAVE private repository your project fetches; introduce a distinct variable only if a repository needs a different credential.

Troubleshooting

tlm-bridge: required variable(s) not set: TLM_GITLAB_TOKEN

Parsing stopped before any fetch because the token did not reach BitBake. Export TLM_GITLAB_TOKEN in the shell that runs kas, and check that your kas configuration includes kas/gitlab-auth.yml, directly or through kas/offline.yml.

A GitLab sign-in dialog appears during the build

Most often the token was exported unquoted, so the shell mangled it before the build could use it. Export it quoted:

export TLM_GITLAB_TOKEN="<access-token>"

If the dialog still appears, git is falling back to its interactive credential helper. Disable the prompt so the build fails with an error:

export GIT_TERMINAL_PROMPT="0"
unset GIT_ASKPASS SSH_ASKPASS

Fetch fails with an authentication error

Check that the token is non-empty and matches the one DAVE provided. A valid-looking token that is still rejected may have expired or lost access — contact DAVE to have it renewed. Test it directly:

GIT_TERMINAL_PROMPT=0 GIT_ASKPASS= git ls-remote \
  "https://oauth2:${TLM_GITLAB_TOKEN}@gitlab.com/DAVEEmbeddedSystems/innovation-lab/tlm/edge/linux/tlm-bridge.git"

See also