Script for Laboratory: Designing embedded ASIPs - CES

More documents

Recommendations

Info

Projects of the current working directory. An example for an absolute path is /home/asip01/test. e. Changing the current working directory: To change the current working directory use the cd command with a path name as the argument, i.e.: i. cd /home/asip01 ii. cd .. iii. cd ../asip02/ASIPMeisterProjects iv. cd ./dlx_basis/Applications f. Creating/Removing directories: the mkdir command takes a pathname as an argument and creates a new directory accessible via this path. The “-p” parameter tells mkdir to create any missing subdirectories as well. “rmdir” deletes empty directories. To remove non-empty directories use the “rm” command with the “-r” option (see below). Examples: i. mkdir ~/ASIPMeisterProjects/dlx_basis/Applications ii. rmdir ../dlx_basis/test1 iii. mkdir –p ~/some/non_existing/directory g. Listing directory contents: To examine directory contents use the ls command. Without parameters, it will show the file and directory names of the current working directory. The ls command has many parameters, all described in the man page. Typical ones are “-l” to provide a detailed listing, “-a” to show hidden files (filenames starting with a “.”), “-ltc” give a detailed listing with the last file modification time and sort by it (actually these are three parameters). Examples: i. ls ii. ls –l ../ASIPMeisterProjects iii. ls –ltc ASIPMeisterProjects/dlx_basis/ModelSim h. Moving and removing files: To move or rename a file use the mv command with the filename or directory as the argument. To remove a file use rm; the “-r” option causes recursive removal of subdirectories and their contents. Examples: i. mv Applications/tset Applications/test ii. rm /home/asip01/oldfile iii. rm –r ../dlx_basis - 8 -
i. Copying files: the cp command copies files and directories. Its arguments are: optional switches, then the source and the target. The “-r” switch enables recursive copying. Examples: i. cp TestData.IM TestData.IM-backup ii. cp –r dlx_basis dlx_custom • Shell operation: a. Input/Output redirection: Some programs read data on their standard input file descriptor (stdin), some write output to the standard output (stdout). Usually stdin is linked to the keyboard and stdout to the terminal screen. However, you can change this when calling a program. “someotherfile” will redirect stdout to write to “someotherfile” (if it doesn’t exist, it will be created, if it does, it will be truncated first – use “>>someotherfile” to append instead of truncate). Redirection is also possible to/from other processes via pipes: use “program1 | program2” to direct the output of program1 to the input of program2. Examples: i. ls –ltc >filelisting ii. ls | sort iii. cat >file2 (this appends the contents of file1 to file2). b. Job control: Processes started from the shell are often referred to as “jobs”. Usually, when the shell launches a program it will take control of the terminal and the shell will be suspended until the process terminates – the job “is running in the foreground”. To launch a job “in the background” – start it, but give control back to the shell immediately, append “&” to the parameter list. To list any jobs launched from this shell (they all have to be in the background), type “jobs” – this will give you the job-IDs with the program names and parameters of the jobs. To bring a job to the foreground, use “fg %job-ID” (substitute job-ID for the actual job ID). Sometimes you will want to temporarily stop a job – if the program is in the foreground, hit “CTRL-Z” (job suspension). To continue job execution in the foreground use “fg” as described above, or “bg %job-ID” to continue execution in the background. To terminate a job in the foreground, hit “CTRL-C” (send keyboard interrupt). Note that if a process is unresponsive (due to bugs – i.e. endless loop and signal processing disabled) it can ignore this; the only way to terminate it is to send a KILL signal (more on that further down). • Basic programs and commands a. Process/Activity listing. To view a complete list of running processes, use the ps program. It is mostly used with the “auxw” options to provide a complete and detailed listing. The output is usually quite long, so it is often piped into less or head. - 9 -
Page 1 and 2: Laboratory: “Designing Applicatio
Page 3 and 4: 6 Validating the CPU in Prototyping
Page 5 and 6: Figure 1-1 GPPs, ASIPs and ASICs [H
Page 7: • Command line interpreter Intera
Page 11 and 12: . Copying via ssh: Not all machines
Page 13 and 14: dlx_basis Applications ModelSim mei
Page 15 and 16: makeCoSy contCoSy Filename Explanat
Page 17 and 18: 3 Dlxsim Dlxsim [DLX-Package] is an
Page 19 and 20: Successful Successful dissolving di
Page 21 and 22: Instruction Description Instruction
Page 23 and 24: Option Description -dbb# (Debug Bas
Page 25 and 26: Instruction Format Parameters NO_AR
Page 27 and 28: Command Description stop {options}
Page 29 and 30: 3.3.2 Debugging with dlxsim This ch
Page 31 and 32: addComment1(); functionY(); addComm
Page 33 and 34: • If you manually want to write a
Page 35 and 36: 4.3 Tutorial for the “Flexible Ha
Page 37 and 38: in direction; The in keyword means
Page 39 and 40: amount : in std_logic_vector(7 down
Page 41 and 42: Add the three signals to the contro
Page 43 and 44: data_in : in std_logic_vector($W1 d
Page 45 and 46: 5 ModelSim ModelSim is a full-featu
Page 47 and 48: 5.1.3 Compile the project Figure 5-
Page 49 and 50: Mark the wave.do file in your Model
Page 51 and 52: Figure 5-6 ModelSim waves Signal Ex
Page 53 and 54: • Always invoke ModelSim in the s
Page 55 and 56: If you don’t already have a proje
Page 57 and 58: CPU VHDL Files have been generated
Page 59 and 60:
After the TestData-files for your a
Page 61 and 62:
However, you can’t force the synt
Page 63 and 64:
Timing (Timing Analyzer)” will op
Page 65 and 66:
7 Power estimation In this tutorial
Page 67 and 68:
- Start the simulation (Simulate/ s
Page 69 and 70:
8 CoSy compiler The CoSy compiler d
Page 71 and 72:
When you manually have to fix some
Page 73 and 74:
of the makeCoSy script. If an error
Page 75 and 76:
the automatically generated compile
Page 77 and 78:
instruction, as different custom in
Page 79 and 80:
Directive Explanation .restrict .ch
Page 81 and 82:
Now we will demonstrate how you can
Page 83 and 84:
the user changes the value of the b
Page 85 and 86:
• Huge decrease of cycle count
Page 87 and 88:
of instructions together it might t
Page 89 and 90:
Table of Figures Figure 1-1 GPPs, A
Page 91:
References [CES] Homepage of the Ch
show all

Script for Laboratory: Designing embedded ASIPs - CES

Create successful ePaper yourself

Delete template?

Save as template?