RLink. Getting Started. Document version 25 October Raisonance: a KEOLABS brand

Transcription

1 RLink Getting Started Document version 25 October 2012 Raisonance: a KEOLABS brand

2 RLink Getting Started Contents 1. INTRODUCTION License Purpose of this manual Scope of this manual Additional help or information What is KEOLABS? RLINK VERSIONS RLink1.xx RLink2.xx RLink3.xx RLink4.xx INSTALLING RLINK Automatic installation of the RLink USB driver Manual installation of the RLink USB driver Uninstallation of the RLink USB driver Alternative recovery procedure Reading RLink serial number Reading RLink serial number from Ride Reading RLink serial number from RFlasher Reading RLink serial number from any Windows command prompt Register and activate the software (if upgrade or support required) USING RLINK Before using RLink a KEOLABS brand

3 RLink Getting Started 4.2 Using RLink with different target CPUs Using RLink with the host software RLink connectors Adapter schematics Connecting and powering Operating conditions Support and FAQ Checklist of items to prepare before contacting support CONFORMITY GLOSSARY INDEX HISTORY a KEOLABS brand

4 1. Introduction RLink Getting Started 1. Introduction RLink is a versatile high-performance microcontroller debugger and programmer which supports a range of target interfaces (JTAG, SWD, SWIM, ICC) and can connect to a wide range of 32-bit and 8- bit microcontrollers to program the target device and debug applications in real-time. The RLink is available in a number of formats: as a standalone product, embedded on a board, or as part of a package from another company. 1.1 License Purchase of an RLink includes the appropriate Ride7 RKit software, and includes upgrades and support for a year. After one year, if you require support, or if you wish to upgrade the kit, you will need to purchase a new license for the RKit. 1.2 Purpose of this manual This manual gives an overview of the RLink and gives users links to the documentation that is relevant to their RLink application. The RLinkTools_API software interface allows users to manage the RLink 24-pin connector I/Os to customize the use of the RLink, this is detailed in the RLinkTools_API user manual. This manual does NOT explain how to configure and use the Raisonance software for communicating with the target CPU through RLink. This is explained in the Ride7 Getting Started document dedicated to the Ride7 support of this CPU family: GettingStartedARM, GettingStartedSTM8, etc. Please refer to these documents for information on how to actually use the RLink. 1.3 Scope of this manual The manual provides an overview that is applicable to all RLinks. 1.4 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 Raisonance microcontroller web site or contact our microcontroller support team. Web: support-mcu@raisonance.com 1.5 What is KEOLABS? In 2012 Raisonance merged with another company (Soliatis) and changed its name to become KEOLABS. Raisonance is now the KEOLABS brand for Microcontroller (MCU) tools. All references to Raisonance as a company, in this file or others, should now be understood as references to KEOLABS. Raisonance products purchased before the name change continue to be licensed, supported and maintained by KEOLABS as they were by Raisonance. All licenses, support and maintenance contracts, etc. are transferred from Raisonance to KEOLABS a KEOLABS brand

5 RLink Getting Started 1. Introduction Here are the updated versions of the warranty and software licenses that apply to all KEOLABS (and Raisonance) products now: You can find more information about this change of status here: a KEOLABS brand

6 2. RLink versions RLink Getting Started 2. RLink versions 2.1 RLink1.xx This independent device is not produced anymore. It works in the 3V-5.5V range. It can only be connected to a µpsd and is in a white plastic box. 2.2 RLink2.xx RLink version 2.xx is not produced anymore. It works in the 2.5V-5.5V range. It is attached to a REva2,xx board and can be snapped off if required. It can drive ARM, ST7, STM8, PPC and µpsd devices. 2.3 RLink3.xx Version 3.xx is the current version. This RLink can be: stand-alone, inside a grey plastic box, part of a REva3.xx board (cannot be snapped off), part of a Primer: ST7FOX-Primer, STM8A-Primer, STM3210B-Primer (circle), etc. It is compatible with µpsd, ST7, STM8 and ARM devices. However, when it is part of a Primer it can only be used with the CPU in the Primer. It works in the 2.5V-5.5V range, and down to 1.5V with some protocols and adapters, like for example STM8-SWIM. It comes in two formats, Standard and Pro, which both offer unlimited flash programming of all supported 8-bit and 32-bit devices: RLink-STD provides unlimited debugging of applications on supported 8-bit devices via the same connection while driven from the Ride7 integrated development environment. Debugging of supported ARM core-based 32-bit devices is limited to 32 Kbytes of code in Flash or RAM. Flash programming is not limited. This is the default type of RLink, present in REva boards and all Primers. They can be upgraded to have the same capabilities as the RLink-Pro, KEOLABS simply sends the customer an encrypted text file which contains a reference to the RLink's unique Serial Number. RLink-PRO provides unlimited debugging of applications on supported 8-bit and 32-bit devices. It is only provided in a stand-alone version, but all standard RLinks, including the ones in REva boards (even REva2.xx) and in Primers can be upgraded to the PRO specification by software. There are also a number of specific versions of this RLink, for PPC, CoolRISC, BIRD, and some confidential target microcontroller architectures. Most of the information in this doc about USB drivers, voltage range, connections, support, etc. also applies to these special RLinks. However, you should consult the targetspecific documentation for more details, hints, warnings, etc a KEOLABS brand

7 RLink Getting Started 2. RLink versions 2.4 RLink4.xx Version 4.xx is the next generation, and is already included in some products. It is sometimes called "RLinkP", which is different from "RLink- PRO". The Open4 base includes an RLink4. When a daughterboard is plugged in the base, as in a Primer the RLink can only be used with the CPU that is present on the daughterboard. When the OP4-RLink-ADP daughterboard is plugged in the Open4 base, the resulting Open4-RLink can be used as a standalone RLink, with the same adapters as a standalone RLink. With current software versions, this RLink: Works only with Cortex-M (SWD) and STM8 (SWIM) devices. It does NOT support ARM7, ARM9, upsd, PPC (JTAG), ST7 (ICC), etc. It supports SWO low-level trace with Cortex-M devices (which the older RLinks do not support). It can work in the 2.5V-3.3V range, down to 1.5V with the STM8-SWIM protocol. Like the RLink3, the RLink4 comes in STD and PRO versions, with the same differences (debug limitation for 32-bit devices, possibility to upgrade from STD to PRO by software, etc.). Future versions of software and hardware products will add more features and flavours to this RLink a KEOLABS brand

8 3. Installing RLink RLink Getting Started 3. Installing RLink RLink uses Raisonance software to connect to a Windows USB driver and to communicate with the RLink via USB. This USB driver and its configuration file are provided by Raisonance along with Ride7. There are two USB drivers: WinDriver, from Jungo, is used for Windows XP32 with SP3 (SP3 is required.). WinUSB, from Microsoft, is used for Windows Vista32, Vista64, and all newer versions. (7, 8) Note: XP64 is not supported. 3.1 Automatic installation of the RLink USB driver Here is the normal procedure for installing the RLink driver on all supported versions of Windows: 1. Make sure the RLink is NOT connected to the PC. 2. Make sure you are logged in as Administrator, or a user that has administrator rights. 3. Install Ride7 or run RLinkUSBInstall.exe. In Vista, you must take care of running this in 'run as admin' mode. This program detects which version of Windows you are running and installs the correct driver (WinDriver or WinUSB) accordingly. On Vista and recent versions of XP, this pre-installs the driver in Windows DriverStore (or DRVSTORE), on older versions, it will install it directly in the Windows drivers directory. 4. Remove any CDs from the drives (this is important!). 5. Plug in the RLink. Check that the PWR and BUSY LEDs turn ON. The PWR LED means that the RLink is powered (!) and the BUSY LED means that the RLink firmware is running correctly. This validates most of the RLink hardware and firmware. 6. Tell the 'Found new hardware' wizard from Windows not to search on the internet. 7. Tell the 'Found new hardware' wizard from Windows to search automatically in Windows but do not point it to other places (this should be the default answer). 8. It should then find the driver, install it, and associate it with this RLink. 9. Then you should see the BUSY LED turning OFF, which means that Windows and the RLink are able to communicate through the USB driver and cable. 10. Check with RLinkCapab that you are able to read the RLink serial number as explained later in this documentation. Note: You must install the driver before you plug the RLink on the PC. Plugging the RLink before installing the driver can lead to the installation of incorrect files in Windows, preventing you from performing the installation afterwards. If this happens, you will have to uninstall all RLink drivers, as explained later in this document a KEOLABS brand

9 RLink Getting Started 3. Installing RLink 3.2 Manual installation of the RLink USB driver This procedure should only be used when the automatic procedure fails, which can happen on some versions of Windows with special configurations. For XP (and earlier) users: 1. Make sure the RLink is NOT connected to the PC. 2. Make sure you are logged in as Administrator, or a user that has administrator rights. 3. Install Ride7. 4. Remove any CDs from the drives, including the Ride7 CD (this is important!). 5. Open a command prompt. 6. Change Directory to <Ride>\Driver\RLinkDrv\Jungo_WinDriver_2000_NT_XP\ 7. Execute wdreg -inf windrvr6.inf install (watch out for error messages). 8. Execute wdreg -inf RLinkDrv_WDP.inf install (watch out for error messages). 9. If you have a recent version of XP, or if you have automatic updates activated, check that there are two directories in C:\WINDOWS\SYSTEM32\DRVSTORE\..., one with the name starting with windrvr6, and the second with RLinkDRV. 10. Plug in the RLink. Check that the PWR and BUSY LEDs turn ON. The PWR LED means that the RLink is powered (!) and the BUSY LED means that the RLink firmware is running correctly. This validates most of the RLink hardware and firmware. 11. Tell the Windows 'Found new hardware' wizard not to search on the internet. 12. Tell the Windows 'Found new hardware' wizard not to search automatically, but point it to <Ride>\Driver\RLinkDrv\Jungo_WinDriver_2000_NT_XP\ 13. It should then find the driver, finish to install it, and associate it with this RLink. 14. Then you should see the BUSY LED turning OFF, which means that Windows and the RLink are able to communicate through the USB driver and cable. 15. Check with RLinkCapab that you are able to read the RLink serial number as explained later in this documentation. For Vista, Win7 (and later) users: 1. Make sure the RLink is NOT connected to the PC. 2. Make sure you are logged in as Administrator, or a user that has administrator rights. 3. Install Ride7 in 'Run as Admin' mode. 4. Remove any CDs from the drives, including the Ride7 CD (this is important!). 5. Open a command prompt in 'Run as Admin' mode. 6. Change Directory to <Ride>\Driver\RLinkDrv\MS_WinUSB_XP_Vista\ 7. Execute RLink_WinUSB_Install_verbose.bat (watch out for error messages) 8. Check that there is a directory in C:\Windows\System32\DriverStore\FileRepository\... with the name starting with rlink_winusb. 9. Plug in the RLink. Check that the PWR and BUSY LEDs turn ON. The PWR LED means that the RLink is powered (!) and the BUSY LED means that the RLink firmware is running correctly. This validates most of the RLink hardware and firmware. 10. Tell the Windows 'Found new hardware' wizard not to search on the internet 11. Tell the Windows 'Found new hardware' wizard not to search automatically, but point it to <Ride>\Driver\RLinkDrv\MS_WinUSB_XP_Vista\ 12. It should then find the driver, finish to install it, and associate it with this RLink. 13. Then you should see the BUSY LED turning OFF, which means that Windows and the RLink are able to communicate through the USB driver and cable. 14. Check with RLinkCapab that you are able to read the RLink serial number as explained later in this documentation a KEOLABS brand

10 3. Installing RLink RLink Getting Started 3.3 Uninstallation of the RLink USB driver Sometimes you need to completely uninstall the RLink driver. Normally it is because a wrong driver (for the wrong version of Windows) has been installed. If that happens, you must completely uninstall the driver, which is no easy task. You must get to the point where when you plug in RLink and let Windows search automatically for a driver, it doesn't find any. Only then can you install the correct driver using one of the procedures described previously. If you cannot reach this point, see the next subsection which gives a method to force Windows to use the driver you choose. Standard procedure Here is how to uninstall the RLink driver: 1. Plug in the RLink. 2. If a driver is loaded for it, go to the Device Manager and ask Windows to uninstall it (the driver, not just the RLink). 3. If you see a "Jungo" section in the Device Manager, you should also try to uninstall it. 4. Then unplug the RLink. 5. Remove all the files, directories and registry keys (using regedit.exe started as admin) in the list below. In DriverStore (Vista) or DRVSTORE (XP), try to remove the whole directories. If you cannot, remove as many of the files in them as you can. Also try to remove the registry entries, you will need to change the ownership to yourself, recursively, then give "everyone" complete access to the keys, directories and files, then you should be able to remove them. 6. Go back to the first point of this procedure, plugging in the RLink, and repeat the process until Windows does not find any driver for the RLink when you ask it to search automatically. If after several tries it still finds one, go to the Device Manager, display the details of the driver that is associated with RLink, and try to locate the inf and/or sys files that are used. Then, repeat the procedure and make sure that you remove those files. Other items to remove (if they exist) Files and folders to remove: C:\Windows\inf\Windrvr6.* C:\Windows\inf\RLink*.* C:\Windows\System32\Drivers\Windrvr6.* C:\Windows\System32\Drivers\RLink*.* C:\Windows\System32\DriverStore\FileRepository\Windrvr6*.* C:\Windows\System32\DriverStore\FileRepository\RLink*.* C:\Windows\System32\DRVSTORE\Windrvr6*.* C:\Windows\System32\DRVSTORE\FileRepository\RLink*.* search for all C:\Windows\inf\oem*.inf files that contain the string RLink or Jungo. If you find any, you must remove them, and also the associated oem*.pnf files. Registry key to remove: HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Enum/USB/VID_138E&PID_9000/ a KEOLABS brand

11 RLink Getting Started 3. Installing RLink 3.4 Alternative recovery procedure In some situations, uninstalling the USB driver as described in the previous section can be difficult, because Windows keeps hidden copies of the drivers. If after several attempts you still don't manage to get to the point where Windows doesn't find any driver for the RLink, then you can follow this procedure. This procedure should only be used if the normal procedure described in the previous section has failed, because this second procedure must be done for all your RLinks. The normal procedure need only be performed once even if you have several RLinks. Manually install drivers with RLinkUSBInstall.exe from <Ride>\Drivers\... Plug in the RLink, let Windows associate it with the (wrong) driver it already has. In the Device Manager, Right-click on RLink -> choose Update Driver. Select Do not connect to Windows Update -> Click Next. Select Software from list -> Click Next. Select Don't search, I will choose... -> Click Next. Select List compatible hardware -> Choose RLink USB if in XP, RLinkWinUSBDevice if in Vista/Win7 -> Click Next. Finish. Note: The exact sequence and quotes above might differ a little depending on the version and configuration of Windows, and of course the language. But all versions of Windows should propose this procedure or an equivalent a KEOLABS brand

12 3. Installing RLink RLink Getting Started 3.5 Reading RLink serial number Reading the serial number of the RLink is the simplest way to check that the USB communication between RLink and the host PC is correctly configured and working. If this works, it validates the USB driver and its installation, the USB cable, and the USB and firmware parts of the RLink. You will be asked for your RLink's serial number whenever you contact our support team about RLink. Note: This serial number is different from that used for registration. The latter corresponds to a license, not to an RLink product Reading RLink serial number from Ride7 1. Open an ST7, STM8 or ARM project. 2. Choose RLink as Debug Environment in the Advanced Options. 3. Select Options > Project Properties > RLink Configuration > Advanced Options. 4. Click on the box Connect to RLink and read Serial Number Reading RLink serial number from RFlasher 1. Open RFlasher. 2. Select an ST7, STM8 or ARM Target CPU. 3. Click the button on the panel named Connect to RLink [and read serial number] Reading RLink serial number from any Windows command prompt 1. Execute RLinkCapab.exe Note: This application is installed along with Ride7. You can also download it from the link below: ftp:// 3.6 Register and activate the software (if upgrade or support required) You can use the software for a year. After this period you can continue to use your RLink with its existing software, but.you cannot upgrade or have support until you purchase, register and activate the newest RKit software. For details, refer to the Ride7 Getting Started document dedicated to the Ride7 support of your CPU family: GettingStartedARM, GettingStartedSTM8, etc a KEOLABS brand

13 RLink Getting Started 4. Using RLink 4. Using RLink 4.1 Before using RLink Before plugging in and using RLink, you must: Install Ride7 and the kit corresponding to your target CPU (ARM, STM8, etc.). Remove the CD from the drive (see the driver section for more information). 4.2 Using RLink with different target CPUs Refer to the Getting Started document for your Ride7 kit, which explains how to use RLink (and the other Raisonance tools) with the associated CPU family. Here is a non-exhaustive list: GettingStartedSTM8.pdf, installed with the RKit-STM8 kit, contains information on using the Raisonance tools, including the RLink, with STM8 and ST7 devices. GettingStartedARM_Ride7.pdf, installed with the RKit-ARM kit, contains information on using the Raisonance tools, including the RLink, with ARM7, ARM9 and Cortex-M3 devices. 4.3 Using RLink with the host software Once you have installed Ride7, RLink can be driven by Raisonance s integrated development environment (Ride7) or by other tools such as RFlasher7 and some command-line programming executables. Ride7 drives the RLink and offers seamless control of software development tools (project manager, editor, compiler, assembler, linker, debugger, etc.) from an intuitive graphical interface. It offers full integration of the relevant C/C++ toolsets, project management, code editor and SIMICE instruction set simulator. Refer to the Ride7 Getting Started document related to your CPU for more information on how to use RLink with Ride7 for this CPU. (GettingStartedARM, GettingStartedSTM8 and so on). The RFlasher7 easy-to-use device programming interface drives RLink and allows users to erase, program, view and verify microcontroller memory. RFlasher7 also includes an automated mode for automatic execution of programming sequences for mass programming and a project mode that allows users to save these programming configurations. Refer to the Ride7 Getting Started document related to your CPU for more information on how to use RLink with RFlasher for this CPU. (GettingStartedARM, GettingStartedSTM8,...). The command-line executables, such as STM8_pgm.exe, Cortex_pgm.exe, etc., allow you to execute all the standard programming operations, in a way that can easily be integrated into a mass production environment. They can be called from batch files and any kind of script that is able to start a process. They are installed along with Ride7 and contain their own documentation: just execute them without any argument from a command prompt to see the help a KEOLABS brand

14 4. Using RLink RLink Getting Started 4.4 RLink connectors The RLink must be connected to a PC via a USB link which also provides power to the RLink. Before this it must also be connected to a device on an application board via one of three adapters (or directly in case of RLinks 1 and 2). These adapters provide connections which follow the standards defined by the CPU manufacturers (ARM, ST, etc.), as shown here: Connector Protocol Device Relevant document 20-pin JTAG ARM core-base ARM Getting started 20-pin (or 10) JTAG/SWD ARM Cortex-M3 ARM Getting started 14-pin JTAG μpsd Application Note pin ICC ST7 STM8/ST7 Getting started 4-pin SWIM STM8 STM8/ST7 Getting started Note: Using a different connector / adapter is possible but not guaranteed. If hardware is damaged when doing this, the waranty does not apply. 4.5 Adapter schematics The RLink adapters used with the standalone version of RLink3.xx feature connectors to plug onto the target board. These connectors follow the standards of their respective designers (ARM for JTAG- ARM, ST for ICC-ST7 and SWIM-STM8, etc.). Here are the internet links where you can find the schematics of these adapters: RLink adapter schematic spdfs links ADP JTAG-μPSD ADP ICC-ST7 and SWIM-STM8 ADP JTAG-SWD (replaces old ADP JTAG-ARM) ftp:// ftp:// ftp:// Older adapter schematics links ADP ICC-ST7 v1.0 ADP ICC-ST7 v1.2 ftp:// ftp:// a KEOLABS brand

15 RLink Getting Started 4. Using RLink 4.6 Connecting and powering To avoid electrical problems, potentially leading to hardware damage or personal health injury, it is advised to follow these simple recommendations. Ensure the target board is powered either from RLink (if the ADP allows it) or from its own power supply, but not from both. If the target board is powered from its own supply, you must make sure that it is properly isolated from the mains (because the RLink is connected to ground via the USB and host PC). Ensure the voltage is in the voltage range supported by your RLink, ADP and protocol. You should follow this order as much as possible to connect and power the PC/RLink/ADP/target system. The order of connecting non-powered connections (points 1, 2 and 3) is not very important, but it is critical to make all non-power connections (1, 2, 3) before all the power connections. (4, 5): 1. Plug/unplug the jumpers on the RLink ADP(s) required for your target device and protocol (or REva board) as required (if there are jumpers on your ADP). Refer to the documentation of Ride for your target architecture (for example GettingStartedSTM8.pdf) for details about these jumpers, and if/how to set them. 2. Connect the RLink to the RLink ADP(s) required for your target device and protocol (not required for Primers and REva boards). 3. Connect the RLink ADP to the target board. (be careful about the way you plug it if the connector does not provide a key) (not required for Primers and REva boards). 4. Power the target board (if it is not powered by the RLink). Be careful about using an isolated power supply, as the RLink will be connected to the Ground through the USB and PC. 5. Plug the RLink's USB to the PC. (after powering the PC itself of course). Unpowering and disconnecting should be performed in the reverse order. Note: Using a different (dis)connection order is possible in some circumstances, but is not recommended and not guaranteed. If some hardware is damaged when doing this, the warranty does not apply. Finally, note that using a different (dis)connection order can appear to work, whilst it in fact slowly deteriorates your hardware and eventually burns it a KEOLABS brand

16 4. Using RLink RLink Getting Started 4.7 Operating conditions The RLink is designed to operate in "normal laboratory conditions". This means, among other things: Respect the voltage ranges, power scheme (ensure isolation from mains, avoid conflict between several power supplies, etc.), order of connecting and powering, etc. mentioned earlier in this document (which depends on the version of RLink, target protocol, etc.) Use it only with official, licensed (or demo) software from KEOLABS or its partners. Use it in reasonable conditions of temperature, pressure, electro-magnetic environment, etc. Avoid exposing it to strong or persistent mechanical or electromechanical stress (shocks, vibrations, heat, pressure, microwaves, magnets, X-Ray, etc.) even when not using it. Do not open it (unless our support team tells you to). Do not try to reverse-engineer it in any way, including software. This list is not exhaustive. Use your common sense to avoid problems. Note: Failure to meet these requirements will make you lose the warranty on the product. Even if you meet these requirements, KEOLABS and its partners cannot be held responsible of any damage or loss occurring from the use of RLink and its associated products (ADPs, Primers, REva/OP4 motherboards and daughterboards, etc.). 4.8 Support and FAQ The KEOLABS and Raisonance web sites contain a lot of useful information, documents and FAQ: a KEOLABS brand

17 RLink Getting Started 4. Using RLink 4.9 Checklist of items to prepare before contacting support Here is a list of questions that we will ask whenever you request any support from KEOLABS about RLink. If you plan to contact us by , telephone or on the forum, please include all this information in your message (or have it ready if calling on the phone). For an easier, faster and more efficient support, the best is to copy the text from this form into an answer each question in the line below the question, and then send it to support@raisonance.com. The rest of this section lists an obsolete list of questions to give you an idea of the information needed. 1 Questions on the KEOLABS tools 1.1 What is your customer serial number, if you have one? (open Ride7, click Help>About and look for Serial Number, or send us a screen shot). 1.2 What is the version of your software? (Ride7) If in Ride6, what is the build number of your Ride6? (open Ride6, click Help>About and look for BN, or send us a screen shot) If in Ride7, what are the versions of your Ride7 kits? (open Ride7, click Help>About and look for Installed Products, or send us a screen shot) If you are using other software (STVD, CAPS,...), we will need the name(s) and version number(s). 1.3 What kind(s) of RLink(s) do you have? (REva? RLink-Std? RLink-STX?) 2 Questions on the RLink 2.1 Does the PWR LED turn ON when you connect RLink to the PC? 2.2 Is the USB driver correctly installed? Does the BUSY LED turn ON and then OFF when you connect RLink to the PC? Does RLink appear under the Jungo section in Windows Device Manager when it is plugged in? What is your host system (CPU, version of Windows, service pack(s), etc.)? Can you read the RLink serial number? (open RFlasher, select any ST7 or ARM device as target and RLink as programmer, click Connect to RLink) Note: if you think that the USB driver is not installed, reinstall Ride7 or run RLinkUSBInstall.exe which is available on the Ride7 CDs and in the Ride7 installs. 2.3 What is your RLink(s) serial number? (see above. the SN is not written on the RLink itself). 3 Questions on the target 3.1 What is your target CPU (we need the complete name of the derivative)? 3.2 What is your target board(s)? Please send us the schematic of the board If it is a commercial board, what is its manufacturer and exact reference? (and have you modified it?) What is the configuration of the jumpers and switches on the board, if any? How do you power the board? If we need to get the real board for testing, under what conditions would it be possible (sign a NDA, return it after the tests,...)? a KEOLABS brand

18 4. Using RLink RLink Getting Started 4 Questions on the problem itself. 4.1 Please describe the problem you are experiencing as precisely as you can What software are you using (Ride7, RFlasher, CAPS, STVP7,...)? What is the simplest sequence of operation that we can perform in order to trigger the problem? How does the problem manifest itself (please write down all error messages, if any, or make screen shots)? Did the problem appear in a configuration that was working before? If the answer to the previous question was "yes", can you think of anything that changed between the last time it succeeded and the first time it failed? 4.2 Do you have any comment or personal interpretation of the problem? 4.3 Please do a few tests If you have other software, (from ST, Signum,...) does it all show the same problem? (please tell us what you could test and how it went) If you have other programmers/debuggers, even other RLinks, do they all show the same problem? (please tell us what you could test and how it went) If you have other boards/cpus, (demo boards,...) even other boards identical to the one showing the problem, do they all show the same problem? (please tell us what you could test and how it went) If the problem appears with a particular application, can you send us your project? Note: If we need it, we will need the complete project folder, including source, include, object, hex and listing files. In some specific cases, the hex file might be enough, but we cannot guarantee that. We can sign NDAs if this information is confidential. We can work with a reduced version of the application, if it shows the same problem, but we need a complete project that we can recompile at KEOLABS If you only have one application, please try to reproduce the problem with one of the examples provided with Ride7, or try to reduce your application until there is only the minimum remaining to show the problem. 5 Can we share the information in the answers to this form with our partners? Note: This is NOT for advertising purposes. Depending on the problem you have, our partners (mostly, but not only, the chip manufacturers like ST) might have more technical information than us on the cause of your problem and be able to answer faster and more accurately, or just to help us a little. Thank you for taking the time to answer. You will see that it has not been wasted, because it allows us to provide you with fast and efficient support a KEOLABS brand

19 RLink Getting Started 5. Conformity 5. Conformity 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 a KEOLABS brand

20 6. Glossary RLink Getting Started 6. Glossary Term CScript RScript Description Microsoft Windows' script tool Script language a KEOLABS brand

21 RLink Getting Started 7. Index 7. Index Additional help or information...4 CE...19 Compliance...19 Conformity...19 Directive...19 DriverStore...8 DRVSTORE...8 FCC...19 Found new hardware...8 incorrect files...8 Jungo...8 Jungo_WinDriver_2000_NT_XP...9 KEOLABS...4 Lead...19 MS_WinUSB_XP_Vista...9 Purpose of this manual...4 Raisonance...4 rlink_winusb...9 RLinkCapab...8, 9 RLinkDRV...9 RLinkUSBInstall.exe...8 ROHS...19 Scope of this manual...4 Vista Vista WEEE...19 WinDriver...8 windrvr6...9 WinUSB...8 XP...9 XP XP a KEOLABS brand

22 8. History RLink Getting Started 8. History Date Description 24/02/09 Initial version. V0.2 16/06/09 Add alternative recovery procedure for USB driver installation. V1.0 23/04/12 Add information about RLink4 and operating conditions. 10/07/12 Modified cover page, final page and section 1.3 Additional help or information for KEOLABS a KEOLABS brand

23 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 license 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