RLink - Raisonance Microcontroller.. Questions on the Raisonance tools (we will need this information even for the simplest question). Your Serial Key (Serial Number software purchased before June 2. Atmel SAM7S/SE ARM-based Flash MCUs is a step up from 8/16-bit MCU with added performance, extended memory, and optimized system integration. ARM Microcontroller books. This tutorial-based book is giving you the key concepts required to develop programs in C with a Cortex M- based processor. For software purchased after June 2. Raisonance Support Extranet account under Home . What is the version of your software? What kind(s) of RLink(s) do you have? Questions about the RLink. Does the PWR LED turn ON when you connect the RLink to the PC? KEOLABS' Raisonance brand application development tools (compilers, debuggers, programmers, integrated development environments) for ARM Cortex, ARM7, ARM9, 8051. The original ARM7 was based on the earlier ARM6 design and used the same ARMv3 instruction set. The ARM710 variant was used in a CPU module for the Acorn Risc. UM10470 All information provided in this document is subject to legal disclaimers.Is the USB driver correctly installed? Does the BUSY LED turn ON and then OFF when you connect RLink to the PC? Does the RLink appear under the Jungo section in Windows device manager when it is plugged in? What is your host system? Can you read the RLink Serial Number? Questions on the target..
What is your target CPU? What is(are) your target board(s)? Please send us the schematic of the board. If it is a commercial board, who is its manufacturer and what is its exact reference? 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? Questions on the problem itself.. What software are you using? How does the problem manifest itself? Did the problem appear in a configuration that was working before? If the answer to the previous question was ? Please make a few tests.. If you have other software, (from ST, Signum, ..) do they all show the same problem? If you have other programmers/debuggers, even other RLinks, do they all show the same problem? 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? If the problem appears with a particular application, can you send us your project? 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 here at Raisonance. If you only have one application, please try to reproduce the problem with one of the examples provided with RIDE, or try to reduce your application until there is only the minimum remaining to show the problem. Do you allow us to share the information in the answers to this form with our partners? 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. In January 2. 00. Microsoft Windows XP SP3 driver installation procedure changed the way drivers are selected when there are several candidates. It uses the . inf file date tag to select between the drivers that it finds and chooses the latest (in previous versions it asked which one to take, when it found several). It also always searches on CDs, even when you tell it not to(previously, it searched CDs only if you asked it to, and only if it did not find a preinstalled driver in Driver. Store). As a result, it now tries to use the RLink. Win. USB driver, which is for Vista, when it should use the Jungo driver for XP. All CDs that were shipped before that to distributors along with RLinks, Primers or REva boards might show this problem (only on XP with automatic update activated, or very recent Windows with brand new PCs or CDs). For this you must plug in the RLink and tell the Windows Device Manager to uninstall the driver. In case of problems, here is an advanced procedure for that, more complex but with more chance of success. You must also take care not to let Windows search in . So, if you select the manual driver search, you must point to . There are no specific problems with executing Ride. RFlasher. 7 on Windows. RLink USB driver on Windows Vista and/or 6. PCA: Versions of RIDE after 2. Win. USB/RLink. Win. USB) for Windows Vista and Vista. You must reinstall all your RIDE kits to use the new driver. You might also need to uninstall the old driver (Vista. You can download the latest software from the Raisonance Support Extranet. Here is a version (V7. V) of the installation that should work in these systems (as well as the older systems like Windows XP and older that use the old driver (Jungo/RLink. WDP)): ftp: //www. Support/RLink/RLink. Here some things to try to make it work. I don't expect that to have much effect, but it's cleaner to try it. Then, unplug the RLink. In Driver. Store, try to remove the directories. If you cannot, remove as many of the files in them as you can. Also remove the registry entries if you manage to do it. You'll need to change the ownership to yourself, recursively, then give . Being an administrator is not enough with Vista. You have to trick it all the time. So you must also search. C: \Windows\System. DRVSTORE\File. Repository\Windrvr. C: \Windows\System. DRVSTORE\File. Repository\RLink*.*. When you have removed everything you can, run RLink. USBInstall again (in admin mode, not just while being logged as admin) leave it at least 2 minutes to complete and then plug the RLink. Check that you see the BUSY LED turning ON (means the RLink is started) and then OFF. Why? A: In recent versions of GCC, which are provided with Ride. C code is often split in two (or more) parts. The first part is for initialization and the second part for execution. For a block of C code, the initialization of all lines of C code in the block is done first, followed by all the executions. This allows factorization of the initialization parts between several lines of C code or other really efficient optimizations. This also often makes people think that there is a bug in the compiler or debugger when in fact it's just optimization. For example.. The first block is for initialization and the second block is for execution. If you only look at the C code, you might think that it has executed the line but in fact the LEDs have not changed. But if you go on stepping a few times, then it will go back to this line and perform the execution a little later. Activate optimization only after the C code is validated. Code very similar to yours has been tested with every optimization level and all compiler options during the validation process of the compiler (unless you are doing something very, very, very unusual). Watch out for 'split code' (two or more blocks of assembler for a single line of C). Also, give it a few more C steps as second chance. This is normal optimization. Always use volatile variables for delay loops and such. So if your code works in opti level 0, but not in opti level 1, it is not necessarily a compiler bug. It is more likely to be a non- volatile variable that should have been volatile, or something like that. Then, when it is validated, you can either put it back in the calling function, or declare the sub- function as static, so that it is inlined in the calling function and produces no more code than really needed. This makes it reasonable to use the optimizer for programs that might have bugs. Wih this license debugging code size is limited. Compiler and programming code size are unlimited. Connect for JTAG (except DBGRQ). NOTE: RST (CPU reset) and TRST (JTAG reset) are two different signals. They must not be connected to each other, and they must both be connected between the RLink and the target CPU. The correct configuration is described below. RLink CPU. RST - -- -- -- -- -- -- -- -- -- -- - xxxxx. RSTTRST - -- -- -- -- -- -- -- -- -- -- - xxxxx. TRST. On your board make sure that. CPU. these two signals are never connected together (). Programing and Debugging processes. An RLink serial number (starts with the string . An Rlink serial number allows activation of a software license (typically limited licenses . Software capabilities under these licenses are indicated in the product information in the online catalog here at www. Getting Started documents that are provided on the Raisonance Support Extranet. All these connectors follow the standards designed by their respective designers (ARM for ARM- JTAG, ST for ST7- ICC and STM8- SWIM, etc.). You will need this if you need to use a protocol that did not exist when you purchased the RLink, or if you loose or break an adapter. They MUST NOT be connected to each other! Other programmers from ST or that have been in any way validated by ST, very probably use the same connector. To make sure, look at the ICC documentation from ST. Here is the pinout summary. GND: 1, 3, 5, 1. 0ICCDATA: 2. ICCCLK: 4. RESET: 6. VCC: 7. ICCSEL/VPP: 8 (not used for ST7. Litexx)1. 2MHz: 9. Which position should I use for internal movable connectors of the adapter ? They are not for the ST7. Why can't my RLink connect to STR7. A: There are two known issues you can check: The STR7. MB3. 93. B cannot be programmed by RLink and Ride. This issue is fixed in versions more recent than Ride. RKit- ARM 1. 1. 3. If you have this version or older, the workaround is. Close Ride. 7 and RFlasher. There is a problem on RLink- STD (the version in the dark gray box) on the STR7. STR7. 11, 7. 12 or 7. What can I do? A: Sometimes, a working STR9 stops working after a program is downloaded to it. This is very probably the manifestation of a hardware bug that is documented in section 2. STR9 . Most of the time, it happens when you are trying to write the clock configuration part of your project. The number of NOPs needed depends on the PLL frequency. The total NOPexecution time must be greater than 1. OSC clock periods (one PLL clock is needed toexecute one NOP). Workaround using Rev B and Rev D1. To prevent the CPU from losing its clock, do not disable the PLL while it is the selectedmain clock source.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2017
Categories |