Ride7 for PowerPC. Raisonance Tools for SPC56xx family. Getting Started. Document version 21 August A KEOLABS brand

Transcription

1 Ride7 for PowerPC Raisonance Tools for SPC56xx family Getting Started Document version 21 August 2012

2 Contents 1. INTRODUCTION Purpose of this manual Scope of this manual Additional help or information RAISONANCE TOOLS FOR SPC56XX POWERPC FAMILY Ride RLink Supported SPC56xx derivatives REGISTERING THE NEW RAISONANCE TOOLS FOR PPC Install the software Register using an RLink Register using a serial key BUILDING A NEW APPLICATION Create a new project Compile, Assemble and Link the application Mandatory command examples Other options Build/compile/assemble/link the application DEBUGGING PRECOMPILED APPLICATIONS ELF (or HEX) file format Debug/Load Command DEBUGGING WITH RLINK RLink programming and debugging features RLink Presentation RLink versions and capabilities RLink JTAG-PPC ADP Setting Ride7 to use the RLink Selecting hardware debugging tool RLink-specific configuration Hints and troubleshooting Launching the debugger

3 6.3.1 Using the debugger Using breakpoints CONFORMITY AND RECYCLING GLOSSARY INDEX HISTORY

4 1. Introduction 1. Introduction Raisonance integrated development environment (Ride7) for PowerPC-based devices can be used with the RLink USB to JTAG debugger/programmer from Raisonance to debug applications for SPC56xx PowerPC projects. The applications should have been built in the standard ELF format. 1.1 Purpose of this manual This guide should be used by anyone who is interested in Ride7 for PowerPC. 1.2 Scope of this manual This document describes how to get started using Ride7 for PowerPC to program and debug your application or one of the included sample applications. It assumes that you have the prerequisite knowledge of the C and assembly languages and CPUs. 1.3 Additional help or information If you want additional help or information, if you find any errors or omissions, or if you have suggestions for improving this manual, look at KEOLABS' microcontroller web site or contact our microcontroller support team. Web: support-mcu@raisonance.com -4-

5 2. Raisonance tools for SPC56xx PowerPC family 2. Raisonance tools for SPC56xx PowerPC family The Raisonance tools Ride7 and RLink can be used with the PowerPC CPUs. 2.1 Ride7 This integrated development environment is the interface for all the other tools, providing an editor, a project manager and a debugging user interface that can be used with the RLink hardware debugging tool. 2.2 RLink This JTAG standard debugger/programmer with a USB interface allows you to program the SPC56xx PowerPC devices on an application board and debug the application while it runs on the target. It uses the JTAG protocol. Raisonance s REva evaluation boards feature an embedded RLink. RLinks have different capabilities for programming and debugging SPC56xx PowerPC microcontrollers. Your RLink s capability to program and debug any Ride7-supported target microcontroller can be verified when Ride7 reads your RLink s serial number. For a description of the different debugging capabilities, refer to the Debugging with RLink section. 2.3 Supported SPC56xx derivatives Ride7 for PowerPC supports existing SPC56xx derivatives to various degrees. At the time this document is written, the supported derivatives are: SPC560P40, SPC560P50, SPC560P60, SPC56AP60. SPC560B40, SPC560B50, SPC560B64. SPC56EC74. SPC563M60, SPC563M64. SPC564A80, SPC564A70. SPC5EL60, SPC5EL70. In the current version, debugging is implemented for single-core applications only. Multicore devices can be debugged, but only using core 0. The up-to-date list of supported derivatives can be seen in the Target Options in Ride7. Derivatives not listed there are not supported. The up-to-date list of supported derivatives, limitations and new features can be seen in the Release Note: <Ride>\doc\PPC\Release_notes_RKit-PPC.txt Check out the Raisonance website for software updates that can include support for other derivatives: -5-

6 3. Registering the new Raisonance tools for PPC 3. Registering the new Raisonance tools for PPC Ride7 and RKit-PPC must be registered to operate correctly. Registration requires a Raisonance hardware product or software product license that is under a valid support contract (a standard support contract expires one year after the date of purchase). Products that allow activation of RKit-PPC include the RKit-PPC license (Serial number or Dongle) and the RLink-PPC of different types (RLink-PPC-STD, RLink-PPC-PRO, REva-PPC starter kit, PPC Primer). Unregistered software functions for a 7-day evaluation period with full Enterprise version features. After 7 days the software can no longer be used. If this occurs, contact info@raisonance.com. 3.1 Install the software Perform these steps to install your new software: 1. Remove all old versions of Ride7 and kits. 2. Install the new Ride7 software, then the RKit-PPC software, then validate its operation (test 3. compilation, connection to RLink and to target CPU, etc.). 4. Launch Ride7 and select Help > License. In this interface you can register by providing: a. Software serial number (purchasers of RKit-PPC-Enterprise or RKit-PPC-Lite tool sets). b. Hardware dongle number (purchasers of RKit-PPC-Enterprise or RKit-PPC-Lite tool sets). c. RLink serial number (purchasers of RLink-PPC, REva-PPC or PPC Primer). 5. Register the software by selecting the menu item Help > License... Note: During the registration process, you will be notified if your product's support contract has expired. This notification includes information about how to renew your tool's support contract 3.2 Register using an RLink Automatic registration requires that you have the PC connected to the internet and a hardware serial number, or software serial key that is covered by a valid support contract. Follow these steps to register your RLink automatically: 1. Log on as admin, ensure you have internet access, a working default browser and a working address. 2. Plug in the RLink and make sure the BUSY LED turns OFF (USB enumeration). 3. Open Ride7 or RFlasher7. If it does not open automatically click Help->About Ride7. 4. Click the Change License button. Select RLink Activation, click Next. 5. If the software finds the RLink, it says RLink detected. Ready for registration. Click Next. 6. Connect to the internet and click Get Activation code online to open your browser on the Raisonance server. 7. Fill in the form and click Generate and Send Activation code. 8. Check your server for an from Raisonance Support team with the Activation Code. 9. Copy the Activation Code from the to the Ride7 window. Click Finish. 10. Close Ride7 and open it again. Check in the About Ride7 window that you are in "Lite Suite" for RKit-PPC and "Standard version" for Ride7. Otherwise please contact our technical support (support@raisonance.com). -6-

7 3. Registering the new Raisonance tools for PPC 3.3 Register using a serial key You must use this procedure for: Old RLink, REva, or Primers (Monaco Primers) RKit-PPC-Enterprise software licenses (Serial Number or Dongle) RLink-PPC-STD, REva-PPC or PPC Primers purchased more than one year ago, that have been upgraded to "Pro". If your product was purchased: less than one year ago, you will need to provide your proof of purchase. more than one year ago, you will need to purchase the annual support extension. Perform these steps to register using a serial key: 1. Contact Raisonance (info@raisonance.com) to obtain a Serial Key. They need your Software or RLink Serial Number (For RLink, click Connect to RLink in RFlasher7 or Ride7 debug options). 2. Log on as admin, ensure you have internet access, a working default browser and a working address. 3. Open Ride7 or RFlasher7. If it does not open automatically, click Help->About Ride7. 4. Click the Change License button. Select the Serial Activation method, click Next. 5. Enter the Serial Key provided to you. Click Next. 6. Connect to the internet and click Get Activation code online to open your browser on the Raisonance server. 7. Fill in the form and click Generate and Send Activation code. 8. Check your server for an from Raisonance Support team with the Activation Code. 9. Copy the Activation Code from the to the Ride7 window. Click Finish. 10. Close Ride7 and open it again. Check in the About Ride7 window that you are in "Lite Suite" for RKit-PPC and "Standard version" for Ride7. Otherwise please contact our technical support (support@raisonance.com). -7-

8 4. Building a new application 4. Building a new application Ride7 provides an interface that allows you to build projects with your chosen software. You simply create a new project, add your source files to the project, then compile, assemble and link them using the Ride7 Application Options. 4.1 Create a new project If you have an existing project that you want to use, go to the menu Project > Open Project and select the project. If you want to add a new project, follow these steps: 1. In Ride7, go to the menu Project > New Project. 2. Select New application to be built, then select your PowerPC derivative target (and instruction set if applicable), and choose in which directory you want to create the debugging project (usually the same as the application's directory). 3. Click on Finish to generate your project. 4. Insert your source files into this project. Your project's local settings should now contain Compiler, Assembler and Linker sections. -8-

9 4. Building a new application 4.2 Compile, Assemble and Link the application The Compiler, Assembler and Linker sections are all used in a similar way: 1. You enter a mandatory command which contains the variables required by the third party software (compiler, assembler or linker). 2. You then have the option to add another command that will be processed after successful completion of the mandatory command. - In the case of the linker, you may add 3 additional commands. - In the case of Compiler and Assembler you may specify dependent include files. 3. You right click on the Source file and select Run compiler/ Run assembler/run linker, or select the project and Build. These steps are explained in more detail in the following sections Mandatory command examples Examples can be found in Raisonance/Ride/Examples/PPC/Generictests, and Help about the commands is available in Ride7 Documentation>Working with Ride7 IDE> Setting project options. Here are some example command lines: These commands are run in the same way as in the Windows Command prompt screen. $(DirPath) is replaced by your predefined Path. You can see the expanded code in the build log window after you do a compile, for example: \MyCompiler.exe -i"." -i"c:\program Files\Raisonance\Ride\Lib\PPC\include" +debug +rev +warn +modv -l -cl"c:\program Files\RAISONANCE\Ride\examples\PPC\gen_test\SPCtest" -co"c:\program Files\RAISONANCE\Ride\examples\PPC\gen_test\SPCtest" "C:\Program Files\RAISONANCE\Ride\examples\PPC\gen_test\SPCtest\src\crossbar_init.c" Other options If you wish to do a Make of just one file you must list all the included dependent files in the Dependencies option of the Compiler and Assembler steps, otherwise the make will not work. Other commands can be entered for the Compiler, Assembler and Linker in additional options. -9-

10 4. Building a new application Build/compile/assemble/link the application To compile a source file, right click on the.c file, select Run GENERIC compile Similarly for the other options, right click and select your option. To build the project from Ride7, Select Project, Build

11 5. Debugging precompiled applications 5. Debugging precompiled applications The Ride7 IDE allows you to debug projects that have been compiled by other IDEs, scripts, command-line or on other PCs. 5.1 ELF (or HEX) file format Ride7 can only load and debug applications that were compiled and linked in the standard ELF format. If your linker generates its output in another format, you will have to convert it to ELF format. Many utilities can do this with the most common formats. Compiler vendors usually provide them along with the linker. You could also load and debug applications in HEX format, but then you will only be able to debug the disassembled code, without labels (variables and functions names,...), and without any link to the source code. 5.2 Debug/Load Command To debug a precompiled application, open Ride7 and click Debug and then Load: Ride7 will then ask you which.elf or.hex file you want to debug

12 5. Debugging precompiled applications You must then tell Ride7 on which PowerPC derivative (and using which instruction set if applicable) you want to debug the application, and in which directory you want to create the debugging project (usually the same as the application's directory):

13 5. Debugging precompiled applications After that Ride7 creates and opens the project to be debugged: You can then debug it like any other project, as described in the next chapter: Debugging with RLink

14 6. Debugging with RLink 6. Debugging with RLink The Ride7 for PowerPC can be used with the RLink hardware debugging tool. RLink is a USB to JTAG emulator from Raisonance which supports all the microcontrollers that are supported by Ride7. See the up-to-date list in the Advanced PowerPC Options > Processor > Processor name. The debugger lets you check your code and the interaction between your code and the peripherals, before going on to production programming. This section shows the use of the debugger for PowerPC microcontrollers. The interface is the same for all targets and all Ride7 debuggers, hardware and software. Complete debugger documentation is in the Ride7 general documentation. 6.1 RLink programming and debugging features RLink Presentation The RLink is a USB to JTAG interface device designed by Raisonance. It allows programming and debugging of various microcontrollers, including all the PowerPC microcontrollers supported by Ride7, through the standard 14-point connector defined for PowerPC. In order to use RLink, be sure that you have installed the associated USB driver. Unless you have specified otherwise, it is installed along with Ride7. If the USB driver has not been installed, launch the program RLinkUSBInstall.exe. For standard installations of Ride7 for PowerPC, it is located at: C:\Program Files\Raisonance\Ride\driver\RlinkDrv\RLinkUSBInstall.exe After running this program, when you plug an RLink in, Windows recognizes it automatically. The recognition could take some time on the first connection. The following connections of the same RLink on the same PC will be faster. The REva evaluation board includes an embedded RLink. The whole board can be powered by USB through the RLink. The target microcontrollers are on interchangeable daughter boards so that one evaluation board supports several different targets. See the REva documentation for more information. The Primers also include an RLink, but unlike the REva board, the target CPU cannot be changed. For Ride7, there is no difference between operating the REva, the Primer or using an RLink with any other board with a JTAG connector RLink versions and capabilities RLinks have different capabilities for programming and debugging of PowerPC, ARM, STM8, ST7 and upsd microcontrollers. Your RLink will fall into one of the following categories: PPC standard RLinks: Stand-alone Standard RLinks for PowerPC, RLinks in REva Starter Kits for PowerPC, RLinks in PowerPC Primers. These RLinks have limited access to PowerPC microcontrollers, you can program and debug up to 64 Kbytes, you can also program (and execute) the full Flash memory, but you cannot debug it if the application is larger than 64 K. PPC Pro RLinks: These stand-alone RLinks permit full access (programming and debugging) to PowerPC targets without any limitations. Other RLinks: These RLinks are made for other target CPU families. (ARM, ST7, STM8, etc.) They cannot connect to PowerPC devices at all. Your RLink s capability to program and debug PowerPC targets can be verified when Ride7 reads your RLink s serial number. To verify what kind of RLink you have, use the Test Connection to RLink in the Connection tests section of the debug options (see below). Note: RLink (all categories) cannot work in external memory mode

15 6. Debugging with RLink RLink JTAG-PPC ADP A stand-alone RLink needs an ADP to adapt the RLink s 24-pin connector to the target connector. The following table shows the ADP connections, in case you want to make your own. Signal 14-point connector pin number 24-point connector pin number GND 2, 4, 6, 12 3, 4, 10, 17, 19, 21, 22 VCC 11 1 JCOMP 14 6 RST 9 11 TMS TCK 5 13 TDO 3 15 TDI Setting Ride7 to use the RLink Selecting hardware debugging tool Within Ride7, you can choose your target hardware debugger from 2 menus. Project Options window, if it is open. Options > Project Properties menu, Advanced PowerPC Options > Debug Environment. Ride7 for PowerPC only supports RLink for debugging and programming of PowerPC microcontrollers. To use this option you need either: an RLink connected to the application board's target PowerPC CPU via a JTAG connector a REva evaluation board, which includes an embedded RLink, and a PowerPC daughterboard RLink-specific configuration After selecting RLink as your debugging tool, click on the Advanced Options button to open the Debug options dialog box shown next

16 6. Debugging with RLink Operations Check Internal IDs (MIDR) can be unchecked when working on prototype CPUs. Otherwise keep it checked in order to avoid connecting to the wrong device, which could damage the hardware. Erase Flash before programming can be unchecked when debugging RAM applications that do not use the Flash at all, or that uses it as persistent data. That allows to keep the Flash content unchanged when starting the debug session, in case you want to keep it or in order to speed up the starting of the debug session. Of course, programming might fail, and then debugging will not start, if the debugged application contains data for some previously nonblank Flash addresses. Blank-Check before programming can be unchecked when debugging applications that use the Flash as persistent data or for multi-part programming. (OS/bootloader/application/SerialNumber) That allows to partially keep the previous Flash content when starting the debug session. Of course, programming might fail, and debugging will not start, if the debugged application contains data for some previously non-blank Flash addresses. Check Checksum after programming can be checked to quickly verify the programming. Use this is executing a slightly modified version of your application can lead to grave problems. (motor control, etc.) Launch debug session after programming tells the debugger to debug your application. (!) Uncheck this option if you want to use RLink as a simple programmer, e.g. if you want to try the application on the PowerPC without debugging it. When this option is unchecked, launching a debug session simply programs the code to your PowerPC CPU and starts execution. This is useful when developing applications that exceed the 64K debug limitation, or for verifying that the application executes correctly when it is not under the control of the debugger. Note that for simply programming without debugging, you can rather use RFlasher7 or RLink_PPC_pgm.exe. RFlasher7 has its own documentation file, and RLink_PPC_pgm.exe shows its own doc when launched without argument in a command prompt. Freeze Timers on debug events tells the debugger to Freeze the timers when the execution of the application is halted in debug mode (after a reset, breakpoint or stop command in the GUI). This option simply sets the DBCR0.FT flag. See the PowerPC core spec for more information on this. This option has no effect if the Launch debug session after programming option is deactivated

17 6. Debugging with RLink Connection tests This section allows you to carry out the tests below without leaving this dialog box. This is useful for testing connections and retrieving information from the RLink and your PowerPC. View REva Jumpers shows how you must set the jumpers on the REva board's RLink for using it to program and debug PowerPC. You must be sure that the jumpers are correctly set before powering the board, and of course before any attempt to communicate with it. Test Connection to RLink checks that the RLink is working and properly connected and that the USB driver is correctly installed. It also allows you to read the RLink serial number, which you will be asked for if you contact our support team. When Ride7 checks the RLink serial number, the resulting message includes information about your RLink s capabilities and limitations for the currently selected target microcontroller. See RLink types and capabilities above. Test Connection to PowerPC allows you to read the JTAG IdCodes of the target CPU. Use this to test the connections and power of the target PowerPC CPU. Help displays the help in this window Address Range This section allows you to select the range of addresses that will be affected by all operations. This applies to the Instant Actions of this window, and also to programming and debugging in Ride. You can select the range either by ignoring some regions of the memory (main flash, shadow flash, data flash) or by entering values for the start and end addresses Flash censorship This section allows you to prevent accidental securing or locking (=securing that cannot be unsecured) of the device. They become active if shadow Flash programming is enabled. This section also allows you to activate the Unsecure Sequence and specify the Password required for performing this sequence. See the ST documentation about shadow Flash, security, unsecure sequence, etc. IMPORTANT: If you don't know what this is, make sure you keep the shadow Flash programming disabled. Otherwise there is a risk of locking the device, without any possibility to erase and reprogram it RLink-REva jumpers When using a REva Starter Kit embedded RLink (no plastic casing), ensure that your jumpers are set correctly on the RLink. To do this, click on View REva jumpers. That will open a window that illustrates the PPC configuration for the RLink jumpers.: If these pictures differ from those in Ride7 documentation, assume that those shown in Ride7 are correct. If you purchased RLink as part of a PowerPC starter kit (such as the REva evaluation board for SPC56xx), then the jumpers should already be correctly set. For this reason, you should only need to adjust these jumpers if they were accidentally unplugged, or if you are using an RLink that was configured for another microcontroller, such as ST

18 6. Debugging with RLink Instant actions This section allows you to carry out these instant actions without leaving this dialog box. This is useful for testing connections and retrieving information from the RLink and your PowerPC, as well as for configuring and programming the PowerPC. Blank-Check Flash indicates if the Flash of the target device is currently programmed or not. Erase Flash completely erases the target CPU's Flash (writing 0xFF). Program Flash allows you to program the Flash with the contents of a.hex file, then launch the execution. Read Flash reads the contents of the Flash and writes it in a.hex file JTAG chain description Single PowerPC device indicates if there are several JTAG devices chained or only one device. The check box should remain checked if there is only one device. The JTAG standard permits JTAG devices to be chained but this complex process should only be done if you have a good knowledge of the JTAG protocol. You can configure Ride7 to access a PowerPC microcontroller that is chained with other JTAG devices by unchecking the check box and entering the four parameters that the software needs to access the correct target in the chain. You need to know how many devices are in the chain, what order they are in, and the size of the IR register of each of them. Then, you must tell Ride7 how many devices are before (and after) the target in the chain. You must also tell it the sum of the lengths of the IR registers of the devices before and after the target

19 6. Debugging with RLink Hints and troubleshooting Example projects The <Ride>\Examples\PPC directory contains example applications for different boards featuring CPUs supported by Ride7. The examples in the <Ride>\Examples\PPC\REva directory are configured for use with the REva evaluation board, which includes the RLink. For standard installations they are found in C:\Program Files\Raisonance\Ride\EXAMPLES\PPC\REva. Before using an example, look at it and make sure that the jumpers on the REva evaluation board are set correctly (enable switches for the LEDs, etc). Usually, there is some important information in comments at the beginning of the main file (i.e. the file that contains the main function). There are also examples for the Primer and ST evaluation board in the corresponding directories Testing USB driver, connections and power supplies To test the USB driver installation and the operation of RLink, use the Connection test Test connection to RLink. When it is correctly recognized, the RLink appears in Windows' device manager under the Jungo section if in Windows XP, and under the RLinkWinUSBClass section if in Windows Vista or Windows 7. To test the connections and power of the target board and PowerPC CPU, use the Connection test Test Connection to PowerPC whilst using RLink to connect to the PowerPC. This test ensures that it is powered, correctly connected to RLink, and that the rest of the application board does not interfere with the communication between RLink and the PowerPC CPU. It also checks that the target CPU is of the correct type

20 6. Debugging with RLink 6.3 Launching the debugger To launch the debugger, type CTRL D or select Debug > Start in the main menu. You are now in the debugger. Your Ride7 window should look like the following: 1. The upper part of the Debug tab, which shows the different Data views available on a given microcontroller. To see a specific view, double-click on its name. 2. The lower part of the Debug tab, which shows the peripherals available on a given microcontroller. To see a specific peripheral, double-click on its name. Most of these peripherals are NOT simulated. 3. The source file as edited in C or in assembly language. The red boxes on the left indicate lines that contain instructions where you can place breakpoints. The blue arrow indicates the current PC. This is the next instruction to be executed. 4. The Disassembly View window displays the instruction to be executed by the target CPU. It is a dump of the memory where the code is located. The line highlighted in blue indicates the current PC, as the blue arrow in the source window. The following columns are available in the Code window: Address: address where the instruction is located. Symbol: name of the symbol, if a symbol is located at this address. Code: byte-code located at this address. Mnemonic: mnemonic corresponding to the byte-code

21 6. Debugging with RLink 5. The Debug Output window provides feedback on the status of debugging process. Status information can include errors as well as debugging event logs. Some message lines are hyperlinked with a PC address, clicking on the PC item displays the Disassembly view at the PC address where the event occurred. 6. Data Dumps Views (here Memory (32-bits) View) is only available during a debug session, and allows you to observe the content of the different memory dumps. The addresses associated with symbols are highlighted with pink color. A status bar on the bottom of this view displays the symbols and eventually informs of a read or write access. You can modify the content of the target device memory from this view. Select the value you want to alter, type the new value and press Enter. Double clicking the ASCII value also lets you type directly the value in ASCII format. 7. The toolbar, which allows you to control the debugging (see next section for more information) Using the debugger The debugger is controlled by the debugger toolbar: 1. Run: Pressing this button launches the application. When the application is running, this button is grey, and the Pause button is available. 2. Pause: Pressing this button stops the application. 3. Reset: Pressing this button resets the application. 4. Step Into: On a function call in a line of the C source code, this button steps into the called function. If it is not a function call, it goes to the next line in the source code. 5. Step Over: On a function call in a line of the C source code, this button steps over the called function. 6. Step Out: In a function this button gets out of the function. 7. Run To: Run the program until the cursor. 8. Toggle breakpoint: If there is no breakpoint on the current line, Ride7 sets a breakpoint on it. If there is one, the breakpoint is removed. 9. Clear All breakpoints: Clear all the breakpoints set. 10. Project: Open the Project window. 11. Find in files: Pressing this button opens the Find in files window allowing the search an expression in files of the project directory. 12. Binoculars: This opens the search window. 13. Documentation: Pressing this button opens the Documentation window allowing to open Help html files. 14. Toolbar Options: Allows to Add or Remove buttons in the menu

22 6. Debugging with RLink Using breakpoints You can set a breakpoint either in the source file, or in the code view. Make sure that the application is not running (click on PAUSE). You can see on the left side of the source code some lines with red boxes. These lines are code lines (and not comments) where a breakpoint can be set. Click on the red box Toggle Breakpoint and a red point appears on this line, which means that a breakpoint has been set on this line. Then, click on the RUN button and the application will stop running when this line is reached: Refer to Ride7 general documentation for information about the debugger Graphical User Interface

23 7. Conformity and recycling 7. Conformity and recycling ROHS Compliance (Restriction of Hazardous Substances) KEOLABS products are certified to comply with the European Union RoHS Directive (2002/95/EC) which restricts the use of six hazardous chemicals in its products for the protection of human health and the environment. The restricted substances are as follows: lead, mercury, cadmium, hexavalent chromium, polybrominated biphenyls (PBB), and polybrominated diphenyl ethers (PBDE). CE Compliance (Conformité Européenne) KEOLABS products are certified to comply with the European Union CE Directive. In a domestic environment, the user is responsible for taking protective measures from possible radio interference the products may cause. FCC Compliance (Federal Communications Commission) KEOLABS products are certified as Class A products in compliance with the American FCC requirements. In a domestic environment, the user is responsible for taking protective measures from possible radio interference the products may cause. WEEE Compliance (The Waste Electrical & Electronic Equipment Directive) KEOLABS disposes of its electrical equipment according to the WEEE Directive (2002/96/EC). Upon request, KEOLABS can recycle customer s redundant products. For more information on conformity and recycling, please visit the KEOLABS website

24 8. Glossary 8. Glossary Term Description ADP Adapter JTAG Joint Test Action Group (or "IEEE Standard "). A standard specifying how to control and monitor the pins of compliant devices on a printed circuit board. PPC PowerPC/Performance Optimized With Enhanced RISC Processor Chip Ride Raisonance integrated development environment RLink Raisonance s in-circuit debugging and programming tool REva Raisonance's universal evaluation board

25 9. Index 9. Index Additional help or information...4 Building a new application...8 CE...23 Compliance...23 Conformity...23 Debug/Load Command...11 Debugging precompiled applications...11 Debugging with RLink...14 Directive...23 FCC...23 Introduction...4 Launching the debugger...20 Lead...23 Purpose of this manual...4 Raisonance tools for SPC56xx PowerPC family...5 Registering the new Raisonance tools for PPC...6 RLink...5 RLink programming and debugging features...14 RLink-specific configuration...15 ROHS...23 Scope of this manual...4 Selecting hardware debugging tool...15 Serial Key...7 Setting Ride7 to use the RLink...15 Supported SPC56xx derivatives...5 Using breakpoints...22 Using the debugger...21 WEEE

26 10. History 10. History Date Description 10 Nov 09 First complete and presentable version 23 Nov 09 Added compiler/assembler Dependency option 8 Dec 09 Updated SPC563M54 and SPC560B60 in supported devices list and added description of Erase and Freeze Timers options in RLink Debug Options 06 Jun 11 Added information about MIDR check, new devices SPC560P40 and SPC560B40, shadow flash and censorship support 29 Aug 12 Modified cover page, final page and section 1.3 Additional help or information for KEOLABS

27 Disclaimer Information in this document is subject to change without notice and does not represent a commitment on the part of the manufacturer. The software described in this document is provided under license and may only be used or copied in accordance with the terms of the agreement. It is illegal to copy the software onto any medium, except as specifically allowed in the licence or nondisclosure agreement. No part of this manual may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or information storage and retrieval systems, for any purpose other than the purchaser s personal use, without prior written permission. Every effort has been made to ensure the accuracy of this manual and to give appropriate credit to persons, companies and trademarks referenced herein. This manual exists both in paper and electronic form (pdf). Please check the printed version against the.pdf installed on the computer in the installation directory of the most recent version of the software, for the most up-to-date version. The examples of code used in this document are for illustration purposes only and accuracy is not guaranteed. Please check the code before use. Copyright KEOLABS 2012 All rights reserved