Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in
Toggle navigation
C
Conv TTL Blocking
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
5
Issues
5
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
Wiki
Wiki
image/svg+xml
Discourse
Discourse
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Commits
Issue Boards
Open sidebar
Projects
Conv TTL Blocking
Commits
5cde488a
Commit
5cde488a
authored
Jan 26, 2015
by
Theodor-Adrian Stana
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
sw: Updated top-level software readme file
parent
b6b4374d
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
30 additions
and
0 deletions
+30
-0
README.txt
software/README.txt
+30
-0
No files found.
software/README.txt
View file @
5cde488a
...
@@ -14,6 +14,36 @@ multiboot/ -- MultiBoot-related files
...
@@ -14,6 +14,36 @@ multiboot/ -- MultiBoot-related files
pulsetest/ -- Python script for running pulse tests
pulsetest/ -- Python script for running pulse tests
regtest/ -- Python script for running communication tests
regtest/ -- Python script for running communication tests
All of the scripts in this folder connect via Telnet to communicate to a board
inside a crate. The ei2c/ folder contains scripts that are used by all other
test scripts to control the connection. Of particular interest is the
ei2c/ei2cdefine.py script, where there are declarations of variables used by
all test scripts to control connecting to the board to be probed (see also
Getting Started below).
For more information on the scripts in each folder, refer to the README.txt
For more information on the scripts in each folder, refer to the README.txt
file in the respective folder.
file in the respective folder.
Getting started
===============
Normally, you would use these test scripts to connect to boards in multiple
crates. In this case, you will type in the crate's hostname or IP, user name
and password from the keyboard, which is the default state of the scripts
when you clone the repository.
Alternatively, should you want to work on a board in a single crate, perform
these steps:
1. Set the ENABLED variable to True in ei2c/ei2cdefine.py; this will enable the
use of the next three variables when connecting to a crate. The scripts will
now stop asking for a hostname, username and password every time you use them.
2. Set the HNAME variable to the hostname or IP to the appropriate value
according to the crate you connect to
3. Set the USER variable to the username to which you wish to connect on the
crate ("user" or "admin")
4. Set the PWD variable to the password for the previously-selected username
5. Should you want to debug the communication, the DUMP variable will enable
the generation of a file containing the dump of the communication (Telnet
command and its reply). The dump file will be a file called "dump.txt" in the
same directory as the script being run.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment