DOCSLIB.ORG

Title: Setting up the TS7300 Boards Author: Craig Duffy 5/10/08, 22/11/10 Module: System on Chip Awards: CSE3, BENG, Robotics 3, MENG

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Title: Setting up the TS7300 Boards Author: Craig Duffy 5/10/08, 22/11/10 Module: System on Chip Awards: CSE3, BENG, Robotics 3, MENG Title: Setting up the TS7300 boards Author: Craig Duffy 5/10/08, 22/11/10 Module: System on Chip Awards: CSE3, BENG, Robotics 3, MENG. Prerequisites: TSboard, SD cards The purpose of this worksheet it to show how the TS7300 board boots up and how to install Linux on it. We will also look at how to configure the Linux installation on the boards. The TS7300 startup The TS7300 has a rather different startup routine from many embedded boards. Like on most boards the CPU, the ARM9, looks for a device to boot from. Rather than using on board FLASH chips the system boots to a small EEPROM on the board. This contains a very small boot strap program, < 2K bytes, this boot strap has a few functions, some to do a basic board initialisation, some to handle the screen and serial ports and a routine to load the boot sector of the first SD card. If there are problems with the SD card the watchdog timer on the board is set up on system initialisation and will force a reboot. If the EEPROM is corrupted then the board is pretty much dead! The EEPROM code should give the message, >> TS-SDBOOT - built Jul 6 2006 >> Copyright (c) 2006, Technologic Systems . The dots (.) represent disk read activity, if there is no disk the system will keep restarting itself every 8 seconds. If there is a SD card in the first slot, the one nearest the ARM CPU, and it has had a boot sector correctly installed, then the system may be able to boot into Linux. The boot sector is a very small program, written in ARM Thumb 16 bit instructions, that will load into memory the first 2 partitions of the SD card. These 2 partitions contain the Linux kernel in partition 1 and an initial RAM disk (initrd) in partition 2. The kernel is loaded in address 0x218000 in RAM and the initrd is loaded at address 0x1000000. The final thing the boot sector program does is to jump to the start of the kernel to execute it. You should then see the initial kernel message, Booting Linux... It is possible that it might go into fastboot mode, in which case you will see the message, Finished booting in 1.66 seconds Type 'exit' for full boot - remove JP6 to make this the default $ exit 1 If you type in exit at this point then the system should boot up into Linux, and see something like this, >> Booting Linux... INIT: version 2.86 booting Creating extra device nodes...done. Started device management daemon v1.3.25 for /dev symbol: "fixscsigenericperms" not found in /lib/devfsd/scsigenericperms.so umount: /initrd: device is busy Checking root file system... fsck 1.37 (21-Mar-2005) e2fsck 1.37 (21-Mar-2005) /dev/sdcard0/disc0/part3: clean, 15437/60000 files, 244038/244224 blocks Cleaning up ifupdown...done. Loading modules: usbcore zd pcipool usb-ohci usb-ohci-ep93xx af_packet Checking all file systems... fsck 1.37 (21-Mar-2005) e2fsck 1.37 (21-Mar-2005) /dev/sdcard0/disc0/part4: clean, 11/93888 files, 2959/187712 blocks ... done. /dev/sdcard0/disc0/part4 on /mnt/part4 type ext2 (rw,noatime) Setting up networking...done. Starting hotplug subsystem: usb isapnp ide scsi. Starting portmap daemon: portmap. Starting portmapper...Mounting remote filesystems... mount: RPC: Remote system error - Network is unreachable Recovering nvi editor sessions... done. INIT: Entering runlevel: 2 Starting internet superserver: inetd. Starting OpenBSD Secure Shell server: sshdCould not load host key: /etc/ssh/sshy Could not load host key: /etc/ssh/ssh_host_dsa_key Disabling protocol version 2. Could not load host key sshd: no hostkeys available -- exiting. Starting NFS common utilities: statd. Starting periodic command scheduler: cron. Debian GNU/Linux 3.1 ts7000 ttyAM0 ts7000 login: If the system requests a password then try logging in with user id root without a password. 2 Go through the output above and try to figure out what the systems is doing – note that there are error messages! Your system may well differ from the above output. Talking to the TS7300 In order to talk to the board the easiest form of connection is through the serial port. You will need a null modem serial cable – there are lots hanging up in the labs. Connect to serial port 1 on the ts7300 – next to the USB port and onto serial port 1 on the desktop PC. The program to manage the connection is called minicom, it is available on most Linux distros, it is installed on the Netlabs Linux. To connect you can type in %minicom -o pup1 The -o stops minicom sending any modem control signals down the wire, the pup1 is a configuration script for the puppeteer boards. These board have the same settings as the ts7300, so we can use their config files. The setting are (if you want to do it manually – no hardware or software flow control, 115200 baud. If you have connected to the 2nd serial port you need to use the pup2 config file. %minicom -o pup2 Connect to the board and boot it up – you should see some of the output mentioned above. To get a minicom menu type ^A (control A). You can follow that by another command - ^AZ shows you a menu of commands, ^AQ quits from minicom. Installing Linux on an SD card It is quite likely that you will need to install Linux onto an SD card or upgrade your version. If you have a laptop, running Linux, with an SD card reader then it is possible to do the installation without using the TS board. Before powering up the board, put the Linux bootable SD card into slot 1 and the new card into slot 2. Power up and boot the system. You should find that the system on boot has found the cards. You can either look in the systems diagnostic messages, using dmesg | more, or by looking in the file /proc/devices. In the dmesg output you should find that it reports the partitions that the disk has, sdcard0: Technologic Systems SD card controller, address 0x13000000 sdcard0: card size 1999872 sectors Partition check: sdcard0a: p1 p2 p3 ..... ...... 3 sdcard1: Technologic Systems SD card controller, address 0x72000020 sdcard1: card size 1999872 sectors sdcard1a: p1 p2 p3 p4 This shows that SD card 0 has 3 sectors and card 1 has 4. It is likely that with a new card that it will have 1 large sector. In order to change this we will need to edit the disk's partition table using the fdisk command. The fdisk command, the commands name is lost in the history of MSDOS, is a fairly bruttal program that is used for editing disks' partition tables. The commands only argument is the name of the disk partition, so to look at SD card 0's partition table printing out the disk sizes in sectors rather than cylinders (much more useful), then type fdisk -lu /dev/discs/disk0/disc This will output root@ts7000:root# fdisk -ul /dev/discs/disc0/disc Disk /dev/discs/disc0/disc: 1023 MB, 1023934464 bytes 4 heads, 16 sectors/track, 31248 cylinders, total 1999872 sectors Units = sectors of 1 * 512 = 512 bytes Device Boot Start End Blocks Id System /dev/discs/disc0/part1 16 9855 4920 da Non-FS data /dev/discs/disc0/part2 9856 17727 3936 da Non-FS data /dev/discs/disc0/part3 17728 1999871 991072 83 Linux Copying the Boot sector In order to make an SD card bootable the first sector of the disk must contain some boot loader code as well as the partition. As the boot sector is not part of the mountable file system it is also not available to commands that manipulate those file systems. For example, you can't use a command like cp (copy) to copy the boot sector onto the disc as the boot sector is 'outside' of the file system. Fortunately Linux comes with command that can deal with such situations and the 'raw' disk is made available to developers. The command that is most commonly used is dd. This command reads data from an input stream and copies, with possible transformations, to an output stream. It doesn't sound too exciting but the important point is that it makes no assumptions about the format of the data and isn't restricted where it writes it. In order to copy the boot sector from one SD disk to the other we need to know where they are and how big they are. Finding the boot sectors is fairly easy, they are at the beginning of the raw drives. So for SD card01 the raw disc is /dev/discs/disc0/disc, for 1 is /dev/discs/disc1/disc. 4 Although the boot sector is only 512 bytes, we can copy across the whole sector 1k (1024 bytes). The command to do this is dd if=/dev/discs/disc0/disc of=/dev/discs/disc1/disc bs=1k count=1 Read the manual entry for dd – man dd. Be careful to distinguish between the command name dd and the arguments -l, bs=..,etc, You can use the tab character to automatically complete path names, which may help. So we can see that the input and output files are correct, the block size (bs) to be copied is 1 k and the number of blocks is 1. WARNING – if you get the source and destination mixed up then you could end up with an unbootable disc! You should receive the following (or similar) message on completion, 1+0 records in 1+0 records out 1024 bytes (1.0 kB) copied, 0.0238498 s, 42.9 kB/s As well as copying the boot loader code it will have also have copied across the partition table for the disc.
Load more

Recommended publications
  • Click to Add Title Click to Add Subtitle (If Applicable) Click to Add
    Identifying Command, Control and Communication Networks from Interactions and Activities Observations Georgiy Levchuk, Ph.D., Aptima Inc. Yuri Levchuk, Ph.D., Aptima Inc. CCRTS, 2006 © 2006, Aptima, Inc. 1 Agenda Challenges of tactical operations Proposed integrated solution concept Focus of this research: adversary organization identification Technical approach Results and conclusions © 2006, Aptima, Inc. 2 3 Major Challenges of Tactical Operations Conflicts Trends Technology/Information Trends Adversary’s Trends 70 4500 Past 60 4000 Large-size forces of well-known 3500 50 organizational forms 3000 40 Current 2500 Main telephone lines 30 Small- to moderate-size militia 2000 Mobile cellular forces taking many less #, Millions subscribers 20 1500 Internet users organized forms # of US forces ops forces US # of 10 1000 Future: Adaptive Enemy 0 500 Almost unrestricted ability to 1946-1969 1970-1990 1991-2006 0 connect and coordinate 1992 1998 2004 2010 (est) Years Year Can change size and adapt Past Past structure Slow-time conflict Mainly hard-line communications Numbered engagements Current Internet traffic doubles/year Current 630,000 phone lines installed/week Tactical Planning Issues Asymmetric threats and 50,000 new wireless users/day changing missions 650M SIGINT cables generated High manpower needs (~0.001% to products) Takes long time Future: Increased # of Ops 34M voice mail messages/day High info gaps, complexity, Fast-paced engagements 7.7M e-mails sent/min overload Larger number of and Future: Data Explosion Biases of human decisions higher time criticality Data impossible to analyze manually © 2006, Aptima, Inc. 3 Solution: A System to Aid Battlefield CMDR to Design Effective Counteractions against Tactical Adversary Semi-automated System CMDR & planning staff Battlefield Execute attacks against enemy Gather intel INPUT PRODUCT •comm.
    [Show full text]
  • Powerview Command Reference
    PowerView Command Reference TRACE32 Online Help TRACE32 Directory TRACE32 Index TRACE32 Documents ...................................................................................................................... PowerView User Interface ............................................................................................................ PowerView Command Reference .............................................................................................1 History ...................................................................................................................................... 12 ABORT ...................................................................................................................................... 13 ABORT Abort driver program 13 AREA ........................................................................................................................................ 14 AREA Message windows 14 AREA.CLEAR Clear area 15 AREA.CLOSE Close output file 15 AREA.Create Create or modify message area 16 AREA.Delete Delete message area 17 AREA.List Display a detailed list off all message areas 18 AREA.OPEN Open output file 20 AREA.PIPE Redirect area to stdout 21 AREA.RESet Reset areas 21 AREA.SAVE Save AREA window contents to file 21 AREA.Select Select area 22 AREA.STDERR Redirect area to stderr 23 AREA.STDOUT Redirect area to stdout 23 AREA.view Display message area in AREA window 24 AutoSTOre ..............................................................................................................................
    [Show full text]
  • S.Ha.R.K. Installation Howto Tools Knoppix Live CD Linux Fdisk HD
    S.Ha.R.K. Installation Tools HowTo • Linux fdisk utility • A copy of Linux installation CD • A copy of Windows® installation CD Tullio Facchinetti University of Pavia - Italy • Some FreeDOS utilities • A copy of S.Ha.R.K. S.Ha.R.K. Workshop S.Ha.R.K. Workshop Knoppix live CD Linux fdisk Command action a toggle a bootable flag Download ISO from b edit bsd disklabel c toggle the dos compatibility flag d delete a partition http://www.knoppix.org l list known partition types m print this menu n add a new partition o create a new empty DOS partition table p print the partition table q quit without saving changes • boot from CD s create a new empty Sun disklabel t change a partition's system id • open a command shell u change display/entry units v verify the partition table • type “su” (become root ), password is empty w write table to disk and exit x extra functionality (experts only) • start fdisk (ex. fdisk /dev/hda ) Command (m for help): S.Ha.R.K. Workshop S.Ha.R.K. Workshop HD partitioning HD partitioning 1st FreeDOS FAT32 FreeDOS must be installed Primary 2nd Windows® FAT32 into the first partition of your HD or it may not boot 3rd Linux / extX Data 1 FAT32 format data partitions as ... Extended FAT32, so that you can share Data n FAT32 your data between Linux, last Linux swap swap Windows® and FreeDOS S.Ha.R.K. Workshop S.Ha.R.K. Workshop 1 HD partitioning Windows ® installation FAT32 Windows® partition type Install Windows®..
    [Show full text]
  • Net Search — Search the Internet for Installable Packages
    Title stata.com net search — Search the Internet for installable packages Description Quick start Syntax Options Remarks and examples Also see Description net search searches the Internet for community-contributed additions to Stata, including, but not limited to, community-contributed additions published in the Stata Journal (SJ) and in the Stata Technical Bulletin (STB). net search lists the available additions that contain the specified keywords. The community-contributed materials found are available for immediate download by using the net command or by clicking on the link. In addition to typing net search, you may select Help > Search... and choose Search net resources. This is the recommended way to search for community-contributed additions to Stata. Quick start Search community-contributed commands for all terms word1, word2, and word3 net search word1 word2 word3 As above, but search for any term net search word1 word2 word3, or Search Internet sources other than the Stata Journal and the Stata Technical Bulletin net search word1 word2 word3, nosj 1 2 net search — Search the Internet for installable packages Syntax net search word word ::: , options options Description or list packages that contain any of the keywords; default is all nosj search non-SJ and non-STB sources tocpkg search both tables of contents and packages; the default toc search tables of contents only pkg search packages only everywhere search packages for match filenames search filenames associated with package for match errnone make return code 111 instead of 0 when no matches found Options or is relevant only when multiple keywords are specified. By default, net search lists only packages that include all the keywords.
    [Show full text]
  • Configuring Your Login Session
    SSCC Pub.# 7-9 Last revised: 5/18/99 Configuring Your Login Session When you log into UNIX, you are running a program called a shell. The shell is the program that provides you with the prompt and that submits to the computer commands that you type on the command line. This shell is highly configurable. It has already been partially configured for you, but it is possible to change the way that the shell runs. Many shells run under UNIX. The shell that SSCC users use by default is called the tcsh, pronounced "Tee-Cee-shell", or more simply, the C shell. The C shell can be configured using three files called .login, .cshrc, and .logout, which reside in your home directory. Also, many other programs can be configured using the C shell's configuration files. Below are sample configuration files for the C shell and explanations of the commands contained within these files. As you find commands that you would like to include in your configuration files, use an editor (such as EMACS or nuTPU) to add the lines to your own configuration files. Since the first character of configuration files is a dot ("."), the files are called "dot files". They are also called "hidden files" because you cannot see them when you type the ls command. They can only be listed when using the -a option with the ls command. Other commands may have their own setup files. These files almost always begin with a dot and often end with the letters "rc", which stands for "run commands".
    [Show full text]
  • System Analysis and Tuning Guide System Analysis and Tuning Guide SUSE Linux Enterprise Server 15 SP1
    SUSE Linux Enterprise Server 15 SP1 System Analysis and Tuning Guide System Analysis and Tuning Guide SUSE Linux Enterprise Server 15 SP1 An administrator's guide for problem detection, resolution and optimization. Find how to inspect and optimize your system by means of monitoring tools and how to eciently manage resources. Also contains an overview of common problems and solutions and of additional help and documentation resources. Publication Date: September 24, 2021 SUSE LLC 1800 South Novell Place Provo, UT 84606 USA https://documentation.suse.com Copyright © 2006– 2021 SUSE LLC and contributors. All rights reserved. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or (at your option) version 1.3; with the Invariant Section being this copyright notice and license. A copy of the license version 1.2 is included in the section entitled “GNU Free Documentation License”. For SUSE trademarks, see https://www.suse.com/company/legal/ . All other third-party trademarks are the property of their respective owners. Trademark symbols (®, ™ etc.) denote trademarks of SUSE and its aliates. Asterisks (*) denote third-party trademarks. All information found in this book has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither SUSE LLC, its aliates, the authors nor the translators shall be held liable for possible errors or the consequences thereof. Contents About This Guide xii 1 Available Documentation xiii
    [Show full text]
  • Recursive Static Route
    Recursive Static Route The Recursive Static Route feature enables you to install a recursive static route into the Routing Information Base (RIB) even if the next-hop address of the static route or the destination network itself is already available in the RIB as part of a previously learned route. This module explains recursive static routes and how to configure the Recursive Static Route feature. • Finding Feature Information, on page 1 • Restrictions for Recursive Static Route, on page 1 • Information About Recursive Static Route, on page 2 • How to Install Recursive Static Route, on page 3 • Configuration Examples for Recursive Static Route, on page 7 • Additional References for Recursive Static Route, on page 8 • Feature Information for Recursive Static Route, on page 8 Finding Feature Information Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required. Restrictions for Recursive Static Route When recursive static routes are enabled using route maps, only one route map can be entered per virtual routing and forwarding (VRF) instance or topology. If a second route map is entered, the new map will overwrite the previous one.
    [Show full text]
  • Chrome Immediately Removes and Deletes Downloaded Files Chrome Immediately Removes and Deletes Downloaded Files
    chrome immediately removes and deletes downloaded files Chrome immediately removes and deletes downloaded files. 7 Apr 2016 schedule [email protected] Issue 153212: Downloaded files disappearing on Windows. Reported by schedule. To review release notes for the Firebase console and for other Firebase platforms and related SDKs, refer to the Firebase Release Notes. 7 Aug 2014 A download could also be interrupted by accidentally removing the electrical power Rename it by deleting the “.crdownload” extension as shown below. Confirm that file has been downloaded by checking the download location. 31 Power Tips for Chrome That Will Improve Your Browsing Instantly. 2 Mar 2015 When Chrome finishes downloading the entire file, Chrome will rename it to Song.mp3, removing the .crdownload file extension. 6 days ago Deletes typed URLs, Cache, Cookies, your Download and Browsing Erase temporary files - Clear cookies and Empty cache - Delete client-side Web SQL instantly, with one click on the TP roll icon in the Chrome toolbar. Common issues with downloading files and folders from the Internet is that a file, it either instantly gets opened for viewing or downloaded to the computer. from the Chrome Web Store and see “NETWORK_FAILED” error, remove the Delete or rename the handlers.json file (for example, rename it handlers.json.old ). While most of us know how to erase our browser history in Chrome or Firefox, that That means that clearing your browser history does not delete any of your I recommend downloading one file to your PC and then creating a copy on an If you delete files from Dropbox, they are recoverable for up to 30 days.
    [Show full text]
  • Partition-Rescue
    Partition-Rescue Revision History Revision 1 2008-11-24 09:27:50 Revised by: jdd mainly title change in the wiki Partition-Rescue Table of Contents 1. Revision History..............................................................................................................................................1 2. Beginning.........................................................................................................................................................2 2.1. What's in...........................................................................................................................................2 2.2. What to do right now?.......................................................................................................................2 2.3. Legal stuff.........................................................................................................................................2 2.4. What do I need to know right now?..................................................................................................3 3. Technical info..................................................................................................................................................4 3.1. Disks.................................................................................................................................................4 3.2. Partitions...........................................................................................................................................4 3.3. Why is
    [Show full text]
  • CST118. Microsoft Command Line
    10/27/2020 https://curricunet.com/washtenaw/reports/course_outline_HTML.cfm?courses_id=10906 Washtenaw Community College Comprehensive Report CST 118 Microsoft Command Line Fundamentals Effective Term: Winter 2021 Course Cover Division: Business and Computer Technologies Department: Computer Science & Information Technology Discipline: Computer Systems Technology Course Number: 118 Org Number: 13400 Full Course Title: Microsoft Command Line Fundamentals Transcript Title: MS Command Line Fundamentals Is Consultation with other department(s) required: No Publish in the Following: College Catalog , Time Schedule , Web Page Reason for Submission: Three Year Review / Assessment Report Change Information: Course description Pre-requisite, co-requisite, or enrollment restrictions Outcomes/Assessment Objectives/Evaluation Rationale: There are three areas of change which are to be implemented once this three year Syllabus Review has been approved. The rationale for these changes is a result of the rapidly changing developments in the computer technology area which have made some of the existing objectives in this course either obsolete or at least in need of alteration. These include: 1. Removal of the objective dealing with disk tracks and sectors (and the associated lab project) since present day file systems and disk controllers have more than enough addressing. 2. Incorporation into the actual course an additional section on batch file programming (lecture and lab) that had been previously extra credit. With the recent changes to the Networking Degree, it was the intent to provide additional elementary programming experience in both the MS Command Line Course and the first Linux course. This additional advanced batch file section helps accomplish that purpose. 3. Expansion of the Powershell section of the Command Line course due to the elimination of the Powershell course from the Networking degree.
    [Show full text]
  • Partition.Pdf
    Linux Partition HOWTO Anthony Lissot Revision History Revision 3.5 26 Dec 2005 reorganized document page ordering. added page on setting up swap space. added page of partition labels. updated max swap size values in section 4. added instructions on making ext2/3 file systems. broken links identified by Richard Calmbach are fixed. created an XML version. Revision 3.4.4 08 March 2004 synchronized SGML version with HTML version. Updated lilo placement and swap size discussion. Revision 3.3 04 April 2003 synchronized SGML and HTML versions Revision 3.3 10 July 2001 Corrected Section 6, calculation of cylinder numbers Revision 3.2 1 September 2000 Dan Scott provides sgml conversion 2 Oct. 2000. Rewrote Introduction. Rewrote discussion on device names in Logical Devices. Reorganized Partition Types. Edited Partition Requirements. Added Recovering a deleted partition table. Revision 3.1 12 June 2000 Corrected swap size limitation in Partition Requirements, updated various links in Introduction, added submitted example in How to Partition with fdisk, added file system discussion in Partition Requirements. Revision 3.0 1 May 2000 First revision by Anthony Lissot based on Linux Partition HOWTO by Kristian Koehntopp. Revision 2.4 3 November 1997 Last revision by Kristian Koehntopp. This Linux Mini−HOWTO teaches you how to plan and create partitions on IDE and SCSI hard drives. It discusses partitioning terminology and considers size and location issues. Use of the fdisk partitioning utility for creating and recovering of partition tables is covered. The most recent version of this document is here. The Turkish translation is here. Linux Partition HOWTO Table of Contents 1.
    [Show full text]
  • Axis Title Options — Options for Specifying Axis Titles
    Title stata.com axis title options — Options for specifying axis titles Description Quick start Syntax Options Remarks and examples Also see Description axis title options specify the titles to appear on axes. Quick start Give the y axis the title “My Y Title” graph_command ::: , ::: ytitle("My Y Title") Give the x axis a two-line title “My Somewhat Longer X Title” graph_command ::: , ::: xtitle("My somewhat" "longer X Title") Specify that no y-axis title be printed graph_command ::: , ::: ytitle("") Specify that the x title be printed in green graph_command ::: , ::: xtitle(, color(green)) Leave a medium-sized margin between the y axis and its title graph_command ::: , ::: ytitle("My Y Title", margin(medium)) 1 2 axis title options — Options for specifying axis titles Syntax axis title options are a subset of axis options; see[ G-3] axis options. axis title options control the titling of an axis. axis title options Description ytitle(axis title) specify y-axis title xtitle(axis title) specify x-axis title ttitle(axis title) specify t (time)-axis title ztitle(axis title) specify contour legend axis title The above options are merged-explicit; see[ G-4] Concept: repeated options. where axis title is "string" "string" ::: , suboptions string may contain Unicode characters and SMCL tags to render mathematical symbols, italics, etc.; see[ G-4] text. suboptions Description axis(#) which axis, 1 ≤ # ≤ 9 prefix combine options suffix combine options textbox options control details of text appearance; see[ G-3] textbox options Options ytitle(axis title), xtitle(axis title), and ttitle(axis title) specify the titles to appear on the y, x, and t axes.
    [Show full text]