Lh7a40x.linux.bsp.User.manual

7/28/2019 Lh7a40x.linux.bsp.User.manual

1/18

NXP Linux 2.6LH7A40x BSP

2008-2009 NXP Semiconductors. All rights reserved.

1

NXP LH7A40x Linux Users Manual


2/18



2

Version historyRelease Date Comments1.00 10/23/2009 Initial release


3/18



3

Table of contents

1 Introduction......................................................................................................................................... 5

1.1 Copyrights and limitations.......................................................................................................... 5

1.2 Where to start.............................................................................................................................. 5

1.3 Required hardware and software................................................................................................ 51.3.1 Host system requirements....................................................................................................... 51.3.2 Target board requirements...................................................................................................... 6

1.4 About this document.................................................................................................................... 6

2 BSP overview....................................................................................................................................... 7

2.1 Supported hardware.................................................................................................................... 7

2.2 BSP information..........................................................................................................................7

2.2.1 LTIB integration..................................................................................................................... 72.2.2 Apex 1.6.8.............................................................................................................................. 72.2.3 Linux 2.6.29.6......................................................................................................................... 8

3 Building your Linux system............................................................................................................... 9

3.1 Downloading and installing LTIB............................................................................................... 9

3.2 Configuring LTIB........................................................................................................................93.2.1 First time running LTIB.......................................................................................................... 93.2.2 LTIB options........................................................................................................................103.2.3 LTIB build cycle...................................................................................................................113.2.4 Re-building the system......................................................................................................... 113.2.5 More on LTIB.......................................................................................................................11

4 Linux deployment methods.............................................................................................................. 12

4.1 Load and install Apex on the board........................................................................................... 124.1.1 Booting Apex from a Compact Flash card........................................................................... 134.1.2 Booting Apex from a TFT server over the network.............................................................. 134.1.3 Booting Apex from a NOR FLASH..................................................................................... 13

4.2 Booting the Linux kernel ........................................................................................................... 134.2.1 Kernel command line............................................................................................................ 134.2.2 Automating Apex boot......................................................................................................... 144.2.3 NFS mounted root filesystem............................................................................................... 144.2.4 EXT2 mounted root filesystem............................................................................................. 14

5 Additional information.....................................................................................................................155.1 Getting the BSP files.................................................................................................................. 15

5.1.1 Where to get the Linux Apex and kernel patches................................................................. 155.1.2 LTIB and GCC toolchain compatibility and dependency issues.......................................... 155.1.3 Known issues........................................................................................................................155.1.4 TFTP and NFS help..............................................................................................................155.1.5 ALSA device support...........................................................................................................165.1.6 Compact Flash (IDE) support............................................................................................... 165.1.7 Other links............................................................................................................................ 17


4/18



4


5/18



5

1 IntroductionThis document details the Linux 2.6.29.6 BSP for the NXP LH7A40x SoC (System on

Chip). The BSP provides a complete Linux port for the Logic PD LPD7A404 platformusing the LH7A404 MCU, but can be easily ported to other platforms.

This document covers many aspects of the Linux and the Linux operating system. Someof the areas covered include:

System and target board setup on the Logic PD LH7A40x board Using LTIB to build a complete Linux system Deployment methods for the target board

1.1 Copyrights and limi tations

The LH7A40x BSP is provided free of charge and with no support from NXP. Portions ofthe BSP are copyrighted by NXP Semiconductors.

1.2 Where to start

If you have limited or no experience with building Linux based systems, you should startwith using LTIB (Linux Target Image Builder). LTIB handles most of the hard work foryou deploying a complete Linux system with an easy to use menu interface. If you arethis type of user, start at Section 3.

If you already have experience setting up, building, and deploying a Linux system, youmay want to skip to just getting the necessary patches for Apex and the Linux kernel.These patches are available on the NXP website.

1.3 Required hardware and software

1.3.1 Host system requirements

To develop Linux for the LH7A40x, a host PC running the Linux operating system isneeded. Because of the many variations of Linux releases and supported packages, it isunknown if the tools included with the BSP will work correctly on a specific release ofLinux.

This BSP and the supporting tools have been tested with the Fedora 9 and 10 and Ubuntu

Linux releases. Although other releases may work fine, they are currently untested.

In some cases, default Linux distributions may lack all the necessary packages to buildLinux. When installing or building your system, examine the error messages closely they usually indicate if the error occurred due to a missing package. If this type of erroroccurs, add the missing package usingyumor the software manager and try the buildagain.


6/18



6

1.3.2 Target board requirements

The LH7A40x Linux port supports the following boards.

1.3.2.1Logic PD LPD7A404 and LPF7A400 boardsThe Logic PD LH7A404 board has been tested with the Linux port.

The boards include a bootloader called Lolo that sets up the target hardware prior to theLinux bootloader. Lolo is used to initially setup the board and then boot into Apex. Moreinformation about Lolo is included with the documentation that comes with the Logic PDboards or can be downloaded from Logic PDs website.

1.4 About this document

The intended use of this document is to provide initial help in developing a Linuxoperating system for the Lh7A40x MCU. The steps required to download the BSP all the

way to deploying Linux to the Logic PD LPD7A404 board are covered.

This document is broken into the following sections:BSP overview

Getting the BSPWhere to get the patches, toolchain, and LTIB

Building your Linux systemUsing LTIB to configure and build Linux, Linux kernel configuration

Linux deployment methodsNFS deployment, SDMMC (EXT2) card deployment, MTD (JFFS2) deployment

Additional information

Other resources, links, and other information


7/18



7

2 BSP overviewThis section gives a brief overview of the BSP contents, features, and supported

peripherals. This BSP has been developed to support Linux kernel 2.6.29.6.

The term BSP refers to the files specific to the LH7A40x Linux port. These include thekernel and u-boot patch file(s), pre-built GCC toolchain, and necessary LTIB files tobuild a Linux distribution. Note that most of the drivers and architecture files for theLH7A40x SoC are part of the Linux mainline.

Developers are welcome to use their own toolchains or develop a Linux system withoutusing LTIB.

2.1 Supported hardware

This BSP supports the NXP LH7A40x SoC and most of its built-in peripherals. Severalexternal peripherals that may be required to use optional interfaces are also supported.

2.2 BSP information

2.2.1 LTIB integration

LTIB (Linux Image Target Builder) provides a convenient method to build thebootloader, kernel image, and root filesystem and then deploy them to your target. LTIBprovides an environment that allows easy setup, configuration, and build of the bootloader, Linux kernel, deployment methods, build tools, etc. If LTIB is used to develop acomplete Linux system, the work of downloading and installing packages, building the

root filesystem, and an assortment of other tasks is greatly simplified.

2.2.2 Apex 1.6.8

The LPD7A40x Linux kernel requires the Apex bootloader to load and boot the kernel.Apex is built as a part of the LTIB build procedure.

2.2.2.1Apex-1.6.8 for LPD7A40x boards

Apex initializes most of the peripherals on the LPD7A404 board, but relies on an externalbootloader to setup memory. The LPD7A404 board come pre-installed with a bootloadercalled Lolo that provides low level board and memory initialization. Lolo can be

configured to automatically load and run a program after board initialization is complete.

The LPD7A40x version of Apex provides the following features:Persistent configuration of Apex and boot parametersKernel image boot from NOR FLASH or EthernetEthernet network configuration


8/18



8

2.2.3 Linux 2.6.29.6

This section describes the system and driver support included with the LH7A40x Linux2.6.29.6 BSP.

2.2.3.1LH7A40x architecture support

The following LH7A40x peripherals are supported as part of the core systemarchitecture:

Timer (system tick)Interrupt controllerDMA

2.2.3.2LH7A40x driver support

The following Linux drivers are provided as part of the BSP:Color LCD controller (AMBA CLCD driver)

Touchscreen controllerUARTs (up to 3)AC97 audio playbackUSB hostUSB gadget

2.2.3.2.1LPD7A404 board driver support

The following additional support is provided for the LPD7A404 board:Ethernet controllerCompact FLASH (IDE) support


9/18



9

3 Building your Linux system

This section explains how to configure and build a Linux system for the Logic PDLPD7A404 board using LTIB. Deployment of the root filesystem will be handled viaNFS.

3.1 Downloading and installing LTIB

LTIB needs to be downloaded and installed on the Linux host machine. To start thisprocess, go tohttp://www.bitshrine.org/ and follow the instructions there to downloadand install LTIB. It is highly recommended to use the netinstall script to install LTIB oruse a direct CVS download (explained in the LTIB FAQ). Using a fixed snapshot imagemay not get you the latest files.

Installation of LTIB should be followed as per the instructions on thewww.bitshrine.orgwebsite. The LH7A40x BSP will be automatically downloaded and installedafter theLTIB packages have been installed from the web and the Logic PD LPD7A404 board hasbeen selected in the LTIB platform selection menu. The LTIB installation package cantake a few hours or more to install. Per the LTIB instructions, make sure you performyour build with a user account do not use root!

After installation is complete, a screen will appear that will allow you to select aplatform. Select the NXP LH7A404 on the Logic PD LPF7A404 board platform andsave the configuration. You will then be passed to the LTIB configuration menu.

3.2 Configuring LTIB

3.2.1 First time running LTIB

If this is the first time you are running LTIB, a default configuration will be provided foryou that will setup the pre-built toolchain, build Apex, build a kernel image, and setup aroot filesystem. A pre-selected Linux kernel configuration is also provided with most ofthe supported interfaces selected for the LH7A40x and the LPD7A404 board. A pre-selected set of packages has also been made for your root filesystem image. One of thepre-selected packages isbusybox, which will provide most of the basic system commandline functions and the console shell.Busyboxis also preconfigured as part of LPD7A404port of LTIB. Deployment options have also been setup, with NFS being the default root

filesystem mount setup.

Although each LTIB configuration items is explained here, it is recommended that thedefault selections and configurations be tried for the first build to verify that everything isworking. This is the fastest way to verify that your host system is correctly configuredand that you target board is working properly. For now, just exit the menu and save theconfiguration. Once you exit the menu, the build process will start.


10/18



10

The next time you LTIB, the LTIB configuration menu will not show up and the buildprocess will start again with the previously saved options. You can show the menu again

with the LTIB config option.3.2.2 LTIB options

The LTIB configuration menu allows some customization over how your Linux system isbuilt. The options are broken into the following categories toolchain, bootloader,kernel, package list, system configuration, and deployment. Specific options for eachcategory are selected from the LTIB menus. A general overview of each section isprovided.

3.2.2.1Toolchain selection and setup

You can either select a pre-built toolchain or setup your own toolchain with LTIB.

Start by selecting the Target C library type). Selecting it will enter into a submenu thatwill allow choices between GLIBC and UCLIBC. Y our choice of a pre-built toolchain istailored by this option. Currently, only GCC 4.3.2 with GLIBC 2.7 is supported as a pre-built toolchain option.

If you select GLIBC as the C library, you have an option of selecting a toolchain ofGCC-4.3.2-glibc-2.7 or custom. If you select the custom option, you will need toprovide your own toolchain as well as the toolchain path, toolchain prefix, and toolchainbuild options.

3.2.2.2Bootloader selection and optionsWith the bootloader choice option, you can select either the u-boot bootloader ornone. If you select none, the bootloader and its patches will not be downloaded andbuilt.

3.2.2.3Kernel build options

You can choose which kernel (version and board) in the kernel section of the menu.Selecting the Configure the kernel option will bring up the kernel configuration menubefore the kernel starts building. If the Leave the kernel sources after building optionisnt selected and the Linux source tree hasnt been built yet, the Linux source tree willbe erased after the Linux kernel has been built.

3.2.2.4Package list

This submenu allows you to select the packages you want in your Linux system. Someoptions are important for building a root filesystem. A few select packages have beenpre-selected including busybox and the device nodes. It is possible that the somepackages may not compile with the ARM architecture.


11/18



11

3.2.2.5Target system configuration

This submenu allows customization of the kernel startup. You can set up kernel optionssuch as networking addresses, custom startup, or start services. Depending on which

packages you install, the menu may change to provide additional options for selectedpackages.

3.2.2.6Target image generation

This submenu allows further customization of the target image. You can specify theimage type to build (such as JFFS2, compressed EXT2, or a flat NFS tree) and specify ifthe target filesystem is read-only. Regardless of which image type you choose, a flatimage suitable for NFS will be located in the ./rootfs directory.

3.2.3 LTIB build cycle

After all the LTIB options are selected and you exit LTIB (and save the configuration),

the LTIB build cycle will start. The build cycle downloads and builds any packagesenabled in the LTIB configuration and then generates the target root filesystem image.LTIB will only build packages that have changed since the last build (generally).

A shortened build cycle is similar to this:Download and install toolchain (if not using custom toolchain)Download, build, and install support packagesBuild root filesystem skeletonMove target libraries to root filesystemDownload u-boot and patches and build it move u-boot to root filesystemDownload Linux kernel and patches and build it move kernel to root filesystem

Download needed target packages and build them move to root filesystemSetup kernel boot configurationBuld root filesystem image (ie, J FFS2)

The generated root filesystem area is in your LTIB directory under ./rootfs. You canusually NFS mount this directory. The apex.bin (bootloader image) and zImage (kernelimage) files are located in boot directory of the root filesystem.

3.2.4 Re-building the system

To rebuild the system, invokeltibagain. Note that some options on the LTIBconfiguration menu may need to be selected to force builds of some components (such as

the Linux kernel). The LTIB configuration menu can be shown with the config option.

3.2.5 More on LTIB

Go tohttp://www.bitshrine.org/ for more detailed information on the use of LTIB.


12/18



12

4 Linux deployment methods

One the Apex bootloader, the Linux kernel, and root filesystem are built as explained inSection 3, the images can be deployed to the board. This section explains how to get theLinux running on the board once the Linux system images are built.

On powerup or reset, the LPD7A40x boards loads and start Lolo, the built-in bootloaderincluded on the board. Lolo will need to be configured to boot Apex either from thenetwork via TFTP, NOR FLASH, or from the CF card.

Once Apex has booted, Apex needs to be configured to load and boot the Linux kernelfrom the network via TFTP or NOR FLASH. The command line for Linux also needs tobe setup prior to booting Linux. Apex will then boot the kernel.

Once the kernel is up and running, the root filesystem is mounted. The filesystem can bemounted from RAM, a Compact Flash card, or over the network using NFS.

4.1 Load and install Apex on the board

Before the Linux kernel can be booted, the Apex bootloader needs to be installed on thetarget board.

Development boards from Logic PD ship with the Lolo bootloader already installed. Lolomay be used to load APEX from a tftp server, from a CompactFlash card or viaTeraTermPro running on a Windows host. Note Apex doesnt replace Lolo, but loads and

runs from Lolo.

Once Apex is installed and running, the first UART port on the board is used to executeApex commands. This port needs to be configured for 115.2K-8N1 operation.

APEX Boot Loader 1.6.8 -- Copyright (c) 2004-2008 Marc Singercompiled for Logic Product Development LPD7A404 on 2009.Oct.22-09:56:19

APEX comes with ABSOLUTELY NO WARRANTY. It is free software andyou are welcome to redistribute it under certain circumstances.For details, refer to the file COPYING in the program source.

apex =>mem:0xc0200000+0x11178 (70008 bytes)env =>nor:256k+64k (no-write)

Use the command 'help help' to get started.

#


13/18



13

4.1.1 Booting Apex from a Compact Flash card

Format a CF card (fdisk and mkfs.msdos) with at least one FAT partition. It doesn't haveto be the first one. (Since CF cards come out of the package with one FAT partition, so

you may not have to do this part.)

Locate the apex.bin file generated with LTIB in the ./ltib/rootfs/boot/ directory. Copyapex.bin to the FAT partition of the CF card. Flush the data to CF card and then eject it.Insert it into the SDK board CompactFlash slot. Reset the SDK board and you should seethe LogicLoader startup message followed by the losh>prompt.

Loading APEX requires a few steps. Mount the CF, load the apex.bin file and execute it.The steps are detailed below:losh> mount fatfs /cflosh> load raw 0xc0200000 0x00030000 /cf/apex.bin

losh>exec 0xc0200000

4.1.2 Booting Apex from a TFT server over the network

Setup the apex.bin file in your TFTP servers file transfer area. Use the steps to transferthe file to the board and start it: Be sure to replace the IP addresses in the steps belowwith your addresses suitable for your network.losh>ipconfig sm0 192.68.1.55losh>load raw 0xc0200000 0x00030000 /tftp/192.168.1.51/zImagelosh>exec 0xc0200000

4.1.3 Booting Apex from a NOR FLASHOnce Apex has been transferred to the board using the network or Compact Flashapproach, the image can be saved in NOR FLASH and booted from there. See the LogicPD board documentation for the latest procedure on how to do this.

Be careful with programming NOR FLASH. You can inadvertently erase the Lolobootloader on the board and the board will no longer boot.

4.2 Booting the Linux kernel

Apex can be used to load and boot the kernel from NOR FLASH, a Compact Flash card,or over the network using TFTP. The basic steps for each procedure are shown in the

following sections.

4.2.1 Kernel command line

Regardless of which approach you use to load and boot the kernel, the Linux commandline passed to the kernel during kernel boot needs to be configured in Apex before thekernel is booted.


14/18



14

Thecmdlineenvironment variable in Apex is used to setup the kernel command lineparameter. The following is an example of how it is setup in Apex.

apex>setenv cmdline console=ttyAM1,115200n81 rw root=/dev/hdc1 ip=dhcp

For most setups, the default initial console will be on ttyAM1, but the mount point for theroot filesystem may be located on an EXT2 partition of the Compact Flash card or overthe network using NFS.

4.2.2 Automating Apex boot

Apex can be setup to automatically load and start the kernel with thestartupenvironmentvariable. The example below will setup Apex to load and boot the kernel image over anetwork using TFTP and then start it with the command line in thecmdlineenvironmentvariable.

apex>setenv startup ipconfig 192.168.1.55; copy tftp://192.168.1.51/zImage0xc0010000; boot -g 0xc0010000

4.2.3 NFS mounted root filesystem

The LTIB filesystem image is location in the ./ltib/rootfs directory. If you are going touse NFS for mounting your root filesystem, you can setup your Linux command line touse the root filesystem area as follows. Be sure to change the IP addresses and paths tosuitable values for your environment.

setenv cmdline console=ttyAM1,115200n81 rw root=/dev/nfsnfsroot=192.168.1.51:/home/usb10132/ltib/rootfs ip=dhcp

4.2.4 EXT2 mounted root filesystem

You can also partition a CF card with an EXT2 partition and install the root files there.The following Linux command line shows an example of how to use the Compact Flashcard (first partition) for the root filesystem mount point.

setenv cmdline console=ttyAM1,115200n81 rw root=/dev/hdc1 rootfstype=ext2 ip=dhcp


15/18



15

5 Addit ional information

5.1 Getting the BSP files

5.1.1 Where to get the Linux Apex and kernel patches

A comprehensive patch that contains all the necessary support and updates to the 2.6.29.6kernel can be downloaded from NXPs website.

5.1.2 LTIB and GCC toolchain compatibil ity and dependency issues

LTIB and the pre-built GCC toolchain have been tested on a Fedora Core 9 and 10 andUbuntu Linux systems. Although they should run fine on modern Linux distributions, itis not possible to test it with every Linux distribution and version. Per field and customer

tests, other non-Fedora Linux distributions seem to work fine. Some older versions ofFedora had issues running the pre-built toolchain.

5.1.3 Known issues

The USB gadget driver is not functional. USB host works fine.

5.1.4 TFTP and NFS help

There is a lot of great information on the internet for setting up a tftp sor NFS server. Thegeneral steps required to get them going are explained here.

5.1.4.1Setting up a tftp server

As a general setup procedure, a tftp server is setup by editing the flags and values in the/etc/xinit.d/tftp file. Several import flags are shown below:

disable =noserver_args =-s /tftpboot/

Make sure thedisableflag is set tonoor your tftp service wont be enabled. Also set theserver_argsvalue with the directory where your files are located when a tftp requestoccurs. In this specific setup, the /tftpboot directory is used to store files for the tftpserver. If a tftp client requests a path/file, the path/file needs to be located or linked here .

When the target board powers up, it will request the kernel image file uImage from thehost via tftp if tftp kernel boot is setup on the target. If uImage is not located or linked in/tftpboot, the transfer will fail.

If tftp continues to fail, verify that your tftp service is running on the host machine.


16/18



16

5.1.4.2Setting up an NFS server

As a general setup procedure, the /etc/exports file needs to be edited to add the rootfilesystem directory for NFS. The change will appear similar to the entry below:

192.168.1.* (rw,no_root_squash,no_subtree_check,sync)

After the edits are made, you will need to restart the NFS server (or enable it if it isdisabled).

For example, if LTIB is installed in your home directory. The following entry wouldexport your LTIB root filesystem to IP clients in the range of 192.168.1.*./home/user/ltib/rootfs 192.168.1.* (rw,no_root_squash,no_subtree_check,sync)

5.1.5 ALSA device support

If your kernel image is setup for audio playback, you may need to setup the ALSA device

nodes before ALSA will work correctly. Use the following steps from the kernel shell tosetup the ALSA device nodes.

[root@nxp /]#cat /proc/asound/devices0: [ 0] : control16: [ 0- 0]: digital audio playback33: : timer[root@nxp /]#mkdir /dev/snd[root@nxp /]#cd /dev/snd[root@nxp snd]#mknod controlC0 b 1160[root@nxp snd]#mknod pcmC0D0p b 11616

[root@nxp snd]#Note the device minor numbers for the control and digital audio playback nodes maydiffer on your system. When doing the mknod command, use the numbers that appear onyour system.

5.1.6 Compact Flash (IDE) support

The device node for the Compact FLASH device may not already be statically built in theroot filesystem. If the IDE device doesnt work on your system, do these steps to createthe correct device nodes.

[root@nxp snd]#cat /proc/devicesCharacter devices:1 mem2 pty3 ttyp4 /dev/vc/04 tty5 /dev/tty


17/18



17

5 /dev/console5 /dev/ptmx7 vcs

10 misc13 input14 sound29 fb90 mtd116 alsa128 ptm136 pts180 usb189 usb_device204 ttyAM254 usb_endpoint

Block devices:3 ide0

259 blkext7 loop22 ide131 mtdblock[root@nxp snd]#cd /dev[root@nxp snd]#mknod hdc b 22 0[root@nxp snd]#mknod hdc1 b 22 1[root@nxp snd]#mknod hdc2 b 22 2

5.1.7 Other links

Other related links are shown below.The LH7A400 and LH7A404 Common Driver Library (CDL) can be found athttp://www.standardics.nxp.com/support/documents/microcontrollers/zip/code.package.lh7a400.sdk7a400.zipandhttp://www.standardics.nxp.com/support/documents/microcontrollers/zip/code.package.lh7a404.sdk7a404.zip. These packages provide a generic set of reference drivers, startupcode, and examples for the LPD7A40x Socs and supported boards.

More information about the Logic PD LPD7A40x boards can be found athttp://www.logicpd.com/.

The NXP standard ICs website is a good resource to get Users Manuals, trainingmaterials, or other information. http://www.standardics.nxp.com/

Link to the LTIB project at savannah.org


18/18



18

https://savannah.nongnu.org/projects/ltib

Link to the GPP used for the LTIB package pool

http://www.bitshrine.org/

Lh7a40x.linux.bsp.User.manual

Documents

Transcript of Lh7a40x.linux.bsp.User.manual