HW wiki - User contributions [en]

Xilinx Vivado

2019-09-20T20:56:57Z

Sojka: /* Tips, Tricks, Workarounds */

== Tips, Tricks, Workarounds ==

* For remote hosts (Tools → Settings → Remote Hosts → Manual Configuration) to work (at least on Debian system) ''sh'' command on local system must run ''bash'', not ''dash''. If you don't want to set this globally, the following command does it only for Vivado: <tt>ln -s /bin/bash /opt/Xilinx/Vivado/2019.1/bin/sh</tt>

* DocNav complains about SSL and you cannot download anything. See [https://www.xilinx.com/support/answers/72509.html this]. On Debian, solve it with downloading [https://packages.debian.org/stretch/amd64/libssl1.0.2/download libssl1.0.2] and copying the content of ''/usr/lib/x86_64-linux-gnu/'' to ''/opt/Xilinx/DocNav/lib''. Then create a symlink as follows: <tt>ln -s libssl.so.1.0.2 /opt/Xilinx/DocNav/lib/libssl.so</tt>

Xilinx Vivado

2019-09-04T19:45:17Z

Sojka: /* Tips, Tricks, Workarounds */

== Tips, Tricks, Workarounds ==

* For remote hosts (Tools → Settings → Remote Hosts → Manual Configuration) to work (at least on Debian system) ''sh'' command on local system must run ''bash'', not ''dash''. If you don't want to set this globally, the following command does it only for Vivado: <tt>ln -s /bin/bash /opt/Xilinx/Vivado/2019.1/bin/sh</tt>

* DocNav complains about SSL and you cannot download anything. See [https://www.xilinx.com/support/answers/72509.html this]. On Debian, solve it with downloading [https://packages.debian.org/stretch/amd64/libssl1.0.2/download libssl1.0.2] and copying the content of ''/usr/lib/x86_64-linux-gnu/'' to ''/opt/Xilinx/DocNav/lib''. The create a symlink as follows: <tt>ln -s libssl.so.1.0.2 /opt/Xilinx/DocNav/lib/libssl.so</tt>

Xilinx Vivado

2019-09-04T19:44:32Z

Sojka: /* Tips, Tricks, Workarounds */

== Tips, Tricks, Workarounds ==

* For remote hosts (Tools → Settings → Remote Hosts → Manual Configuration) to work (at least on Debian system) ''sh'' command must run ''bash'', not ''dash''. If you don't want to set this globally, the following command does it only for Vivado: <tt>ln -s /bin/bash /opt/Xilinx/Vivado/2019.1/bin/sh</tt>

* DocNav complains about SSL and you cannot download anything. See [https://www.xilinx.com/support/answers/72509.html this]. On Debian, solve it with downloading [https://packages.debian.org/stretch/amd64/libssl1.0.2/download libssl1.0.2] and copying the content of ''/usr/lib/x86_64-linux-gnu/'' to ''/opt/Xilinx/DocNav/lib''. The create a symlink as follows: <tt>ln -s libssl.so.1.0.2 /opt/Xilinx/DocNav/lib/libssl.so</tt>

Xilinx Vivado

2019-09-04T19:44:22Z

Sojka: /* Tips, Tricks, Workarounds */

Xilinx Vivado

2019-09-04T19:39:40Z

Sojka: /* Tips, Tricks, Workarounds */

Xilinx Vivado

2019-09-04T19:39:11Z

Sojka: Created page with " == Tips, Tricks, Workarounds == * For remote hosts (Tools → Settings → Remote Hosts → Manual Configuration) to work (at least on Debian system) ''sh'' command must run..."

Template:Main Page/Software

2019-09-04T19:33:44Z

Sojka: /* Software */

== Software ==

* [[System-Less Framework]]
* [[OMK]]
* [[OSELAS.Toolchain]]
* [[Cross compilers]]
* [[How to build GNU cross-compilers]]
* [[RTEMS]]
* [[Code Porting]]
* [[Xilinx ISE]]
* [[Xilinx Vivado]]

Git repository on this server

2019-04-12T13:54:51Z

Sojka: /* Creating repositories */

Repositories on rtime server are managed by [http://github.com/sitaramc/gitolite Gitolite tool], which allows to conveniently manage repository permissions. World readable repositories can be [http://rtime.felk.cvut.cz/gitweb browsed online].

In addition to gitolite repositories, users with shell account can create [[Git repositories in home directories|Git repositories in their home directory]]. This does not require any coordination with the administrator.

== Getting write access to repositories ==

Write access to the repositories can only be given to users who send the following information to the [http://rtime.felk.cvut.cz/~sojka/ administrator]:

# OpenSSH public key
# Login name (for ČVUT people) or email address (for others).

=== SSH key creation ===

The SSH key can be created with one of the following ways. Note that under Windows, methods 1 and 2 only work if [[Media:git-plink.jpg|OpenSSH]] has been selected during Git installation.

# Under Linux/Unix (or in Git Bash under Windows) run: <pre>ssh-keygen</pre>
# In Git Gui (under Linux or Windows) choose [[Media:Git-gui-key.jpg|Help -> Show SSH key -> Generate key]].
# Under Windows use PuTTYgen. Use this if you have chosen to [[Media:git-plink.jpg|use Plink]] during Git installation.

It is stored by default at <tt>~/.ssh/id_rsa.pub</tt>.

=== Password-protected keys ===

During the key creation you will be asked for a passphrase. If you do not specify any passphrase, anybody with access to your <tt>~/.ssh</tt> directory could access your repositories. If you specify the passphrase, it will need to be entered whenever you want to push to or pull from the server. By using <tt>ssh-add</tt> command (or Pageant program under Windows) you can specify the passphrase only once and the decrypted key will be remembered in the memory.

== Creating repositories ==

There are two ways how a repository can be created:

# Send an email to the [http://rtime.felk.cvut.cz/~sojka/ administrator] with the name of the repository, a short description and a list of people (login or email) who should have access to the repository. The administrator creates the repository for you and notifies you when it's done.
# Our group staff members can create their repositories without asking the administrator. See below.

=== Automatic creation of repositories (staff members only) ===

It is simply a matter of pushing the repository to a special URL containing the login, like this:

git push --set-upstream ssh://git@rtime.felk.cvut.cz/«login»/«whatever» HEAD

This will create a new repository called «whatever» (if it does not exist yet) and push the current HEAD to it. It also makes this repository the default for pushing and pulling (this is what --set-upstream does).

Such repository is by default accessible only to the creator. If you want this repository to be public, run
ssh git@rtime.felk.cvut.cz perms «login»/«whatever» + READERS @all

If you want to set a [https://rtime.felk.cvut.cz/gitweb/orte.git Gitweb description] for public repositories created this way, use gitolite's desc commands. I.e. you can set the description by:
ssh git@rtime.felk.cvut.cz desc «login»/«whatever» "Description"

== Accessing the repository ==

After [[Git#Install_Git|installing Git]] on your local computer, you
can access the repository as follows.

=== Cloning the repository ===

Read/Write access (for users with registered SSH key):
git clone ssh://git@rtime.felk.cvut.cz/''repo-name''

Read-only access (for public repositories only):
git clone git://rtime.felk.cvut.cz/''repo-name''.git
git clone http://rtime.felk.cvut.cz/git/''repo-name''.git

=== First push to admin-created repositories ===

After an empty repository is created by the admin, you can push (i.e. upload) the data to it:

* [[#Cloning the repository|Clone]] the empty repository.
* Put your sources into your cloned repository
git add . # tells git to track all files in your project
git commit # commits the added files to the repository
* Push your sources to the server
git push

=== Pushing to non-master branches ===

If you are not allowed to push to the master branch but to a different one, you have to push like this:
git push origin master:your-branch
which pushes your local master branch to the remote branch ''your-branch''.

To make this behavior default run
git config remote.origin.push master:your-branch

And from now on, it is sufficient to run only
git push

== Managing repositories ==

=== Finding available repositories ===

You can find the list of repositories you have access to by running:

ssh git@rtime.felk.cvut.cz info [filter]

where filter is optional string used to filter the list.

=== Permissions to automatic repositories ===

The owners of automatically created repositories can manage the access permissions by themselves.

The current permissions can be listed by:

ssh git@rtime.felk.cvut.cz perms -l «repo»

You can add permissions for either reading of writing the repo with:
ssh git@rtime.felk.cvut.cz perms «repo» + READERS «login»
ssh git@rtime.felk.cvut.cz perms «repo» + WRITERS «login»

The permissions can be removed by replacing '''+''' with '''-'''.

To make your repository visible on [https://rtime.felk.cvut.cz/gitweb/ gitweb], run:
ssh git@rtime.felk.cvut.cz perms «repo» + READERS @all

== Links to git related documents ==

* [http://support.dce.felk.cvut.cz/mediawiki/index.php/gitolite Gitolite documentation on DCE IT pages]

[[Category:Git]]

Git repository on this server

2019-02-26T11:11:44Z

Sojka: /* SSH key creation */

Repositories on rtime server are managed by [http://github.com/sitaramc/gitolite Gitolite tool], which allows to conveniently manage repository permissions. World readable repositories can be [http://rtime.felk.cvut.cz/gitweb browsed online].

In addition to gitolite repositories, users with shell account can create [[Git repositories in home directories|Git repositories in their home directory]]. This does not require any coordination with the administrator.

== Getting write access to repositories ==

Write access to the repositories can only be given to users who send the following information to the [http://rtime.felk.cvut.cz/~sojka/ administrator]:

# OpenSSH public key
# Login name (for ČVUT people) or email address (for others).

=== SSH key creation ===

The SSH key can be created with one of the following ways. Note that under Windows, methods 1 and 2 only work if [[Media:git-plink.jpg|OpenSSH]] has been selected during Git installation.

# Under Linux/Unix (or in Git Bash under Windows) run: <pre>ssh-keygen</pre>
# In Git Gui (under Linux or Windows) choose [[Media:Git-gui-key.jpg|Help -> Show SSH key -> Generate key]].
# Under Windows use PuTTYgen. Use this if you have chosen to [[Media:git-plink.jpg|use Plink]] during Git installation.

It is stored by default at <tt>~/.ssh/id_rsa.pub</tt>.

=== Password-protected keys ===

During the key creation you will be asked for a passphrase. If you do not specify any passphrase, anybody with access to your <tt>~/.ssh</tt> directory could access your repositories. If you specify the passphrase, it will need to be entered whenever you want to push to or pull from the server. By using <tt>ssh-add</tt> command (or Pageant program under Windows) you can specify the passphrase only once and the decrypted key will be remembered in the memory.

== Creating repositories ==

There are to ways how a repository can be created:

# Send an email to the [http://rtime.felk.cvut.cz/~sojka/ administrator] with the name of the repository, a short description and a list of people (login or email) who should have access to the repository. The administrator creates the repository for you and notifies you when it's done.
# Our group staff members can create their repositories without asking the administrator. See below.

=== Automatic creation of repositories (staff members only) ===

It is simply a matter of pushing the repository to a special URL containing the login, like this:

git push --set-upstream ssh://git@rtime.felk.cvut.cz/«login»/«whatever» HEAD

This will create a new repository called «whatever» (if it does not exist yet) and push the current HEAD to it. It also makes this repository the default for pushing and pulling (this is what --set-upstream does).

Such repository is by default accessible only to the creator. If you want this repository to be public, run
ssh git@rtime.felk.cvut.cz perms «login»/«whatever» + READERS @all

If you want to set a [https://rtime.felk.cvut.cz/gitweb/orte.git Gitweb description] for public repositories created this way, use gitolite's desc commands. I.e. you can set the description by:
ssh git@rtime.felk.cvut.cz desc «login»/«whatever» "Description"

== Accessing the repository ==

After [[Git#Install_Git|installing Git]] on your local computer, you
can access the repository as follows.

=== Cloning the repository ===

Read/Write access (for users with registered SSH key):
git clone ssh://git@rtime.felk.cvut.cz/''repo-name''

Read-only access (for public repositories only):
git clone git://rtime.felk.cvut.cz/''repo-name''.git
git clone http://rtime.felk.cvut.cz/git/''repo-name''.git

=== First push to admin-created repositories ===

After an empty repository is created by the admin, you can push (i.e. upload) the data to it:

* [[#Cloning the repository|Clone]] the empty repository.
* Put your sources into your cloned repository
git add . # tells git to track all files in your project
git commit # commits the added files to the repository
* Push your sources to the server
git push

=== Pushing to non-master branches ===

If you are not allowed to push to the master branch but to a different one, you have to push like this:
git push origin master:your-branch
which pushes your local master branch to the remote branch ''your-branch''.

To make this behavior default run
git config remote.origin.push master:your-branch

And from now on, it is sufficient to run only
git push

== Managing repositories ==

=== Finding available repositories ===

You can find the list of repositories you have access to by running:

ssh git@rtime.felk.cvut.cz info [filter]

where filter is optional string used to filter the list.

=== Permissions to automatic repositories ===

The owners of automatically created repositories can manage the access permissions by themselves.

The current permissions can be listed by:

ssh git@rtime.felk.cvut.cz perms -l «repo»

You can add permissions for either reading of writing the repo with:
ssh git@rtime.felk.cvut.cz perms «repo» + READERS «login»
ssh git@rtime.felk.cvut.cz perms «repo» + WRITERS «login»

The permissions can be removed by replacing '''+''' with '''-'''.

To make your repository visible on [https://rtime.felk.cvut.cz/gitweb/ gitweb], run:
ssh git@rtime.felk.cvut.cz perms «repo» + READERS @all

== Links to git related documents ==

* [http://support.dce.felk.cvut.cz/mediawiki/index.php/gitolite Gitolite documentation on DCE IT pages]

[[Category:Git]]

NVIDIA Jetson TX2

2019-01-28T11:36:13Z

Sojka: /* Tips and tricks */

== Remote access to the TX2 board ==

We have a remotely manageable NVIDIA Jetson TX2 kit. You can remotely power on/off and reset the board. Also the serial debug interface is available through the SSH connection. Maintainer of this board is [mailto:michal.sojka@cvut.cz Michal Sojka]. If you want to get access to the board or something does not work as expected, contact him.

The TX2 is connected to a local network accessible from rtime.felk.cvut.cz server.

Only single user can be logged remotely at the same time using the following procedure. In case another user is already logged in you will see a message indicating this and you will be granted access to the kit as soon as the other user disconnects.

For remote access to the kit you need to follow these steps:

1. Use Linux distribution and have SSH client installed. On Debian-based distributions you can use the following commands:

$ sudo apt-get update
$ sudo apt-get install openssh-client

2. Generate a public/private SSH keypair.

$ ssh-keygen

3. Send the generated public key to [mailto:michal.sojka@cvut.cz Michal Sojka]. You should get a response afterwards indicating, that You now have access to the TX2.

4. Now You can remotely access the TX2 by issuing commands from next sections:

=== Remote power-cycle/reset ===

To power on the kit use:
$ ssh tx2@rtime.felk.cvut.cz on

To forcefully power off the kit (i.e. equivalent to holding the power button on the TX2 for a few seconds) use:
$ ssh tx2@rtime.felk.cvut.cz off

To reset the kit use:
$ ssh tx2@rtime.felk.cvut.cz reset

=== Command line access ===

==== Serial console over SSH ====

To gain access to the serial console use:
$ ssh tx2@rtime.felk.cvut.cz

==== SSH from CIIRC network (IIG vlan) ====

If you are in CIIRC and your IP address starts with 10.35.95.*, don't need to use port forwarding. Just use:

$ ssh nvidia@tx2-stud

==== SSH from non-CIIRC network ====

In order to login through SSH to TX2 you need to setup port forwarding in the above (serial console) command:
$ ssh -L 2222:tx2-stud:22 tx2@rtime.felk.cvut.cz

If you want to be able to use ROS nodes on both the TX2 and your own PC, then you will need to forward additional ports:
$ ssh -L 2222:tx2-stud:22 -L 11311:tx2-stud:11311 tx2@rtime.felk.cvut.cz

These commands will open a remote serial console on the TX2 and forward port 22 (used by SSH server) to port 2222 your local machine (the second command forwards also port 11311 used by ROS). Then you can finally connect to the TX2 through SSH by opening another terminal and issuing the following command (do no disconnect the previous ssh connection, otherwise the port forwarding from the internal CTU network will stop working):
$ ssh -p 2222 nvidia@localhost

You can use whatever user account on the TX2 you want instead of 'nvidia'.

=== Disconnect ===

In order to disconnect from the TX2, you first close the ssh opened through the forwarded port (by pressing Ctrl+D) and then you press '~.' to close the serial console ssh session. Sometimes it does not work for the first time, if this is the case you have to press Enter and input '~.' again.

There is an auto power down feature, that ensures the TX2 is switched off if not used for prolonged periods in order to save energy. This is accomplished in a way that is equivalent to using:
$ ssh tx2@rtime.felk.cvut.cz off

This can cause data loss. In order to avoid that use the following command before logging out of the TX2:
$ sync

It is also advisable not to leave tasks running (e.g. by launching the 'screen' program and then detaching) on the TX2 and logout, because the board might shut down.

== Tips and tricks ==

* When you want to copy the filesystem from one board to another or to a NFS server for network boot, delete <tt>/var/lib/dhcp/dhclient.leases</tt> file. Otherwise the board changes its IP address during boot to that of the original board, which causes things like IP address collision or inability to communicate with the NFS server.

* When you add a new user, add him/her at least to the <tt>video</tt> group. This is necessary to run CUDA programs.

NVIDIA Jetson TX2

2019-01-23T14:30:06Z

Sojka:

NVIDIA Jetson TX2

2019-01-23T14:27:50Z

Sojka:

NVIDIA Jetson TX2

2018-12-13T09:47:35Z

Sojka:

We have a remotely manageable NVIDIA Jetson TX2 kit. You can remotely power on/off and reset the board. Also the serial debug interface is available through the SSH connection. Maintainer of this board is [mailto:martin.vajnar@cvut.cz Martin Vajnar]. If you want to get access to the board or something does not work as expected, contact him.

The TX2 is connected to a local network accessible from rtime.felk.cvut.cz server.

Only single user can be logged remotely at the same time using the following procedure. In case another user is already logged in you will see a message indicating this and you will be granted access to the kit as soon as the other user disconnects.

== Remote SSH access to the TX2 ==

For remote access to the kit you need to follow these steps:

1. Use Linux distribution and have SSH client installed. On Debian-based distributions you can use the following commands:

$ sudo apt-get update
$ sudo apt-get install openssh-client

2. Generate a public/private SSH keypair.

$ ssh-keygen

3. Send the generated public key to [mailto:michal.sojka@cvut.cz Michal Sojka]. You should get a response afterwards indicating, that You now have access to the TX2.

4. Now You can remotely access the TX2 by issuing commands from next sections:

=== Remote power-cycle/reset ===

To power on the kit use:
$ ssh tx2@rtime.felk.cvut.cz on

To forcefully power off the kit (i.e. equivalent to holding the power button on the TX2 for a few seconds) use:
$ ssh tx2@rtime.felk.cvut.cz off

To reset the kit use:
$ ssh tx2@rtime.felk.cvut.cz reset

=== Command line access ===

==== Serial console over SSH ====

To gain access to the serial command line use:
$ ssh tx2@rtime.felk.cvut.cz

==== SSH from non-CIIRC network ====

In order to login through SSH to TX2 you need to setup port forwarding in the above command:
$ ssh -L 2222:tx2-stud:22 tx2@rtime.felk.cvut.cz

If you want to be able to use ROS nodes on both the TX2 and your own PC, then you will need to forward additional ports:
$ ssh -L 2222:tx2-stud:22 -L 11311:tx2-stud:11311 tx2@rtime.felk.cvut.cz

These commands will open a remote serial console on the TX2 and forward port 22 (used by SSH server) to port 2222 your local machine (the second command forwards also port 11311 used by ROS). Then you can finally connect to the TX2 through SSH by opening another terminal and issuing the following command (do no disconnect the previous ssh connection, otherwise the port forwarding from the internal CTU network will stop working):
$ ssh -p 2222 nvidia@localhost

You can use whatever user account on the TX2 you want instead of 'nvidia'.

==== SSH from CIIRC network (IIG vlan) ====

If you are in CIIRC and your IP address starts with 10.35.95.*, don't need to use port forwarding. Just use:

$ ssh nvidia@tx2-stud

=== Disconnect ===

In order to disconnect from the TX2, you first close the ssh opened through the forwarded port (by pressing Ctrl+D) and then you press '~.' to close the serial console ssh session. Sometimes it does not work for the first time, if this is the case you have to press Enter and input '~.' again.

There is an auto power down feature, that ensures the TX2 is switched off if not used for prolonged periods in order to save energy. This is accomplished in a way that is equivalent to using:
$ ssh tx2@rtime.felk.cvut.cz off

This can cause data loss. In order to avoid that use the following command before logging out of the TX2:
$ sync

It is also advisable not to leave tasks running (e.g. by launching the 'screen' program and then detaching) on the TX2 and logout, because the board might shut down.

NVIDIA Jetson TX2

2018-02-20T14:31:01Z

Sojka:

We have a remotely manageable NVIDIA Jetson TX2 kit. You can remotely power on/off and reset the board. Also the serial debug interface is available through the SSH connection. Maintainer of this board is [mailto:martin.vajnar@cvut.cz Martin Vajnar]. If you want to get access to the board or something does not work as expected, contact him.

The TX2 is connected to a local network accessible from rtime.felk.cvut.cz server.

Only single user can be logged remotely at the same time using the following procedure. In case another user is already logged in you will see a message indicating this and you will be granted access to the kit as soon as the other user disconnects.

== Remote SSH access to the TX2 ==

For remote access to the kit you need to follow these steps:

1. Use Linux distribution and have SSH client installed. On Debian-based distributions you can use the following commands:

$ sudo apt-get update
$ sudo apt-get install openssh-client

2. Generate a public/private SSH keypair.

$ ssh-keygen

3. Send the generated public key to [mailto:martin.vajnar@cvut.cz Martin Vajnar]. You should get a response afterwards indicating, that You now have access to the TX2.

4. Now You can remotely access the TX2 by issuing commands from next sections:

=== Remote power-cycle/reset ===

To power on the kit use:
$ ssh tx2@rtime.felk.cvut.cz on

To forcefully power off the kit (i.e. equivalent to holding the power button on the TX2 for a few seconds) use:
$ ssh tx2@rtime.felk.cvut.cz off

To reset the kit use:
$ ssh tx2@rtime.felk.cvut.cz reset

=== Command line access ===

==== Serial console over SSH ====

To gain access to the serial command line use:
$ ssh tx2@rtime.felk.cvut.cz

==== SSH from non-CIIRC network ====

In order to login through SSH to TX2 you need to setup port forwarding in the above command:
$ ssh -L 2222:tx2-stud:22 tx2@rtime.felk.cvut.cz

If you want to be able to use ROS nodes on both the TX2 and your own PC, then you will need to forward additional ports:
$ ssh -L 2222:tx2-stud:22 -L 11311:tx2-stud:11311 tx2@rtime.felk.cvut.cz

These commands will open a remote serial console on the TX2 and forward port 22 (used by SSH server) to port 2222 your local machine (the second command forwards also port 11311 used by ROS). Then you can finally connect to the TX2 through SSH by opening another terminal and issuing the following command (do no disconnect the previous ssh connection, otherwise the port forwarding from the internal CTU network will stop working):
$ ssh -p 2222 nvidia@localhost

You can use whatever user account on the TX2 you want instead of 'nvidia'.

==== SSH from CIIRC network (IIG vlan) ====

If you are in CIIRC and your IP address starts with 10.35.95.*, don't need to use port forwarding. Just use:

$ ssh nvidia@tx2-stud

=== Disconnect ===

In order to disconnect from the TX2, you first close the ssh opened through the forwarded port (by pressing Ctrl+D) and then you press '~.' to close the serial console ssh session. Sometimes it does not work for the first time, if this is the case you have to press Enter and input '~.' again.

There is an auto power down feature, that ensures the TX2 is switched off if not used for prolonged periods in order to save energy. This is accomplished in a way that is equivalent to using:
$ ssh tx2@rtime.felk.cvut.cz off

This can cause data loss. In order to avoid that use the following command before logging out of the TX2:
$ sync

It is also advisable not to leave tasks running (e.g. by launching the 'screen' program and then detaching) on the TX2 and logout, because the board might shut down.

Zynq

2017-12-13T10:02:57Z

Sojka:

This page applies mostly to [http://microzed.org/product/microzed Microzed board] and to Microzed with our [https://cw.fel.cvut.cz/wiki/courses/b35apo/documentation/mz_apo/start MZ_APO extension board].

* Linux kenrel for Xilinx Zynq http://rtime.felk.cvut.cz/gitweb/zynq/linux.git

* Configs, Makefiles etc. for Linux on Xilinx Zynq http://rtime.felk.cvut.cz/gitweb/zynq/linux-build.git

* eLinux Wiki Zynq category http://elinux.org/Category:Zynq

* Toolchain for Debian or Ubuntu

* [https://www.xilinx.com/support/documentation/user_guides/ug585-Zynq-7000-TRM.pdf Zynq-7000 Technical Reference Manual]

echo "deb http://debian.pengutronix.de/debian/ sid main contrib non-free" >/etc/apt/sources.list.d/pengutronix.list
aptitude update
aptitude install oselas.toolchain-2014.12.2-arm-cortexa8-linux-gnueabihf-gcc-4.9.2-glibc-2.20-binutils-2.24-kernel-3.16-sanitized

Build kernel

mkdir zynq
git clone git://rtime.felk.cvut.cz/zynq/linux-build.git
cd linux-build
git submodule update --init

Check that toolchain location matches CROSS_COMPILE variable in [http://rtime.felk.cvut.cz/gitweb/zynq/linux-build.git/blob/refs/heads/master:/build/xlnx_4.0.8-rt6/linux/GNUmakefile build/xlnx_4.0.8-rt6/linux/GNUmakefile]. Then invoke

cd build/xlnx_4.0.8-rt6/linux/
make

U-boot arguments for MicroZed board

bootargs=root=/dev/mmcblk0p2 rw console=ttyPS1,115200 earlyprintk

Install Debian ARMhf distribution to the media on x86 host with use of chroot and qemu

Preparation of FPGA configuration files for direct FPGA configuration by Linux or U-boot requires to prepare <code>system.bif</code>:

all:
{
system.bit
}

then <code>bootgen</code> is used to prepare binary file

bootgen -image system.bif -w -process_bitstream bin

Runtime FPGA reconfiguration

cat system.bit.bin > /dev/xdevcfg

=== Debian Linux Install ===

Debootstrap on x86 system

Install

apt-get install binfmt-support qemu qemu-user-static debootstrap

Create directory for target system

mkdir debian_armhf

debootstrap --arch=armhf --foreign --include=debian-keyring,mc,libc6-de,libstdc ++6,busybox,aptitude jessie debian-armhf/ ftp://ftp.cz.debian.org/debian/

Install static version of QEMU which is able to interpret target architecture userspace programs

cp /usr/bin/qemu-arm-static debian_armhf/usr/bin

Finish the second stage of deboostrap

LC_ALL=C LANGUAGE=C LANG=C chroot debian_armhf /debootstrap/debootstrap --second-stage
LC_ALL=C LANGUAGE=C LANG=C chroot debian_armhf dpkg --configure -a

=== Booting VxWorks ===

In U-Boot:

dhcp
tftpboot 0x1000000 /zynq/vxWorks
setenv bootaddr 0x101100
setenv bootdev gem(0,0)
bootvx 0x1000000

Zynq

2017-12-13T10:00:44Z

Sojka: /* Debian Linux Install */

This page applies mostly to [http://microzed.org/product/microzed Microzed board] and to Microzed with our [https://cw.fel.cvut.cz/wiki/courses/b35apo/documentation/mz_apo/start MZ_APO extension board].

* Linux kenrel for Xilinx Zynq http://rtime.felk.cvut.cz/gitweb/zynq/linux.git

* Configs, Makefiles etc. for Linux on Xilinx Zynq http://rtime.felk.cvut.cz/gitweb/zynq/linux-build.git

* eLinux Wiki Zynq category http://elinux.org/Category:Zynq

* Toolchain for Debian or Ubuntu

echo "deb http://debian.pengutronix.de/debian/ sid main contrib non-free" >/etc/apt/sources.list.d/pengutronix.list
aptitude update
aptitude install oselas.toolchain-2014.12.2-arm-cortexa8-linux-gnueabihf-gcc-4.9.2-glibc-2.20-binutils-2.24-kernel-3.16-sanitized

Build kernel

mkdir zynq
git clone git://rtime.felk.cvut.cz/zynq/linux-build.git
cd linux-build
git submodule update --init

Check that toolchain location matches CROSS_COMPILE variable in [http://rtime.felk.cvut.cz/gitweb/zynq/linux-build.git/blob/refs/heads/master:/build/xlnx_4.0.8-rt6/linux/GNUmakefile build/xlnx_4.0.8-rt6/linux/GNUmakefile]. Then invoke

cd build/xlnx_4.0.8-rt6/linux/
make

U-boot arguments for MicroZed board

bootargs=root=/dev/mmcblk0p2 rw console=ttyPS1,115200 earlyprintk

Install Debian ARMhf distribution to the media on x86 host with use of chroot and qemu

Preparation of FPGA configuration files for direct FPGA configuration by Linux or U-boot requires to prepare <code>system.bif</code>:

all:
{
system.bit
}

then <code>bootgen</code> is used to prepare binary file

bootgen -image system.bif -w -process_bitstream bin

Runtime FPGA reconfiguration

cat system.bit.bin > /dev/xdevcfg

=== Debian Linux Install ===

Debootstrap on x86 system

Install

apt-get install binfmt-support qemu qemu-user-static debootstrap

Create directory for target system

mkdir debian_armhf

debootstrap --arch=armhf --foreign --include=debian-keyring,mc,libc6-de,libstdc ++6,busybox,aptitude jessie debian-armhf/ ftp://ftp.cz.debian.org/debian/

Install static version of QEMU which is able to interpret target architecture userspace programs

cp /usr/bin/qemu-arm-static debian_armhf/usr/bin

Finish the second stage of deboostrap

LC_ALL=C LANGUAGE=C LANG=C chroot debian_armhf /debootstrap/debootstrap --second-stage
LC_ALL=C LANGUAGE=C LANG=C chroot debian_armhf dpkg --configure -a

=== Booting VxWorks ===

In U-Boot:

dhcp
tftpboot 0x1000000 /zynq/vxWorks
setenv bootaddr 0x101100
setenv bootdev gem(0,0)
bootvx 0x1000000

Zynq

2017-12-13T09:59:04Z

Sojka:

This page applies mostly to [http://microzed.org/product/microzed Microzed board] and to Microzed with our [https://cw.fel.cvut.cz/wiki/courses/b35apo/documentation/mz_apo/start MZ_APO extension board].

* Linux kenrel for Xilinx Zynq http://rtime.felk.cvut.cz/gitweb/zynq/linux.git

* Configs, Makefiles etc. for Linux on Xilinx Zynq http://rtime.felk.cvut.cz/gitweb/zynq/linux-build.git

* eLinux Wiki Zynq category http://elinux.org/Category:Zynq

* Toolchain for Debian or Ubuntu

echo "deb http://debian.pengutronix.de/debian/ sid main contrib non-free" >/etc/apt/sources.list.d/pengutronix.list
aptitude update
aptitude install oselas.toolchain-2014.12.2-arm-cortexa8-linux-gnueabihf-gcc-4.9.2-glibc-2.20-binutils-2.24-kernel-3.16-sanitized

Build kernel

mkdir zynq
git clone git://rtime.felk.cvut.cz/zynq/linux-build.git
cd linux-build
git submodule update --init

Check that toolchain location matches CROSS_COMPILE variable in [http://rtime.felk.cvut.cz/gitweb/zynq/linux-build.git/blob/refs/heads/master:/build/xlnx_4.0.8-rt6/linux/GNUmakefile build/xlnx_4.0.8-rt6/linux/GNUmakefile]. Then invoke

cd build/xlnx_4.0.8-rt6/linux/
make

U-boot arguments for MicroZed board

bootargs=root=/dev/mmcblk0p2 rw console=ttyPS1,115200 earlyprintk

Install Debian ARMhf distribution to the media on x86 host with use of chroot and qemu

Preparation of FPGA configuration files for direct FPGA configuration by Linux or U-boot requires to prepare <code>system.bif</code>:

all:
{
system.bit
}

then <code>bootgen</code> is used to prepare binary file

bootgen -image system.bif -w -process_bitstream bin

Runtime FPGA reconfiguration

cat system.bit.bin > /dev/xdevcfg

=== Debian Linux Install ===

Debootstrap on x86 system

Install

apt-get install binfmt-support qemu qemu-user-static debootstrap

Create directory for target system

mkdir debian_armhf

debootstrap --arch=armhf --foreign --include=debian-keyring,mc,libc6-de,libstdc ++6,busybox,aptitude jessie debian-armhf/ ftp://ftp.cz.debian.org/debian/

Install static version of QEMU which is able to interpret target architecture userspace programs

cp /usr/bin/qemu-arm-static debian_armhf/usr/bin

Finish the second stage of deboostrap

LC_ALL=C LANGUAGE=C LANG=C chroot debian_armhf /debootstrap/debootstrap --second-stage
LC_ALL=C LANGUAGE=C LANG=C chroot debian_armhf dpkg --configure -a

Template:Main Page/Hardware

2017-11-16T09:58:35Z

Sojka: /* Hardware */

== Hardware ==

* [[A0B36APO Virtual Hardware]]
* [[Alpha PWS500a]]
* [[AT91SAM7X256]]
* [[Boa5200]]
* [[ColdFire_DEMO52233 | ColdFire DEMO52233 (Board from Freescale)]]
* [[ColdFire_MCF548x | ColdFire MCF548x (resources and experiments)]]
* [[Dell XPS12]]
* [[FPGA]]
* [[FTDI2232 JTAG]]
* [[H8S/2638]]
* [[HC12 | Motorola HC12]]
* [[Humusoft MF6xx]]
* [[LX CPU1]]
* [[LPC21xx]]
* [[MIDAM MPC5200 DB1]] (Mikroklima)
* [[ML403 | ML403 Xilinx Virtex-4]]
* [[MSP430F5529 Launchpad]]
* [[NetFPGA]]
* [[NVIDIA_Jetson_TX1 | NVIDIA Jetson TX1]]
* [[NVIDIA_Jetson_TX2 | NVIDIA Jetson TX2]]
* [[OJ10 - welding robot]]
* [[PiMX1]] i.MX1 processor based board
* [[Raspberry Pi]] (RPi, BCM2835)
* [[STM32 VLDISCOVERY]]
* [[TC1798|TC1798 - Infineon AUDO MAX]]
* [[TMS570LS3137]]
* [[USB2CAN 8devices]]
* [[Wireless_Sensor_Networks | Wireless Sensor Networks (WSNs)]]
* [[XC2S100-kit|Xilinx Spartan II XC2S100 Demo Board]]
* [[XC2V1000-kit|Xilinx Virtex II XC2V1000 Demo Board]]
* [[Zynq|Xilinx Zynq-7000]]

Git repository on this server

2016-02-29T16:02:56Z

Sojka: /* Permissions to automatic repositories */

Repositories on rtime server are managed by [http://github.com/sitaramc/gitolite Gitolite tool], which allows to conveniently manage repository permissions. World readable repositories can be [http://rtime.felk.cvut.cz/gitweb browsed online].

In addition to gitolite repositories, users with shell account can create [[Git repositories in home directories|Git repositories in their home directory]]. This does not require any coordination with the administrator.

== Getting write access to repositories ==

Write access to the repositories can only be given to users who send the following information to the [http://rtime.felk.cvut.cz/~sojka/ administrator]:

# OpenSSH public key
# Login name (for ČVUT people) or email address (for others).

=== SSH key creation ===

The SSH key can be created with one of the following ways. Note that under Windows, methods 1 and 2 only work if [[Media:git-plink.jpg|OpenSSH]] has been selected during Git installation.

# Under Linux/Unix (or in Git Bash under Windows) run: <pre>ssh-keygen</pre>
# In Git Gui (under Linux or Windows) choose [[Media:Git-gui-key.jpg|Help -> Show SSH key -> Generate key]].
# Under Windows use PuTTYgen. Use this if you have chosen to [[Media:git-plink.jpg|use Pling]] during Git installation.

It is stored by default at <tt>~/.ssh/id_rsa.pub</tt>.

=== Password-protected keys ===

During the key creation you will be asked for a passphrase. If you do not specify any passphrase, anybody with access to your <tt>~/.ssh</tt> directory could access your repositories. If you specify the passphrase, it will need to be entered whenever you want to push to or pull from the server. By using <tt>ssh-add</tt> command (or Pageant program under Windows) you can specify the passphrase only once and the decrypted key will be remembered in the memory.

== Creating repositories ==

There are to ways how a repository can be created:

# Send an email to the [http://rtime.felk.cvut.cz/~sojka/ administrator] with the name of the repository, a short description and a list of people (login or email) who should have access to the repository. The administrator creates the repository for you and notifies you when it's done.
# Our group staff members can create their repositories without asking the administrator. See below.

=== Automatic creation of repositories (staff members only) ===

It is simply a matter of pushing the repository to a special URL containing the login, like this:

git push --set-upstream ssh://git@rtime.felk.cvut.cz/«login»/«whatever» HEAD

This will create a new repository called «whatever» (if it does not exist yet) and push the current HEAD to it. It also makes this repository the default for pushing and pulling (this is what --set-upstream does).

Such repository is by default accessible only to the creator. If you want this repository to be public, run
ssh git@rtime.felk.cvut.cz perms «login»/«whatever» + READERS @all

If you want to set a [https://rtime.felk.cvut.cz/gitweb/orte.git Gitweb description] for public repositories created this way, use gitolite's desc commands. I.e. you can set the description by:
ssh git@rtime.felk.cvut.cz desc «login»/«whatever» "Description"

== Accessing the repository ==

After [[Git#Install_Git|installing Git]] on your local computer, you
can access the repository as follows.

=== Cloning the repository ===

Read/Write access (for users with registered SSH key):
git clone ssh://git@rtime.felk.cvut.cz/''repo-name''

Read-only access (for public repositories only):
git clone git://rtime.felk.cvut.cz/''repo-name''.git
git clone http://rtime.felk.cvut.cz/git/''repo-name''.git

=== First push to admin-created repositories ===

After an empty repository is created by the admin, you can push (i.e. upload) the data to it:

* [[#Cloning the repository|Clone]] the empty repository.
* Put your sources into your cloned repository
git add . # tells git to track all files in your project
git commit # commits the added files to the repository
* Push your sources to the server
git push

=== Pushing to non-master branches ===

If you are not allowed to push to the master branch but to a different one, you have to push like this:
git push origin master:your-branch
which pushes your local master branch to the remote branch ''your-branch''.

To make this behavior default run
git config remote.origin.push master:your-branch

And from now on, it is sufficient to run only
git push

== Managing repositories ==

=== Finding available repositories ===

You can find the list of repositories you have access to by running:

ssh git@rtime.felk.cvut.cz info [filter]

where filter is optional string used to filter the list.

=== Permissions to automatic repositories ===

The owners of automatically created repositories can manage the access permissions by themselves.

The current permissions can be listed by:

ssh git@rtime.felk.cvut.cz perms -l «repo»

You can add permissions for either reading of writing the repo with:
ssh git@rtime.felk.cvut.cz perms «repo» + READERS «login»
ssh git@rtime.felk.cvut.cz perms «repo» + WRITERS «login»

The permissions can be removed by replacing '''+''' with '''-'''.

To make your repository visible on [https://rtime.felk.cvut.cz/gitweb/ gitweb], run:
ssh git@rtime.felk.cvut.cz perms «repo» + READERS @all

== Links to git related documents ==

* [http://support.dce.felk.cvut.cz/mediawiki/index.php/gitolite Gitolite documentation on DCE IT pages]

[[Category:Git]]

USB2CAN 8devices

2014-12-11T13:47:24Z

Sojka: Created page with "* http://www.8devices.com/usb2can == Use under Linux == ip link set can0 up type can bitrate 500000 candump can0 cansend can0 123#45"

* http://www.8devices.com/usb2can

== Use under Linux ==

ip link set can0 up type can bitrate 500000
candump can0
cansend can0 123#45

Template:Main Page/Hardware

2014-12-11T13:46:04Z

Sojka: /* Hardware */

== Hardware ==

* [[A0B36APO Virtual Hardware]]
* [[Alpha PWS500a]]
* [[AT91SAM7X256]]
* [[Boa5200]]
* [[ColdFire_DEMO52233 | ColdFire DEMO52233 (Board from Freescale)]]
* [[ColdFire_MCF548x | ColdFire MCF548x (resources and experiments)]]
* [[Dell XPS12]]
* [[FPGA]]
* [[FTDI2232 JTAG]]
* [[H8S/2638]]
* [[HC12 | Motorola HC12]]
* [[Humusoft MF6xx]]
* [[LX CPU1]]
* [[LPC21xx]]
* [[MIDAM MPC5200 DB1]] (Mikroklima)
* [[ML403 | ML403 Xilinx Virtex-4]]
* [[MSP430F5529 Launchpad]]
* [[OJ10 - welding robot]]
* [[PiMX1]] i.MX1 processor based board
* [[Raspberry Pi]] (RPi, BCM2835)
* [[STM32 VLDISCOVERY]]
* [[TC1798|TC1798 - Infineon AUDO MAX]]
* [[TMS570LS3137]]
* [[USB2CAN 8devices]]
* [[Wireless_Sensor_Networks | Wireless Sensor Networks (WSNs)]]
* [[XC2S100-kit|Xilinx Spartan II XC2S100 Demo Board]]
* [[XC2V1000-kit|Xilinx Virtex II XC2V1000 Demo Board]]

Git repository on this server

2014-08-14T19:03:19Z

Sojka: /* SSH key creation */

Repositories on rtime server are managed by [http://github.com/sitaramc/gitolite Gitolite tool], which allows to conveniently manage repository permissions. World readable repositories can be [http://rtime.felk.cvut.cz/gitweb browsed online].

In addition to gitolite repositories, users with shell account can create [[Git repositories in home directories|Git repositories in their home directory]]. This does not require any coordination with the administrator.

== Getting write access to repositories ==

Write access to the repositories can only be given to users who send the following information to the [http://rtime.felk.cvut.cz/~sojka/ administrator]:

# OpenSSH public key
# Login name (for ČVUT people) or email address (for others).

=== SSH key creation ===

The SSH key can be created with one of the following ways. Note that under Windows, methods 1 and 2 only work if [[Media:git-plink.jpg|OpenSSH]] has been selected during Git installation.

# Under Linux/Unix (or in Git Bash under Windows) run: <pre>ssh-keygen</pre>
# In Git Gui (under Linux or Windows) choose [[Media:Git-gui-key.jpg|Help -> Show SSH key -> Generate key]].
# Under Windows use PuTTYgen. Use this if you have chosen to [[Media:git-plink.jpg|use Pling]] during Git installation.

It is stored by default at <tt>~/.ssh/id_rsa.pub</tt>.

=== Password-protected keys ===

During the key creation you will be asked for a passphrase. If you do not specify any passphrase, anybody with access to your <tt>~/.ssh</tt> directory could access your repositories. If you specify the passphrase, it will need to be entered whenever you want to push to or pull from the server. By using <tt>ssh-add</tt> command (or Pageant program under Windows) you can specify the passphrase only once and the decrypted key will be remembered in the memory.

== Creating repositories ==

There are to ways how a repository can be created:

# Send an email to the [http://rtime.felk.cvut.cz/~sojka/ administrator] with the name of the repository, a short description and a list of people (login or email) who should have access to the repository. The administrator creates the repository for you and notifies you when it's done.
# Our group staff members can create their repositories without asking the administrator. See below.

=== Automatic creation of repositories (staff members only) ===

It is simply a matter of pushing the repository to a special URL containing the login, like this:

git push --set-upstream ssh://git@rtime.felk.cvut.cz/«login»/«whatever» HEAD

This will create a new repository called «whatever» (if it does not exist yet) and push the current HEAD to it. It also makes this repository the default for pushing and pulling (this is what --set-upstream does).

Such repository is by default accessible only to the creator. If you want this repository to be public, run
ssh git@rtime.felk.cvut.cz perms «login»/«whatever» + READERS @all

If you want to set a [https://rtime.felk.cvut.cz/gitweb/orte.git Gitweb description] for public repositories created this way, use gitolite's desc commands. I.e. you can set the description by:
ssh git@rtime.felk.cvut.cz desc «login»/«whatever» "Description"

== Accessing the repository ==

After [[Git#Install_Git|installing Git]] on your local computer, you
can access the repository as follows.

=== Cloning the repository ===

Read/Write access (for users with registered SSH key):
git clone ssh://git@rtime.felk.cvut.cz/''repo-name''

Read-only access (for public repositories only):
git clone git://rtime.felk.cvut.cz/''repo-name''.git
git clone http://rtime.felk.cvut.cz/git/''repo-name''.git

=== First push to admin-created repositories ===

After an empty repository is created by the admin, you can push (i.e. upload) the data to it:

* [[#Cloning the repository|Clone]] the empty repository.
* Put your sources into your cloned repository
git add . # tells git to track all files in your project
git commit # commits the added files to the repository
* Push your sources to the server
git push

=== Pushing to non-master branches ===

If you are not allowed to push to the master branch but to a different one, you have to push like this:
git push origin master:your-branch
which pushes your local master branch to the remote branch ''your-branch''.

To make this behavior default run
git config remote.origin.push master:your-branch

And from now on, it is sufficient to run only
git push

== Managing repositories ==

=== Finding available repositories ===

You can find the list of repositories you have access to by running:

ssh git@rtime.felk.cvut.cz info [filter]

where filter is optional string used to filter the list.

=== Permissions to automatic repositories ===

The owners of automatically created repositories can manage the access permissions by themselves.

The current permissions can be listed by:

ssh git@rtime.felk.cvut.cz perms -l «repo»

You can add permissions for either reading of writing the repo with:
ssh git@rtime.felk.cvut.cz perms «repo» + READERS «login»
ssh git@rtime.felk.cvut.cz perms «repo» + WRITERS «login»

The permissions can be removed by replacing '''+''' with '''-'''.

To make your repository visible on gitweb, run:
ssh git@rtime.felk.cvut.cz perms «repo» + READERS @all

== Links to git related documents ==

* [http://support.dce.felk.cvut.cz/mediawiki/index.php/gitolite Gitolite documentation on DCE IT pages]

[[Category:Git]]

TMS570LS3137

2014-08-12T15:43:22Z

Sojka: /* NHET Assembler */

[[File:TMS570LS31x HDK Kit.jpg|right|300px]]
[[File:Rpp.jpg|right]]

== Documentation ==
* [http://www.ti.com/product/tms570ls3137 Main TI page] containing datasheets.
* [http://e2e.ti.com/support/microcontrollers/hercules/f/312.aspx TI TMS570 related forum]
* [http://processors.wiki.ti.com/index.php/Category:TMS570 TMS570 Wiki]

* [http://processors.wiki.ti.com/index.php/HALCoGen_Ethernet_Driver_and_lwIP_Integration_Demonstration LwIP integration]

* [[Media:Studim_procesoru.pdf]] Notes from documentation (in Czech language)

== Programming ==

Tools recommended by TI for programming of this microcontroller:

* [http://processors.wiki.ti.com/index.php/Category:Code_Composer_Studio_v5 Code Composer Studio] (runs on Win and Linux).
* [http://www.ti.com/tool/halcogen HalCoGen] (for Windows only, but also runs quite well in Wine).
** [[TMS570LS3137 HalCoGen Bugs|TMS570LS3137 HalCoGen Bugs]]

=== CCS5.3.0.00090_linux in Ubuntu 12.04 64bits ===

After installation the application can be run with:

<code>
cd <install_dir>/ccsv5/eclipse/

./ccstudio
</code>

If the application fails to start is because CCS5 is a 32bits application a thus requires 32bits libraries:

<code>
sudo apt-get install libgtk2.0-0:i386 libxtst6:i386 gtk2-engines-pixbuf:i386 libcanberra-gtk-module:i386
</code>

If the application crashes with a segmentation fault do:

Edit <code><install_dir>/ccsv5/eclipse/plugins/com.ti.ccstudio.branding_<your version number>/plugin_customization.ini</code>

And change key <code>org.eclipse.ui/showIntro</code> to <code>false</code>.

Choose "FREE License - for use with XDS100 JTAG Emulators" on the licensing options.

You may create a symbolic link and a desktop entry:

<code>
sudo ln -s <install_dir>/ccsv5/eclipse/ccstudio /usr/local/bin/ccstudio
</code>

And put in <code>~/.local/share/applications/ccs5.desktop</code>

<nowiki>
[Desktop Entry]
Version=1.0
Type=Application
Terminal=false
Exec=ccstudio
Name=Code Composer Studio
Icon=/usr/local/ti/ccsv5/eclipse/icon.xpm
</nowiki>

=== CCS5.5.0.00077_windows on Windows 7x64 ===

Download ccs_setup_5.5.0.00077.exe from http://ti.com and run.

Choose component:
* Safety MCUs

Choose Compiler tools:
* TI ARM Compiler Tools
* TI Documentation

Coose JTAG Emulator Support
* XDS100 Class Emulator Support

=== NHET Assembler ===

http://www.ti.com/tool/nhet-assembler

Installer doesn't work under Wine (Debian unstable, wine-1.6.2) even after installing the following packages, which wine complained about: <tt>apt-get install p11-kit-modules:i386 gnome-keyring:i386</tt>

If it is installed under windows, the resulting ''hetp.exe'' runs under Wine correctly.

== FreeRTOS ==
Installation is easy, simply create new project in HalCoGen

* New -> Project
* Select Family:TMS570LS31x
* Select Device: TMS570LS3137ZWT_FREERTOS

All necessary files will be added into project automaticaly.

== Matlab/Simulink Embedded Coder target ==
We have implemented support for Matlab/Simulink which allows to use
designed peripherals support libraries from Simulink model design.

For further information look at separate pages for the target

http://rtime.felk.cvut.cz/rpp-tms570/

== Hardware ==
Developement board we are using: [http://processors.wiki.ti.com/index.php?title=TMS570LS31x_HDK_Kit TMS570LS31x_HDK_Kit]

=== SDRAM setup ===

* Simple code to setup SDRAM for use from OpenOCD and others code loaders
** https://github.com/hornmich/tms570ls3137-hdk-sdram

Setup of bit 31 in GPREG1 is required ele EMIF does not work as expected.
From UM 4.3.3 Control of Special Multiplexed Options: Any application that requires the EMIF functionality
must set GPREG1[31]. This allows these 8 EMIF module outputs to be driven on to the assigned balls.

<pre>systemREG1->GPREG1 |= 0x80000000;</pre>

{| class="wikitable"
! Parameter !! Value for HDK / Conn test !! Value for RPP !! Notice
|-
| Chip || IS42S16400F-7BL || IS45S16320 ||
|-
| banks || 4 (2 bits) || 4 (2 bits) ||
|-
| rows || 4096 (12 bits) || 8192 (13 bits) ||
|-
| columns || 256 (8 bit) || 1024 (10 bits) ||
|-
| CL || 2/3 || 2/3 ||
|-
| refresh [ms] || || 64 / 16 @ 80 °C ||
|-
| self. ref. exit [ns] || || 67 ||
|-
| HCLK [MHz] || 160 / 160 || 160 ||
|-
| EMIF Clock / VCLK3 || 80 / 80?? || 80 ||
|-
! CLK2CNTL !! !! !! Clock 2 Control Register
|-
| VCLK3R (3-0) || 2-1 / 4-1?? || 2-1 || HCKL to EMIF VCLK3 ration
|-
! SDTIMR !! !! !! SDRAM Timing Register
|-
| TRF_C (31-27) || 6-1 / 6 || 9-1 || REFR to REFR
|-
| T_RP (26-24) || 2-1 / 1 || 3-1 || PRE to ACTIV or REFR
|-
| (23) || 0 || 0 ||
|-
| T_RCD (22-20) || 2-1 / 1 || 3-1 || ACTIV to RD/WR
|-
| (19) || 0 || 0 ||
|-
| T_WR (18-16) || 2-1 / 2 || 2-1 || WRITE to PRE
|-
| T_RAS (15-12) || 4-1 / 4 || 6-1 || ACTIV to PRE
|-
| T_RC (11-8) || 6-1 / 3 || 9-1 || ACTIV to ACTIV
|-
| (7) || 0 / 0 || 0 ||
|-
| T_RRD (6-4) || 2-1 / 1 || 2-1 || ACTIV to ACTIV other bank
|-
| (3) || 0 || 0 ||
|-
! SDSRETR !! !! !! Self Refresh Exit Timing Register
|-
| T_XS (XSR) || 5 / 6 || 5+3-1 ||
|-
! SDRCR !! !! !!
|-
| RR (12-0) || 312 / 1250 || 156 || 80e6 * 16e-3 / 8192 => less or equal to 156
|-
! SDCR !! !! !! SDRAM Configuration Register
|-
| SR (31) || 0 / 0 || 0 || self refresh mode
|-
| PD (30) || 0 / 0 || 0 || power down
|-
| PDWR (29) || 0 / 0 || 0 || refresh in PD
|-
| NM (14) || 1 / 1 || 1 || narrow mode
|-
| CL (11-9) || 2 / 3 || 3 || CAS latency
|-
| BIT11_9LOCK (8) || 1 / 1 || 1 || CAS latency lock
|-
| IBANK (6-4) || 2 / 2 || 2 (4 banks) || banks
|-
| PAGESIZE (2-0) || 0 / 0 || 2 (10 bit) || counted in elements
|}

===SCI port===
We have connected serial port on Expansion Connector P3 (see HDK documentation) pin W3 and N2. TX is connected to N2 pin and RX to W3 pin. This brings us consequences as both pins are mutexed.

When you want to use SCI, you have to set few things in HalCoGen.
* Enable driver SCI (not LIN or SCI2 driver)
* In tab PINMUX select SCI and check conflict with other drivers
* In tab SCI choose and set data format.
When you want use interrupts in adittion, do the following:
* In tab VIM Channel 64-95 select interrupt 64: SCI level0 interrupt for high level interrupt or 74: SCI Level1 for low level interrupt
* In SCI tab enable TX and/or RX interrupt and select High or Low.
* In your code enable IRQ using _enable_IRQ() function, than enable notification using sciEnableNotification() function.
* Implement notification callback sciNotification() in notificatin.c

In your code don't forget to initialize sci using sciInit() function.

== Debug over JTAG ==

=== XDS100v2 JTAG Interface from Ti ===

The XDS100v2 is equipped with Ti specific 14-pin JTAG connector.
Next cable wires placement allows to use it with TMS570LS31x_HDK_Kit
or other device with ARM JTAG pin placement.

{| class="wikitable"
!colspan="2"| 14 pin Ti
!colspan="2"| 20 pin ARM
|-
| 1 || TMS || TMS || 7
|-
| 2 || TRST || NTRST || 3
|-
| 3 || TDI || TDI || 5
|-
| 4 || DIS || GND || 6
|-
| 5 || VD || VREF || 1 (2)
|-
| 6 || NC || || --
|-
| 7 || TDO || TDO || 13
|-
| 8 || GND || GND || (4)
|-
| 9 || RTCK || RTCK || 11
|-
| 10 || GND || GND || 8 (12)
|-
| 11 || TCK || TCK || 9
|-
| 12 || GND || GND || 10 (14)
|-
| 13 || EMU0 || ||
|-
| 14 || EMU1 || ||
|}

=== Setup XDS100v2 on Linux ===

By default the device (if nothing more connected then <code>/dev/ttyUSB0</code>) is added with permissions 664 with
<code>root</code> as user and group. You access the device we need write access for current user. To do so we need
to create a new udev rules:

sudo nano /etc/udev/rules.d/45-pes-rpp.rules

And add line:

SUBSYSTEM=="usb", ATTR{idVendor}=="0403", ATTR{idProduct}=="a6d0", MODE="0660", GROUP="plugdev"

Then reload udev rules with:

sudo udevadm control --reload-rules

You can check device properties like <code>idVendor</code> or <code>idProduct</code> with the following command:

udevadm info -a -p $(udevadm info -q path -n /dev/ttyUSB0)

== RS232 communication setup ==

Connect serial communication pins to computer's RS232 port or to USB through a FTDI adapter. If using RS232 port the
device should be <code>/dev/ttyS0</code>, if using FTDI it should be something like <code>/dev/ttyUSBx</code>
(check <code>dmesg</code> for details).

Make sure minicom or similar terminal program is installed:

sudo apt-get install minicom

Then configure minicon:

sudo minicom -s

And use the following configuration "9600 81N":

Serial Device : /dev/ttyS0
Lockfile Location : /var/lock
Callin Program :
Callout Program :
Bps/Par/Bits : 9600 8N1
Hardware Flow Control : No
Software Flow Control : No

Start terminal session and type <code>HELP</code> command to test communication.

== GCC build for Cortex-R4 Big-Endian ==

GCC options <pre>-mbig-endian -march=armv7-r -mthumb</pre>

GCC options with hard float <pre>-mbig-endian -mthumb -march=armv7-r -mfpu=vfpv3-d16 -mfloat-abi=hard</pre>

GCC multilib options

armv7-r/thumb2/be;@mbig-endian@mthumb@march=armv7-r
armv7-r/thumb2/vfpv3/be;@mbig-endian@mthumb@mfloat-abi=hard@march=armv7-r@mfpu=vfpv3-d16

* https://answers.launchpad.net/gcc-arm-embedded/+question/189066

* Patch to enable GCC and Newlib with big-endian support for RTEMS proposal
** http://lists.rtems.org/pipermail/devel/2014-June/007232.html
** Toolchain for RTEMS port to Cortex-R4F big-endian (TMS570LS3137)

* Sebastian Huber's version to push upstream
** http://lists.rtems.org/pipermail/devel/2014-July/007244.html
** RTEMS: Add multilibs for ARM

* Newlib correction
** http://lists.rtems.org/pipermail/devel/2014-July/007251.html
** Remaining arch issue in Newlib optimized ARM ASM memchr for Cortex-R

== RTEMS Cortex-R4 TMS570 BSP Deveopment (GSoC 2014 project) ==

* http://wiki.rtems.org/wiki/index.php/RTEMSPortToCortexR4
* http://github.com/AoLaD/rtems/tree/tms570-bsp
* http://github.com/AoLaD/rtems-tms570-utils

== Contacts ==

* Management: [http://dce.felk.cvut.cz/hanzalek/ Prof. Zdeněk Hanzálek]
* Technical: [http://cmp.felk.cvut.cz/~pisa/ Pavel Píša, Ph.D.]

TMS570LS3137

2014-08-12T15:20:16Z

Sojka: /* CCS5.5.0.00077_windows on Windows 7x64 */

[[File:TMS570LS31x HDK Kit.jpg|right|300px]]
[[File:Rpp.jpg|right]]

== Documentation ==
* [http://www.ti.com/product/tms570ls3137 Main TI page] containing datasheets.
* [http://e2e.ti.com/support/microcontrollers/hercules/f/312.aspx TI TMS570 related forum]
* [http://processors.wiki.ti.com/index.php/Category:TMS570 TMS570 Wiki]

* [http://processors.wiki.ti.com/index.php/HALCoGen_Ethernet_Driver_and_lwIP_Integration_Demonstration LwIP integration]

* [[Media:Studim_procesoru.pdf]] Notes from documentation (in Czech language)

== Programming ==

Tools recommended by TI for programming of this microcontroller:

* [http://processors.wiki.ti.com/index.php/Category:Code_Composer_Studio_v5 Code Composer Studio] (runs on Win and Linux).
* [http://www.ti.com/tool/halcogen HalCoGen] (for Windows only, but also runs quite well in Wine).
** [[TMS570LS3137 HalCoGen Bugs|TMS570LS3137 HalCoGen Bugs]]

=== CCS5.3.0.00090_linux in Ubuntu 12.04 64bits ===

After installation the application can be run with:

<code>
cd <install_dir>/ccsv5/eclipse/

./ccstudio
</code>

If the application fails to start is because CCS5 is a 32bits application a thus requires 32bits libraries:

<code>
sudo apt-get install libgtk2.0-0:i386 libxtst6:i386 gtk2-engines-pixbuf:i386 libcanberra-gtk-module:i386
</code>

If the application crashes with a segmentation fault do:

Edit <code><install_dir>/ccsv5/eclipse/plugins/com.ti.ccstudio.branding_<your version number>/plugin_customization.ini</code>

And change key <code>org.eclipse.ui/showIntro</code> to <code>false</code>.

Choose "FREE License - for use with XDS100 JTAG Emulators" on the licensing options.

You may create a symbolic link and a desktop entry:

<code>
sudo ln -s <install_dir>/ccsv5/eclipse/ccstudio /usr/local/bin/ccstudio
</code>

And put in <code>~/.local/share/applications/ccs5.desktop</code>

<nowiki>
[Desktop Entry]
Version=1.0
Type=Application
Terminal=false
Exec=ccstudio
Name=Code Composer Studio
Icon=/usr/local/ti/ccsv5/eclipse/icon.xpm
</nowiki>

=== CCS5.5.0.00077_windows on Windows 7x64 ===

Download ccs_setup_5.5.0.00077.exe from http://ti.com and run.

Choose component:
* Safety MCUs

Choose Compiler tools:
* TI ARM Compiler Tools
* TI Documentation

Coose JTAG Emulator Support
* XDS100 Class Emulator Support

=== NHET Assembler ===

http://www.ti.com/tool/nhet-assembler

It doesn't work on Wine (Debian unstable, wine-1.6.2) even after installing the following packages, which wine complained about:

apt-get install p11-kit-modules:i386 gnome-keyring:i386

== FreeRTOS ==
Installation is easy, simply create new project in HalCoGen

* New -> Project
* Select Family:TMS570LS31x
* Select Device: TMS570LS3137ZWT_FREERTOS

All necessary files will be added into project automaticaly.

== Matlab/Simulink Embedded Coder target ==
We have implemented support for Matlab/Simulink which allows to use
designed peripherals support libraries from Simulink model design.

For further information look at separate pages for the target

http://rtime.felk.cvut.cz/rpp-tms570/

== Hardware ==
Developement board we are using: [http://processors.wiki.ti.com/index.php?title=TMS570LS31x_HDK_Kit TMS570LS31x_HDK_Kit]

=== SDRAM setup ===

* Simple code to setup SDRAM for use from OpenOCD and others code loaders
** https://github.com/hornmich/tms570ls3137-hdk-sdram

Setup of bit 31 in GPREG1 is required ele EMIF does not work as expected.
From UM 4.3.3 Control of Special Multiplexed Options: Any application that requires the EMIF functionality
must set GPREG1[31]. This allows these 8 EMIF module outputs to be driven on to the assigned balls.

<pre>systemREG1->GPREG1 |= 0x80000000;</pre>

{| class="wikitable"
! Parameter !! Value for HDK / Conn test !! Value for RPP !! Notice
|-
| Chip || IS42S16400F-7BL || IS45S16320 ||
|-
| banks || 4 (2 bits) || 4 (2 bits) ||
|-
| rows || 4096 (12 bits) || 8192 (13 bits) ||
|-
| columns || 256 (8 bit) || 1024 (10 bits) ||
|-
| CL || 2/3 || 2/3 ||
|-
| refresh [ms] || || 64 / 16 @ 80 °C ||
|-
| self. ref. exit [ns] || || 67 ||
|-
| HCLK [MHz] || 160 / 160 || 160 ||
|-
| EMIF Clock / VCLK3 || 80 / 80?? || 80 ||
|-
! CLK2CNTL !! !! !! Clock 2 Control Register
|-
| VCLK3R (3-0) || 2-1 / 4-1?? || 2-1 || HCKL to EMIF VCLK3 ration
|-
! SDTIMR !! !! !! SDRAM Timing Register
|-
| TRF_C (31-27) || 6-1 / 6 || 9-1 || REFR to REFR
|-
| T_RP (26-24) || 2-1 / 1 || 3-1 || PRE to ACTIV or REFR
|-
| (23) || 0 || 0 ||
|-
| T_RCD (22-20) || 2-1 / 1 || 3-1 || ACTIV to RD/WR
|-
| (19) || 0 || 0 ||
|-
| T_WR (18-16) || 2-1 / 2 || 2-1 || WRITE to PRE
|-
| T_RAS (15-12) || 4-1 / 4 || 6-1 || ACTIV to PRE
|-
| T_RC (11-8) || 6-1 / 3 || 9-1 || ACTIV to ACTIV
|-
| (7) || 0 / 0 || 0 ||
|-
| T_RRD (6-4) || 2-1 / 1 || 2-1 || ACTIV to ACTIV other bank
|-
| (3) || 0 || 0 ||
|-
! SDSRETR !! !! !! Self Refresh Exit Timing Register
|-
| T_XS (XSR) || 5 / 6 || 5+3-1 ||
|-
! SDRCR !! !! !!
|-
| RR (12-0) || 312 / 1250 || 156 || 80e6 * 16e-3 / 8192 => less or equal to 156
|-
! SDCR !! !! !! SDRAM Configuration Register
|-
| SR (31) || 0 / 0 || 0 || self refresh mode
|-
| PD (30) || 0 / 0 || 0 || power down
|-
| PDWR (29) || 0 / 0 || 0 || refresh in PD
|-
| NM (14) || 1 / 1 || 1 || narrow mode
|-
| CL (11-9) || 2 / 3 || 3 || CAS latency
|-
| BIT11_9LOCK (8) || 1 / 1 || 1 || CAS latency lock
|-
| IBANK (6-4) || 2 / 2 || 2 (4 banks) || banks
|-
| PAGESIZE (2-0) || 0 / 0 || 2 (10 bit) || counted in elements
|}

===SCI port===
We have connected serial port on Expansion Connector P3 (see HDK documentation) pin W3 and N2. TX is connected to N2 pin and RX to W3 pin. This brings us consequences as both pins are mutexed.

When you want to use SCI, you have to set few things in HalCoGen.
* Enable driver SCI (not LIN or SCI2 driver)
* In tab PINMUX select SCI and check conflict with other drivers
* In tab SCI choose and set data format.
When you want use interrupts in adittion, do the following:
* In tab VIM Channel 64-95 select interrupt 64: SCI level0 interrupt for high level interrupt or 74: SCI Level1 for low level interrupt
* In SCI tab enable TX and/or RX interrupt and select High or Low.
* In your code enable IRQ using _enable_IRQ() function, than enable notification using sciEnableNotification() function.
* Implement notification callback sciNotification() in notificatin.c

In your code don't forget to initialize sci using sciInit() function.

== Debug over JTAG ==

=== XDS100v2 JTAG Interface from Ti ===

The XDS100v2 is equipped with Ti specific 14-pin JTAG connector.
Next cable wires placement allows to use it with TMS570LS31x_HDK_Kit
or other device with ARM JTAG pin placement.

{| class="wikitable"
!colspan="2"| 14 pin Ti
!colspan="2"| 20 pin ARM
|-
| 1 || TMS || TMS || 7
|-
| 2 || TRST || NTRST || 3
|-
| 3 || TDI || TDI || 5
|-
| 4 || DIS || GND || 6
|-
| 5 || VD || VREF || 1 (2)
|-
| 6 || NC || || --
|-
| 7 || TDO || TDO || 13
|-
| 8 || GND || GND || (4)
|-
| 9 || RTCK || RTCK || 11
|-
| 10 || GND || GND || 8 (12)
|-
| 11 || TCK || TCK || 9
|-
| 12 || GND || GND || 10 (14)
|-
| 13 || EMU0 || ||
|-
| 14 || EMU1 || ||
|}

=== Setup XDS100v2 on Linux ===

By default the device (if nothing more connected then <code>/dev/ttyUSB0</code>) is added with permissions 664 with
<code>root</code> as user and group. You access the device we need write access for current user. To do so we need
to create a new udev rules:

sudo nano /etc/udev/rules.d/45-pes-rpp.rules

And add line:

SUBSYSTEM=="usb", ATTR{idVendor}=="0403", ATTR{idProduct}=="a6d0", MODE="0660", GROUP="plugdev"

Then reload udev rules with:

sudo udevadm control --reload-rules

You can check device properties like <code>idVendor</code> or <code>idProduct</code> with the following command:

udevadm info -a -p $(udevadm info -q path -n /dev/ttyUSB0)

== RS232 communication setup ==

Connect serial communication pins to computer's RS232 port or to USB through a FTDI adapter. If using RS232 port the
device should be <code>/dev/ttyS0</code>, if using FTDI it should be something like <code>/dev/ttyUSBx</code>
(check <code>dmesg</code> for details).

Make sure minicom or similar terminal program is installed:

sudo apt-get install minicom

Then configure minicon:

sudo minicom -s

And use the following configuration "9600 81N":

Serial Device : /dev/ttyS0
Lockfile Location : /var/lock
Callin Program :
Callout Program :
Bps/Par/Bits : 9600 8N1
Hardware Flow Control : No
Software Flow Control : No

Start terminal session and type <code>HELP</code> command to test communication.

== GCC build for Cortex-R4 Big-Endian ==

GCC options <pre>-mbig-endian -march=armv7-r -mthumb</pre>

GCC options with hard float <pre>-mbig-endian -mthumb -march=armv7-r -mfpu=vfpv3-d16 -mfloat-abi=hard</pre>

GCC multilib options

armv7-r/thumb2/be;@mbig-endian@mthumb@march=armv7-r
armv7-r/thumb2/vfpv3/be;@mbig-endian@mthumb@mfloat-abi=hard@march=armv7-r@mfpu=vfpv3-d16

* https://answers.launchpad.net/gcc-arm-embedded/+question/189066

* Patch to enable GCC and Newlib with big-endian support for RTEMS proposal
** http://lists.rtems.org/pipermail/devel/2014-June/007232.html
** Toolchain for RTEMS port to Cortex-R4F big-endian (TMS570LS3137)

* Sebastian Huber's version to push upstream
** http://lists.rtems.org/pipermail/devel/2014-July/007244.html
** RTEMS: Add multilibs for ARM

* Newlib correction
** http://lists.rtems.org/pipermail/devel/2014-July/007251.html
** Remaining arch issue in Newlib optimized ARM ASM memchr for Cortex-R

== RTEMS Cortex-R4 TMS570 BSP Deveopment (GSoC 2014 project) ==

* http://wiki.rtems.org/wiki/index.php/RTEMSPortToCortexR4
* http://github.com/AoLaD/rtems/tree/tms570-bsp
* http://github.com/AoLaD/rtems-tms570-utils

== Contacts ==

* Management: [http://dce.felk.cvut.cz/hanzalek/ Prof. Zdeněk Hanzálek]
* Technical: [http://cmp.felk.cvut.cz/~pisa/ Pavel Píša, Ph.D.]

TMS570LS3137

2014-07-02T22:05:26Z

Sojka: /* CCS5.3.0.00090_linux in Ubuntu 12.04 64bits */

MIDAM MPC5200 DB1

2014-01-23T22:55:06Z

Sojka: /* Root file system */

==Description==

Two sets of the MIDAM MPC5200 was delivered by the Mikroklima s.r.o. for our purposes. Each set consist of the:

* Shark MPC52000 CPU module (pin compatible with TQ Components TQM5200 module),
* MPC5200 v1.1 2008/02 carrier board.

Set #1 has s/n: '''008770''' and set #2 has s/n: '''008771'''.

* [[Media:SHARK_V1_1_DOC_CZ.pdf|SHARK_V1_1_DOC_CZ.pdf‎]]
* [[Media:SHARK_V1_0_linux_DOC_CZ.pdf|SHARK_V1_0_linux_DOC_CZ.pdf]]

==Schematics and components==
Download schematics in PDF: [[:File:Midam_expand_v1b.pdf]]

===List of components===
This list is not complete. It is just a subset of components needed for educational purpose.

'''POWER SUPPLY'''

C9 CAP1206 220pF
C10 CAP1206 22nF
C11 CAP1206 10uF
C12 tantal el. 330uF 6.3V D
C23 el. 470uF, 50V
C29 CAP0805 100n
C30 CAP0805 100n
C31 CAP0805 100n
C32 CAP0805 100n
C35 CAP0805 100n
C36 47uF10V B
C37 47uF10V B
C38 47uF10V B
C39 47uF10V B
D6 STPS2L30A
D9 LED 1206
D10 STPS2L30A
J7 PWR-CON
J10 SMD switch
L2 INDUCTOR DR127-150
R19 RES0805 4k7
R20 RES0805 5k6
R21 RES0805 3k3
R25 RES0805 330R
U11 STM811SW16F MPU LOW RESET 2.93V
U9 ST-L5973D

'''MIDAM HEADER'''

R34 RES0805 10k
R35 RES0805 10k
J1 Socket

'''USB-CLIENT'''

C5 CAP0805 100nF
C26 CAP0805 100n
D3 LED 1206
D4 LED 1206
L7 BLM21AG601SN1D FERRITE, BEAD, 0805, 0.21OHM, 0.6A
J4 USB-B
R9 RES0805 4k7
R10 RES0805 10k
R11 RES0805 270R
R12 RES0805 270R
R48 RES0805 10k
R49 RES0805 10k
U2 FT232RL

'''EXPAND HEADER'''

D5 ULN2803 DIO
D11 LED 1206
D12 LED 1206
D13 LED 1206
D14 LED 1206
D15 LED 1206
D16 LED 1206
D17 LED 1206
D18 LED 1206
D19 LED 1206
D20 LED 1206
J8 SMD SWITCH
J9 SMD SWITCH
R13 RES0805 330R
R14 RES0805 1k
R15 RES0805 1k
R16 RES0805 1k
R17 RES0805 330R
R18 RES0805 330R
R28 RES0805 10k
R29 RES0805 10k
R30 RES0805 2k
R31 RES0805 330R
R32 RES0805 2k
R33 RES0805 330R
R38 RES0805 330R
R39 RES0805 330R
R40 RES0805 330R
R41 RES0805 330R
R42 RES0805 330R
R43 RES0805 330R
R44 RES0805 330R
U3 BSS138 ANA
U4 BSS138 ANA
U6 BSS138 ANA
U7 BSS138 ANA
U8 BSS138 ANA
Q1 BC856ALT1G TRANSISTOR, PNP
Q2 BC856ALT1G TRANSISTOR, PNP

'''ETHERNET'''

C18 CAP0805 22nF
J2 TE Connectivity AMP 5-6605758-1

== Mailing List ==

Discussion related to this board happen in a [http://rtime.felk.cvut.cz/mailman/listinfo/shark5200 mailing list].

==Board overview==

[[Image:Board overview.jpg]]

==Serial line (system console)==

* Loader system console is attached to the ttyPSC0 port.
* The '''ttyPSC0 port is done in the LVTTL 3.3V logic''', so appropriate 3.3V to RS-232 converter (e.g. [http://pdfserv.maxim-ic.com/en/ds/MAX3222-MAX3241.pdf MAX3232]) is required for the serial console.

'''Communication parameters:'''
* baud rate: 115200 bps
* bits: 8 bit
* stop bits: 1 bit
* Parity: none
* Flow control: none

==Module memory map==
The MPC5200B is 32 bit CPU, so it has a 32 bit address space. It is able to address up to 4 294 967 295 B (0xFFFFFFFF) - 4096 MB. The Shark module has been equipped with '''128 MB''' DDR RAM and '''64 MB''' NOR flash memory.
* RAM chips: Samsung K4S511632D-UC(L)75, order: 32M x 16
* Address space '''BASE address''' is 0x00000000
* RAM is from 0x00000000 to 0x08000000 (128 MB)

Flash memory is being mapped at the and of address space (from 3.9375 GB).
* '''Flash BASE address''' is 0xFC000000 (last address is 0xFFFFFFFF)
* Flash memory size is 0x04000000 (64 MB)

There are three MTD partitions in the flash (defined in shark.dts). The flat device tree file syntax uses first address and length of the partition for its definition.
* u-Boot (1 MB) from 0x00000000 to 0x00100000, length 0x00100000
* kernel (3 MB) from 0x00100000 to 0x00400000, length 0x00300000
* '''file-system''' (56 MB) from 0x00400000 to 0x04000000, length 0x03C00000
All these addresses are offsets against Flash BASE.

==Boot loader==
These boards are preinstalled with [http://www.denx.de/wiki/DULG/Manual Das u-Boot] boot loader.
Behaviour of the u-Boot can be handled by its environment variables. Here are some useful commands:

*'''printenv [variable]''' - prints complete environment or only given variable.
*'''saveenv''' - commits whole environment in flash memory

For running linux kernel >2.6.25 it's necessary to have u-Boot 1.3.2 or later, which is able to hand over flat device tree to the kernel. When older revision is present, it is necessary to upgrade. Binary of u-Boot can be downloaded here: [ftp://rtime.felk.cvut.cz/shark-mpc5200/u-boot.bin u-boot.bin].

'''U-Boot upgrade howto:'''

During the upgrade procedure it is necessary to proceed with utmost precaution, because '''there is no backup image''' of the u-Boot in the flash for recovery purposes. Fail-flash recovery isn't possible without JTAG interface. So, you have been warned. In future builds of the u-Boot there should be a support for recovery image. Follow this commands to upgrade U-Boot's image in flash memory:

dhcp
tftp 800000 u-boot.bin
protect off fc000000 fc09ffff
erase fc000000 fc09ffff
cp.b 800000 fc000000 ${filesize}
protect on fc000000 fc09ffff

Now reboot and than commit new default environment:

saveenv

===How to access U-Boot environment variables from Linux ?===
The U-Boot environment variables is possible to read and write trough utilities ... TO DO

==Cross-tool chain==
Necessary cross-tool chain for PowerPC platform can be build using Crossdev tool. You can install Crossdev on your Gentoo distro very simply:

emerge -av crossdev

Some dependencies may go before. Building of tool chain itself will take some time, so let's go to take some coffee.

crossdev --b 2.18-r3 --k 2.6.23-r3 --g 4.1.2 --without-headers -t powerpc-unknown-linux-gnu

For Debian, you can use a [[Cross compilers|packages]] prepared by Pavel Píša.

== Linux kernel ==

=== Instructions for recent kernels ===

You need [https://rtime.felk.cvut.cz/gitweb/shark/linux.git/commitdiff/87a8e2b9406cc7f8779f02047e0cd1594c570b78 this simple patch] to boot Linux on MIDAM/RYU board.

=== Instructions for old kernels ===

It is necessary to use patched Linux sources. We maintain them in our [[Git]] [http://rtime.felk.cvut.cz/gitweb/shark/linux.git repository]. You can clone it by:
git clone git://rtime.felk.cvut.cz/shark/linux.git

Now you can choose the kernel revision you want to compile:

git branch -r # there you can see all branches available
git checkout origin/shark/2.6.28.8 # choose the one you desire

Note: See [[Linux sources]] for the description of the repository and patch management techniques we use.

Now let's begin with the kernel configuration and compilation. The following recipe can be used to compile the kernel out of source directory, which is helpful if you want to compile a single kernel version with several configurations.
* <tt>cd linux</tt>
* <tt>mkdir -p _build/midam</tt>
* <tt>cd _build/midam</tt>
* Copy the following code to <tt>GNUmakefile</tt> file
<pre>
VERSION = 2
PATCHLEVEL = 6

KERNELSRC := $(shell cd ../..; pwd)
KERNELOUTPUT := $(patsubst $(KERNELSRC)/%,%,$(shell pwd))

KERNELRELEASE = $(shell cat include/config/kernel.release 2> /dev/null)

MAKEFLAGS += --no-print-directory

ARCH=powerpc
CROSS_COMPILE=powerpc-linux-gnu-

TFTPBOOT=/var/lib/tftpboot/ryu

export INSTALL_MOD_PATH=$(KERNELSRC)/../MPC5200_root

.PHONY: install all $(MAKECMDGOALS)

all:
$(MAKE) ARCH=$(ARCH) CROSS_COMPILE=$(CROSS_COMPILE) -C $(KERNELSRC) O=$(KERNELOUTPUT)

Makefile:;

$(filter-out all Makefile,$(MAKECMDGOALS)) %/:
$(MAKE) ARCH=$(ARCH) CROSS_COMPILE=$(CROSS_COMPILE) -C $(KERNELSRC) O=$(KERNELOUTPUT) $@
</pre>

* <tt>make 52xx/midam_defconfig</tt> # or use <tt>52xx/ryu_defconfig</tt> for RYU board
* <tt>make menuconfig</tt> # if you need additional configuration
* <tt>make</tt> # start compilation; <tt>u-boot-tools</tt> should be properly installed before compilation

The compiled image can be found in linux/_build/midam/arch/powerpc/boot
It is the file uImage. Copy it to your tftpboot directory.

'''How to build the Flat Device Tree file'''

Since kernel version 2.6.25 is description of the platform hardware provided trough the Flat Device Tree. Necessary sources are now part of the kernel sources. Appropriate image could be build with this command:

make ARCH=powerpc shark.dtb DTS_FLAGS="-S65536"

If DTS_FLAGS parameter omitted than following error will occur, because there is not enough space in the file, where the u-Boot can store some additional data about buses timing, etc.:

WARNING: could not create /chosen FDT_ERR_NOSPACE.
ERROR: /chosen node create failed - must RESET the board to recover.

==Root file system==

Use [http://buildroot.uclibc.org/ buildroot] to build one.

== TO DO - UnionFS for root FS in flash ==

For long term usage is not really good to repeatedly overwrite block in the NOR flash chip, because memory cells are being punished. So it would be better to use jffs2 root FS only as RO file system and create RW tmpfs of same size. UnionFS than could be used to merge these two file systems and provide one RW file system. Changes in FS as a lock and log files can be made without permanent effect.

==SocketCan==

SocketCan is currently tested only with kernels 2.6.28 or lower. If you want to use Socket Can, it is currently recommended to use kernel 2.6.28. To enable SocketCan support, it is neccesary to run

make menuconfig

before building the kernel and set the following:

Networking Support / CAN bus subsystem support (yes)
Raw CAN Protocol (raw access with CAN-ID filtering) (yes)
CAN Device Drivers / Virtual Local CAN Interface (vcan) (yes)
Prompt for platform CAN drivers with sysfs support (yes)
Support for a Freescale MSCAN based chips (yes)
Freescale MPC5200 onboard CAN controller (yes)

make KERNELDIR=/home/marsark/src/linux-2.6.26.5/_build/mpc5200_ryu/ CONFIG_CAN_MPC52XX=m CONFIG_CAN_MSCAN=m

CAN subsystem init script:

modprobe can
modprobe mscan-mpc52xx
modprobe can-raw

echo 1000000 > /sys/class/net/can0/can_bittiming/bitrate
echo 1000000 > /sys/class/net/can1/can_bittiming/bitrate

If the above commands fail, you have a new version of socketcan and you need to use ip tool to set bitrate. See bellow.

ifconfig can0 up
ifconfig can1 up

Warning - the ip tool is not working properly yet!

Test the setup:

cansend can0 123#4567

=== Using ip tool ===

ip link set can0 type can bitrate 1000000
ip link set up dev can0
ip link set can1 type can bitrate 1000000
ip link set up dev can1

==== Compilation ====

git clone git://git.kernel.org/pub/scm/network/iproute2/iproute2.git
cd iproute2
make CC=powerpc-linux-gnu-gcc

The make will probably fail but fortunately the <tt>ip/ip</tt> is already compiled.

== GPIO how set pin value ==
In MPC5200 have two kind of GPIO. The first one have wakeup capability, the second one is standard GPIO pins. Each of this sets have its own register sets, so some PSC ports are splitted in to two parts. See MOC5200B documentation section 7.3.2.1 and 7.3.2.2. The availability GPIO of PSC depends on GPS Port Configuration Register settings. For RYU boards is available all GPIO in PSC3 port (HW notation).

'''TODO: kernel still fails to initialise GPIO drivers on our boards !!!'''

cat /sys/class/gpio/gpiochip248/label //todo

=== Setting GPIO with wakeup capability ===
GPIO with wakeup using
/sys/class/gpio/gpiochip248/

Pin notation:
0 -> GPIO_WKUP_7
1 -> GPIO_WKUP_6
2 -> PSC6_1
3 -> PSC6_0
4 -> ETH_17
5 -> PSC3_9
6 -> PSC2_4
7 -> PSC1_4

Final value is 248 + requested pin (example for PSC2_4 248+6 => 254)

Enable PIN for GPIO:
echo 254 >/sys/class/gpio/export
Set GPIO as output or input
echo out >/sys/class/gpio/gpio254/direction
echo in >/sys/class/gpio/gpio254/direction
Set GPIO to 0 or 1 if configured as output pin
echo 0 >/sys/class/gpio/gpio254/value
echo 1 >/sys/class/gpio/gpio254/value

=== Setting standard GPIO not tested ===
Standard GPIO using
/sys/class/gpio/gpiochip216/

Pin notation:
0..1 > reserved
2..3 > IRDA
4..7 > ETHR
8..11 > reserved
12..15 > USB
16..17 > reserved
18..23 > PSC3
24..27 > PSC2
28..31 > PSC1

Final value is 216 + requested pin (example for PSC3_3 216+20 => 236)

Enable PIN for GPIO:
echo 236 >/sys/class/gpio/export
Set GPIO as output or input
echo out >/sys/class/gpio/gpio236/direction
echo in >/sys/class/gpio/gpio236/direction
Set GPIO to 0 or 1 if configured as output pin
echo 0 >/sys/class/gpio/gpio236/value
echo 1 >/sys/class/gpio/gpio236/value

== RS485/RS422 selection on PSC1 ==

In MPC5200 or schematic it is PSC2. In linux is PSC numbered from 0 so it is PSC1.

Pin configuration:
echo 254 >/sys/class/gpio/export
echo out >/sys/class/gpio/gpio254/direction

Run for RS485:
echo 1 >/sys/class/gpio/gpio254/value

Run for RS422:
echo 0 >/sys/class/gpio/gpio254/value

== Linux boot possibilities ==
=== PIN configuration ===
Bootloader is responsible for pin configuration. This is done by writing to '''GPS Port Configuration Register'''. The value written there is set by:
set psc_cfg 91551044

GPS Port Configuration Register values for our boards:
* original Midam board: 0x90552444
* RYU_EDU_midam v1.B: 0x91551044

=== Kernel and root filesystem from flash ===

This is the default boot command. If you want to quickly switch several boot combinations, you can store these commands to a variable and use run command to boot linux from flash quickly.

set bootcmd_linux 'set bootargs ${linux_console} ${bootargs_flash}; mw f0000b00 ${psc_cfg}; bootm fc120000 - fc100000'
set bootcmd 'run bootcmd_linux'
=== Kernel from flash and root filesystem over NFS===

set bootcmd_nfsroot 'set bootargs ${linux_console} ${bootargs_nfs}; dhcp; mw f0000b00 ${psc_cfg}; bootm fc120000 - fc100000'
set bootargs_nfs 'root=/dev/nfs nfsroot=/midam rw ip=dhcp'
run bootcmd_nfsroot

=== Kernel from TFTP and root filesystem over NFS===

set serverip 147.32.86.30
set nfspath "/home/wsh/ppc/MPC5200/root-shark"
set imagefile /srv/tftp/ryu/uImage
set devicetreefile /srv/tftp/ryu/shark-ryu.dtb
set bootcmd_tftpnfs 'dhcp; tftp 800000 ${imagefile}; tftp 7f0000 ${devicetreefile}; set bootargs ${linux_console} root=/dev/nfs nfsroot=${serverip}:${nfspath} rw ip=dhcp; mw f0000b00 ${psc_cfg}; bootm 800000 - 7f0000'
run bootcmd_tftpnfs

==== Without DHCP server (static IP configuration) ====

set ipaddr 192.168.2.3
set netmask 255.255.255.0
set serverip 192.168.2.2
set imagefile ryu/uImage
set devicetreefile ryu/shark-ryu.dtb
set nfspath /srv/nfs/root-shark
set bootcmd_tftpnfs_static 'tftp 800000 ${imagefile}; tftp 7f0000 ${devicetreefile}; set bootargs ${linux_console} root=/dev/nfs nfsroot=${serverip}:${nfspath} rw ip=${ipaddr}; mw f0000b00 ${psc_cfg}; bootm 800000 - 7f0000'
set bootcmd 'run bootcmd_tftpnfs_static'

=== Updating kernel image in flash memory ===

set serverip 10.1.1.101
set imagefile /srv/tftp/ryu/uImage
set devicetreefile /srv/tftp/ryu/shark-ryu.dtb
run update_kernel

It is supposed that update_kernel is set to the following value
set update_kernel 'dhcp; tftp 800000 ${imagefile}; erase fc100000 fc3fffff; cp.b 800000 fc120000 ${filesize}; tftp 800000 ${devicetreefile}; cp.b 800000 fc100000 ${filesize};'

=== Updating root filesystem image in flash memory ===

==== From Linux with NFS root ====
Erase flash in U-Boot:
erase fc400000 ffffffff

Boot Linux with NFS root and run:
mount -t jffs2 /dev/mtdblock2 /mnt
cd /
cp -a `ls | grep -v '$mnt\|proc\|sys\|tmp$'` /mnt
cd /mnt; mkdir mnt proc sys tmp

== Running RT kernel ==

cyclictest -p 80 -t5 -n
0.93 0.68 0.28 1/51 562

T: 0 ( 544) P:80 I:1000 C: 354314 Min: 16 Act: 76 Avg: 69 Max: 190
T: 1 ( 545) P:79 I:1500 C: 236209 Min: 17 Act: 35 Avg: 53 Max: 131
T: 2 ( 546) P:78 I:2000 C: 177157 Min: 21 Act: 46 Avg: 56 Max: 123
T: 3 ( 547) P:77 I:2500 C: 141726 Min: 21 Act: 41 Avg: 53 Max: 155
T: 4 ( 548) P:76 I:3000 C: 118105 Min: 23 Act: 30 Avg: 56 Max: 126

==== Kernel shark/2.6.33.7-rt29 ====

root@shark ~> cyclictest -p 80 -t5 -n
policy: fifo: loadavg: 117.09 33.86 11.60 1/47 981

T: 0 ( 550) P:80 I:1000 C: 293846 Min: 26 Act: 77 Avg: 58 Max: 132
T: 1 ( 551) P:79 I:1500 C: 195897 Min: 31 Act: 60 Avg: 68 Max: 170
T: 2 ( 552) P:78 I:2000 C: 146924 Min: 32 Act: 78 Avg: 65 Max: 137
T: 3 ( 553) P:77 I:2500 C: 117539 Min: 36 Act: 62 Avg: 60 Max: 199
T: 4 ( 554) P:76 I:3000 C: 97949 Min: 32 Act: 41 Avg: 62 Max: 128

Note: hackbench was executed during the test to load the CPU.

== VxWorks Support ==

=== Booting VxWorks ===

set ethaddr 00:04:9f:00:27:xx
set psc_cfg 91551044
set bootcmd_vxworks 'set serverip 147.32.87.34; dhcp; mw f0000b00 ${psc_cfg}; tftp 0x100000 vxworks/vxWorks-midam.bin; go 0x100000'
set bootcmd 'run bootcmd_vxworks'
saveenv

Older tests:
dhcp; set serverip 147.32.86.187; set bootfile vxWorks.bin; tftp 0x00100000; go 0x00100000

=== Compiling VxWorks ===

It is assumed that VxWorks in installed under <tt>/opt/WindRiver</tt>

/opt/WindRiver/wrenv.sh -p vxworks-6.7
cd <bsp_project>
make

VxWorks BSP and kernel projects used for [http://rtime.felk.cvut.cz/psr/ PSR course] can be downloaded [http://rtime.felk.cvut.cz/~sojka/vxworks/midam-vxworks.tar.gz as a tarball].

== RTEMS Support ==

MIDAM MPC5200 board is compatible with [http://www.rtems.org/ RTEMS] [http://www.rtems.org/wiki/index.php/Gen5200#IceCube IceCube] BSP.

The PowerPC [[Cross compilers| cross-compiler]] tool-chain for RTEMS-4.9 branch for Debian Intel 32 and 64-bit hosts
can be installed from Rtime local DEB repository [ftp://rtime.felk.cvut.cz/debian/pool/rtems-4.9/].

* Add APT source:
echo deb ftp://rtime.felk.cvut.cz/debian unstable main >/etc/apt/sources.list.d/rtime-debs.list
* Update list of available packages
apt-get update

Next packages can be installed from cross-dev section (e.g. using apt-get, aptitude or synaptic)
* binutils-powerpc-rtems4.10
* gcc-powerpc-rtems4.10
* rtems4.10-common
* rtems4.10-icecube

The configurations used for above binutils, GCC and RTEMS BSP packages build are stored
in [http://rtime.felk.cvut.cz/gitweb/rtems-devel.git local RTEMS development GIT repository]
in a [http://rtime.felk.cvut.cz/gitweb/rtems-devel.git/tree/HEAD:/rtems-build/powerpc-rtems build directory for PowerPC architecture].

The short cross-tools build recipe:
git clone git://rtime.felk.cvut.cz/rtems-devel.git
cd rtems-devel
mkdir src
cd src
tar -xjf path-to/gcc-4.3.4.tar.bz2
ln -s gcc-4.3.4 gcc
tar -xjf path-to/binutils-2.20
ln -s binutils-2.20 binutils
tar -xzf path-to/newlib-1.16.0.tar.gz
ln -s newlib-1.16.0 newlib
cd gcc
ln -s ../newlib/newlib .
ln -s ../../gcc-patches/4.3.4 patches
quilt push -a
cd ../newlib
ln -s ../../newlib-patches/newlib-1.16.0 patches
quilt push -a
cd ../..
ln -s src/gcc src/binutils src/rtems .
( cd rtems-build/powerpc-rtems/binutils && ./binutils-powerpc-rtems.cfg && make && make install )
( cd rtems-build/powerpc-rtems/gcc && ./gcc-powerpc-rtems.cfg && make && make install )
( cd rtems-build/powerpc-rtems/rtems-icecube && ./rtems-mpc5200-sys.cfg && make && make install )

Applications can be easily build by starting from
[http://rtime.felk.cvut.cz/gitweb/rtems-devel.git/tree/HEAD:/rtems-omk-template RTEMS application template]
based on [http://rtime.felk.cvut.cz/omk OMK] rules:
cd rtems-omk-template
echo "RTEMS_MAKEFILE_PATH=/opt/rtems4.9/powerpc-rtems4.9/icecube" >config.target
make default-config all

Compiled application ELF images are located in _compiled/icecube/bin directory. The ELF file needs to be
be converted into U-boot image to be transferred and started on target board
powerpc-rtems4.9-objcopy -R -S -O binary appfoo appfoo.bin
cat appfoo.bin | gzip -9 >appfoo.gz
mkimage -A ppc -O rtems -T kernel -a 0x00010000 -e 0x00010000 -n RTEMS -d appfoo.gz appfoo.img

The image tranfer and boot sequence can be initiated from target board U-boot prompt
mw f0000b00 ${psc_cfg}
dhcp
#set serverip 192.168.202.251
tftp 1000000 appfoo.img
bootm

The [http://rtime.felk.cvut.cz/gitweb/rtems-devel.git/blob/HEAD:/rtems-build/powerpc-rtems/rtems-icecube/rtems-mpc5200-mkimg script rtems-mpc5200-mkimg]
to pack ELF file to U-boot image is part of development repository as well.

=== NFS on RTEMS ===

Following OMK based example includes configuration required
to build network and NFS enabled application on RTEMS

[http://rtime.felk.cvut.cz/gitweb/rtems-devel.git/tree/HEAD:/rtems-omk-template/appnet rtems-omk-template/appnet]

Mounting NFS into RTEMS
mkdir /mnt
mkdir /mnt/nfs
mount -t nfs 192.168.2.2:/srv/nfs/root-shark /mnt/nfs

=== Open Real-Time Ethernet (ORTE) on RTEMS ===

ORTE is an open source C implementation of the Data Distribution
Service (DDS) and RTPS protocol.

ORTE project home page: http://orte.sourceforge.net/

Example fro RTEMS shell is included in ORTE code main repository

[http://sourceforge.net/p/orte/orte/ci/master/tree/orte/examples/rtems-shell/ orte/examples/rtems-shell/]

Running [http://orte.sourceforge.net/ ORTE] manager
spawn ortemanager -p 192.168.2.2 -e

Running [http://orte.sourceforge.net/ ORTE] ping
spawn orteping -s
spawn orteping -p

[[Category:Hardware]]
[[Category:MPC5200]]

MIDAM MPC5200 DB1

2014-01-23T22:53:44Z

Sojka: /* Linux kernel */

==Description==

Two sets of the MIDAM MPC5200 was delivered by the Mikroklima s.r.o. for our purposes. Each set consist of the:

* Shark MPC52000 CPU module (pin compatible with TQ Components TQM5200 module),
* MPC5200 v1.1 2008/02 carrier board.

Set #1 has s/n: '''008770''' and set #2 has s/n: '''008771'''.

* [[Media:SHARK_V1_1_DOC_CZ.pdf|SHARK_V1_1_DOC_CZ.pdf‎]]
* [[Media:SHARK_V1_0_linux_DOC_CZ.pdf|SHARK_V1_0_linux_DOC_CZ.pdf]]

==Schematics and components==
Download schematics in PDF: [[:File:Midam_expand_v1b.pdf]]

===List of components===
This list is not complete. It is just a subset of components needed for educational purpose.

'''POWER SUPPLY'''

C9 CAP1206 220pF
C10 CAP1206 22nF
C11 CAP1206 10uF
C12 tantal el. 330uF 6.3V D
C23 el. 470uF, 50V
C29 CAP0805 100n
C30 CAP0805 100n
C31 CAP0805 100n
C32 CAP0805 100n
C35 CAP0805 100n
C36 47uF10V B
C37 47uF10V B
C38 47uF10V B
C39 47uF10V B
D6 STPS2L30A
D9 LED 1206
D10 STPS2L30A
J7 PWR-CON
J10 SMD switch
L2 INDUCTOR DR127-150
R19 RES0805 4k7
R20 RES0805 5k6
R21 RES0805 3k3
R25 RES0805 330R
U11 STM811SW16F MPU LOW RESET 2.93V
U9 ST-L5973D

'''MIDAM HEADER'''

R34 RES0805 10k
R35 RES0805 10k
J1 Socket

'''USB-CLIENT'''

C5 CAP0805 100nF
C26 CAP0805 100n
D3 LED 1206
D4 LED 1206
L7 BLM21AG601SN1D FERRITE, BEAD, 0805, 0.21OHM, 0.6A
J4 USB-B
R9 RES0805 4k7
R10 RES0805 10k
R11 RES0805 270R
R12 RES0805 270R
R48 RES0805 10k
R49 RES0805 10k
U2 FT232RL

'''EXPAND HEADER'''

D5 ULN2803 DIO
D11 LED 1206
D12 LED 1206
D13 LED 1206
D14 LED 1206
D15 LED 1206
D16 LED 1206
D17 LED 1206
D18 LED 1206
D19 LED 1206
D20 LED 1206
J8 SMD SWITCH
J9 SMD SWITCH
R13 RES0805 330R
R14 RES0805 1k
R15 RES0805 1k
R16 RES0805 1k
R17 RES0805 330R
R18 RES0805 330R
R28 RES0805 10k
R29 RES0805 10k
R30 RES0805 2k
R31 RES0805 330R
R32 RES0805 2k
R33 RES0805 330R
R38 RES0805 330R
R39 RES0805 330R
R40 RES0805 330R
R41 RES0805 330R
R42 RES0805 330R
R43 RES0805 330R
R44 RES0805 330R
U3 BSS138 ANA
U4 BSS138 ANA
U6 BSS138 ANA
U7 BSS138 ANA
U8 BSS138 ANA
Q1 BC856ALT1G TRANSISTOR, PNP
Q2 BC856ALT1G TRANSISTOR, PNP

'''ETHERNET'''

C18 CAP0805 22nF
J2 TE Connectivity AMP 5-6605758-1

== Mailing List ==

Discussion related to this board happen in a [http://rtime.felk.cvut.cz/mailman/listinfo/shark5200 mailing list].

==Board overview==

[[Image:Board overview.jpg]]

==Serial line (system console)==

* Loader system console is attached to the ttyPSC0 port.
* The '''ttyPSC0 port is done in the LVTTL 3.3V logic''', so appropriate 3.3V to RS-232 converter (e.g. [http://pdfserv.maxim-ic.com/en/ds/MAX3222-MAX3241.pdf MAX3232]) is required for the serial console.

'''Communication parameters:'''
* baud rate: 115200 bps
* bits: 8 bit
* stop bits: 1 bit
* Parity: none
* Flow control: none

==Module memory map==
The MPC5200B is 32 bit CPU, so it has a 32 bit address space. It is able to address up to 4 294 967 295 B (0xFFFFFFFF) - 4096 MB. The Shark module has been equipped with '''128 MB''' DDR RAM and '''64 MB''' NOR flash memory.
* RAM chips: Samsung K4S511632D-UC(L)75, order: 32M x 16
* Address space '''BASE address''' is 0x00000000
* RAM is from 0x00000000 to 0x08000000 (128 MB)

Flash memory is being mapped at the and of address space (from 3.9375 GB).
* '''Flash BASE address''' is 0xFC000000 (last address is 0xFFFFFFFF)
* Flash memory size is 0x04000000 (64 MB)

There are three MTD partitions in the flash (defined in shark.dts). The flat device tree file syntax uses first address and length of the partition for its definition.
* u-Boot (1 MB) from 0x00000000 to 0x00100000, length 0x00100000
* kernel (3 MB) from 0x00100000 to 0x00400000, length 0x00300000
* '''file-system''' (56 MB) from 0x00400000 to 0x04000000, length 0x03C00000
All these addresses are offsets against Flash BASE.

==Boot loader==
These boards are preinstalled with [http://www.denx.de/wiki/DULG/Manual Das u-Boot] boot loader.
Behaviour of the u-Boot can be handled by its environment variables. Here are some useful commands:

*'''printenv [variable]''' - prints complete environment or only given variable.
*'''saveenv''' - commits whole environment in flash memory

For running linux kernel >2.6.25 it's necessary to have u-Boot 1.3.2 or later, which is able to hand over flat device tree to the kernel. When older revision is present, it is necessary to upgrade. Binary of u-Boot can be downloaded here: [ftp://rtime.felk.cvut.cz/shark-mpc5200/u-boot.bin u-boot.bin].

'''U-Boot upgrade howto:'''

During the upgrade procedure it is necessary to proceed with utmost precaution, because '''there is no backup image''' of the u-Boot in the flash for recovery purposes. Fail-flash recovery isn't possible without JTAG interface. So, you have been warned. In future builds of the u-Boot there should be a support for recovery image. Follow this commands to upgrade U-Boot's image in flash memory:

dhcp
tftp 800000 u-boot.bin
protect off fc000000 fc09ffff
erase fc000000 fc09ffff
cp.b 800000 fc000000 ${filesize}
protect on fc000000 fc09ffff

Now reboot and than commit new default environment:

saveenv

===How to access U-Boot environment variables from Linux ?===
The U-Boot environment variables is possible to read and write trough utilities ... TO DO

==Cross-tool chain==
Necessary cross-tool chain for PowerPC platform can be build using Crossdev tool. You can install Crossdev on your Gentoo distro very simply:

emerge -av crossdev

Some dependencies may go before. Building of tool chain itself will take some time, so let's go to take some coffee.

crossdev --b 2.18-r3 --k 2.6.23-r3 --g 4.1.2 --without-headers -t powerpc-unknown-linux-gnu

For Debian, you can use a [[Cross compilers|packages]] prepared by Pavel Píša.

== Linux kernel ==

=== Instructions for recent kernels ===

You need [https://rtime.felk.cvut.cz/gitweb/shark/linux.git/commitdiff/87a8e2b9406cc7f8779f02047e0cd1594c570b78 this simple patch] to boot Linux on MIDAM/RYU board.

=== Instructions for old kernels ===

It is necessary to use patched Linux sources. We maintain them in our [[Git]] [http://rtime.felk.cvut.cz/gitweb/shark/linux.git repository]. You can clone it by:
git clone git://rtime.felk.cvut.cz/shark/linux.git

Now you can choose the kernel revision you want to compile:

git branch -r # there you can see all branches available
git checkout origin/shark/2.6.28.8 # choose the one you desire

Note: See [[Linux sources]] for the description of the repository and patch management techniques we use.

Now let's begin with the kernel configuration and compilation. The following recipe can be used to compile the kernel out of source directory, which is helpful if you want to compile a single kernel version with several configurations.
* <tt>cd linux</tt>
* <tt>mkdir -p _build/midam</tt>
* <tt>cd _build/midam</tt>
* Copy the following code to <tt>GNUmakefile</tt> file
<pre>
VERSION = 2
PATCHLEVEL = 6

KERNELSRC := $(shell cd ../..; pwd)
KERNELOUTPUT := $(patsubst $(KERNELSRC)/%,%,$(shell pwd))

KERNELRELEASE = $(shell cat include/config/kernel.release 2> /dev/null)

MAKEFLAGS += --no-print-directory

ARCH=powerpc
CROSS_COMPILE=powerpc-linux-gnu-

TFTPBOOT=/var/lib/tftpboot/ryu

export INSTALL_MOD_PATH=$(KERNELSRC)/../MPC5200_root

.PHONY: install all $(MAKECMDGOALS)

all:
$(MAKE) ARCH=$(ARCH) CROSS_COMPILE=$(CROSS_COMPILE) -C $(KERNELSRC) O=$(KERNELOUTPUT)

Makefile:;

$(filter-out all Makefile,$(MAKECMDGOALS)) %/:
$(MAKE) ARCH=$(ARCH) CROSS_COMPILE=$(CROSS_COMPILE) -C $(KERNELSRC) O=$(KERNELOUTPUT) $@
</pre>

* <tt>make 52xx/midam_defconfig</tt> # or use <tt>52xx/ryu_defconfig</tt> for RYU board
* <tt>make menuconfig</tt> # if you need additional configuration
* <tt>make</tt> # start compilation; <tt>u-boot-tools</tt> should be properly installed before compilation

The compiled image can be found in linux/_build/midam/arch/powerpc/boot
It is the file uImage. Copy it to your tftpboot directory.

'''How to build the Flat Device Tree file'''

Since kernel version 2.6.25 is description of the platform hardware provided trough the Flat Device Tree. Necessary sources are now part of the kernel sources. Appropriate image could be build with this command:

make ARCH=powerpc shark.dtb DTS_FLAGS="-S65536"

If DTS_FLAGS parameter omitted than following error will occur, because there is not enough space in the file, where the u-Boot can store some additional data about buses timing, etc.:

WARNING: could not create /chosen FDT_ERR_NOSPACE.
ERROR: /chosen node create failed - must RESET the board to recover.

==Root file system==

New root file system has been built for MIDAM MPC5200 board. It's based on:
* Vanilla linux kernel v2.6.26.5
* Busybox v1.12.1
* Dropbear v0.51
* thttpd v2.25b

TODO: How to build a new root file system

== TO DO - UnionFS for root FS in flash ==

For long term usage is not really good to repeatedly overwrite block in the NOR flash chip, because memory cells are being punished. So it would be better to use jffs2 root FS only as RO file system and create RW tmpfs of same size. UnionFS than could be used to merge these two file systems and provide one RW file system. Changes in FS as a lock and log files can be made without permanent effect.

==SocketCan==

SocketCan is currently tested only with kernels 2.6.28 or lower. If you want to use Socket Can, it is currently recommended to use kernel 2.6.28. To enable SocketCan support, it is neccesary to run

make menuconfig

before building the kernel and set the following:

Networking Support / CAN bus subsystem support (yes)
Raw CAN Protocol (raw access with CAN-ID filtering) (yes)
CAN Device Drivers / Virtual Local CAN Interface (vcan) (yes)
Prompt for platform CAN drivers with sysfs support (yes)
Support for a Freescale MSCAN based chips (yes)
Freescale MPC5200 onboard CAN controller (yes)

make KERNELDIR=/home/marsark/src/linux-2.6.26.5/_build/mpc5200_ryu/ CONFIG_CAN_MPC52XX=m CONFIG_CAN_MSCAN=m

CAN subsystem init script:

modprobe can
modprobe mscan-mpc52xx
modprobe can-raw

echo 1000000 > /sys/class/net/can0/can_bittiming/bitrate
echo 1000000 > /sys/class/net/can1/can_bittiming/bitrate

If the above commands fail, you have a new version of socketcan and you need to use ip tool to set bitrate. See bellow.

ifconfig can0 up
ifconfig can1 up

Warning - the ip tool is not working properly yet!

Test the setup:

cansend can0 123#4567

=== Using ip tool ===

ip link set can0 type can bitrate 1000000
ip link set up dev can0
ip link set can1 type can bitrate 1000000
ip link set up dev can1

==== Compilation ====

git clone git://git.kernel.org/pub/scm/network/iproute2/iproute2.git
cd iproute2
make CC=powerpc-linux-gnu-gcc

The make will probably fail but fortunately the <tt>ip/ip</tt> is already compiled.

== GPIO how set pin value ==
In MPC5200 have two kind of GPIO. The first one have wakeup capability, the second one is standard GPIO pins. Each of this sets have its own register sets, so some PSC ports are splitted in to two parts. See MOC5200B documentation section 7.3.2.1 and 7.3.2.2. The availability GPIO of PSC depends on GPS Port Configuration Register settings. For RYU boards is available all GPIO in PSC3 port (HW notation).

'''TODO: kernel still fails to initialise GPIO drivers on our boards !!!'''

cat /sys/class/gpio/gpiochip248/label //todo

=== Setting GPIO with wakeup capability ===
GPIO with wakeup using
/sys/class/gpio/gpiochip248/

Pin notation:
0 -> GPIO_WKUP_7
1 -> GPIO_WKUP_6
2 -> PSC6_1
3 -> PSC6_0
4 -> ETH_17
5 -> PSC3_9
6 -> PSC2_4
7 -> PSC1_4

Final value is 248 + requested pin (example for PSC2_4 248+6 => 254)

Enable PIN for GPIO:
echo 254 >/sys/class/gpio/export
Set GPIO as output or input
echo out >/sys/class/gpio/gpio254/direction
echo in >/sys/class/gpio/gpio254/direction
Set GPIO to 0 or 1 if configured as output pin
echo 0 >/sys/class/gpio/gpio254/value
echo 1 >/sys/class/gpio/gpio254/value

=== Setting standard GPIO not tested ===
Standard GPIO using
/sys/class/gpio/gpiochip216/

Pin notation:
0..1 > reserved
2..3 > IRDA
4..7 > ETHR
8..11 > reserved
12..15 > USB
16..17 > reserved
18..23 > PSC3
24..27 > PSC2
28..31 > PSC1

Final value is 216 + requested pin (example for PSC3_3 216+20 => 236)

Enable PIN for GPIO:
echo 236 >/sys/class/gpio/export
Set GPIO as output or input
echo out >/sys/class/gpio/gpio236/direction
echo in >/sys/class/gpio/gpio236/direction
Set GPIO to 0 or 1 if configured as output pin
echo 0 >/sys/class/gpio/gpio236/value
echo 1 >/sys/class/gpio/gpio236/value

== RS485/RS422 selection on PSC1 ==

In MPC5200 or schematic it is PSC2. In linux is PSC numbered from 0 so it is PSC1.

Pin configuration:
echo 254 >/sys/class/gpio/export
echo out >/sys/class/gpio/gpio254/direction

Run for RS485:
echo 1 >/sys/class/gpio/gpio254/value

Run for RS422:
echo 0 >/sys/class/gpio/gpio254/value

== Linux boot possibilities ==
=== PIN configuration ===
Bootloader is responsible for pin configuration. This is done by writing to '''GPS Port Configuration Register'''. The value written there is set by:
set psc_cfg 91551044

GPS Port Configuration Register values for our boards:
* original Midam board: 0x90552444
* RYU_EDU_midam v1.B: 0x91551044

=== Kernel and root filesystem from flash ===

This is the default boot command. If you want to quickly switch several boot combinations, you can store these commands to a variable and use run command to boot linux from flash quickly.

set bootcmd_linux 'set bootargs ${linux_console} ${bootargs_flash}; mw f0000b00 ${psc_cfg}; bootm fc120000 - fc100000'
set bootcmd 'run bootcmd_linux'
=== Kernel from flash and root filesystem over NFS===

set bootcmd_nfsroot 'set bootargs ${linux_console} ${bootargs_nfs}; dhcp; mw f0000b00 ${psc_cfg}; bootm fc120000 - fc100000'
set bootargs_nfs 'root=/dev/nfs nfsroot=/midam rw ip=dhcp'
run bootcmd_nfsroot

=== Kernel from TFTP and root filesystem over NFS===

set serverip 147.32.86.30
set nfspath "/home/wsh/ppc/MPC5200/root-shark"
set imagefile /srv/tftp/ryu/uImage
set devicetreefile /srv/tftp/ryu/shark-ryu.dtb
set bootcmd_tftpnfs 'dhcp; tftp 800000 ${imagefile}; tftp 7f0000 ${devicetreefile}; set bootargs ${linux_console} root=/dev/nfs nfsroot=${serverip}:${nfspath} rw ip=dhcp; mw f0000b00 ${psc_cfg}; bootm 800000 - 7f0000'
run bootcmd_tftpnfs

==== Without DHCP server (static IP configuration) ====

set ipaddr 192.168.2.3
set netmask 255.255.255.0
set serverip 192.168.2.2
set imagefile ryu/uImage
set devicetreefile ryu/shark-ryu.dtb
set nfspath /srv/nfs/root-shark
set bootcmd_tftpnfs_static 'tftp 800000 ${imagefile}; tftp 7f0000 ${devicetreefile}; set bootargs ${linux_console} root=/dev/nfs nfsroot=${serverip}:${nfspath} rw ip=${ipaddr}; mw f0000b00 ${psc_cfg}; bootm 800000 - 7f0000'
set bootcmd 'run bootcmd_tftpnfs_static'

=== Updating kernel image in flash memory ===

set serverip 10.1.1.101
set imagefile /srv/tftp/ryu/uImage
set devicetreefile /srv/tftp/ryu/shark-ryu.dtb
run update_kernel

It is supposed that update_kernel is set to the following value
set update_kernel 'dhcp; tftp 800000 ${imagefile}; erase fc100000 fc3fffff; cp.b 800000 fc120000 ${filesize}; tftp 800000 ${devicetreefile}; cp.b 800000 fc100000 ${filesize};'

=== Updating root filesystem image in flash memory ===

==== From Linux with NFS root ====
Erase flash in U-Boot:
erase fc400000 ffffffff

Boot Linux with NFS root and run:
mount -t jffs2 /dev/mtdblock2 /mnt
cd /
cp -a `ls | grep -v '$mnt\|proc\|sys\|tmp$'` /mnt
cd /mnt; mkdir mnt proc sys tmp

== Running RT kernel ==

cyclictest -p 80 -t5 -n
0.93 0.68 0.28 1/51 562

T: 0 ( 544) P:80 I:1000 C: 354314 Min: 16 Act: 76 Avg: 69 Max: 190
T: 1 ( 545) P:79 I:1500 C: 236209 Min: 17 Act: 35 Avg: 53 Max: 131
T: 2 ( 546) P:78 I:2000 C: 177157 Min: 21 Act: 46 Avg: 56 Max: 123
T: 3 ( 547) P:77 I:2500 C: 141726 Min: 21 Act: 41 Avg: 53 Max: 155
T: 4 ( 548) P:76 I:3000 C: 118105 Min: 23 Act: 30 Avg: 56 Max: 126

==== Kernel shark/2.6.33.7-rt29 ====

root@shark ~> cyclictest -p 80 -t5 -n
policy: fifo: loadavg: 117.09 33.86 11.60 1/47 981

T: 0 ( 550) P:80 I:1000 C: 293846 Min: 26 Act: 77 Avg: 58 Max: 132
T: 1 ( 551) P:79 I:1500 C: 195897 Min: 31 Act: 60 Avg: 68 Max: 170
T: 2 ( 552) P:78 I:2000 C: 146924 Min: 32 Act: 78 Avg: 65 Max: 137
T: 3 ( 553) P:77 I:2500 C: 117539 Min: 36 Act: 62 Avg: 60 Max: 199
T: 4 ( 554) P:76 I:3000 C: 97949 Min: 32 Act: 41 Avg: 62 Max: 128

Note: hackbench was executed during the test to load the CPU.

== VxWorks Support ==

=== Booting VxWorks ===

set ethaddr 00:04:9f:00:27:xx
set psc_cfg 91551044
set bootcmd_vxworks 'set serverip 147.32.87.34; dhcp; mw f0000b00 ${psc_cfg}; tftp 0x100000 vxworks/vxWorks-midam.bin; go 0x100000'
set bootcmd 'run bootcmd_vxworks'
saveenv

Older tests:
dhcp; set serverip 147.32.86.187; set bootfile vxWorks.bin; tftp 0x00100000; go 0x00100000

=== Compiling VxWorks ===

It is assumed that VxWorks in installed under <tt>/opt/WindRiver</tt>

/opt/WindRiver/wrenv.sh -p vxworks-6.7
cd <bsp_project>
make

VxWorks BSP and kernel projects used for [http://rtime.felk.cvut.cz/psr/ PSR course] can be downloaded [http://rtime.felk.cvut.cz/~sojka/vxworks/midam-vxworks.tar.gz as a tarball].

== RTEMS Support ==

MIDAM MPC5200 board is compatible with [http://www.rtems.org/ RTEMS] [http://www.rtems.org/wiki/index.php/Gen5200#IceCube IceCube] BSP.

The PowerPC [[Cross compilers| cross-compiler]] tool-chain for RTEMS-4.9 branch for Debian Intel 32 and 64-bit hosts
can be installed from Rtime local DEB repository [ftp://rtime.felk.cvut.cz/debian/pool/rtems-4.9/].

* Add APT source:
echo deb ftp://rtime.felk.cvut.cz/debian unstable main >/etc/apt/sources.list.d/rtime-debs.list
* Update list of available packages
apt-get update

Next packages can be installed from cross-dev section (e.g. using apt-get, aptitude or synaptic)
* binutils-powerpc-rtems4.10
* gcc-powerpc-rtems4.10
* rtems4.10-common
* rtems4.10-icecube

The configurations used for above binutils, GCC and RTEMS BSP packages build are stored
in [http://rtime.felk.cvut.cz/gitweb/rtems-devel.git local RTEMS development GIT repository]
in a [http://rtime.felk.cvut.cz/gitweb/rtems-devel.git/tree/HEAD:/rtems-build/powerpc-rtems build directory for PowerPC architecture].

The short cross-tools build recipe:
git clone git://rtime.felk.cvut.cz/rtems-devel.git
cd rtems-devel
mkdir src
cd src
tar -xjf path-to/gcc-4.3.4.tar.bz2
ln -s gcc-4.3.4 gcc
tar -xjf path-to/binutils-2.20
ln -s binutils-2.20 binutils
tar -xzf path-to/newlib-1.16.0.tar.gz
ln -s newlib-1.16.0 newlib
cd gcc
ln -s ../newlib/newlib .
ln -s ../../gcc-patches/4.3.4 patches
quilt push -a
cd ../newlib
ln -s ../../newlib-patches/newlib-1.16.0 patches
quilt push -a
cd ../..
ln -s src/gcc src/binutils src/rtems .
( cd rtems-build/powerpc-rtems/binutils && ./binutils-powerpc-rtems.cfg && make && make install )
( cd rtems-build/powerpc-rtems/gcc && ./gcc-powerpc-rtems.cfg && make && make install )
( cd rtems-build/powerpc-rtems/rtems-icecube && ./rtems-mpc5200-sys.cfg && make && make install )

Applications can be easily build by starting from
[http://rtime.felk.cvut.cz/gitweb/rtems-devel.git/tree/HEAD:/rtems-omk-template RTEMS application template]
based on [http://rtime.felk.cvut.cz/omk OMK] rules:
cd rtems-omk-template
echo "RTEMS_MAKEFILE_PATH=/opt/rtems4.9/powerpc-rtems4.9/icecube" >config.target
make default-config all

Compiled application ELF images are located in _compiled/icecube/bin directory. The ELF file needs to be
be converted into U-boot image to be transferred and started on target board
powerpc-rtems4.9-objcopy -R -S -O binary appfoo appfoo.bin
cat appfoo.bin | gzip -9 >appfoo.gz
mkimage -A ppc -O rtems -T kernel -a 0x00010000 -e 0x00010000 -n RTEMS -d appfoo.gz appfoo.img

The image tranfer and boot sequence can be initiated from target board U-boot prompt
mw f0000b00 ${psc_cfg}
dhcp
#set serverip 192.168.202.251
tftp 1000000 appfoo.img
bootm

The [http://rtime.felk.cvut.cz/gitweb/rtems-devel.git/blob/HEAD:/rtems-build/powerpc-rtems/rtems-icecube/rtems-mpc5200-mkimg script rtems-mpc5200-mkimg]
to pack ELF file to U-boot image is part of development repository as well.

=== NFS on RTEMS ===

Following OMK based example includes configuration required
to build network and NFS enabled application on RTEMS

[http://rtime.felk.cvut.cz/gitweb/rtems-devel.git/tree/HEAD:/rtems-omk-template/appnet rtems-omk-template/appnet]

Mounting NFS into RTEMS
mkdir /mnt
mkdir /mnt/nfs
mount -t nfs 192.168.2.2:/srv/nfs/root-shark /mnt/nfs

=== Open Real-Time Ethernet (ORTE) on RTEMS ===

ORTE is an open source C implementation of the Data Distribution
Service (DDS) and RTPS protocol.

ORTE project home page: http://orte.sourceforge.net/

Example fro RTEMS shell is included in ORTE code main repository

[http://sourceforge.net/p/orte/orte/ci/master/tree/orte/examples/rtems-shell/ orte/examples/rtems-shell/]

Running [http://orte.sourceforge.net/ ORTE] manager
spawn ortemanager -p 192.168.2.2 -e

Running [http://orte.sourceforge.net/ ORTE] ping
spawn orteping -s
spawn orteping -p

[[Category:Hardware]]
[[Category:MPC5200]]

Git repository on this server

2013-11-01T16:23:48Z

Sojka: /* Cloning the repository */

Repositories on rtime server are managed by [http://github.com/sitaramc/gitolite Gitolite tool], which allows to conveniently manage repository permissions. World readable repositories can be [http://rtime.felk.cvut.cz/gitweb browsed online].

In addition to gitolite repositories, users with shell account can create [[Git repositories in home directories|Git repositories in their home directory]]. This does not require any coordination with the administrator.

== Getting write access to repositories ==

Write access to the repositories can only be given to users who send the following information to the [http://rtime.felk.cvut.cz/~sojka/ administrator]:

# OpenSSH public key
# Login name (for ČVUT people) or email address (for others).

=== SSH key creation ===

The SSH key can be created with one of the following ways:

# Under Linux/Unix (or in Git Bash under Windows) run: <pre>ssh-keygen</pre>
# In Git Gui (under Linux or Windows) choose [[Media:Git-gui-key.jpg|Help -> Show SSH key -> Generate key]].
# Under Windows use PuTTYgen. Use this if you have chosen to [[Media:git-plink.jpg|use Pling]] during Git installation.

It is stored by default at <tt>~/.ssh/id_rsa.pub</tt>.

=== Password-protected keys ===

During the key creation you will be asked for a passphrase. If you do not specify any passphrase, anybody with access to your <tt>~/.ssh</tt> directory could access your repositories. If you specify the passphrase, it will need to be entered whenever you want to push to or pull from the server. By using <tt>ssh-add</tt> command (or Pageant program under Windows) you can specify the passphrase only once and the decrypted key will be remembered in the memory.

== Creating repositories ==

There are to ways how a repository can be created:

# Send an email to the [http://rtime.felk.cvut.cz/~sojka/ administrator] with the name of the repository, a short description and a list of people (login or email) who should have access to the repository. The administrator creates the repository for you and notifies you when it's done.
# Our group staff members can create their repositories without asking the administrator. See below.

=== Automatic creation of repositories (staff members only) ===

It is simply a matter of pushing the repository to a special URL containing the login, like this:

git push --set-upstream ssh://git@rtime.felk.cvut.cz/«login»/«whatever» HEAD

This will create a new repository called «whatever» (if it does not exist yet) and push the current HEAD to it. It also makes this repository the default for pushing and pulling (this is what --set-upstream does).

Such repository is by default accessible only to the creator. If you want this repository to be public, run
ssh git@rtime.felk.cvut.cz perms «login»/«whatever» + READERS @all

If you want to set a [https://rtime.felk.cvut.cz/gitweb/orte.git Gitweb description] for public repositories created this way, use gitolite's desc commands. I.e. you can set the description by:
ssh git@rtime.felk.cvut.cz desc «login»/«whatever» "Description"

== Accessing the repository ==

After [[Git#Install_Git|installing Git]] on your local computer, you
can access the repository as follows.

=== Cloning the repository ===

Read/Write access (for users with registered SSH key):
git clone ssh://git@rtime.felk.cvut.cz/''repo-name''

Read-only access (for public repositories only):
git clone git://rtime.felk.cvut.cz/''repo-name''.git
git clone http://rtime.felk.cvut.cz/git/''repo-name''.git

=== First push to admin-created repositories ===

After an empty repository is created by the admin, you can push (i.e. upload) the data to it:

* [[#Cloning the repository|Clone]] the empty repository.
* Put your sources into your cloned repository
git add . # tells git to track all files in your project
git commit # commits the added files to the repository
* Push your sources to the server
git push

=== Pushing to non-master branches ===

If you are not allowed to push to the master branch but to a different one, you have to push like this:
git push origin master:your-branch
which pushes your local master branch to the remote branch ''your-branch''.

To make this behavior default run
git config remote.origin.push master:your-branch

And from now on, it is sufficient to run only
git push

== Managing repositories ==

=== Finding available repositories ===

You can find the list of repositories you have access to by running:

ssh git@rtime.felk.cvut.cz info [filter]

where filter is optional string used to filter the list.

=== Permissions to automatic repositories ===

The owners of automatically created repositories can manage the access permissions by themselves.

The current permissions can be listed by:

ssh git@rtime.felk.cvut.cz perms -l «repo»

You can add permissions for either reading of writing the repo with:
ssh git@rtime.felk.cvut.cz perms «repo» + READERS «login»
ssh git@rtime.felk.cvut.cz perms «repo» + WRITERS «login»

The permissions can be removed by replacing '''+''' with '''-'''.

To make your repository visible on gitweb, run:
ssh git@rtime.felk.cvut.cz perms «repo» + READERS @all

== Links to git related documents ==

* [http://support.dce.felk.cvut.cz/mediawiki/index.php/gitolite Gitolite documentation on DCE IT pages]

[[Category:Git]]

Git repository on this server

2013-11-01T16:22:43Z

Sojka: /* Automatic creation of repositories (staff members only) */

Repositories on rtime server are managed by [http://github.com/sitaramc/gitolite Gitolite tool], which allows to conveniently manage repository permissions. World readable repositories can be [http://rtime.felk.cvut.cz/gitweb browsed online].

In addition to gitolite repositories, users with shell account can create [[Git repositories in home directories|Git repositories in their home directory]]. This does not require any coordination with the administrator.

== Getting write access to repositories ==

Write access to the repositories can only be given to users who send the following information to the [http://rtime.felk.cvut.cz/~sojka/ administrator]:

# OpenSSH public key
# Login name (for ČVUT people) or email address (for others).

=== SSH key creation ===

The SSH key can be created with one of the following ways:

# Under Linux/Unix (or in Git Bash under Windows) run: <pre>ssh-keygen</pre>
# In Git Gui (under Linux or Windows) choose [[Media:Git-gui-key.jpg|Help -> Show SSH key -> Generate key]].
# Under Windows use PuTTYgen. Use this if you have chosen to [[Media:git-plink.jpg|use Pling]] during Git installation.

It is stored by default at <tt>~/.ssh/id_rsa.pub</tt>.

=== Password-protected keys ===

During the key creation you will be asked for a passphrase. If you do not specify any passphrase, anybody with access to your <tt>~/.ssh</tt> directory could access your repositories. If you specify the passphrase, it will need to be entered whenever you want to push to or pull from the server. By using <tt>ssh-add</tt> command (or Pageant program under Windows) you can specify the passphrase only once and the decrypted key will be remembered in the memory.

== Creating repositories ==

There are to ways how a repository can be created:

# Send an email to the [http://rtime.felk.cvut.cz/~sojka/ administrator] with the name of the repository, a short description and a list of people (login or email) who should have access to the repository. The administrator creates the repository for you and notifies you when it's done.
# Our group staff members can create their repositories without asking the administrator. See below.

=== Automatic creation of repositories (staff members only) ===

It is simply a matter of pushing the repository to a special URL containing the login, like this:

git push --set-upstream ssh://git@rtime.felk.cvut.cz/«login»/«whatever» HEAD

This will create a new repository called «whatever» (if it does not exist yet) and push the current HEAD to it. It also makes this repository the default for pushing and pulling (this is what --set-upstream does).

Such repository is by default accessible only to the creator. If you want this repository to be public, run
ssh git@rtime.felk.cvut.cz perms «login»/«whatever» + READERS @all

If you want to set a [https://rtime.felk.cvut.cz/gitweb/orte.git Gitweb description] for public repositories created this way, use gitolite's desc commands. I.e. you can set the description by:
ssh git@rtime.felk.cvut.cz desc «login»/«whatever» "Description"

== Accessing the repository ==

After [[Git#Install_Git|installing Git]] on your local computer, you
can access the repository as follows.

=== Cloning the repository ===

Read/Write access (for users with registered SSH key):
git clone ssh://git@rtime.felk.cvut.cz/''repo-name''

Read-only access (for public repositories only):
git clone git://rtime.felk.cvut.cz/''repo-name''.git

=== First push to admin-created repositories ===

After an empty repository is created by the admin, you can push (i.e. upload) the data to it:

* [[#Cloning the repository|Clone]] the empty repository.
* Put your sources into your cloned repository
git add . # tells git to track all files in your project
git commit # commits the added files to the repository
* Push your sources to the server
git push

=== Pushing to non-master branches ===

If you are not allowed to push to the master branch but to a different one, you have to push like this:
git push origin master:your-branch
which pushes your local master branch to the remote branch ''your-branch''.

To make this behavior default run
git config remote.origin.push master:your-branch

And from now on, it is sufficient to run only
git push

== Managing repositories ==

=== Finding available repositories ===

You can find the list of repositories you have access to by running:

ssh git@rtime.felk.cvut.cz info [filter]

where filter is optional string used to filter the list.

=== Permissions to automatic repositories ===

The owners of automatically created repositories can manage the access permissions by themselves.

The current permissions can be listed by:

ssh git@rtime.felk.cvut.cz perms -l «repo»

You can add permissions for either reading of writing the repo with:
ssh git@rtime.felk.cvut.cz perms «repo» + READERS «login»
ssh git@rtime.felk.cvut.cz perms «repo» + WRITERS «login»

The permissions can be removed by replacing '''+''' with '''-'''.

To make your repository visible on gitweb, run:
ssh git@rtime.felk.cvut.cz perms «repo» + READERS @all

== Links to git related documents ==

* [http://support.dce.felk.cvut.cz/mediawiki/index.php/gitolite Gitolite documentation on DCE IT pages]

[[Category:Git]]

Git repository on this server

2013-11-01T16:19:52Z

Sojka: /* Creating repositories */

Repositories on rtime server are managed by [http://github.com/sitaramc/gitolite Gitolite tool], which allows to conveniently manage repository permissions. World readable repositories can be [http://rtime.felk.cvut.cz/gitweb browsed online].

In addition to gitolite repositories, users with shell account can create [[Git repositories in home directories|Git repositories in their home directory]]. This does not require any coordination with the administrator.

== Getting write access to repositories ==

Write access to the repositories can only be given to users who send the following information to the [http://rtime.felk.cvut.cz/~sojka/ administrator]:

# OpenSSH public key
# Login name (for ČVUT people) or email address (for others).

=== SSH key creation ===

The SSH key can be created with one of the following ways:

# Under Linux/Unix (or in Git Bash under Windows) run: <pre>ssh-keygen</pre>
# In Git Gui (under Linux or Windows) choose [[Media:Git-gui-key.jpg|Help -> Show SSH key -> Generate key]].
# Under Windows use PuTTYgen. Use this if you have chosen to [[Media:git-plink.jpg|use Pling]] during Git installation.

It is stored by default at <tt>~/.ssh/id_rsa.pub</tt>.

=== Password-protected keys ===

During the key creation you will be asked for a passphrase. If you do not specify any passphrase, anybody with access to your <tt>~/.ssh</tt> directory could access your repositories. If you specify the passphrase, it will need to be entered whenever you want to push to or pull from the server. By using <tt>ssh-add</tt> command (or Pageant program under Windows) you can specify the passphrase only once and the decrypted key will be remembered in the memory.

== Creating repositories ==

There are to ways how a repository can be created:

# Send an email to the [http://rtime.felk.cvut.cz/~sojka/ administrator] with the name of the repository, a short description and a list of people (login or email) who should have access to the repository. The administrator creates the repository for you and notifies you when it's done.
# Our group staff members can create their repositories without asking the administrator. See below.

=== Automatic creation of repositories (staff members only) ===

It is simply a matter of pushing the repository to a special URL containing the login, like this:

git push --set-upstream ssh://git@rtime.felk.cvut.cz/«login»/«whatever» HEAD

This will create a new repository called «whatever» (if it does not exist yet) and push the current HEAD to it. It also makes this repository the default for pushing and pulling (this is what --set-upstream does).

If you want to set a [https://rtime.felk.cvut.cz/gitweb/orte.git Gitweb description] for repositories created this way, use gitolite's desc commands. I.e. you can set the description by:
ssh git@rtime.felk.cvut.cz desc «login»/«whatever» "Description"

== Accessing the repository ==

After [[Git#Install_Git|installing Git]] on your local computer, you
can access the repository as follows.

=== Cloning the repository ===

Read/Write access (for users with registered SSH key):
git clone ssh://git@rtime.felk.cvut.cz/''repo-name''

Read-only access (for public repositories only):
git clone git://rtime.felk.cvut.cz/''repo-name''.git

=== First push to admin-created repositories ===

After an empty repository is created by the admin, you can push (i.e. upload) the data to it:

* [[#Cloning the repository|Clone]] the empty repository.
* Put your sources into your cloned repository
git add . # tells git to track all files in your project
git commit # commits the added files to the repository
* Push your sources to the server
git push

=== Pushing to non-master branches ===

If you are not allowed to push to the master branch but to a different one, you have to push like this:
git push origin master:your-branch
which pushes your local master branch to the remote branch ''your-branch''.

To make this behavior default run
git config remote.origin.push master:your-branch

And from now on, it is sufficient to run only
git push

== Managing repositories ==

=== Finding available repositories ===

You can find the list of repositories you have access to by running:

ssh git@rtime.felk.cvut.cz info [filter]

where filter is optional string used to filter the list.

=== Permissions to automatic repositories ===

The owners of automatically created repositories can manage the access permissions by themselves.

The current permissions can be listed by:

ssh git@rtime.felk.cvut.cz perms -l «repo»

You can add permissions for either reading of writing the repo with:
ssh git@rtime.felk.cvut.cz perms «repo» + READERS «login»
ssh git@rtime.felk.cvut.cz perms «repo» + WRITERS «login»

The permissions can be removed by replacing '''+''' with '''-'''.

To make your repository visible on gitweb, run:
ssh git@rtime.felk.cvut.cz perms «repo» + READERS @all

== Links to git related documents ==

* [http://support.dce.felk.cvut.cz/mediawiki/index.php/gitolite Gitolite documentation on DCE IT pages]

[[Category:Git]]

Git repository on this server

2013-11-01T16:18:02Z

Sojka: /* Getting write access to repositories */

Repositories on rtime server are managed by [http://github.com/sitaramc/gitolite Gitolite tool], which allows to conveniently manage repository permissions. World readable repositories can be [http://rtime.felk.cvut.cz/gitweb browsed online].

In addition to gitolite repositories, users with shell account can create [[Git repositories in home directories|Git repositories in their home directory]]. This does not require any coordination with the administrator.

== Getting write access to repositories ==

Write access to the repositories can only be given to users who send the following information to the [http://rtime.felk.cvut.cz/~sojka/ administrator]:

# OpenSSH public key
# Login name (for ČVUT people) or email address (for others).

=== SSH key creation ===

The SSH key can be created with one of the following ways:

# Under Linux/Unix (or in Git Bash under Windows) run: <pre>ssh-keygen</pre>
# In Git Gui (under Linux or Windows) choose [[Media:Git-gui-key.jpg|Help -> Show SSH key -> Generate key]].
# Under Windows use PuTTYgen. Use this if you have chosen to [[Media:git-plink.jpg|use Pling]] during Git installation.

It is stored by default at <tt>~/.ssh/id_rsa.pub</tt>.

=== Password-protected keys ===

During the key creation you will be asked for a passphrase. If you do not specify any passphrase, anybody with access to your <tt>~/.ssh</tt> directory could access your repositories. If you specify the passphrase, it will need to be entered whenever you want to push to or pull from the server. By using <tt>ssh-add</tt> command (or Pageant program under Windows) you can specify the passphrase only once and the decrypted key will be remembered in the memory.

== Creating repositories ==

There are to ways how a repository can be created:

# Send an email to the [http://rtime.felk.cvut.cz/~sojka/ administrator] with the name of the repository, a short description and a list of people (SSH public keys) who should have access to the repository. The administrator creates the repository for you and notifies you when it's done.
# Our group staff members can create their repositories without asking the administrator. See below.

=== Automatic creation of repositories (staff members only) ===

It is simply a matter of pushing the repository to a special URL containing the login, like this:

git push --set-upstream ssh://git@rtime.felk.cvut.cz/«login»/«whatever» HEAD

This will create a new repository called «whatever» (if it does not exist yet) and push the current HEAD to it. It also makes this repository the default for pushing and pulling (this is what --set-upstream does).

If you want to set a [https://rtime.felk.cvut.cz/gitweb/orte.git Gitweb description] for repositories created this way, use gitolite's desc commands. I.e. you can set the description by:
ssh git@rtime.felk.cvut.cz desc «login»/«whatever» "Description"

== Accessing the repository ==

After [[Git#Install_Git|installing Git]] on your local computer, you
can access the repository as follows.

=== Cloning the repository ===

Read/Write access (for users with registered SSH key):
git clone ssh://git@rtime.felk.cvut.cz/''repo-name''

Read-only access (for public repositories only):
git clone git://rtime.felk.cvut.cz/''repo-name''.git

=== First push to admin-created repositories ===

After an empty repository is created by the admin, you can push (i.e. upload) the data to it:

* [[#Cloning the repository|Clone]] the empty repository.
* Put your sources into your cloned repository
git add . # tells git to track all files in your project
git commit # commits the added files to the repository
* Push your sources to the server
git push

=== Pushing to non-master branches ===

If you are not allowed to push to the master branch but to a different one, you have to push like this:
git push origin master:your-branch
which pushes your local master branch to the remote branch ''your-branch''.

To make this behavior default run
git config remote.origin.push master:your-branch

And from now on, it is sufficient to run only
git push

== Managing repositories ==

=== Finding available repositories ===

You can find the list of repositories you have access to by running:

ssh git@rtime.felk.cvut.cz info [filter]

where filter is optional string used to filter the list.

=== Permissions to automatic repositories ===

The owners of automatically created repositories can manage the access permissions by themselves.

The current permissions can be listed by:

ssh git@rtime.felk.cvut.cz perms -l «repo»

You can add permissions for either reading of writing the repo with:
ssh git@rtime.felk.cvut.cz perms «repo» + READERS «login»
ssh git@rtime.felk.cvut.cz perms «repo» + WRITERS «login»

The permissions can be removed by replacing '''+''' with '''-'''.

To make your repository visible on gitweb, run:
ssh git@rtime.felk.cvut.cz perms «repo» + READERS @all

== Links to git related documents ==

* [http://support.dce.felk.cvut.cz/mediawiki/index.php/gitolite Gitolite documentation on DCE IT pages]

[[Category:Git]]

Git repository on this server

2013-11-01T16:14:52Z

Sojka:

Repositories on rtime server are managed by [http://github.com/sitaramc/gitolite Gitolite tool], which allows to conveniently manage repository permissions. World readable repositories can be [http://rtime.felk.cvut.cz/gitweb browsed online].

In addition to gitolite repositories, users with shell account can create [[Git repositories in home directories|Git repositories in their home directory]]. This does not require any coordination with the administrator.

== Getting write access to repositories ==

Write access to the repositories can only be given to users who sent their Open SSH public key to the [http://rtime.felk.cvut.cz/~sojka/ administrator] together with their university assigned login name (if any).

=== SSH key creation ===

The SSH key can be created with one of the following ways:

# Under Linux/Unix (or in Git Bash under Windows) run: <pre>ssh-keygen</pre>
# In Git Gui (under Linux or Windows) choose [[Media:Git-gui-key.jpg|Help -> Show SSH key -> Generate key]].
# Under Windows use PuTTYgen. Use this if you have chosen to [[Media:git-plink.jpg|use Pling]] during Git installation.

It is stored by default at <tt>~/.ssh/id_rsa.pub</tt>.

=== Password-protected keys ===

During the key creation you will be asked for a passphrase. If you do not specify any passphrase, anybody with access to your <tt>~/.ssh</tt> directory could access your repositories. If you specify the passphrase, it will need to be entered whenever you want to push to or pull from the server. By using <tt>ssh-add</tt> command (or Pageant program under Windows) you can specify the passphrase only once and the decrypted key will be remembered in the memory.

== Creating repositories ==

There are to ways how a repository can be created:

# Send an email to the [http://rtime.felk.cvut.cz/~sojka/ administrator] with the name of the repository, a short description and a list of people (SSH public keys) who should have access to the repository. The administrator creates the repository for you and notifies you when it's done.
# Our group staff members can create their repositories without asking the administrator. See below.

=== Automatic creation of repositories (staff members only) ===

It is simply a matter of pushing the repository to a special URL containing the login, like this:

git push --set-upstream ssh://git@rtime.felk.cvut.cz/«login»/«whatever» HEAD

This will create a new repository called «whatever» (if it does not exist yet) and push the current HEAD to it. It also makes this repository the default for pushing and pulling (this is what --set-upstream does).

If you want to set a [https://rtime.felk.cvut.cz/gitweb/orte.git Gitweb description] for repositories created this way, use gitolite's desc commands. I.e. you can set the description by:
ssh git@rtime.felk.cvut.cz desc «login»/«whatever» "Description"

== Accessing the repository ==

After [[Git#Install_Git|installing Git]] on your local computer, you
can access the repository as follows.

=== Cloning the repository ===

Read/Write access (for users with registered SSH key):
git clone ssh://git@rtime.felk.cvut.cz/''repo-name''

Read-only access (for public repositories only):
git clone git://rtime.felk.cvut.cz/''repo-name''.git

=== First push to admin-created repositories ===

After an empty repository is created by the admin, you can push (i.e. upload) the data to it:

* [[#Cloning the repository|Clone]] the empty repository.
* Put your sources into your cloned repository
git add . # tells git to track all files in your project
git commit # commits the added files to the repository
* Push your sources to the server
git push

=== Pushing to non-master branches ===

If you are not allowed to push to the master branch but to a different one, you have to push like this:
git push origin master:your-branch
which pushes your local master branch to the remote branch ''your-branch''.

To make this behavior default run
git config remote.origin.push master:your-branch

And from now on, it is sufficient to run only
git push

== Managing repositories ==

=== Finding available repositories ===

You can find the list of repositories you have access to by running:

ssh git@rtime.felk.cvut.cz info [filter]

where filter is optional string used to filter the list.

=== Permissions to automatic repositories ===

The owners of automatically created repositories can manage the access permissions by themselves.

The current permissions can be listed by:

ssh git@rtime.felk.cvut.cz perms -l «repo»

You can add permissions for either reading of writing the repo with:
ssh git@rtime.felk.cvut.cz perms «repo» + READERS «login»
ssh git@rtime.felk.cvut.cz perms «repo» + WRITERS «login»

The permissions can be removed by replacing '''+''' with '''-'''.

To make your repository visible on gitweb, run:
ssh git@rtime.felk.cvut.cz perms «repo» + READERS @all

== Links to git related documents ==

* [http://support.dce.felk.cvut.cz/mediawiki/index.php/gitolite Gitolite documentation on DCE IT pages]

[[Category:Git]]

Git repository on this server

2013-09-12T13:47:24Z

Sojka: /* Getting write access to repositories */

Repositories on rtime server are managed by [http://github.com/sitaramc/gitolite Gitolite tool], which allows to conveniently manage repository permissions. World readable repositories can be [http://rtime.felk.cvut.cz/gitweb browsed online]. Alternatively, users with shell account can create [[Git repositories in home directories|Git repositories in their home directory]].

== Getting write access to repositories ==

Write access to the repositories can only be given to users who sent their Open SSH public key to the [http://rtime.felk.cvut.cz/~sojka/ administrator] together with their university assigned login name (if any).

=== SSH key creation ===

The SSH key can be created with one of the following ways:

# Under Linux/Unix (or in Git Bash under Windows) run: <pre>ssh-keygen</pre>
# In Git Gui (under Linux or Windows) choose [[Media:Git-gui-key.jpg|Help -> Show SSH key -> Generate key]].
# Under Windows use PuTTYgen. Use this if you have chosen to [[Media:git-plink.jpg|use Pling]] during Git installation.

It is stored by default at <tt>~/.ssh/id_rsa.pub</tt>.

=== Password-protected keys ===

During the key creation you will be asked for a passphrase. If you do not specify any passphrase, anybody with access to your <tt>~/.ssh</tt> directory could access your repositories. If you specify the passphrase, it will need to be entered whenever you want to push to or pull from the server. By using <tt>ssh-add</tt> command (or Pageant program under Windows) you can specify the passphrase only once and the decrypted key will be remembered in the memory.

== Creating repositories ==

There are to ways how a repository can be created:

# Send an email to the [http://rtime.felk.cvut.cz/~sojka/ administrator] with the name of the repository, a short description and a list of people (SSH public keys) who should have access to the repository. The administrator creates the repository for you and notifies you when it's done.
# Our group staff members can create their repositories without asking the administrator. See below.

=== Automatic creation of repositories (staff members only) ===

It is simply a matter of pushing the repository to a special URL containing the login, like this:

git push --set-upstream ssh://git@rtime.felk.cvut.cz/«login»/«whatever» HEAD

This will create a new repository called «whatever» (if it does not exist yet) and push the current HEAD to it. It also makes this repository the default for pushing and pulling (this is what --set-upstream does).

If you want to set a [https://rtime.felk.cvut.cz/gitweb/orte.git Gitweb description] for repositories created this way, use gitolite's desc commands. I.e. you can set the description by:
ssh git@rtime.felk.cvut.cz desc «login»/«whatever» "Description"

== Accessing the repository ==

After [[Git#Install_Git|installing Git]] on your local computer, you
can access the repository as follows.

=== Cloning the repository ===

Read/Write access (for users with registered SSH key):
git clone ssh://git@rtime.felk.cvut.cz/''repo-name''

Read-only access (for public repositories only):
git clone git://rtime.felk.cvut.cz/''repo-name''.git

=== First push to admin-created repositories ===

After an empty repository is created by the admin, you can push (i.e. upload) the data to it:

* [[#Cloning the repository|Clone]] the empty repository.
* Put your sources into your cloned repository
git add . # tells git to track all files in your project
git commit # commits the added files to the repository
* Push your sources to the server
git push

=== Pushing to non-master branches ===

If you are not allowed to push to the master branch but to a different one, you have to push like this:
git push origin master:your-branch
which pushes your local master branch to the remote branch ''your-branch''.

To make this behavior default run
git config remote.origin.push master:your-branch

And from now on, it is sufficient to run only
git push

== Managing repositories ==

=== Finding available repositories ===

You can find the list of repositories you have access to by running:

ssh git@rtime.felk.cvut.cz info [filter]

where filter is optional string used to filter the list.

=== Permissions to automatic repositories ===

The owners of automatically created repositories can manage the access permissions by themselves.

The current permissions can be listed by:

ssh git@rtime.felk.cvut.cz perms -l «repo»

You can add permissions for either reading of writing the repo with:
ssh git@rtime.felk.cvut.cz perms «repo» + READERS «login»
ssh git@rtime.felk.cvut.cz perms «repo» + WRITERS «login»

The permissions can be removed by replacing '''+''' with '''-'''.

To make your repository visible on gitweb, run:
ssh git@rtime.felk.cvut.cz perms «repo» + READERS @all

== Links to git related documents ==

* [http://support.dce.felk.cvut.cz/mediawiki/index.php/gitolite Gitolite documentation on DCE IT pages]

[[Category:Git]]

Git repository on this server

2013-09-12T13:43:37Z

Sojka: /* Getting write access to repositories */

Repositories on rtime server are managed by [http://github.com/sitaramc/gitolite Gitolite tool], which allows to conveniently manage repository permissions. World readable repositories can be [http://rtime.felk.cvut.cz/gitweb browsed online]. Alternatively, users with shell account can create [[Git repositories in home directories|Git repositories in their home directory]].

== Getting write access to repositories ==

Write access to the repositories can only be given to users who sent their Open SSH public key to the [http://rtime.felk.cvut.cz/~sojka/ administrator] together with their university assigned login name (if any). The SSH key can be created with one of the following ways:

# Under Linux/Unix (or in Git Bash under Windows) run: <pre>ssh-keygen</pre>
# In Git Gui (under Linux or Windows) choose [[Media:Git-gui-key.jpg|Help -> Show SSH key -> Generate key]].
# Under Windows use PuTTYgen. Use this if you have chosen to [[Media:git-plink.jpg|use Pling]] during Git installation.

It is stored by default at <tt>~/.ssh/id_rsa.pub</tt>.

During the key creation you will be asked for a passphrase. If you do not specify any passphrase, anybody with access to your <tt>~/.ssh</tt> directory could access your repositories. If you specify the key, the passphrase will need to be entered whenever to use the key. By using <tt>ssh-add</tt> command you can specify the passphrase only once and the decrypted key will be remembered in the memory.

== Creating repositories ==

There are to ways how a repository can be created:

# Send an email to the [http://rtime.felk.cvut.cz/~sojka/ administrator] with the name of the repository, a short description and a list of people (SSH public keys) who should have access to the repository. The administrator creates the repository for you and notifies you when it's done.
# Our group staff members can create their repositories without asking the administrator. See below.

=== Automatic creation of repositories (staff members only) ===

It is simply a matter of pushing the repository to a special URL containing the login, like this:

git push --set-upstream ssh://git@rtime.felk.cvut.cz/«login»/«whatever» HEAD

This will create a new repository called «whatever» (if it does not exist yet) and push the current HEAD to it. It also makes this repository the default for pushing and pulling (this is what --set-upstream does).

If you want to set a [https://rtime.felk.cvut.cz/gitweb/orte.git Gitweb description] for repositories created this way, use gitolite's desc commands. I.e. you can set the description by:
ssh git@rtime.felk.cvut.cz desc «login»/«whatever» "Description"

== Accessing the repository ==

After [[Git#Install_Git|installing Git]] on your local computer, you
can access the repository as follows.

=== Cloning the repository ===

Read/Write access (for users with registered SSH key):
git clone ssh://git@rtime.felk.cvut.cz/''repo-name''

Read-only access (for public repositories only):
git clone git://rtime.felk.cvut.cz/''repo-name''.git

=== First push to admin-created repositories ===

After an empty repository is created by the admin, you can push (i.e. upload) the data to it:

* [[#Cloning the repository|Clone]] the empty repository.
* Put your sources into your cloned repository
git add . # tells git to track all files in your project
git commit # commits the added files to the repository
* Push your sources to the server
git push

=== Pushing to non-master branches ===

If you are not allowed to push to the master branch but to a different one, you have to push like this:
git push origin master:your-branch
which pushes your local master branch to the remote branch ''your-branch''.

To make this behavior default run
git config remote.origin.push master:your-branch

And from now on, it is sufficient to run only
git push

== Managing repositories ==

=== Finding available repositories ===

You can find the list of repositories you have access to by running:

ssh git@rtime.felk.cvut.cz info [filter]

where filter is optional string used to filter the list.

=== Permissions to automatic repositories ===

The owners of automatically created repositories can manage the access permissions by themselves.

The current permissions can be listed by:

ssh git@rtime.felk.cvut.cz perms -l «repo»

You can add permissions for either reading of writing the repo with:
ssh git@rtime.felk.cvut.cz perms «repo» + READERS «login»
ssh git@rtime.felk.cvut.cz perms «repo» + WRITERS «login»

The permissions can be removed by replacing '''+''' with '''-'''.

To make your repository visible on gitweb, run:
ssh git@rtime.felk.cvut.cz perms «repo» + READERS @all

== Links to git related documents ==

* [http://support.dce.felk.cvut.cz/mediawiki/index.php/gitolite Gitolite documentation on DCE IT pages]

[[Category:Git]]

File:Git-gui-key.jpg

2013-09-12T13:41:01Z

Sojka:

File:Putty-key-import.png

2013-09-12T13:40:51Z

Sojka:

File:Git-plink.jpg

2013-09-12T13:40:36Z

Sojka:

File:Git-path.jpg

2013-09-12T13:40:26Z

Sojka:

Git repository on this server

2013-09-12T13:39:49Z

Sojka: /* Getting write access to repositories */

Repositories on rtime server are managed by [http://github.com/sitaramc/gitolite Gitolite tool], which allows to conveniently manage repository permissions. World readable repositories can be [http://rtime.felk.cvut.cz/gitweb browsed online]. Alternatively, users with shell account can create [[Git repositories in home directories|Git repositories in their home directory]].

== Getting write access to repositories ==

Write access to the repositories can only be given to users who sent their Open SSH public key to the [http://rtime.felk.cvut.cz/~sojka/ administrator] together with their university assigned login name (if any). The SSH key can be created with one of the following ways:

# Under Linux/Unix (or in Git Bash under Windows) run: <pre>ssh-keygen</pre>
# In Git Gui (under Linux or Windows) choose ''Help -> Show SSH key -> Generate key''.
# Under Windows use PuTTYgen. Use this if you have chosen to use Pling during Git installation.

It is stored by default at <tt>~/.ssh/id_rsa.pub</tt>.

During the key creation you will be asked for a passphrase. If you do not specify any passphrase, anybody with access to your <tt>~/.ssh</tt> directory could access your repositories. If you specify the key, the passphrase will need to be entered whenever to use the key. By using <tt>ssh-add</tt> command you can specify the passphrase only once and the decrypted key will be remembered in the memory.

== Creating repositories ==

There are to ways how a repository can be created:

# Send an email to the [http://rtime.felk.cvut.cz/~sojka/ administrator] with the name of the repository, a short description and a list of people (SSH public keys) who should have access to the repository. The administrator creates the repository for you and notifies you when it's done.
# Our group staff members can create their repositories without asking the administrator. See below.

=== Automatic creation of repositories (staff members only) ===

It is simply a matter of pushing the repository to a special URL containing the login, like this:

git push --set-upstream ssh://git@rtime.felk.cvut.cz/«login»/«whatever» HEAD

This will create a new repository called «whatever» (if it does not exist yet) and push the current HEAD to it. It also makes this repository the default for pushing and pulling (this is what --set-upstream does).

If you want to set a [https://rtime.felk.cvut.cz/gitweb/orte.git Gitweb description] for repositories created this way, use gitolite's desc commands. I.e. you can set the description by:
ssh git@rtime.felk.cvut.cz desc «login»/«whatever» "Description"

== Accessing the repository ==

After [[Git#Install_Git|installing Git]] on your local computer, you
can access the repository as follows.

=== Cloning the repository ===

Read/Write access (for users with registered SSH key):
git clone ssh://git@rtime.felk.cvut.cz/''repo-name''

Read-only access (for public repositories only):
git clone git://rtime.felk.cvut.cz/''repo-name''.git

=== First push to admin-created repositories ===

After an empty repository is created by the admin, you can push (i.e. upload) the data to it:

* [[#Cloning the repository|Clone]] the empty repository.
* Put your sources into your cloned repository
git add . # tells git to track all files in your project
git commit # commits the added files to the repository
* Push your sources to the server
git push

=== Pushing to non-master branches ===

If you are not allowed to push to the master branch but to a different one, you have to push like this:
git push origin master:your-branch
which pushes your local master branch to the remote branch ''your-branch''.

To make this behavior default run
git config remote.origin.push master:your-branch

And from now on, it is sufficient to run only
git push

== Managing repositories ==

=== Finding available repositories ===

You can find the list of repositories you have access to by running:

ssh git@rtime.felk.cvut.cz info [filter]

where filter is optional string used to filter the list.

=== Permissions to automatic repositories ===

The owners of automatically created repositories can manage the access permissions by themselves.

The current permissions can be listed by:

ssh git@rtime.felk.cvut.cz perms -l «repo»

You can add permissions for either reading of writing the repo with:
ssh git@rtime.felk.cvut.cz perms «repo» + READERS «login»
ssh git@rtime.felk.cvut.cz perms «repo» + WRITERS «login»

The permissions can be removed by replacing '''+''' with '''-'''.

To make your repository visible on gitweb, run:
ssh git@rtime.felk.cvut.cz perms «repo» + READERS @all

== Links to git related documents ==

* [http://support.dce.felk.cvut.cz/mediawiki/index.php/gitolite Gitolite documentation on DCE IT pages]

[[Category:Git]]

Git repository on this server

2013-09-12T13:37:30Z

Sojka: /* Getting write access to repositories */

Repositories on rtime server are managed by [http://github.com/sitaramc/gitolite Gitolite tool], which allows to conveniently manage repository permissions. World readable repositories can be [http://rtime.felk.cvut.cz/gitweb browsed online]. Alternatively, users with shell account can create [[Git repositories in home directories|Git repositories in their home directory]].

== Getting write access to repositories ==

Write access to the repositories can only be given to users who sent their Open SSH public key to the [http://rtime.felk.cvut.cz/~sojka/ administrator] together with their university assigned login name (if any). The SSH key can be created with one of the following ways:

# under Linux/Unix (or in [http://code.google.com/p/msysgit/ MSysGit] shell in Windows) by: <pre>ssh-keygen</pre>
# in Git Gui (under Linux or Windows) by choosing Help -> Show SSH key -> Generate key.
# under Windows with PuTTYgen. Use this if you have chosen to use Pling during Git installation.

It is stored by default at <tt>~/.ssh/id_rsa.pub</tt>.

During the key creation you will be asked for a passphrase. If you do not specify any passphrase, anybody with access to your <tt>~/.ssh</tt> directory could access your repositories. If you specify the key, the passphrase will need to be entered whenever to use the key. By using <tt>ssh-add</tt> command you can specify the passphrase only once and the decrypted key will be remembered in the memory.

== Creating repositories ==

There are to ways how a repository can be created:

# Send an email to the [http://rtime.felk.cvut.cz/~sojka/ administrator] with the name of the repository, a short description and a list of people (SSH public keys) who should have access to the repository. The administrator creates the repository for you and notifies you when it's done.
# Our group staff members can create their repositories without asking the administrator. See below.

=== Automatic creation of repositories (staff members only) ===

It is simply a matter of pushing the repository to a special URL containing the login, like this:

git push --set-upstream ssh://git@rtime.felk.cvut.cz/«login»/«whatever» HEAD

This will create a new repository called «whatever» (if it does not exist yet) and push the current HEAD to it. It also makes this repository the default for pushing and pulling (this is what --set-upstream does).

If you want to set a [https://rtime.felk.cvut.cz/gitweb/orte.git Gitweb description] for repositories created this way, use gitolite's desc commands. I.e. you can set the description by:
ssh git@rtime.felk.cvut.cz desc «login»/«whatever» "Description"

== Accessing the repository ==

After [[Git#Install_Git|installing Git]] on your local computer, you
can access the repository as follows.

=== Cloning the repository ===

Read/Write access (for users with registered SSH key):
git clone ssh://git@rtime.felk.cvut.cz/''repo-name''

Read-only access (for public repositories only):
git clone git://rtime.felk.cvut.cz/''repo-name''.git

=== First push to admin-created repositories ===

After an empty repository is created by the admin, you can push (i.e. upload) the data to it:

* [[#Cloning the repository|Clone]] the empty repository.
* Put your sources into your cloned repository
git add . # tells git to track all files in your project
git commit # commits the added files to the repository
* Push your sources to the server
git push

=== Pushing to non-master branches ===

If you are not allowed to push to the master branch but to a different one, you have to push like this:
git push origin master:your-branch
which pushes your local master branch to the remote branch ''your-branch''.

To make this behavior default run
git config remote.origin.push master:your-branch

And from now on, it is sufficient to run only
git push

== Managing repositories ==

=== Finding available repositories ===

You can find the list of repositories you have access to by running:

ssh git@rtime.felk.cvut.cz info [filter]

where filter is optional string used to filter the list.

=== Permissions to automatic repositories ===

The owners of automatically created repositories can manage the access permissions by themselves.

The current permissions can be listed by:

ssh git@rtime.felk.cvut.cz perms -l «repo»

You can add permissions for either reading of writing the repo with:
ssh git@rtime.felk.cvut.cz perms «repo» + READERS «login»
ssh git@rtime.felk.cvut.cz perms «repo» + WRITERS «login»

The permissions can be removed by replacing '''+''' with '''-'''.

To make your repository visible on gitweb, run:
ssh git@rtime.felk.cvut.cz perms «repo» + READERS @all

== Links to git related documents ==

* [http://support.dce.felk.cvut.cz/mediawiki/index.php/gitolite Gitolite documentation on DCE IT pages]

[[Category:Git]]

Git repository on this server

2013-09-12T13:37:16Z

Sojka: /* Getting write access to repositories */

Repositories on rtime server are managed by [http://github.com/sitaramc/gitolite Gitolite tool], which allows to conveniently manage repository permissions. World readable repositories can be [http://rtime.felk.cvut.cz/gitweb browsed online]. Alternatively, users with shell account can create [[Git repositories in home directories|Git repositories in their home directory]].

== Getting write access to repositories ==

Write access to the repositories can only be given to users who sent their Open SSH public key to the [http://rtime.felk.cvut.cz/~sojka/ administrator] together with their university assigned login name (if any). The SSH key can be created with one of the following ways:

# under Linux/Unix (or in [http://code.google.com/p/msysgit/ MSysGit] shell in Windows) by: <pre>ssh-keygen</pre>
# in Git Gui (under Linux or Windows) by choosing Help -> Show SSH key -> Generate key
# under Windows with PuTTYgen. Use this if you have chosen to use Pling during Git installation.

It is stored by default at <tt>~/.ssh/id_rsa.pub</tt>.

During the key creation you will be asked for a passphrase. If you do not specify any passphrase, anybody with access to your <tt>~/.ssh</tt> directory could access your repositories. If you specify the key, the passphrase will need to be entered whenever to use the key. By using <tt>ssh-add</tt> command you can specify the passphrase only once and the decrypted key will be remembered in the memory.

== Creating repositories ==

There are to ways how a repository can be created:

# Send an email to the [http://rtime.felk.cvut.cz/~sojka/ administrator] with the name of the repository, a short description and a list of people (SSH public keys) who should have access to the repository. The administrator creates the repository for you and notifies you when it's done.
# Our group staff members can create their repositories without asking the administrator. See below.

=== Automatic creation of repositories (staff members only) ===

It is simply a matter of pushing the repository to a special URL containing the login, like this:

git push --set-upstream ssh://git@rtime.felk.cvut.cz/«login»/«whatever» HEAD

This will create a new repository called «whatever» (if it does not exist yet) and push the current HEAD to it. It also makes this repository the default for pushing and pulling (this is what --set-upstream does).

If you want to set a [https://rtime.felk.cvut.cz/gitweb/orte.git Gitweb description] for repositories created this way, use gitolite's desc commands. I.e. you can set the description by:
ssh git@rtime.felk.cvut.cz desc «login»/«whatever» "Description"

== Accessing the repository ==

After [[Git#Install_Git|installing Git]] on your local computer, you
can access the repository as follows.

=== Cloning the repository ===

Read/Write access (for users with registered SSH key):
git clone ssh://git@rtime.felk.cvut.cz/''repo-name''

Read-only access (for public repositories only):
git clone git://rtime.felk.cvut.cz/''repo-name''.git

=== First push to admin-created repositories ===

After an empty repository is created by the admin, you can push (i.e. upload) the data to it:

* [[#Cloning the repository|Clone]] the empty repository.
* Put your sources into your cloned repository
git add . # tells git to track all files in your project
git commit # commits the added files to the repository
* Push your sources to the server
git push

=== Pushing to non-master branches ===

If you are not allowed to push to the master branch but to a different one, you have to push like this:
git push origin master:your-branch
which pushes your local master branch to the remote branch ''your-branch''.

To make this behavior default run
git config remote.origin.push master:your-branch

And from now on, it is sufficient to run only
git push

== Managing repositories ==

=== Finding available repositories ===

You can find the list of repositories you have access to by running:

ssh git@rtime.felk.cvut.cz info [filter]

where filter is optional string used to filter the list.

=== Permissions to automatic repositories ===

The owners of automatically created repositories can manage the access permissions by themselves.

The current permissions can be listed by:

ssh git@rtime.felk.cvut.cz perms -l «repo»

You can add permissions for either reading of writing the repo with:
ssh git@rtime.felk.cvut.cz perms «repo» + READERS «login»
ssh git@rtime.felk.cvut.cz perms «repo» + WRITERS «login»

The permissions can be removed by replacing '''+''' with '''-'''.

To make your repository visible on gitweb, run:
ssh git@rtime.felk.cvut.cz perms «repo» + READERS @all

== Links to git related documents ==

* [http://support.dce.felk.cvut.cz/mediawiki/index.php/gitolite Gitolite documentation on DCE IT pages]

[[Category:Git]]

TMS570LS3137

2013-07-10T08:43:49Z

Sojka: /* CCS5 in Ubuntu 12.04 64bits */

Main Page

2013-07-09T13:44:37Z

Sojka:

__NOTOC__

'''For Czech students:''' Tato wiki by měla sloužit ke sdílení informací při vývoji různého HW na [http://dce.felk.cvut.cz/ katedře řídící techniky] FEL ČVUT. Důvod vzniku této wiki je ten, že se často vyskytuje případ, kdy několik studentu pracuje na stejném a nebo podobném hardwaru a jeden člověk dělá práci, která by se mohla hodit i ostatním. Pokud se to ujme, mohla by tato Wiki sloužit jako místo, kde by se publikovaly výsledky práce jednotlivých lidí tak, aby tato práce mohla být užitečná i pro ostatní. Mohly by se zde vyskytovat různé návody, odkazy na aktuální verze softwaru apod.

Konkrétní obsah závisí jen na vás. Pokud pracujete s nějakým hardwarem, [http://rtime.felk.cvut.cz/~sojka/ kontaktujte mě] a já vám zde zřídím účet. Anonymní editace je zakázaná kvůli spamerům.

--[[Wikipedista:Sojka|Sojka]] 20:29, 5. 5. 2005 (CEST)
<table>
<tr valign="top">
<td style="background-color:#fff2f2; border:2px solid #b26b6b; width:30%; margin:0.5em; padding:0.5em">
{{Main Page/Hardware}}
</td>

<td style="background-color:#f9fff2; border:2px solid #8fb26b; margin:0.5em; padding:0.5em">
{{Main Page/Software}}
</td>

<td style="background-color:#f2ffff; border:2px solid #6bb2b2; padding:0.5em">
{{MainPage/Version Control}}
</td>
</tr>
</table>

<div style="background-color:#f9f2ff; border:2px solid #8f6bb2; margin:0.5em; padding:0.5em; clear:both;">
{{Main Page/HW Links}}
</div>
<div style="clear:both;">
== Wiki documentation ==

Please see [http://meta.wikipedia.org/wiki/MediaWiki_i18n documentation on customizing the interface]
and the [http://meta.wikipedia.org/wiki/MediaWiki_User's_Guide User's Guide] for usage and configuration help.
</div>

TMS570LS3137

2013-05-06T08:04:17Z

Sojka: /* CCS5 in Ubuntu 12.04 65bits */

TMS570LS3137

2013-04-12T12:00:16Z

Sojka: Contacts

Git repository on this server

2013-02-21T15:22:12Z

Sojka: /* Automatic creation of repositories (staff members only) */

Repositories on rtime server are managed by [http://github.com/sitaramc/gitolite Gitolite tool], which allows to conveniently manage repository permissions. World readable repositories can be [http://rtime.felk.cvut.cz/gitweb browsed online]. Alternatively, users with shell account can create [[Git repositories in home directories|Git repositories in their home directory]].

== Getting write access to repositories ==

Write access to the repositories can only be given to users who sent their Open SSH public key to the [http://rtime.felk.cvut.cz/~sojka/ administrator] together with their university assigned login name (if any). The SSH key can be created in Linux/Unix (or in [http://code.google.com/p/msysgit/ MSysGit] shell in Windows) by:

ssh-keygen

It is stored by default at <tt>~/.ssh/id_rsa.pub</tt>.

During the key creation you will be asked for a passphrase. If you do not specify any passphrase, anybody with access to your <tt>~/.ssh</tt> directory could access your repositories. If you specify the key, the passphrase will need to be entered whenever to use the key. By using <tt>ssh-add</tt> command you can specify the passphrase only once and the decrypted key will be remembered in the memory.

== Creating repositories ==

There are to ways how a repository can be created:

# Send an email to the [http://rtime.felk.cvut.cz/~sojka/ administrator] with the name of the repository, a short description and a list of people (SSH public keys) who should have access to the repository. The administrator creates the repository for you and notifies you when it's done.
# Our group staff members can create their repositories without asking the administrator. See below.

=== Automatic creation of repositories (staff members only) ===

It is simply a matter of pushing the repository to a special URL containing the login, like this:

git push --set-upstream ssh://git@rtime.felk.cvut.cz/«login»/«whatever» HEAD

This will create a new repository called «whatever» (if it does not exist yet) and push the current HEAD to it. It also makes this repository the default for pushing and pulling (this is what --set-upstream does).

If you want to set a [https://rtime.felk.cvut.cz/gitweb/orte.git Gitweb description] for repositories created this way, use gitolite's desc commands. I.e. you can set the description by:
ssh git@rtime.felk.cvut.cz desc «login»/«whatever» "Description"

== Accessing the repository ==

After [[Git#Install_Git|installing Git]] on your local computer, you
can access the repository as follows.

=== Cloning the repository ===

Read/Write access (for users with registered SSH key):
git clone ssh://git@rtime.felk.cvut.cz/''repo-name''

Read-only access (for public repositories only):
git clone git://rtime.felk.cvut.cz/''repo-name''.git

=== First push to admin-created repositories ===

After an empty repository is created by the admin, you can push (i.e. upload) the data to it:

* [[#Cloning the repository|Clone]] the empty repository.
* Put your sources into your cloned repository
git add . # tells git to track all files in your project
git commit # commits the added files to the repository
* Push your sources to the server
git push

=== Pushing to non-master branches ===

If you are not allowed to push to the master branch but to a different one, you have to push like this:
git push origin master:your-branch
which pushes your local master branch to the remote branch ''your-branch''.

To make this behavior default run
git config remote.origin.push master:your-branch

And from now on, it is sufficient to run only
git push

== Managing repositories ==

=== Finding available repositories ===

You can find the list of repositories you have access to by running:

ssh git@rtime.felk.cvut.cz info [filter]

where filter is optional string used to filter the list.

=== Permissions to automatic repositories ===

The owners of automatically created repositories can manage the access permissions by themselves.

The current permissions can be listed by:

ssh git@rtime.felk.cvut.cz perms -l «repo»

You can add permissions for either reading of writing the repo with:
ssh git@rtime.felk.cvut.cz perms «repo» + READERS «login»
ssh git@rtime.felk.cvut.cz perms «repo» + WRITERS «login»

The permissions can be removed by replacing '''+''' with '''-'''.

To make your repository visible on gitweb, run:
ssh git@rtime.felk.cvut.cz perms «repo» + READERS @all

== Links to git related documents ==

* [http://support.dce.felk.cvut.cz/mediawiki/index.php/gitolite Gitolite documentation on DCE IT pages]

[[Category:Git]]

Git repository on this server

2013-02-21T15:19:59Z

Sojka: /* Permissions to automatic repositories */

Repositories on rtime server are managed by [http://github.com/sitaramc/gitolite Gitolite tool], which allows to conveniently manage repository permissions. World readable repositories can be [http://rtime.felk.cvut.cz/gitweb browsed online]. Alternatively, users with shell account can create [[Git repositories in home directories|Git repositories in their home directory]].

== Getting write access to repositories ==

Write access to the repositories can only be given to users who sent their Open SSH public key to the [http://rtime.felk.cvut.cz/~sojka/ administrator] together with their university assigned login name (if any). The SSH key can be created in Linux/Unix (or in [http://code.google.com/p/msysgit/ MSysGit] shell in Windows) by:

ssh-keygen

It is stored by default at <tt>~/.ssh/id_rsa.pub</tt>.

During the key creation you will be asked for a passphrase. If you do not specify any passphrase, anybody with access to your <tt>~/.ssh</tt> directory could access your repositories. If you specify the key, the passphrase will need to be entered whenever to use the key. By using <tt>ssh-add</tt> command you can specify the passphrase only once and the decrypted key will be remembered in the memory.

== Creating repositories ==

There are to ways how a repository can be created:

# Send an email to the [http://rtime.felk.cvut.cz/~sojka/ administrator] with the name of the repository, a short description and a list of people (SSH public keys) who should have access to the repository. The administrator creates the repository for you and notifies you when it's done.
# Our group staff members can create their repositories without asking the administrator. See below.

=== Automatic creation of repositories (staff members only) ===

It is simply a matter of pushing the repository to a special URL containing the login, like this:

git push --set-upstream ssh://git@rtime.felk.cvut.cz/«login»/«whatever» HEAD

This will create a new repository called «whatever» (if it does not exist yet) and push the current HEAD to it. It also makes this repository the default for pushing and pulling (this is what --set-upstream does).

If you want to set a [https://rtime.felk.cvut.cz/gitweb/orte.git Gitweb description] for repositories created this way, use gitolite's getdesc/setdesc commands. I.e. you can set the description by:
echo "Description" | ssh git@rtime.felk.cvut.cz setdesc «login»/«whatever»

== Accessing the repository ==

After [[Git#Install_Git|installing Git]] on your local computer, you
can access the repository as follows.

=== Cloning the repository ===

Read/Write access (for users with registered SSH key):
git clone ssh://git@rtime.felk.cvut.cz/''repo-name''

Read-only access (for public repositories only):
git clone git://rtime.felk.cvut.cz/''repo-name''.git

=== First push to admin-created repositories ===

After an empty repository is created by the admin, you can push (i.e. upload) the data to it:

* [[#Cloning the repository|Clone]] the empty repository.
* Put your sources into your cloned repository
git add . # tells git to track all files in your project
git commit # commits the added files to the repository
* Push your sources to the server
git push

=== Pushing to non-master branches ===

If you are not allowed to push to the master branch but to a different one, you have to push like this:
git push origin master:your-branch
which pushes your local master branch to the remote branch ''your-branch''.

To make this behavior default run
git config remote.origin.push master:your-branch

And from now on, it is sufficient to run only
git push

== Managing repositories ==

=== Finding available repositories ===

You can find the list of repositories you have access to by running:

ssh git@rtime.felk.cvut.cz info [filter]

where filter is optional string used to filter the list.

=== Permissions to automatic repositories ===

The owners of automatically created repositories can manage the access permissions by themselves.

The current permissions can be listed by:

ssh git@rtime.felk.cvut.cz perms -l «repo»

You can add permissions for either reading of writing the repo with:
ssh git@rtime.felk.cvut.cz perms «repo» + READERS «login»
ssh git@rtime.felk.cvut.cz perms «repo» + WRITERS «login»

The permissions can be removed by replacing '''+''' with '''-'''.

To make your repository visible on gitweb, run:
ssh git@rtime.felk.cvut.cz perms «repo» + READERS @all

== Links to git related documents ==

* [http://support.dce.felk.cvut.cz/mediawiki/index.php/gitolite Gitolite documentation on DCE IT pages]

[[Category:Git]]

Git repository on this server

2013-02-21T15:19:10Z

Sojka: /* Finding available repositories */

Repositories on rtime server are managed by [http://github.com/sitaramc/gitolite Gitolite tool], which allows to conveniently manage repository permissions. World readable repositories can be [http://rtime.felk.cvut.cz/gitweb browsed online]. Alternatively, users with shell account can create [[Git repositories in home directories|Git repositories in their home directory]].

== Getting write access to repositories ==

Write access to the repositories can only be given to users who sent their Open SSH public key to the [http://rtime.felk.cvut.cz/~sojka/ administrator] together with their university assigned login name (if any). The SSH key can be created in Linux/Unix (or in [http://code.google.com/p/msysgit/ MSysGit] shell in Windows) by:

ssh-keygen

It is stored by default at <tt>~/.ssh/id_rsa.pub</tt>.

During the key creation you will be asked for a passphrase. If you do not specify any passphrase, anybody with access to your <tt>~/.ssh</tt> directory could access your repositories. If you specify the key, the passphrase will need to be entered whenever to use the key. By using <tt>ssh-add</tt> command you can specify the passphrase only once and the decrypted key will be remembered in the memory.

== Creating repositories ==

There are to ways how a repository can be created:

# Send an email to the [http://rtime.felk.cvut.cz/~sojka/ administrator] with the name of the repository, a short description and a list of people (SSH public keys) who should have access to the repository. The administrator creates the repository for you and notifies you when it's done.
# Our group staff members can create their repositories without asking the administrator. See below.

=== Automatic creation of repositories (staff members only) ===

It is simply a matter of pushing the repository to a special URL containing the login, like this:

git push --set-upstream ssh://git@rtime.felk.cvut.cz/«login»/«whatever» HEAD

This will create a new repository called «whatever» (if it does not exist yet) and push the current HEAD to it. It also makes this repository the default for pushing and pulling (this is what --set-upstream does).

If you want to set a [https://rtime.felk.cvut.cz/gitweb/orte.git Gitweb description] for repositories created this way, use gitolite's getdesc/setdesc commands. I.e. you can set the description by:
echo "Description" | ssh git@rtime.felk.cvut.cz setdesc «login»/«whatever»

== Accessing the repository ==

After [[Git#Install_Git|installing Git]] on your local computer, you
can access the repository as follows.

=== Cloning the repository ===

Read/Write access (for users with registered SSH key):
git clone ssh://git@rtime.felk.cvut.cz/''repo-name''

Read-only access (for public repositories only):
git clone git://rtime.felk.cvut.cz/''repo-name''.git

=== First push to admin-created repositories ===

After an empty repository is created by the admin, you can push (i.e. upload) the data to it:

* [[#Cloning the repository|Clone]] the empty repository.
* Put your sources into your cloned repository
git add . # tells git to track all files in your project
git commit # commits the added files to the repository
* Push your sources to the server
git push

=== Pushing to non-master branches ===

If you are not allowed to push to the master branch but to a different one, you have to push like this:
git push origin master:your-branch
which pushes your local master branch to the remote branch ''your-branch''.

To make this behavior default run
git config remote.origin.push master:your-branch

And from now on, it is sufficient to run only
git push

== Managing repositories ==

=== Finding available repositories ===

You can find the list of repositories you have access to by running:

ssh git@rtime.felk.cvut.cz info [filter]

where filter is optional string used to filter the list.

=== Permissions to automatic repositories ===

The owners of automatically created repositories can manage the access permissions by themselves.

The current permissions can be listed by:

ssh git@rtime.felk.cvut.cz perms -l «repo»

You can add permissions for either reading of writing the repo with:
ssh git@rtime.felk.cvut.cz perms «repo» + READERS «login»
ssh git@rtime.felk.cvut.cz perms «repo» + WRITERS «login»

The permissions can be removed by replacing '''+''' with '''-'''.

== Links to git related documents ==

* [http://support.dce.felk.cvut.cz/mediawiki/index.php/gitolite Gitolite documentation on DCE IT pages]

[[Category:Git]]

Git repository on this server

2013-02-21T15:17:41Z

Sojka: /* Managing central repositories */

Repositories on rtime server are managed by [http://github.com/sitaramc/gitolite Gitolite tool], which allows to conveniently manage repository permissions. World readable repositories can be [http://rtime.felk.cvut.cz/gitweb browsed online]. Alternatively, users with shell account can create [[Git repositories in home directories|Git repositories in their home directory]].

== Getting write access to repositories ==

Write access to the repositories can only be given to users who sent their Open SSH public key to the [http://rtime.felk.cvut.cz/~sojka/ administrator] together with their university assigned login name (if any). The SSH key can be created in Linux/Unix (or in [http://code.google.com/p/msysgit/ MSysGit] shell in Windows) by:

ssh-keygen

It is stored by default at <tt>~/.ssh/id_rsa.pub</tt>.

During the key creation you will be asked for a passphrase. If you do not specify any passphrase, anybody with access to your <tt>~/.ssh</tt> directory could access your repositories. If you specify the key, the passphrase will need to be entered whenever to use the key. By using <tt>ssh-add</tt> command you can specify the passphrase only once and the decrypted key will be remembered in the memory.

== Creating repositories ==

There are to ways how a repository can be created:

# Send an email to the [http://rtime.felk.cvut.cz/~sojka/ administrator] with the name of the repository, a short description and a list of people (SSH public keys) who should have access to the repository. The administrator creates the repository for you and notifies you when it's done.
# Our group staff members can create their repositories without asking the administrator. See below.

=== Automatic creation of repositories (staff members only) ===

It is simply a matter of pushing the repository to a special URL containing the login, like this:

git push --set-upstream ssh://git@rtime.felk.cvut.cz/«login»/«whatever» HEAD

This will create a new repository called «whatever» (if it does not exist yet) and push the current HEAD to it. It also makes this repository the default for pushing and pulling (this is what --set-upstream does).

If you want to set a [https://rtime.felk.cvut.cz/gitweb/orte.git Gitweb description] for repositories created this way, use gitolite's getdesc/setdesc commands. I.e. you can set the description by:
echo "Description" | ssh git@rtime.felk.cvut.cz setdesc «login»/«whatever»

== Accessing the repository ==

After [[Git#Install_Git|installing Git]] on your local computer, you
can access the repository as follows.

=== Cloning the repository ===

Read/Write access (for users with registered SSH key):
git clone ssh://git@rtime.felk.cvut.cz/''repo-name''

Read-only access (for public repositories only):
git clone git://rtime.felk.cvut.cz/''repo-name''.git

=== First push to admin-created repositories ===

After an empty repository is created by the admin, you can push (i.e. upload) the data to it:

* [[#Cloning the repository|Clone]] the empty repository.
* Put your sources into your cloned repository
git add . # tells git to track all files in your project
git commit # commits the added files to the repository
* Push your sources to the server
git push

=== Pushing to non-master branches ===

If you are not allowed to push to the master branch but to a different one, you have to push like this:
git push origin master:your-branch
which pushes your local master branch to the remote branch ''your-branch''.

To make this behavior default run
git config remote.origin.push master:your-branch

And from now on, it is sufficient to run only
git push

== Managing repositories ==

=== Finding available repositories ===

You can find the list of repositories you have access to by running:

ssh git@rtime.felk.cvut.cz info [filter]

where filter is optional string used to filter the list.

It there are wildcard (automatic) repositories, as in the example below, you will only see the wildcard pattern and not the created repositories.

C R W fpga/[a-zA-Z0-9].*

To expand the wildcards, use the command <tt>expand</tt> instead of info. This command is a way slower than info command!

ssh git@rtime.felk.cvut.cz expand
ssh git@rtime.felk.cvut.cz expand fpga

=== Permissions to automatic repositories ===

The owners of automatically created repositories can manage the access permissions by themselves.

The current permissions can be listed by:

ssh git@rtime.felk.cvut.cz perms -l «repo»

You can add permissions for either reading of writing the repo with:
ssh git@rtime.felk.cvut.cz perms «repo» + READERS «login»
ssh git@rtime.felk.cvut.cz perms «repo» + WRITERS «login»

The permissions can be removed by replacing '''+''' with '''-'''.

== Links to git related documents ==

* [http://support.dce.felk.cvut.cz/mediawiki/index.php/gitolite Gitolite documentation on DCE IT pages]

[[Category:Git]]

Git repository on this server

2013-02-21T15:17:17Z

Sojka: /* First push */

Repositories on rtime server are managed by [http://github.com/sitaramc/gitolite Gitolite tool], which allows to conveniently manage repository permissions. World readable repositories can be [http://rtime.felk.cvut.cz/gitweb browsed online]. Alternatively, users with shell account can create [[Git repositories in home directories|Git repositories in their home directory]].

== Getting write access to repositories ==

Write access to the repositories can only be given to users who sent their Open SSH public key to the [http://rtime.felk.cvut.cz/~sojka/ administrator] together with their university assigned login name (if any). The SSH key can be created in Linux/Unix (or in [http://code.google.com/p/msysgit/ MSysGit] shell in Windows) by:

ssh-keygen

It is stored by default at <tt>~/.ssh/id_rsa.pub</tt>.

During the key creation you will be asked for a passphrase. If you do not specify any passphrase, anybody with access to your <tt>~/.ssh</tt> directory could access your repositories. If you specify the key, the passphrase will need to be entered whenever to use the key. By using <tt>ssh-add</tt> command you can specify the passphrase only once and the decrypted key will be remembered in the memory.

== Creating repositories ==

There are to ways how a repository can be created:

# Send an email to the [http://rtime.felk.cvut.cz/~sojka/ administrator] with the name of the repository, a short description and a list of people (SSH public keys) who should have access to the repository. The administrator creates the repository for you and notifies you when it's done.
# Our group staff members can create their repositories without asking the administrator. See below.

=== Automatic creation of repositories (staff members only) ===

It is simply a matter of pushing the repository to a special URL containing the login, like this:

git push --set-upstream ssh://git@rtime.felk.cvut.cz/«login»/«whatever» HEAD

This will create a new repository called «whatever» (if it does not exist yet) and push the current HEAD to it. It also makes this repository the default for pushing and pulling (this is what --set-upstream does).

If you want to set a [https://rtime.felk.cvut.cz/gitweb/orte.git Gitweb description] for repositories created this way, use gitolite's getdesc/setdesc commands. I.e. you can set the description by:
echo "Description" | ssh git@rtime.felk.cvut.cz setdesc «login»/«whatever»

== Accessing the repository ==

After [[Git#Install_Git|installing Git]] on your local computer, you
can access the repository as follows.

=== Cloning the repository ===

Read/Write access (for users with registered SSH key):
git clone ssh://git@rtime.felk.cvut.cz/''repo-name''

Read-only access (for public repositories only):
git clone git://rtime.felk.cvut.cz/''repo-name''.git

=== First push to admin-created repositories ===

After an empty repository is created by the admin, you can push (i.e. upload) the data to it:

* [[#Cloning the repository|Clone]] the empty repository.
* Put your sources into your cloned repository
git add . # tells git to track all files in your project
git commit # commits the added files to the repository
* Push your sources to the server
git push

=== Pushing to non-master branches ===

If you are not allowed to push to the master branch but to a different one, you have to push like this:
git push origin master:your-branch
which pushes your local master branch to the remote branch ''your-branch''.

To make this behavior default run
git config remote.origin.push master:your-branch

And from now on, it is sufficient to run only
git push

== Managing central repositories ==

=== Finding available repositories ===

You can find the list of repositories you have access to by running:

ssh git@rtime.felk.cvut.cz info [filter]

where filter is optional string used to filter the list.

It there are wildcard (automatic) repositories, as in the example below, you will only see the wildcard pattern and not the created repositories.

C R W fpga/[a-zA-Z0-9].*

To expand the wildcards, use the command <tt>expand</tt> instead of info. This command is a way slower than info command!

ssh git@rtime.felk.cvut.cz expand
ssh git@rtime.felk.cvut.cz expand fpga

=== Permissions to automatic repositories ===

The owners of automatically created repositories can manage the access permissions by themselves.

The current permissions can be listed by:

ssh git@rtime.felk.cvut.cz perms -l «repo»

You can add permissions for either reading of writing the repo with:
ssh git@rtime.felk.cvut.cz perms «repo» + READERS «login»
ssh git@rtime.felk.cvut.cz perms «repo» + WRITERS «login»

The permissions can be removed by replacing '''+''' with '''-'''.

== Links to git related documents ==

* [http://support.dce.felk.cvut.cz/mediawiki/index.php/gitolite Gitolite documentation on DCE IT pages]

[[Category:Git]]