Cpre584 - User contributions [en]

Useful RedBoot Commands

2010-03-02T14:27:47Z

127.0.0.1: /* NFS Root */

==Load kernel & ramdisk.gz via onboard flash==
<pre>
fis load ramdisk.gz 
fis load zImage 
exec -c "console=ttyAM0 root=/dev/ram" 
</pre>

== Load kernel from onboard flash, Root filesystem on USB flash==
<pre>
fis load zImage 
exec -c "console=ttyAM0 root=/dev/sda1 [rootdelay=10]" 
</pre>

== Load kernel via xmodem/ymodem==
===At RedBoot Shell (via Minicom)===
<pre> load -r -b 0x80000 -m {xmodem|ymodem} </pre>

===Minicom Commands===
In Minicom: Type {Ctrl-a}{s} 
Select {xmodem|ymodem} and locate file 

===Boot the kernel===
<pre> exec -c "console=ttyAM0 root=/path/to/root [rootdelay=10]" </pre>

Note: rootdelay=10 is only necessary if root is located on USB drive 
Note: xmodem/ymodem takes approximately 6 minutes to download 

== Load kernel via TFTP==
<pre>
ip_address [-l <local_ip_address>] -h <tftp_server_address> 
load -r -v -b 0x800000 ramdiskWebMod.gz 
load -r -v -b 0x80000 zImage9302_2.6.21 
exec -r 0x800000 -s <size_of_ramdisk_in_hex> -c "console=ttyAM root=/dev/ram" 
</pre>

==NFS Root==
===Desktop PC Steps===
====Compile the Kernel====
Compile the kernel according to the [http://code.google.com/p/cs-e9302/wiki/HowToCompileTheKernel walkthrough].
====Create NFS Root Filesystem on PC====
<pre>mkdir -p /ep9302/<username>/nfsroot
cp /media/CS-EP930x_A/rootdir.tgz /ep9302/<username>/nfsroot
cd /ep9302/<username>/nfsroot
tar -xzf rootdir.tgz</pre>
*NOTE: The last line will result in errors trying to create the special files in the ''dev'' directory. You will need to contact [mailto:csg@iastate.edu CSG] for access rights to create these files
*NOTE: Optionally remove line about ''/dev/sda1'' from ''/ep9302/<username>/nfsroot/dev/fstab''. This will avoid a mounting error at boot time on the EP9302 board.

===EP9302/RedBoot Steps===
=====Load your compiled kernel=====
<pre>load -r -v -b 0x80000 zImage</pre>
=====Execute the kernel=====
<pre>exec -c "console=ttyAM0 root=/dev/nfs nfsroot=<server_ip>:/path/to/root/ ip=<board_ip>"</pre>
*For me this line was ''exec -c "console=ttyAM0 root=/dev/nfs nfsroot=192.168.1.5:/ep9302/<username>/nfsroot ip=192.168.1.1"''
*NOTE: /path/to/root is path to your nfsroot directory on the desktop relative to the /ep9302 directory
*NOTE: If you receive a warning saying no console found then you need to fix the ''dev'' directory as described above.

==Links==
[http://ecos.sourceware.org/docs-latest/redboot/redboot-guide.html RedBoot Online User Guide] 
[http://www.olimex.com/dev/pdf/ARM/CIRRUS/CS-E9302.pdf EP9302 User Guide] 
[http://olimex.com/dev/cs-e930x.html Olimex Board Website] 
[http://dev.ivanov.eu/projects/cs-e9302/ EP9302 Project Website] 
[http://code.google.com/p/cs-e9302/wiki/HowToCompileTheKernel Kernel Build Walkthrough]

Olimex EP9302

2010-02-10T19:25:46Z

127.0.0.1: New page: Load kernel & ramdisk.gz via onboard flash fis load ramdisk.gz fis load zImage exec -c "console=ttyAM0 root=/dev/ram" *Kernel from onboard flash, Root filesystem on USB flash fis load zIm...

Load kernel & ramdisk.gz via onboard flash
fis load ramdisk.gz
fis load zImage
exec -c "console=ttyAM0 root=/dev/ram"

*Kernel from onboard flash, Root filesystem on USB flash
fis load zImage
exec -c "console=ttyAM0 root=/path/to/root [rootdelay=10]"

*Kernel Load Via xmodem/ymodem (~6 Minutes to download)
At RedBoot Shell (via Minicom)
load -r -b 0x80000 -m {xmodem|ymodem}

Minicom Commands
In Minicom Type: {Ctrl-a}{s}
Select {xmodem|ymodem} and locate file

Boot the kernel
exec -c "console=ttyAM0 root=/path/to/root [rootdelay=10]"

Note: rootdelay=10 only necessary if root is located on USB drive

*Load kernel via TFTP---
ip_address [-l <local_ip_address>] -h <tftp_server_address>
load -r -v -b 0x800000 ramdiskWebMod.gz
load -r -v -b 0x80000 zImage9302_2.6.21
exec -r 0x800000 -s <size_of_ramdisk_in_hex> -c "console=ttyAM root=/dev/ram"

---RedBoot Online User Guide
<a href="http://ecos.sourceware.org/docs-latest/redboot/redboot-guide.html">Test</a> 
---EP9302 User Guide---
http://www.olimex.com/dev/pdf/ARM/CIRRUS/CS-E9302.pdf 
---Olimex Board Website---
http://olimex.com/dev/cs-e930x.html
---Website with kernel compiling instructions & patches---
http://dev.ivanov.eu/projects/cs-e9302/ 
---Kernel build process linked in Dr. Jones' Slides---
http://code.google.com/p/cs-e9302/wiki/HowToCompileTheKernel

Loading Linux on ML507

2009-12-16T23:26:04Z

127.0.0.1:

# The website to be followed is http://xilinx.wikidot.com/powerpc-linux
# The following things need to be taken care while loading linux on ML507 board
## The linux source has to be downloaded using git git clone git://git.xilinx.com/linux-2.6-xlnx.git. Do not try to get the snapshot from the website http://git.xilinx.com . It might not contain the virtex440-ml507.dts file. Instead it might contain ml507.dts, which would lead to errors while building the linux kernel
## In the dts (virtex440-ml507.dts) file the following boot arguments need to be updated
### ip=on (DHCP) => ip=192.168.1.10 (Which assigns linux a static IP address)
### Change root to root=/dev/ram rw. This makes the filesystem read write.
## Before connecting to the ml507 board using the connect command, the fpga must be programmed with the reference bitfile available at https://secure.xilinx.com/webreg/clickthrough.do?cid=111799 (you will need to have a Xilinx account to access the project). It is called ug511_ppc440_emb_ref.zip.The bitfile to be downloaded is ml507_ppc440_emb_ref/ready_for_download/download.bit. Use impact to download this bit file onto FPGA and then connect to the board.
## The kernel image file simpleImage.virtex440-ml507.elf needs to be loaded onto the board instead of the simpleImage.initrd.virtex440-ml507.elf file. The initrd* file contains the ram disk image. However, one of the fall 2009 teams used the simpleImage.initrd.virtex440-ml507.elf successfully, assuming the previous steps.

Detailed notes from Fall 2009 dmrisse/adamj:
I originally wrote this as a script (on this machine), but eventually just used it for notes. Here are the steps for building and loading the kernel enumerated:
# source /usr/local/bin/Xilinx_src
# create a project directory such as /home/$USER/583/project
# cd to that directory
# git clone git://git.xilinx.com/device-tree.git
# git clone git://git.xilinx.com/linux-2.6.git
# edit ./linux-2.6-xlnx/arch/powerpc/boot/dts/virtex440-ml507.dts as shown above for IP address and file system writeability.
# PATH=$PATH:/opt/eldk/usr/bin
# export CROSS_COMPILE=ppc_4xx-
# cd ./linux-2.6-xlnx
# make ARCH=powerpc simpleImage.virtex440-ml507
# make ARCH=powerpc simpleImage.initrd.virtex440-ml507 (this is the image I used)
# Use iMPACT to load a suitable bitfile as described above. We ended up basing our project partially on MP2, so that bitfile provided a basis.
# cd ./arch/powerpc/boot
# (from the website above using XMD:
## connect ppc hw -debugdevice deviceNr 5 cpunr 1
## dow simpleImage.initrd.virtex440-ml507.elf
## run
## (when done) stop
# use minicom to connect to and watch the kernel boot up. Alternately, you can telnet to 192.168.1.10. Login with user and password both "root" (can also FTP in to load files into it). The kernel doesn't come with many binaries; things in /bin are all sym-links to busybox.

How we compiled software for the ppc Linux kernel:
# Since one of this did the VHDL project and the other focused on the software side, I had to include files from his directory. Assuming a Xilinx project like MP2 in /home/$USER/583/project.
# source /usr/local/bin/Xilinx_src
# PATH=/opt/phj_eldk/usr/bin:$PATH
# export CROSS_COMPILE=ppc_4xx-
# cd to directory with source code you want to build (my example is a self-contained .c file).
# powerpc-linux-gcc -static -o myBinary.exe -I /home/$USER/583/project/ppc440_0/include -L /home/$USER/project/ppc_440)0/lib mySource.c
# myBinary.exe is an arbitrary choice, you could leave out the -o file.exe altogether.
# Use FTP to put the executable onto the ppc linux kernel while its running.
# chmod +x the binary on the PPC (or chmod u+x or whatever...).
# now you can run the binary on Linux on the PPC on the FPGA.

Compiling on rcl.ece.iastate.edu

2009-04-21T22:59:20Z

127.0.0.1:

Make Command: make -C /usr/src/kernels/2.6.26.8-57.fc8-i686 M=`pwd` modules

== Makefile ==
obj-m := hello.o

== Load Module ==
sudo insmod filename.ko

== unLoad Module ==
sudo rmmod filename

== See printouts ==
dmesg | tail

MemoCode 2009 Team BarraCuda

2009-03-31T21:58:24Z

127.0.0.1: /* Results */

== Team Name ==
We selected BarraCuda because it is a very fearsome and voracious predator.
You can find more at http://en.wikipedia.org/wiki/Barracuda

== CUDA Documentation ==
http://www.nvidia.com/object/cuda_develop.html 
http://www.nvidia.com/object/cuda_home.html#

== Ported C Code to CPU ==
[http://127.0.0.1/testwiki/images/8/86/MemoCode_InC.zip C Code (zip)]

== Equipment ==
Tesla C870
*http://www.nvidia.com/object/tesla_gpu_server.html
*Host Computer: argyle.ece.iastate.edu
**Contact Mike Steffen (steffma@iastate.edu) for an account.

== Minimum Memory Requirements ==
The green points ("critical values") in the graph below are the fewest points necessary to complete the polar to cartesian interpolation. 

 [[Image:Critical Points1.png]] 

 Each graph below corresponds to a specific N value. For each graph, the x-axis is in terms of theta and ranges from pi/256 to pi/4.
The y-axis shows the minimum number of KB's required to hold the critical values assuming each critical value requires four bytes of memory. There are ten lines on each graph corresponding to specific R values, R = 10, 20, ... , 90, 100 going from the top line to the bottom.
 

[[Image:graph_N10.png]][[Image:graph_N50.png]] 
[[Image:graph_N100.png]][[Image:graph_N200.png]] 
[[Image:graph_N300.png]][[Image:graph_N400.png]] 
[[Image:graph_N500.png]][[Image:graph_N600.png]] 
[[Image:graph_N700.png]][[Image:graph_N800.png]] 
[[Image:graph_N900.png]][[Image:graph_N1000.png]] 

== Final Results ==
 
<table border="1">
<tr><h4>Benchmark Results (Runtime)</h4></tr>
<tr><td>Test Cases</td><td>N</td><td>Theta</td><td>R</td><td>Ref Run Time (usec)</td><td>Cuda Run Time (usec)</td><td>Speedup</td></tr>
<tr><td>0</td><td>10</td><td>asin(0.1)</td><td>10</td><td>10958</td><td>6</td><td>1826.33</td></tr>
<tr><td>1</td><td>700</td><td>asin(0.1)</td><td>10</td><td>55619461</td><td>691</td><td>80491.26</td></tr>
<tr><td>2</td><td>1000</td><td>asin(0.1)</td><td>10</td><td>113455229</td><td>1202</td><td>94388.71</td></tr>
<tr><td>3</td><td>10</td><td>asin(0.0123)</td><td>100</td><td>11033</td><td>5</td><td>2206.6</td></tr>
<tr><td>4</td><td>700</td><td>asin(0.0123)</td><td>100</td><td>56893226</td><td>717</td><td>79348.99</td></tr>
<tr><td>5</td><td>1000</td><td>asin(0.0123)</td><td>100</td><td>116084611</td><td>1215</td><td>95542.89</td></tr>
<tr><td>6</td><td>10</td><td>asin(0.2)</td><td>100</td><td>11021</td><td>7</td><td>1574.43</td></tr>
<tr><td>7</td><td>700</td><td>asin(0.2)</td><td>100</td><td>55963647</td><td>665</td><td>84155.86</td></tr>
<tr><td>8</td><td>1000</td><td>asin(0.2)</td><td>100</td><td>112892176</td><td>1352</td><td>83500.13</td></tr>
<tr><td></td><td></td><td></td><td></td><td></td><td>'''Geometric Mean'''</td><td>23924.63</td></tr>
<tr><td></td><td></td><td></td><td></td><td></td><td>'''Average'''</td><td>58115.02</td></tr>
</table>

Xilinx.ece.iastate.edu

2009-02-25T04:16:16Z

127.0.0.1: /* Xilinx EDK */

__TOC__

==Usage==
===SSH===
Use SSH for either just a terminal or for port forwarding. Make sure that your computer has an X server. For windows use Xming and most linux machine should have it enabled by default.
<pre> ssh -Y xilinx.ece.iastate.edu</pre>
===NX Client===
Use NX Client for a visual desktop similar to remote desktop
[http://www.nomachine.com/download.php NX Client download]

==Sharing==
Turn on messages in your terminal
<pre>mesg y</pre>
See who is all logged into the system
<pre>who</pre>
Send messages to all users logged in
<pre>wall</pre>
Examples
<pre>
-bash-3.2$ mesg y
-bash-3.2$ wall "Is anyone using the HW"
-bash-3.2$ wall "I will use it from 7pm – 7:30pm"
-bash-3.2$ wall "I am finished with the HW"
</pre>

==Software==

===Xilinx EDK===
Source the correct file and then run Xilinx EDK in the background. If not connected through NX client, then you need to enable X11 forwarding.
<pre>
source /usr/local/bin/Xilinx_src
xps &
</pre>

CAT

2009-02-25T04:15:44Z

127.0.0.1: New page: lasdfkalsdkgjlasdkgjas

lasdfkalsdkgjlasdkgjas