User manual

Debugging with Hardware Tools Ride7 for ARM
- 28 -
• "Connect to RLink and read serial number" is useful for checking that 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 serial number message
includes information about your RLink’s capabilities and limitations for the currently
selected target microcontroller. See “RLink types and capabilities” above.
• "Check connection to target" allows you to read the JTAG IdCode of the chip. Use this to
test the connections and power of the target STRx or STM32.
• "Erase target now!" allows you to completely erase the target's FLASH (writing 0xFF).
• "Write target FLASH now!" programs the FLASH with the current application's hex file
generated by the linker. Then, launches the execution.
• "Dump target FLASH to hex file" reads the contents of the FLASH and writes it in a file
in hex format whose name is derived from the current application's name with the
extension .hex (<application name>.hex).
4.2.2.3 JTAG Parameters
 "Single Device" allows determining if there are several JTAG devices chained or only
one device.
The JTAG standard makes it possible to chain JTAG devices. Using JTAG chaining is a
complex process and should only be done if you have a good knowledge of the JTAG
protocol. This section of the debugging options allows you to configure Ride7 to access
an STRx or STM32 microcontroller that is chained with other JTAG devices.
The checkbox should remain checked if there is no other device in the chain. Otherwise,
you should uncheck it and enter 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.
 "Speed of the JTAG clock…" allows determining the clock speed.
If your CPU’s clock is slow, then you must tell Ride7 to use a slow JTAG clock. If the
JTAG clock is too fast compared with the target CPU’s clock, then communication will
fail. This section of the debugging options allows you to specify the JTAG clock speed:
Reducing the JTAG clock does not have very much influence on the programming and
debugging speed because the USB is the bottleneck for most operations. Therefore, don’t
be afraid to use this option and enter the value of your target’s clock speed in KHz.
Note that the RLink clock has a limited number of possible clock speeds. Ride7 will
select the closest possible value that is less than the value you required. The minimum
value is 400KHz. If your clock is slower than this, RLink might not be able to program
and/or debug it. You would then have to purchase JTAGjet, or develop your application
using a faster clock.