Package-based Build System for Blackfin Asterisk. Key differences compared to buildroot based systems like Astfin and uCasterisk:

• End users do not need to compile any software, they just install them on a running Blackfin system, for example:

    root:~> ipkg install asterisk
  

  will grab the latest Asterisk package from a web site and install it on a Blackfin based hardware platform. Use is not limited to Asterisk, it could be used to manage any Blackfin software, including the kernel. The use of ipkg is very common on the OpenWRT project, and similar package based systems are common on x86 Linux, e.g. apt-get, debs, rpms.

  Note that software is installed at run time rather than build time. Packages (via ipkg) are used to install applications like Asterisk, rather than placing everything in a uImage. The target hardware is initially booted with a basic kernel and root file system, then packages are installed as required. We assume availability of persistent (non ram) based file system like yaffs or jffs2.

  The goal is to make installing software on the Blackfin much easier for end-users, more like an x86 experience.

• Compared to buildroot systems BAPS has a flat directory structure to ease development (less wear on your tab key). It is designed to allow modular compilation of packages, e.g. you can compile a single application without building the entire uImage. Faster and less output to wade through. Makefiles (e.g. asterisk.mk) and source (e.g. asterisk-1.4.4) are within one directory level of each other for easy navigation of the source tree. There is less chance of breaking the build system due to decoupling of modules (kernel, root fs, are separate from Asterisk).

In addition to an IP08/IP04/IP01 uImage (kernel plus basic root filesystem) there is a growing list of packages:

The installation of the BAPs uImage is still a little complex (apologies). It requires working with u-boot using the RS-232 console interface. For more information on this process please see the IP04 Wiki or please post to the Blackfin Asterisk forum.

However once the uImage is installed life gets much easier!

This process will erase your IP04 root file system so please backup anything you really need (like your asterisk conf files).

1. Get the baseline BAPs uImage (contains kernel and basic root file system) and place it on your tftp server:

    http://www.rowetel.com/ucasterisk/downloads/uImage_r4.ip08
   

   NOTE: Despite it's name, uImage_r4.ip08 works fine on both the IP04 and IP08.

2. Connect an RS-232 cable to your IP04 (via the daughter board) and stop the boot process at the u-boot prompt. Now we are going to write the new uImage to flash. You only need to configure ethaddr1 if you have two ethernet interfaces.

CAUTION: Do not cut/paste the steps below into your serial terminal program, as they often cannot respond fast enough and lose characters. Type each line carefully by hand.

Install the new uImage into NAND flash using u-boot:

    ip04>set autostart
    ip04>set serverip your.tftp.server
    ip04>tftp 0x1000000 uImage_r2.ip08
    ip04>nand erase clean
    ip04>nand erase
    ip04>nand write 0x1000000 0x0 0x300000
    ip04>set bootargs ethaddr=$(ethaddr) ethaddr1=$(ethaddr1) $(con) root=/dev/mtdblock0 rw
    ip04>save
    ip04>bootm 0x1000000

(uClinux will boot...)

TIP: If Linux doesn't boot or you experience other problems reboot into uboot, type print, and carefully check bootargs.

3. Now we have uClinux running, but using a ram-based ext2 file system (mtdblock0) for root. So we need to copy /root into the yaffs file system:

   On the IP04:

    root:~> copy_rootfs.sh
    root:~> reboot
   

4. Now set up u-boot to mount root from yaffs (some of these env variables may be set already, use print to check):

    ip04>set autostart yes
    ip04>set bootargs ethaddr=$(ethaddr) ethaddr1=$(ethaddr1) $(con) $(root)
    ip04>set nandboot 'nboot 0x2000000 0x0'
    ip04>set bootcmd run nandboot
    ip04>save
    ip04>reset
   

5. Boot IP04 to a uClinux root prompt. Use mount to check that root is mounted on mtdblock2 (yaffs file system).

   Now we can install some packages using ipkg:

    $root:~> ipkg update
    $root:~> ipkg install zaptel-spi asterisk native-sounds
    $root:~> reboot
   

After installation many packages include documentation in the /usr/doc directory of the IP04. These are small files designed to capture Blackfin or IP04 specific information, for example simple tests and notes on differences from other versions of the same package. The documentation files can also be browsed from BAPS2 git.

1. Clone BAPS2:

    $ git clone git://github.com/jlduran/BAPS2.git
    $ cd BAPS2
   

2. You need to install the toolchain and uClibc:

    [BAPS2]$ wget http://download.analog.com/27516/frsrelease/5/0/8/5087/blackfin-toolchain-08r1.5-14.i386.tar.bz2
    [BAPS2]$ tar xjf blackfin-toolchain-08r1.5-14.i386.tar.bz2
    [BAPS2]$ wget http://download.analog.com/27516/frsrelease/5/0/7/5075/blackfin-toolchain-uclibc-default-08r1.5-14.i386.tar.bz2
    [BAPS2]$ tar xjf blackfin-toolchain-uclibc-default-08r1.5-14.i386.tar.bz2
   

   If you untar the toolchain and uClibc in the BAPS2 directory, it will be included in your path automatically. If you untar it somewhere else make sure the bin directories in this toolchain are in your path.

3. Make a BAPS2 uImage that supports ipkg. This also configures uClinux-dist to support compiling of other packages. You need to make uClinux before making any other packages.

    [BAPS2]$ make -f uClinux.mk uClinux
    [BAPS2]$ cp uClinux-dist/images/uImage /tftpboot/uImage
   

   You can then try booting from your uImage via tftp, in u-boot:

    ip04>set autostart
    ip04>set bootargs ethaddr=your:mac:address root=/dev/mtdblock0 rw
    ip04>save
    ip04>tftp 0x1000000 uImage
    ip04>bootm
   

   Or you can flash the uImage as described in the Getting Started section above.

4. Check out ipkg.conf:

    root:~> cat /etc/ipkg.conf
    src snapshots http://rowetel.com/ucasterisk/ipkg
    dest root /
   

   Try installing a simple ipkgs:

    root:~> ipkg update
    root:~> ipkg list
    root:~> ipkg install hello
    root:~> hello
   

5. BAPS uses init.d type start up scripts, for example:

    root:~> ls /etc/init.d
    root:~> /etc/init.d/hello
    root:~> /etc/init.d/hello enable
    root:~> ls -l /etc/rc.d/
   

To build the ipkg:

[BAPS2]$ make -f hello.mk hello
[BAPS2]$ make -f hello.mk hello-package
[BAPS2]$ ls ipkg

To create an index file:

[BAPS2]$ cd ipkg
[BAPS2]$ ../scripts/ipkg-make-index.sh . > Packages
[BAPS2]$ scp Packages /your/web/server

Then change the first line in /etc/ipkg.conf on your IP04:

src snapshots http://you.web.server

And try:

root:~> ipkg update
root:~> ipkg list

1. If you change the post or pre inst scripts, it is a good idea to rm the existing $(TARGET_DIR) (see Makefile for your package), as the package make scripts don't seem to recognise when post/pre scripts have been changed.

2. To debug post/pre inst scripts #!/bin/sh -x is your friend!

3. To test ipkgs you can rcp down to the target:

    [host]$ rcp ipkg/asterisk_1.4.4-1_bfin.ipk root@ip04:/root
    [ip04]$ ipkg install asterisk_1.4.4-1_bfin.ipk
   

   If you get complaints about MD5 mismatch, then:

    [ip04]$ rm /usr/lib/ipkg/lists/snapshots
   

Say you have changed a busybox option, or modified some files in uClinux-dist. To capture the changes to patches in git:

[BAPS2]$ make -f uClinux.mk uClinux-ip04-make-patch
[BAPS2]$ git status

Tips:

To change linux kernel options:

[BAPS2]$ cd uClinux-dist
[uClinux-dist]$ make linux_menuconfig

To change user application and library settings:

[BAPS2]$ cd uClinux-dist
[uClinux-dist]$ make config_menuconfig

To modify the IP04 rc, motd etc:

[BAPS2]$ cd uClinux-dist/vendors/Rowetel/IP04

Then capture changes as above with:

[BAPS2]$ make -f uClinux.mk uClinux-ip04-make-patch

1. Patch files are compatible with Astfin, so hopefully it's possible to move patches back and forth between BAPS2 and Astfin.

2. See TODO.txt

3. To debug init shell scripts, e.g. files/hello.init, add a -x to the first line if the script using vi on the IP04:

    #!/bin/sh -x
   

4. When writing init scripts your will find the busybox msh shell has some quirks, here is a link that explains them:

    http://dslinux.org/cgi-bin/moin.cgi/DSLinuxMshScriptingGuide?action=show&redirect=DSLinux+msh+scripting+guide
   

5. For more information on the IPKG format:

    http://handhelds.org/moin/moin.cgi/Ipkg
   

6. On the target, the ipkg data is stored in /usr/lib/ipkg/info/

ipkg - completed packages are placed here

include - from OpenWRT kamikaze, contains useful stuff for building packages

scripts - useful scripts from OpenWRT kamikaze

patch - patches for all packages

files - start up scripts for packages, get copied to /etc/init.d on target

Thanks to: Jeff Knighton, Alex Tao, Ming C (Vincent) Li, Mike Taht, Keith Huang, Mark Hindess, Nick Basil, Michael O'Conner, Darryl Ross, Jose Luis Duran and Kelvin Chua for contributing.

Some tasks that need doing:

• Work out a way to install uImage.ip08 without u-boot, i.e. from a uClinux root prompt. This will take much of the pain away, kernels can then be treated like packages.
• Can we install kernels (uImage) using a package and no u-boot/RS-232?
• Should we separate kernel from baseline root file system install?
• BAPS uImages for BF537
• A way to build all packages needed for development, like ip08.mk, or maybe set up dependencies in existing Makefile, e.g. so that libssl.mk is called when making asterisk. Not sure about the best way to go here – the idea behind BAPs is to modularise compilation so I am sensitive to having many dependencies and all the extra output that would generate on the command line.
• Fix the Maintainer Field in packages (e.g. specific entries for each package).