Intel IQ80333 manual Configuration

Page 58

Intel® IQ80333 I/O Processor

Getting Started and Debugger

B.3.2

Configuration

 

 

 

 

 

 

 

Examine the main menu of CodeLab EDE for .NET.

 

 

 

 

File

Project

codelab EDE

Tools

Help

 

Edit

View

Build, Debug

Window

 

Since CodeLab is a plug-in to Visual Studio, some of these menu items are Visual Studio and some are specific to CodeLab. Click on any of these menu items and the drop-down menu displays the subordinate menu items. Many of these items have defined tool bar symbols, function keys, and keyboard patterns as alternatives.

Note: Projects can be built under the “codelab EDE” menu or under the “build” menu. Always use the “codelab EDE” menu to perform CodeLab project builds. Builds under the “build” menu invoke the Visual Studio C compiler.

1.On the main menu, select “codelab EDE, Configuration”.

2.When the “codelab EDE Configuration” window appears, click on each of the words in the left box. Notice that the rest of the window changes when you click on different parts of the menu tree. This is a typical feature of CodeLab EDE for .NET.

3.Click on Toolsets.

4.Click on the drop-down arrow and select “RedHat GNU Tools for XScale”. The build tool paths now appear in the box and must be modified as stated below in bold. Note that the assembler and the linker are invoked by GCC.

a.“Compiler path: $(ToolDir)\BIN\XSCALE-ELF-GCC.EXE”.

b.“Assembler path: $(ToolDir)\BIN\XSCALE-ELF-GCC.EXE”.

c.“Linker path: $(ToolDir)\BIN\XSCALE-ELF-GCC.EXE”.

d.“Librarian path: $(ToolDir)\BIN\XSCALE-ELF-AR.EXE”.

5.In the left box, click on “Debugging, General”. When the checkboxes are available in your version, set all four debug options to “false”.

6.Click “Apply” and click “OK”.

7.On the main menu, click “codelab EDE, Project Settings”.

8.When the “codelab Project Settings” window appears, click on “C/C++/Assembler” in the left box. Use the drop-down arrow to select “C compiler” for “Build Tool”.

9.Edit the command line box at the bottom so that it contains the following:

-v -Wall -specs=redboot.specs -gdwarf-2 -O0 -c -mcpu=xscale $(InputRelPath) -o $(OutDir)\$(InputName)$(OutputExt)

10.Use the drop-down arrow to select “Assembler” for “Build Tool. Edit the command line box at the bottom so that it contains the following:

-v -specs=redboot.specs -o $(OutDir)\$(InputName)$(OutputExt) $(InputRelPath)

11.In the left box, click on “Linker”. Edit the command line box at the bottom so that it contains the following:

-v -specs=redboot.specs -o $(OutDir)\$(ProjectName).elf $(ObjectFiles) $(Libraries)

12.Click “Apply” and then click “OK”.

13.In the “Solution Explorer” window, right click “Project80333” and select “Save Project80333”.

58

Customer Reference Board Manual

Image 58
Contents Intel IQ80333 I/O Processor Customer Reference Board ManualCustomer Reference Board Manual Contents Dram 2.2 Figures Tables Revision History Date Revision DescriptionDocument Purpose and Scope Other Related DocumentsElectronic Information Electronic InformationComponent References Component ReferenceTerms and Definitions Terms and DefinitionsDefinition Intel 80333 I/O Processor Intel 80333 I/O Processor Block Diagram 231Summary of Features Feature DefinitionHardware Installation Kit ContentFirst-Time Installation and Test Power Requirements Development Strategy Factory SettingsContents of the Flash Supported Tool BucketsRedHat RedBoot Target MonitorsSerial-UART Communication Host Communications ExamplesJtag Debug Communication Network Communication Network Communication ExampleCommunicating with RedBoot GNUPro GDB/InsightIntel IQ80333 I/O Processor Connecting with GDB GDB set remotebaudThis Page Left Intentionally Blank Target Market Functional DiagramPCI Express RAID card Form-Factor/Connectivity Features Board Form-Factor/ConnectivityPower Power FeaturesBattery Backup Memory SubsystemFlash Memory Requirements Flash Memory RequirementsInterrupt Routing External Interrupt Routing to Intel 80333 I/O ProcessorPeripheral Bus Features 80333 populates the peripheral bus as depicted by FigureFlash ROM Flash ROM FeaturesFlash Connection on Peripheral Bus Non-Volatile RAM Rotary SwitchUart Audio BuzzerBattery Status Buffer Requirements Battery StatusName Description Debug Interface Console Serial PortJtag Port Jtag DebugJtag Port Pin-out Board Reset Scheme Reset Requirements/SchemesDefault Switch Settings of S7A1- Visual Switches and JumpersSwitch Summary Switch SummaryJumper Summary Connector SummaryGeneral Purpose Input/Output Header Switch S6A1 BPCI-X Reset Detail Descriptions of Switches/JumpersSwitch S1C2 Intel 80333 I/O Processor Reset Switch S8A1 RotarySwitch S7A1-3 Retry Settings and Operation Mode Switch S7A1-2 Reset IOP Settings and Operation ModeS7A1-4 PCI-X Bus B Speed Enable Settings and Operation Mode S7A1-9 Operation Mode S7A1-8 Operation ModeS7A1-10 Operation Mode Jumper J1C1 Jtag Chain Jumper J7D1 Flash bit-widthJumper J1D2 Uart Control Jumper J9D3 Buzzer Volume Control Jumper J7B4 SMBus HeaderDram Components on the Peripheral BusFlash Connection to Peripheral Bus Peripheral Bus Memory Map Address Range in Hex Size Data Bus Width DescriptionBoard Support Package BSP Examples Intel 80333 I/O Processor Memory MapRedBoot Intel 80333 I/O Processor Files RedBoot* Intel 80333 I/O Processor Memory MapVirtual Address Physical Address Size Description Mov R8, r4 IQ80321 and IQ80333 Comparisons This Page Left Intentionally Blank Introduction PurposeRelated Web Sites Setup Hardware SetupSoftware Setup Software Flow DiagramNew Project Setup Creating a New ProjectConfiguration Flashing with Jtag OverviewUsing Flash Programmer Debugging Out of Flash Building an Executable File From Example CodeRunning the CodeLab Debugger Launching and Configuring DebuggerManually Loading and Executing an Application Program Using Breakpoints Displaying Source CodeSetting CodeLab Debug Options Stepping Through the CodeExploring the CodeLab Debug Windows Watch Window Registers WindowVariables Window Software Breakpoints Debugging BasicsHardware and Software Breakpoints Hardware BreakpointsExceptions/Trapping