Hardware/ARMEBS/3/DevEnv
From UIT
(Difference between revisions)
m (→Setup) |
Marc.pignat (Talk | contribs) |
||
(One intermediate revision by one user not shown) | |||
Line 1: | Line 1: | ||
− | {{ | + | {{public}} |
{{TOC right}} | {{TOC right}} | ||
= ARMEBS/Linux Development Environment = | = ARMEBS/Linux Development Environment = | ||
Line 55: | Line 55: | ||
TFTPD_ROOT="/opt/armebs3/tftp" | TFTPD_ROOT="/opt/armebs3/tftp" | ||
TFTPD_OPTS="--daemon --user nobody --group nobody" | TFTPD_OPTS="--daemon --user nobody --group nobody" | ||
+ | |||
+ | [[Category:Hardware]] [[Category:ARMEBS]] |
Latest revision as of 14:41, 26 June 2015
|
ARMEBS/Linux Development Environment
Here is the recommented way for setting up a development environment for ARMEBS3/Linux
- A decent x86 running Linux is recommended (all the provided development binaries are for i686-linux host, but if you want to compile all your tools from sources and run it on your OSX machine... you can... If you make it work on cygwin, please let me know, I'm curious how a ntfs filesystem will handle the 560'643 files my /opt/armeb3 directory holds)
- The development machine will be called 'devmachine', and must have standard development tools installed (make, gcc, subversion, a nfs server, libncurses, ...)
- The target armebs3 board will be target
- You need to have root access (for setup and for NFS file access) to your Linux machine and a standard user account, for instance devr
Setup
- setup a work place for daily use
su # got root? mkdir -p /opt/armebs3 # create the working directory mkdir /opt/armebs3/nfs # create the NFS directory mkdir /opt/armebs3/tfp # create the working directory chown devuser:users /opt/armebs3 # change the owner the regular user chown devuser:users /opt/armebs3 # change the owner the regular user exit # quit superuser mode cd /opt/armebs3 # go to it mkdir download # create a directory for file download
- Get all necessary files (into /opt/armebs3/download)
- toolchain download
- jffs2 utility mkfs.jffs2
- mkimage u-boot utility mkimage
- bdi configuration file : armebs3.cfg
- Setup the tool chain
su - # got root? cd /opt/armebs3/ # tar xvzf /opt/armebs3/download/arm-linux-tools-xxx.tar.gz # uncompress/install the toolchain # you can add the /opt/armebs3/cross/bin directory to your path, but this isn't requiered with our Makefiles
exit # quit superuser mode
- Setup the NFS
- /etc/exports: NFS file systems being exported. See exports(5).
/opt/armebs3/nfs 153.109.5.0/255.255.255.0(sync,rw,no_root_squash,no_all_squash)
- Start the NFS server
su - # become root /etc/init.d/nfs start # start the NFS server exit # quit superuser mode
- Setup the TFTP server
- TFTP server is used for holding BDI2000 configuration, files to program, and network booting
- Make sure the bdi will use this armebs3.cfg (only for BDI2000 users)
cd /opt/armebs3 mkdir tftp cp download/armebs3.cfg tftp/
- configuration example for the atftp tftp server
# /etc/conf.d/atftp Config file for tftp server TFTPD_ROOT="/opt/armebs3/tftp" TFTPD_OPTS="--daemon --user nobody --group nobody"