关闭

Getting Started Guide for Logic PD i.MX31 Litekit

645人阅读 评论(0) 收藏 举报
Getting Started Guide for Logic PD i.MX31 Litekit

Contents

Introduction

This document will describe in detail the procedures for booting aLinux kernel image and mounting a root file system over nfs on theLogic PD i.MX31 Litekit.

Prerequisites

Host Requirements

To properly boot a board using software from Timesys, your host machine must meet the following requirements:

  • Modern GNU/Linux Distribution. While you can use nearly any modernLinux distribution released in the last 24 months, Timesys recommendsone of the following:
    • Ubuntu (Most recent release or LTS)
    • Fedora (Most recent release)
  • An internet connection on the Development Host.
  • Root or sudo permission on the Development Host.
  • A copy of the Linux Kernel ( zImage-2.6.24-ts-armv6l) and Root FileSystem (rootfs.tar.gz) for the Target Board downloaded from Factory.These are found in the output directory of your online build, or in thedirectory build_armv5l-timesys-linux-<libc>/images/ on the command line.
  • If you are booting your root file system over the network, you willneed two network cards installed and configured in the DevelopmentHost. One to communicate normally with your LAN/WAN while installinghost packages, the other to communicate solely with the target board.
  • An available serial port on your Development Host.

Target Requirements

To boot the Logic PD i.MX31 Litekit, you will need the following items:

  • Logic PD i.MX31 Litekit Board
  • Serial NULL Modem Cable
  • Ethernet Crossover Cable or Ethernet hub/switch and Ethernet Patch Cables

Once you have all of the necessary components, you should perform the following steps:

  1. Connect the debug port of the board to the serial port of your workstation using the null modem cable.
  2. If you are using a cross-over cable, connect the Ethernet port of the board to the second Ethernet port of your workstation.
  3. If you are using an Ethernet hub or switch, connect the board tothe hub with a straight-through Ethernet cable, then connect the hub tothe second Ethernet port of your workstation.
  4. Connect the power supply to your board.

Preparing the Target

Configuring Serial Communication

The i.MX31LITE uses a serial debug port to communicate with the host machine.

The commands discussed in this section are meant to be performedby a privileged user account. This requires the root login orprepending each command with sudo.

Using Minicom

  1. Start minicom on your host machine in configuration mode. As root:

    # minicom -o -s -w

  2. A menu of configuration should appear. Use the Down-arrowkey to scroll down and select the Serial port setup option, and pressEnter.
  3. Verify that the listed serial port is the same one that isconnected to the target board. If it is not, press A, and enter thecorrect device. This is /dev/ttyS0 on most Linux distributions.
  4. Set the Bps/Par/Bits option by pressing the letter E and using thenext menu to set the appropriate values. You press the key thatcorresponds to the value 115200, then press Enter.
  5. Set Hardware flow control to No using the F key.
  6. Set Software flow control to No using the G key.
  7. Press Enter to return to the main configuration menu, and then press Esc to exit this menu.
  8. Reset the board, and wait for a moment. If you do not see outputfrom the board, press Enter several times until you see the prompt. Ifyou do not see any output from the board, and have verified that theserial terminal connection is setup correctly, contact your boardvendor.

TIP: If you experience an error similar to Device /dev/ttyS0 islocked when starting minicom, it usually means that another process isusing the serial port (which is usually another instance of minicom).You can find the process that is currently using the serial port byexecuting the following:

# fuser /dev/ttyS0
/dev/ttyS0:         28358

# ps 28358
  PID TTY      STAT  TIME COMMAND
  28923 pts/0    S+    0:00 minicom

This process can also be killed directly with fuser as root. Please use this command with caution:

# fuser -k /dev/ttyS0

Using GNU Screen

To quickly connect to a board using Gnu Screen, execute the following:

# screen /dev/ttyS0 115200

For more information about using screen, please consult the man page, or view the manual online at http://www.gnu.org/software/screen/manual/screen.html

Obtain Target Board MAC Address

Use the ifmac command from the losh> prompt to view the MAC address:

Example

losh> ifmac sm0
Current MAC Address: 00:03:04:05:06:07

Note the MAC address of the Target Board as you will need this to configure the DHCP service.

Preparing the Host

Setting up the network

The commands discussed in this section are meant to be performed bya privileged user account. This requires the root login or prependingeach command with sudo.

Identify the network adapter connecting the Host to the Target

Timesys only supports direct Ethernet connections from the developmentHost to the Target board. Ideally, the development Host would havetwo network adapters; one adapter to connect to your LAN, and oneEthernet card to connect directly to the Target board with a crossovercable or Ethernet hub. If your development Host only has one networkinterface it must be directly connected to the Target board.

The Ethernet adapter connected directly to the target board must be:

  • Configured with a proper static IP address and Subnet Mask.
  • Connected directly to the target board with either a crossover cableor its own Ethernet hub.

From a command prompt issue the command:

# /sbin/ifconfig

Each interface will report its IP address, Subnet Mask, and DefaultGateway information:

eth0 Link encap:Ethernet HWaddr 00:19:bb:49:ff:0e      
        inet addr:192.168.3.244 Bcast:192.168.3.255 Mask:255.255.254.0
        inet6 addr: fe80::219:bbff:fe49:ff0e/64 Scope:Link      
        UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1      
        RX packets:57214 errors:0 dropped:0 overruns:0 frame:0      
        TX packets:47272 errors:0 dropped:0 overruns:0 carrier:0
        collisions:0 txqueuelen:1000      
        RX bytes:43109083 (41.1 MB) TX bytes:6308206 (6.0 MB)
        Interrupt:16
eth1 Link encap:Ethernet HWaddr 00:10:b5:4a:c1:a9      
        inet addr:10.0.0.1 Bcast:10.0.0.255 Mask:255.0.0.0      
        UP BROADCAST MULTICAST MTU:1500 Metric:1      
        RX packets:0 errors:0 dropped:0 overruns:0 frame:0      
        TX packets:0 errors:0 dropped:0 overruns:0 carrier:0     
        collisions:0 txqueuelen:1000      
        RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)      
        Interrupt:21 Base address:0x1100
lo  Link encap:Local Loopback      
        inet addr:127.0.0.1 Mask:255.0.0.0      
        inet6 addr: ::1/128 Scope:Host      
        UP LOOPBACK RUNNING MTU:16436 Metric:1      
        RX packets:1974 errors:0 dropped:0 overruns:0 frame:0      
        TX packets:1974 errors:0 dropped:0 overruns:0 carrier:0     
        collisions:0 txqueuelen:0      
        RX bytes:226637 (221.3 KB) TX bytes:226637 (221.3 KB)

Note the IP address and Subnet Mask of the appropriate network connection.You will use this to configure the DHCP server.

Installing the server daemons on the development host

  • On Ubuntu 11.04 and newer:

    # apt-get install xinetd tftp tftpd isc-dhcp-server \
                      nfs-kernel-server portmap

  • On Ubuntu 10.11 and older:

    # apt-get install xinetd tftp tftpd dhcp3-server \
                      nfs-kernel-server portmap
    NOTE: Older versions of Ubuntu use nfs-common and nfs-user-server in place of nfs-kernel-server

  • On Fedora Core:

    # yum install xinetd tftp tftp-server dhcp nfs-utils

Important:

After installing these packages the DHCP server software may startautomatically. Having the DHCP server running while you are connectedto a LAN can interfere with the operation of other computers. Afterthe DHCP service installs and starts issue these commands to stopthe DHCP service and prevent it from starting automatically at boot:

  • To stop the dhcp service:

    • On Ubuntu 11.04 and newer:

      # service isc-dhcp-server stop

    • On Ubuntu 10.11 and older:

      # service dhcp3-server stop

    • On Fedora Core:

      # /etc/init.d/dhcp stop

  • To prevent the service from starting automatically:

    • On Ubuntu 11.04 and newer:

      # chmod 644 /etc/init.d/isc-dhcp-server

    • On Ubuntu 10.11 and older:

      # chmod 644 /etc/init.d/dhcp3-server

    • On Fedora Core:

      1. Click the System Menu
      2. Select Administration
      3. Select Services
      4. Select dhcpd
      5. Click the Customize button
      6. Uncheck Runlevel 2, 3, 4 and 5

Disable SELinux and Firewall on Fedora Core

On Fedora Core, SELinux and the firewall will interfere with many ofthe services that are needed to work with the target board. Theseshould be disabled before continuing.

Generally Ubuntu does not have these services running by default.

  1. Disable SELinux:

    1. Click the System Menu
    2. Select Administration
    3. Select SELinux Management
    4. Change System Default Enforcing Mode to Disabled

  2. Disable Firewall:

    1. Click the System Menu
    2. Select Administration
    3. Select Services
    4. Select iptables
    5. Click the Customize button
    6. uncheck Runlevel 2, 3, 4 and 5

Setting up DHCP

  1. Edit the dhcpd configuration file:

    • On Ubuntu, edit /etc/dhcp/dhcpd.conf and include the followinglines (note: on older versions of Ubuntu this file is at either/etc/dhcp3/dhcpd.conf or /etc/dhcpd.conf):

      subnet 10.0.0.0 netmask 255.0.0.0 {
       host targetboard {
        fixed-address 10.0.0.10;
        hardware ethernet 12:34:56:78:9a:bc;
        option root-path "/full/path/to/rfs";
        filename " zImage-2.6.24-ts-armv6l";
       }
      }

    • On Fedora Core, edit /etc/dhcpd.conf and include the following lines:

      ddns-update-style ad-hoc;
      subnet 10.0.0.0 netmask 255.0.0.0 {
       host targetboard {
        fixed-address 10.0.0.10;
        hardware ethernet 12:34:56:78:9a:bc;
        option root-path "/full/path/to/rfs";
        next-server 10.0.0.1;
        filename " zImage-2.6.24-ts-armv6l";
       }
      }

  2. Test the DHCP server on the network card that is connected to yourdevelopment board. For this example assume eth1. This command willstart the DHCP server in the foreground and output any status or errormessages to the screen.

    • On Ubuntu:

      # service dhcp3-server restart

    • On Fedora Core:

      # /usr/sbin/dhcpd -d eth1

    • It is recommended to start the DHCP server in this manner each timeyou need to boot your Target board.

Setting up TFTP

  1. Edit the xinetd.conf file

    • On Ubuntu, edit /etc/xinetd.conf and add the following lines just above the linethat reads includedir /etc/xinetd.d.

      service tftp
      {
       socket_type = dgram
       protocol = udp
       wait = yes
       user = root
       server = /usr/sbin/in.tftpd
       server_args = -s /tftpboot
       disable = no
      }

    • On Fedora Core, the tftp-server package creates a /etc/xinetd.d/tftp file. Edit thisfile and change the disable line fromyes to no. The contents of the file are:

      service tftp
      {
       socket_type     = dgram
       protocol      = udp
       wait       = yes
       user       = root
       server       = /usr/sbin/in.tftpd
       server_args     = -s /tftpboot
       disable      = no
       per_source      = 11
       cps       = 100 2
       flags       = IPv4
      }

  2. Create the /tftpboot folder if it does not exist:

    # mkdir /tftpboot

  3. Copy the kernel image to the /tftpboot directory:

    # cp /path/to/kernel/image/zImage-2.6.24-ts-armv6l \
                      /tftpboot/zImage-2.6.24-ts-armv6l

    NOTE Also copy other files that are required for booting, such as a device tree blob, to /tftpboot.

  4. Restart the xinetd server with the following command:

    # /etc/init.d/xinetd restart

  5. Test the TFTP server with the following commands

    # tftp localhost
    tftp> get  zImage-2.6.24-ts-armv6l
    Received 1456898 bytes in 0.4 seconds
    tftp> quit

  6. Set xinetd to start automatically on Fedora Core.

    Ubuntu users will skip this step.

    1. Click the System Menu
    2. Select Administration
    3. Select Services
    4. Select xinetd
    5. Click the Customize button
    6. Check Runlevel 2, 3, 4 and 5

Setting up NFS

  1. As root, extract rootfs.tar.gz to a directoryand note the path. This path will be referred to as /full/path/to/rfsin this document.

    # mkdir /full/path/to/rfs
    # cd /full/path/to/rfs
    # sudo tar xvf rootfs.tar.gz

  2. Export this path by editing /etc/exports to include a line similarto the following:

    /full/path/to/rfs 10.0.0.10(rw,no_root_squash)

  3. Restart the NFS services

    • On Ubuntu issue the following commands in order:

      # service portmap stop
      # service nfs-kernel-server stop
      # service portmap start
      # service nfs-kernel-server start
      NOTE: Older versions of Ubuntu use nfs-common and nfs-user-server in place of nfs-kernel-server

    • On Fedora Core:

      # /etc/init.d/nfs restart

  4. Set nfsd to start automatically on Fedora Core. Ubuntu users willskip this step.

    1. Click the System Menu
    2. Select Administration
    3. Select Services
    4. Select nfs
    5. Click the Customize button
    6. Check Runlevel 2, 3, 4 and 5

Booting the Board

NOTE: You must obtain the kernel file size, which must beentered as part of the load commands below. Note the byte size of thekernel image file as follows:

$ ls -al /tftpboot/zImage-2.6.24-ts-armv6l
rwxr-xr-x   1 user.name   group    1933004 Jun 6 13:04 zImage-2.6.24-ts-armv6l

  1. From your serial session issue the command:

    ifconfig sm0 dhcp
    The interface will show success as follows:
    losh> ifconfig sm0 dhcp
    Obtaining DHCP on sm0 .

  2. Verify that the board has received the correct IP Address:

    losh> ifconfig sm0
    sm0:  up 100M full-duplex promisc (5e5)
    sm0:  mac: 00:08:ee:01:f7:c0 ip: 10.0.0.10
    mask: 255.0.0.0 gw: 10.0.0.1
    losh>

  3. Load the kernel by issuing the following command.

    NOTE: the value of "1933004" represents the kernel file size you accessed above.

    losh> load raw 0x81000000 1933004 /tftp/10.0.0.2:zImage-2.6.24-ts-armv6l
    loading from /tftp/10.0.0.2:zImage-2.6.24-ts-armv6l:
    loading raw binary to 0x81000000 (ram) len xxxxxxxx:
    ............................................................
    ............................................................
    ............................................................
    ...........................................................done
    file loaded
    losh>

  4. Issue the kernel command as follows:

    losh> exec -t -i 1236

Additional Information

Factory Documentation


0
0

查看评论
* 以上用户言论只代表其个人观点,不代表CSDN网站的观点或立场
    个人资料
    • 访问:612538次
    • 积分:7762
    • 等级:
    • 排名:第2801名
    • 原创:135篇
    • 转载:182篇
    • 译文:5篇
    • 评论:45条
    最新评论