close
OpenRTLS
OpenRTLS
Search

Software:GIT Account

OpenRTLS uses GIT for version control of files.

1. Prepare public/private keys

In order to use repositories at OpenRTLS you need to generate a private/public key pair.

Open GIT command window, enter:

$ ssh-keygen -t rsa -f ~/.ssh/id_rsa_openrtls

Two files will be generated in the default folder with the same name but different extensions (GIT tells where they are). One file is .pub, which is the public key. The other file without any extension is the private key.

Send the public key ~/.ssh/id_rsa_openrtls.pub to OpenRTLS to request for an account. Always protect your private key ~/.ssh/id_rsa_openrtls.

Info: Default key name is ~/.ssh/id_rsa


2. Repository checkout

If you have a GIT account on OpenRTLS server, use the following command to check out the repositories:

 $ git clone ssh://git@git.openrtls.com/<repository-name>.git

or you can use shorter notation of the same command:

 $ git clone git@git.openrtls.com:<repository-name>.git

Make sure you have your private key in ~/.ssh/id_rsa or ~/.ssh/id_dsa or with the file name that is generated in step 1 above.

Otherwise, if your private key is stored under a different filename, you can change ~/.ssh/config to specify your key file:

$ cat ~/.ssh/config
Host git.openrtls.com
  User git
  IdentityFile ~/.ssh/id_rsa_openrtls           ← name of the private key

To validate whether your key pair is working, enter:

$ ssh -v git@git.openrtls.com

If the last line is "permission denied" then you have to check your steps for generating keys.


The following repositories are available for read-only checkout:

119-antboot           - AntBoot - small and versatile bootloader
120-ecos-current      - eCos Real-Time Operating System
202-openocd-current   - OpenOCD master branch (with modification
                        to support SAM4E/Cortex-M4 and SAMA5D3X/Cortex-A5)
810-tdk               - RTLS Tag Development repository