RF60 Datasheet, PDF (154/157 Pages) –

RF60 CRYSTAL-LESS SOC TRANSMITTER v1.0
35. IDE Development Environment and Debugging Chain
The debugging chain consists of an evaluation board or an evaluation keyfob, USB debug adapter or a
USB based ToolStick, and the IDE development environment.
The debugging chain is using the C2 two wire interface to provide an on-chip debugging capability. The
environment can load the standard OMF-51 object and symbol file only, not any proprietary extensions of
that format as used by some tool manufacturers. For example, on Keil platform it means that the BL51
linker must be used. The IDE will not load outputs generated by the Keil LX51 linker. On Raisonance plat-
form the output is the OMF-51 compliant and the file extension is AOF.
The IDE debugging environment has means to reset the chip without cycling the power. By pressing the
Reset inside of the IDE the digital part of the device is reset and device startup boot sequence is invoked.
All registers are reset to their initial states and all of the Factory values are refreshed in RAM and regis-
ters. If the part is a Factory part, the previously loaded CODE/XDATA RAM content is not disturbed. If the
part is a User part then the User data region is loaded as well, overwriting the content of the CODE/XDATA
RAM.
Using IDE is the only way to reset the chip without cycling the power to it or shutting it down and waking it
up.
35.1. Functionality Limitations While Using IDE Development Environment
Even though using the IDE development environment preserves almost all of the chip func- tionality, there
are some limitations the user should be aware of. Given that the code is running from RAM and that the
C2CLK shares the pin with LED output current driver (GPIO[5]), they are two functionality lim- itations for
code development while using IDE:
1. The user cannot put a Factory or User chip into the shutdown mode and then wake it up by pressing a
button (pulling any of the GPIO to ground). When the chip is in shutdown mode the power to all digital is
lost and therefore the RAM content with the user code will get erased.
2. The LED driver cannot be used when the device is connected to the debug adapters (USB debug
adapter or a ToolStick).
3. Once the part is finalized, programmed as Run part, no further debugging is possible.
Tel: [phone]
Fax: [phone]
154
E-mail: [e-mail] http://www.hoperf.com