ChorusOS 4.0 MPC8260 Target Family Guide

How to Build and Boot a System Image on the Target

For the following procedures, it is assumed that you use the EST Corporation's visionXD tool either to boot the target system or to place the bootMonitor utility in flash memory on the target system. As of the date of publication of this document, the URL for the visionXD tool is:

Building a ChorusOS 4.0 System Image

The following procedure assumes that the ChorusOS 4.0 product has already been correctly installed on the host workstation. See the ChorusOS 4.0 Installation Guide for Solaris Hosts.

  1. Create and change to a build directory where you will build system images:

    $ mkdir build_dir
    $ cd build_dir
  2. Set an environment variable to use with the configure(1CC) command as a shortcut to the base directory.

    For example:

    Set the environment variable... 

    To the family-specific product directory. The default value is... 



  3. Make sure your PATH has been set correctly to include the directory install_dir/4.0/chorus-mpc8260/tools/host/bin, where the default install_dir is /opt/SUNWconn/SEW. Also make sure that your PATH includes /usr/openwin/bin, which contains the imake utility.

  4. Configure the build directory, using the configure(1CC) command:

    If you are building from a binary distribution:

    $ configure -b $DIR/kernel \ 
    $DIR/os \ 
    $DIR/tools \ 
    -s $DIR/src/nucleus/bsp/drv \ 
    $DIR/src/nucleus/bsp/powerpc \ 
    $DIR/src/nucleus/bsp/powerpc/mpc8260ADS \ 

    Note -

    The above command configures the build directory to include components installed during a "Default Install". It does not include optional components, such as the X library or code examples, that you may choose to install separately on Solaris host workstations. For example, in order to include everything in your build environment:

    $ configure -b $DIR/kernel \ 
    $DIR/os \ 
    $DIR/opt/X11 \ 
    $DIR/tools \ 
    -s $DIR/src/nucleus/bsp/drv \ 
    $DIR/src/nucleus/bsp/powerpc \ 
    $DIR/src/nucleus/bsp/powerpc/mpc8260ADS \ 
    $DIR/src/iom \ 

    If you are building from the source distribution, see the ChorusOS 4.0 Production Guide.

    As a result of configuration, build_dir now contains a Makefile, which is used to generate the build environment, and a Paths file, which specifies paths to files required by and created in the build environment.

  5. Generate the build environment:

    $ make
  6. Build a system image:

    $ make chorus

    The resulting system image file is located in the build directory, build_dir and is called chorus.RAM.

    Note -

    You can also make a smaller system image that includes only the operating system kernel:

    $ make kernonly

Setting Up the visionXD and visionICE Tools

See the visionXD and visionICE documentation for detailed installation instructions.

  1. Connect visionICE to the target system, plugging the transceiver into the MII connector and switching the transceiver to UP.

  2. Connect the target system to the network.

  3. Connect and configure visionICE and visionNET.

  4. Install the visionXD tool on the host workstation.

  5. Select Configure Global Settings... from the Tasks menu, and use the dialog box displayed to configure the connection to the target system.

How to Boot the Target System Using EST Corporation's visionXD Tool

Booting with the visionXD Tool
  1. Start the visionXD tool.

  2. Select Connect from the Target menu to connect the visionXD tool to the target system.

  3. Click the terminal button to display a terminal window with the >BKM> prompt.

  4. Enter in at the >BKM> prompt to set initialization values for the target system registers:

    >BKM> in  
  5. Select Load Executable... from the File menu.

  6. Select the chorus.RAM system image and click Load.

  7. After the target system has finished downloading the system image, click the Run button.

How to Boot the Target System from Flash Memory Using bootMonitor

In order to boot the target from flash memory you must perform the following procedures.

Placing the System Image on the Boot Server

See the ChorusOS 4.0 Installation Guide for Solaris Hosts for instructions on how to configure the boot server.

  1. Copy the system image to the boot server.

    For example, on a Solaris host workstation:

    $ rcp chorus.RAM boot_server:/tftpboot
  2. Verify that everyone has at least read access to the system image on the boot server.

    For example:

    $ rlogin boot_server
    Password: password_for_user
    $ ls -l /tftpboot/chorus.RAM
    -rwxr-xr-x   1 user    group     1613824 Dec 15 17:33 chorus.RAM*
  3. (Optional) While logged in to the boot server, create a configuration file for the target.

    For a target system with IP address using a boot server with IP address, the configuration file contains the following:


    The configuration file is named /tftpboot/819DADC7.ChorusOS.4.0, which is constructed from the target system IP address as a concatenation of the following:

    • 129 in decimal translates to 81 in hexadecimal

    • 157 in decimal translates to 9D in hexadecimal

    • 173 in decimal translates to AD in hexadecimal

    • 199 in decimal translates to C7 in hexadecimal

    • (optional) .ChorusOS.4.0 identifies the release, and is appended to the concatenation of the IP address expressed in hexadecimal.

    Note -

    The system first attempts to find the configuration file with the .ChorusOS.4.0 extension. If it fails to find one, however, it attempts to find a configuration file without the .ChorusOS.4.0 extension.

Creating a bootMonitor Image

See bootMonitor(1CC) for details about how bootMonitor works.

  1. Create a build directory where you will build a bootMonitor image:

    $ mkdir bootmon
    $ cd bootmon

    Note that this build directory is different from the directory where you build system images.

  2. Configure the bootMonitor build directory based on the binary distribution:

    $ configure -b $DIR/kernel \ 
    $DIR/os \ 
    $DIR/tools \ 
    -s $DIR/src/nucleus/bsp/drv \ 
    $DIR/src/nucleus/bsp/powerpc \ 
    $DIR/src/nucleus/bsp/powerpc/mcp8260ADS \ 
  3. Generate the build environment:

    $ make
  4. Edit the special bootmon/conf/mini profile so that it reads:

    #	Mini Profile
    #	Kernel features
    -set USER_MODE=false
    -set SEM=false
    -set EVENT=false
    -set MONITOR=false
    -set TIMER=false
    -set DATE=false
    -set RTC=false
    -set PERF=false
    -set IPC=false
    -set MIPC=false
    -set LAPBIND=true # Change this from 'false' to 'true'
    -set LAPSAFE=true # Change this from 'false' to 'true'
    -set MON=false
    -set LOG=false
  5. Configure the build environment for bootMonitor:

    $ configurator -p conf/mini
    $ configurator -set BOOT_MODE=ROM
    $ configurator -set ETHER_ADDR=xx:xx:xx:xx:xx:xx

    As you enter the commands above, replace xx:xx:xx:xx:xx:xx with the target system Ethernet address.

  6. Build a bootMonitor image:

    $ make bootMonitor

    The resulting system image file is located in the build directory, bootmon and is called bootMonitor.ROM.

Flashing the Target System with the bootMonitor Image
  1. Start the visionXD tool.

  2. Click the terminal button to display a terminal window with the >BKM> prompt.

  3. Enter in at the >BKM> prompt to set initialization values for the target system registers.

    >BKM> in  
  4. Enter cs at the >BKM> prompt to check that the SDRAM configuration as coded in the trampoline.s source file used to build the bootMonitor image corresponds to the initialization values set using the in command.

    >BKM> cs  
  5. Select Program Flash... from the Tasks menu.

    The Flash Programmer window is displayed. Use the information in the table below to fill in the necessary fields in the window.

    Figure 1-1 Configuring the Flash Programmer


    Click the Erase and Program button to write the bootMonitor image to flash.

  6. Click Extract in the dialog box that is displayed.

  7. Click OK to confirm the download into flash memory.

Booting the Target System

    Restart the target system to boot from flash.