Ttc Program Usage Guide - Revision history

Wmat: Changing File link to Media Link.

2013-01-09T04:33:44Z

Changing File link to Media Link.

2013-01-08T21:18:29Z

‎Configuration attributes summary

2013-01-08T21:14:22Z

‎Overview

2012-12-12T22:12:16Z

‎Configuration attributes summary

2012-12-12T22:11:53Z

‎Configuration attributes summary

2012-12-12T22:11:31Z

‎Configuration attributes summary

2012-12-12T21:58:33Z

2012-12-12T21:55:29Z

2012-12-12T21:54:32Z

‎Configuration Example

2012-12-12T21:52:31Z

‎interactive vs. automated use

@@ Line 81: / Line 81: @@
 !style="background:#80cccc;"|'''Download Link'''
 |-
-|1.2.3||Public release as of Dec 12, 2012||[[file:Ttc-1.2.3.tgz]]
+|1.2.3||Public release as of Dec 12, 2012||[[Media:Ttc-1.2.3.tgz | Ttc-1.2.3.tgz]]
 |}

@@ Line 490: / Line 490: @@
 |-
 |target        ||Short (one-word) name of the target
-|If the target name starts with a '.', it is not displayed in the list from the command 'ttc list'.  This is similar to Linus directory
+|If the target name starts with a '.', it is not displayed in the list from the command 'ttc list'.  This is similar to Linux directory listings, and is useful for having hidden targets, which other targets use as a base for inheritance.
 listings, and is useful for having hidden targets, which other targets use as a base for inheritance.
 |-
 |description   ||A description of the target board.  Usually multi-line||This field is used for humans to let them know the attributes of the board.

@@ Line 11: / Line 11: @@
 The <code>ttc</code> program can be run interactively, or as part of an automated
-session.  The purpose of target is to make it so that the same commands
+session.  The purpose of <code>ttc</code> is to make it so that the same commands
 can be used to build software and manipulate different target machines, independent of
 differences in the configuration and setup of the machines.  Certain details of

@@ Line 525: / Line 525: @@
 |reboot_cmd    ||Command(s) to reboot the target, from the host
 |This is intended to be a power-cycle of the board, producing a cold boot of the hardware.  Usually this is something like "powerswitch-cycle -n <board-name> -o 3 -d <some-delay>", but it depends on completely on how you have the board wired up for power and what the host needs to do to reboot it.
 |reset_cmd     ||Command(s) to reset the target, from the host
 |This is intended to be a soft reset of the hardware.  If you have automated control of a software reset pin or button on the board, then configure this command to activate it.  Otherwise, you could use something like: reset_cmd=ttc run reboot

@@ Line 525: / Line 525: @@
 |reboot_cmd    ||Command(s) to reboot the target, from the host
 |This is intended to be a power-cycle of the board, producing a cold boot of the hardware.  Usually this is something like "powerswitch-cycle -n <board-name> -o 3 -d <some-delay>", but it depends on completely on how you have the board wired up for power and what the host needs to do to reboot it.
-|reset_cmd     ||Command(s) to reset the target, from the host||This is intended to be a soft reset of the hardware.  If you have automated control of a software reset pin or button on the board, then configure this command to activate it.  Otherwise, you could use something like: reset_cmd=ttc run reboot
+|reset_cmd     ||Command(s) to reset the target, from the host
 |-
 |console_cmd   ||Command(s) to start an interactive console for the target (usually minicom)||.

@@ Line 489: / Line 489: @@
 !style="background:#80cccc;"|'''Notes'''
 |-
-|target        ||Short (one-word) name of the target||.
+|target        ||Short (one-word) name of the target
 |-
-|description   ||A description of the target board.  Usually multi-line||.
+|description   ||A description of the target board.  Usually multi-line||This field is used for humans to let them know the attributes of the board.
 |-
 |TOOL_PATH     ||Path where toolchain tools are located.  This appended to the PATH env. variable||.
@@ Line 521: / Line 523: @@
 |ipaddr        ||Target IP address||.
 |-
-|reset_cmd     ||Command(s) to reset the target, from the host||.
+|reboot_cmd    ||Command(s) to reboot the target, from the host
 |-
 |console_cmd   ||Command(s) to start an interactive console for the target (usually minicom)||.

← Older revision		Revision as of 21:58, 12 December 2012
Line 685:		Line 685:
	; target_bin: Directory on target where binary files are located		; target_bin: Directory on target where binary files are located
	; fsinstall_cmd: Command(s) to install a root filesystem to the target (not implemented yet)		; fsinstall_cmd: Command(s) to install a root filesystem to the target (not implemented yet)
		+	; reserve_cmd: Command(s) to reserve a board (like switching the root filesystem, in case of different users having different root filesystems)
		+	;

@@ Line 684: / Line 684: @@
 ; login_cmd: Command(s) to start an interactive login session with the target (usually telnet)
 ; target_bin: Directory on target where binary files are located
-; fsinstall_cmd: Command(s) to install a root filesystem to the target
+; fsinstall_cmd: Command(s) to install a root filesystem to the target (not implemented yet)

@@ Line 594: / Line 594: @@
 kinstall_cmd==cp -v $KBUILD_OUTPUT/arch/arm/boot/uImage /target/osk2/boot
 reset_cmd==echo "remote reset not supported" ; false
 get_kernel_cmd==tla get -A alp@oak--trial-5 alp-linux--dev $KERNEL_SRC
 get_config_cmd=="""export CVSRSH==/usr/bin/ssh ; cd $TMPDIR ; cvs -d :ext:oak.sm.sony.co.jp:/var/cvsroot co local-dev/team/configs/config-osk-baseline ; cd -
@@ Line 624: / Line 623: @@
 kimage==bzImage
 kinstall_cmd==cp -v $KBUILD_OUTPUT/arch/i386/boot/bzImage /target/nut/boot/vmlinuz
 get_kernel_cmd=="""tar -xjf /home/rbatest/base/linux-2.6.10.tar.bz2
                  mv linux-2.6.10 $KERNEL_SRC"""

@@ Line 430: / Line 430: @@
 ==== interactive vs. automated use ====
 Some tricks for automated use:
-*use the -o option with "ttc setenv" to output the environment variables to a file, then source that file in the current environment
 This solves the problem of setting environment variables in the current shell, rather than in a sub-shell started via "ttc".
 Here's a line which does this:
-<code>
-ttc foo setenv -o >tmp ; source tmp ; rm tmp ; make $kimage
+ ttc foo setenv -o >tmp ; source tmp ; rm tmp ; make $kimage
-</code>
 == Appendix A: Configuration file specification ==