IBM®
Skip to main content
    United States change      Terms of use
 
 
Select a scope:    
     Home      Products      Services & industry solutions      Support & downloads      My account     
alphaWorks  >  Research topics  >  Cell Broadband Engine technology  >  

New to Cell Broadband Engine technology


1. Where can I find more information?


1. What Linux distribution is supported by the Cell BE SDK?

RedHat Fedora Core 4.
Back to top Back to top

1. Where can I find more information?

Back to top Back to top

2. Does this SDK run on Linux distributions other than Fedora 4, such as Red Hat, SUSE and Debian?

It may work on other Linux distributions, but it is tested and certified to run in Fedora Core 4 only.
Back to top Back to top

3. What are the minimal and recommended system requirements (such as computer, CPU speed, memory, and disk space) for using this SDK on an x86-based machine?

Operating systems: RedHat Fedora Core 4
Computer: 2 GHz x86 machine; the faster system, the better.
Hard disk space: 5 GB (minimum) for installing the source package and the accompanying development tools
RAM: 1 GB (minimum) on the host system (less if not using XL C)
Back to top Back to top

4. What is the directory structure?

  • cbe_linux: Contains the source code and build rules for
    • Linux kernel (Version 2.6.14) (vmlinux required by systemsim)
    • libspe (required by SDK examples)
  • ramdisk: Contains the rules needed for building a sysroot_disk. A sysroot_disk is a ramdisk that is needed by the simulator. It is built from RPMs (located in /opt/PPC-FC4/rpms), environment-specific config files found in ramdisk/custom, and SDK example programs found in sysroot.
  • src: The directory for samples and library source code. See the README.txt file in the src directory for further information.
  • systemsim-cell-release: The simulator.
  • docs
Back to top Back to top

5. Are there any RPM packages required that may not be in a typical Fedora Core 4 installation?

Yes. The IBM System Simulator requires libtk8.4.so. You will see the following message when you run the simulator if this package is not installed on your system:
    systemsim-cell-release/run/cell/../../bin/systemsim-cell: error while loading shared libraries: libtk8.4.so: cannot open shared object file: No such file or directory.
In order to get that package, you must do a "yum install tk".
Back to top Back to top

6. What is XL C?

XL C is a C-language compiler supplied by IBM. The version shipped with the Cell BE SDK is compiled to run on Fedora Core 4.

Source code for the compiler is not available.

Back to top Back to top

7. What is systemsim?

systemsim is a Cell BE simulator that emulates the behavior of a Cell BE system. The version shipped with the Cell BE SDK is compiled to run on Fedora Core 4. See the docs subdirectory for complete documentation. Internally within IBM, the simulator is known as mambo. This name may appear in some of the documentation.

Source code for the simulator is not available.

Back to top Back to top

8. How do I transfer files to the simulator?

From within the simulation environment, you would use the callthru utility. This program is located in /usr/bin.

Usage: callthru [exit|sink|source] ...

Examples:

  • callthru source /tmp/foobar>foobar
    This command copies /tmp/foobar from the hosting file system into the current working directory in the simulation environment.
    If foobar is an executable, you should use "chmod +x foobar" prior to running it.
  • callthru sink /tmp/foobar This command copies foobar, the current working directory in the simulation environment, to /tmp/foobar from the hosting file system.
Back to top Back to top

9. What should I do if mkfs fails?

First, try to do a "yum update selinux-policy-targeted".

If that doesn't work, please change your selinux policy from enforcing to permissive. Edit /etc/selinux/config; then press /.autorelabel and reboot. This failure happens on some systems but not others. The exact source of the problem is unknown at this time. The problem is not related to the CBE SDK; any attempt to do a dd/mkfs fails.

Back to top Back to top

10. What packages are necessary in order to run the Cell BE SDK?

  • Installation script: install.sh
  • Kernel patch: cell-linux-patches-1.0.tar.bz2
  • GCC and tools: toolchain-2.3-i686.tar.bz2
  • Simulation environment:
      ppc-fc4-rpms-1.0.0-1.i386.rpm
      systemsim-cell-1.0-fc4-x86.tar.bz2
  • SPE management library source code: libspe-1.0.tar.bz2
  • XL C Compiler:
      xlc-cell-cmp-1.0-1.i386.rpm
      xlc-cell-lib-1.0-1.i386.rpm
  • Sample/library source code: cell-sdk-lib-samples-1.0.tar.bz2
You must put all these packages into the same directory and run the install.sh script.
Back to top Back to top

11. What is the hosting environment for these packages?

Fedora 4 on x86
Back to top Back to top

12. Where can I find the documentation?

The Cell BE architecture-related and software-related documentation on the developerWorks Web site includes all architecture books, as well as all different ABIs and language specifications.

The Cell BE development tool-related documentation (Simulator, XL C, GCC, binutil) is located in the individual packages.

All Cell BE sample/library-related documentation (library, libspe, IDL, README.txt files) can be found in the downloaded SDK package under docs/.

Back to top Back to top

13. Why do you have both XL C and GCC compilers?

GCC is an open-source compiler. XL C Compiler is a prototype based on IBM's world-class compilation technology for Power Architecture™ providing the same advantages for CBEA processors. It supports a subset of GCC extensions and provides industry-leading optimizations that maximize application performance through inter-procedural optimization, auto SIMDization, etc.
Back to top Back to top

14. How do I switch between the XL C and GCC compilers when building the samples and libraries?

In the build environment provided through the library/sample/workload package, you can edit the make.env file and change theSPU_COMPILER and PPU32_COMPILER to "sce" for the SCE GCC compiler or "xlc" for the IBM XL C Compiler.
Back to top Back to top

15. Must I be a root while I install the SDK components?

The first time you run the install.sh script, you must be root so that the RPM packages will get installed. In fact, anytime you are going to re-install or update one of the RPM packages, you must be root. Subsequent installations will detect the presence of packages that must be installed as root and prompt you to re-install. If you are not root, then select No on every package, and the installation and building process will continue.
Back to top Back to top

16. The script failed when creating the sysroot ramdisk. What happened?

You must change your selinux default to "permissive" and re-label your files. Take the following steps:
  1. Edit /etc/selinux/config, changing your policy from "enforcing" to "permissive."
  2. Press /.autorelabel.
  3. Reboot.
Back to top Back to top

17. What is the first thing to do if a sample is compiled successfully but does not run?

The README.txt file in the directory of the sample source code usually provides instructions for running the sample. A sample may need an input data file in order to run properly.
Back to top Back to top

18. Where can I obtain information about the actual hardware?

The Cell microprocessor services page provides information about the hardware.
Back to top Back to top

19. Can I run the samples, workloads, or applications develped by this Cell BE SDK on the real hardware?

Yes; all the test programs, samples, and workloads, except the two programs Oscillator and vse_subdiv, have been tested on real Cell BE hardware. Oscillator and vse_subdiv need special simulator support and, therefore, cannot run directly on a hardware system. The new applications developed by this cross-development environment will be able to run on real Cell BE hardware.
Back to top Back to top

20. What if I have a question about the Cell BE SDK?

You can post questions on the Cell BE forum on IBM developerWorks. The Cell BE programming community uses it for exchanging information.
Back to top Back to top

21. I get syntax errors during the build because of missing /usr/local/GL files.

The Cell BE SDK requires
  • freeglut-devel-2.2.0-16
  • xorg-x11-devel-6.8.2-37.FC4.45

In order to pick up these packages, do the following:

    "yum install freeglut-devel"
    "yum install xorg-x11-devel"
Back to top Back to top
Learning resources
developerWorks Cell Broadband Engine forums Cell Broadband Engine at IBM Research
Cell Broadband Engine architecture IBM Semiconductor Solutions: Cell Broadband Engine documentation
Linux on Cell Broadband Engine-based Sxystems: Barcelona Supercomputing Center Power.org
IBM Journal of Research and Development
Topic feedback
Spotlight

developerWorks Cell Broadband Engine resource center

Cell BE forum


Top downloads

IBM Full-System Simulator for the Cell Broadband Engine Processor

IBM Assembly Visualizer for Cell Broadband Engine

Interactive Ray Tracer for Cell Broadband Engine

IBM Dynamic Application Virtualization


alphaWorks Newsletter
 Subscribe now
 to receive the latest
 from alphaWorks.
 
New! A programming setting for making parallel apps
Use the community to make your Web pages accessible
Analyze Java heap usage


    About IBM Privacy Contact