分类： LINUX
2013-06-10 18:48:31
Altera WIKI上的一篇文章，讲如何医治uclinux系统到fpga的。
Here we will setup the source to build Nios2 uClinux. branch "test-nios2", per 20090730.
(If you already have the toolchain and working git repos from 20080619 tarball, then you can pull updates without downloading the new tarball. There are copies of the update scipts and anonymous sshkey in the nios2-linux/toolchain-build/release_top/ dir. Copy them to nios2-linux dir.
cp -a nios2-linux/toolchain-build/release_top/* nios2-linux
You must get updates to build toolchain with host gcc 4.3 for 20080619 tarball.)
Contents[hide] |
You must have a Linux desktop with software development packages. Login as root or use sudo to install these packages.
(for RHEL or CentOS, please add epel repository, How to use EPEL)
sudo rpm -Uvh
sudo yum install git-all git-gui make gcc ncurses-devel bison byacc flex \ gawk gettext ccache zlib-devel gtk2-devel lzo-devel pax-utilslibglade2-devel
sudo zypper install git-core git-gui make gcc ncurses-devel bison byacc \flex gawk gettext ccache zlib-devel lzo-devel pax-utilslibglade2-devel
sudo apt-get updatesudo apt-get install git-core git-gui make gcc ncurses-dev bison flex gawk \gettext ccache zlib1g-dev libx11-dev texinfo liblzo2-dev pax-utils uboot-mkimage corkscrew
(If Ubuntu/Debian can't find the liblzo2-dev package search for equivalent. This is needed for the MTD tools package.)
Please check your git version with "git --version". If it is older than 1.5.3.x, please update to the latest.
On Ubuntu, check if the default shell is "bash"
ls -l /bin/sh
This should give "/bin/sh -> bash", Otherwise, change it with,
sudo rm /bin/shsudo ln -s bash /bin/sh
followed by a logout and log back in again.
As root, check if you have "cc" which is a symlink to "gcc".
which gccgcc -vwhich cccc -v
if not,
cd /usr/binln -s gcc cc
Before compiling the 20090703 toolchain on a linux ubuntu/kubuntu 9.04 you need to make sure to install gcc version 4.2 (older) and gcc's file system link is properly pointing to it:
sudo apt-get install gcc-4.2sudo rm /usr/bin/gccsudo ln -s gcc-4.2 /usr/bin/gcc
If this isn't done tool chain compilation will buffer overflow on nios2-linux-uclibc-ar
Make sure you have 6GB or more free disk space. Please use wget to download the tar file nios2-linux-20100621.tar , 1.6GB. Best thanks to Altera kindly hosting these files. Please verify the sha1sum after download. (but don't use Windows ftp, it corrupts the files)
wget
sha1sum nios2-linux-20100621.tar
We use "git" to keep the source. You make check out GitServer later. The git database inside the tar file was compressed, so we don't do compression on the tar file.
You can build in any working directory as a user account, eg. in your home (say /home/hippo). The tar file contains a nios2-linux dir.
tar xfnios2-linux-20100621.tar # untar the packagecd nios2-linuxls # see what's inbinutils insight u-boot use_http_for_updatecheckout linux-2.6 uClibc use_ssh443_for_updateelf2flt README uClinux-distgcc3 sshkey updateglibc toolchain-build use_git_for_update# check out the source
./checkout
Now the source files for the Nios2 uClinux and gnutools are ready.
We will proceed to build the toolchain. If you don't want or fail to build it yourself, you may use the prebuildBinaryToolchain.
If you work on x86_64, 64 bits platform, you will need to change the arch to 32 bits , with "setarch i386" , to build gcc.
cd toolchain-buildgcc --version git clean -f -x -d # clean on restartmake gcc elf2flt gdb-host # setarch i386 make gcc elf2flt gdb-host, if you work on x86_64 platform # make -j6 gcc elf2flt gdb-host #if you have a multi-core machine, -j(number of cores +2) gives a nice parallel compilation speedupcd ..
It might take hours to build.
The default installation path is toolchain-build/build/nios2. Then setup the PATH for the tools, you can add a line at the end of file ~/.bash_profile (or ~/.bashrc on Debian/Ubuntu) ( the file is hidden, you have to use "ls -a" to find it . For "gedit" use open Location, and enter the file name), like this
PATH=$PATH:/home/hippo/nios2-linux/toolchain-build/build/nios2/bin
Logout and login again. You can use the tools now. Run this to verify that you have it in your command search path,
nios2-linux-uclibc-gcc -v
Try to compile a simple hello.c like this,
#include
int main(void)
{
printf("hello world");
}
nios2-linux-uclibc-gcc hello.c -o hello -elf2flt
The compiled object format is FLAT.
You may check it with,
nios2-linux-uclibc-flthdr hello
Now you can follow UClinuxDist to build the kernel. You should build in the new source tree, nios2-linux/uClinux-dist .
cd uClinux-distmake menuconfigmake vendor_hwselect SYSPTF=make
(EDIT: ccache links removed because it doesn't work well with blackfin uclinux-dist)
Important changes in this release, nios2-linux-20090730,
Important changes in this release, nios2-linux-20080619,
The latest branch is "test-nios2". Despite the "test" in the name, this does not mean "unstable". All future works and support will base on this branch. I won't update those older branches with the limited time available. Please migrate to the new branch.
The uClinux-dist dose not contain the kernel now. It should stick with "test-nios2" branch. It will merge updates from uclinux.org and blackfin uclinux.
The development of nios2 kernel will stick with mainly the "test-nios2" branch, with proper tags follow Linus' releases. eg "v2.6.26-nios2" tag when Linus release "v2.6.26" stable. Then it will move on to v2.6.27-rc1, but not with a new branch. It is still "test-nios2" branch.
Though there will be some experimental branches from time to time, but they will be merged into the main branch "test-nios2" at proper time. And then deleted.
If you need a "stable" branch, you can create local branch off the stable tags. You might apply patches from stable-queue git. Or you want to freeze. It is all up to you.
# patches for stable releasesgit clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git
After you have first successful boot, you can get updates from server. Change to the nios2-linux dir,
Normally you will use "git" protocol to get update from server if your PC is directly connected to the Internet. Then you should SKIP below and fetch update with git directly.
Only if you are behind a proxy firewall and cannot use git protocol, you can change the git to use ssh tunneling through port 443 to get updates from community server with this command once, "./use_ssh443_for_update" .
You should have ssh tunneling package installed, such as "corkscrew". Add the following 3 lines to your ~/.ssh/config, which should have no public access, "chmod og-rwx config". Replace
IdentityFile ~/.ssh/id_rsa IdentityFile ~/nios2-linux/sshkey/id_rsa ProxyCommand corkscrew
If you failed to use ssh tunnling as above, you may try dumb http protocol with this command, "./use_http_for_update" . But this is very slow and not recommended. You will need to add the setup of proxy to your login profile (.bash_profile or .profile),
export http_proxy=
You may revert to git protocol when there is no firewall blocking with this command, "./use_git_for_update".
Now fetch updates from server with, "./update" .
Fetching updates the first time can be a long lasting process, as there might be lots of patches applied to the version that had been downloaded. This is especially true if you are sitting behind a firewall and are foreced to use the dumb http protocol.
You might see connecion problems (e.g. "error 503") in the "./update" output. This usually does not indicate a permanent problem (if you see other git status messages before the update stops) and git is perfectly able to recover from those errors with the next "./update" run. You just need to redo "./update" until you don't see any lines but "Already up-to-date"
(note) if the kernel couldn't start after update..
Please disable optimize for size, or start with default config again.
General setup -->[ ] Optimize for size <== unselect
If you got such error in updating,
~/nios2-linux/uClinux-dist$ git pull .
vendors/Altera/nios2/config.vendor: needs update fatal: Entry 'vendors/Altera/nios2/config.vendor' not uptodate. Cannot merge.
Please do a "git checkout -f" . Then "git pull" again.
