Skip to main content

By clicking Submit, you agree to the developerWorks terms of use.

The first time you sign into developerWorks, a profile is created for you. Select information in your profile (name, country/region, and company) is displayed to the public and will accompany any content you post. You may update your IBM account at any time.

All information submitted is secure.

  • Close [x]

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerworks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

By clicking Submit, you agree to the developerWorks terms of use.

All information submitted is secure.

  • Close [x]

Cell/B.E. SDK 3.0, Part 3: Create the Cell/B.E. simulator environment

A quick-read intro to the new Multicore Accelerator SDK 3.0 IDE

Sean Curry (seancurry.ut@gmail.com), Software Engineer, IBM
Sean is an undergraduate student at The University of Texas at Austin, working toward a degree in Computer Sciences. As an intern at the IBM Linux Technology Center, Sean works as part of the Linux on Cell/B.E. team, specifically contributing to the IDE for Cell Broadband Engine SDK project. Sean develops source code and conducts integration testing and product release management.

Summary:  This introductory tutorial, designed for the IBM SDK for Multicore Acceleration, Version 3.0 (otherwise known as the Cell Broadband Engine SDK), explores the Cell/B.E. processor IDE and gives developers a click-for-click walk-through of building a simple project in this environment. This tutorial is broken into six quick-perform parts dealing with creating an SPU project, creating a PPU project, creating the Cell/B.E. simulator, configuring the application launcher, debugging and doing performance analysis, using simulator consoles, using the ALF wizard, and setting IDE preferences.

View more content in this series

Date:  13 Nov 2007
Level:  Introductory PDF:  A4 and Letter (287 KB | 12 pages)Get Adobe® Reader®

Activity:  25827 views
Comments:  

Creating the Cell/B.E. simulator environment

Now that the projects are created and properly configured, you can test the program. But first, you need to create and start a Cell/B.E. environment. The Cell/B.E. IDE integrates IBM's full-system simulator for the Cell/B.E. processor into Eclipse so that you're only a few clicks away from testing your application in a Cell/B.E. environment, even if you don't have access to the physical processor.

In the Cell/B.E. Environments view at the bottom, right-click on Local Cell Simulator, and select Create.


Figure 15. Starting the simulator creation
Starting the simulator creation

Configuring the simulator

You see the Local Cell Simulator properties window, which you can use to configure the simulator to meet any specific needs that you might have. You can modify an existing Cell/B.E. environment's configuration at any time (as long as it's not running) by right-clicking on the environment and selecting Edit.

Enter a name for this simulator, such as My Cell Simulator), and click the Simulator tab.


Figure 16. Simulator configuration
Simulator configuration

Using the simulator tab

On the Simulator tab, check the box Show TCL console, then click Finish.


Starting the simulator

Click the + next to Local Cell Simulator, select the new simulator environment, and click the Start the Environment button (green arrow).

The simulator will now begin to launch (this may take a few minutes). It should look like Figure 17:


Figure 17. Warming up the ole simulator
Warming up the ole simulator

You're done. Next!

3 of 6 | Previous | Next

Comments



static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=Multicore acceleration, Open source
ArticleID=268860
TutorialTitle=Cell/B.E. SDK 3.0, Part 3: Create the Cell/B.E. simulator environment
publish-date=11132007
author1-email=seancurry.ut@gmail.com
author1-email-cc=dwpower@us.ibm.com