winIDEA Help

This chapter explains setup for reset in initialization operation. Open Hardware / CPU Options / Reset.

 

 

 

Require correct Device ID when attaching to SoC

Device ID is verified if it is present in the  SoC (SFR/JSON) description. The following warnings are displayed in the Progress window:

 

 

Configured boot core

Selected the boot core according to your application design.

 

 

RESET pin

RESET pin connected

When the reset line from the target is not connected to the debug connector, disable winIDEA to check the level of reset pin by uncheck the checkbox off. This option is checked by default.

 

Latch target RESET

System reset line drivers on debugger side and target side are open collector. Either can pull it low. Assertion from target side can be missed by debugger if it is shorter than poll period of reset line. When the option is checked (default) the debugger hardware latches the reset line when being pulled low by target system. When polled next time the winIDEA acknowledges reset state. This yields a delay from when line is asserted by the target reset and the acknowledgement by winIDEA and potential restart of application. An example is an application where the CPU is periodically set into a power save mode and then woken up by an external reset circuit. In such case a delay introduced by the debugger would yield application not operating properly.

When the target voltage falls below 3 V, the MCU is in reset. However, the reset line is not pulled down, so such reset could be undetected by winIDEA until the reset line falls below logical one, which may take up to 10 seconds. In order to quickly detect such a reset, the Vref line is regularly polled, and when it falls below 3 V, winIDEA shows that the target is in reset. This functionality is only available when the Latch target RESET option is enabled. Polling Vref is executed during the idle cycles in the debugger, and since it takes up to 10 ms to perform a poll, it may affect other functions that are performed during the idle cycles of the debugger, such as data acquisition (DAQ).

 

Drive RESET while Detached:

•no - BlueBox will not drive the RESET line. RESET will or will not occur depending on your application design.

•Low - BlueBox will pull down the RESET line. RESET will most likely not occur.

•High - BlueBox will pull up the RESET line. RESET will most likely occur.

Make sure that this option is set to Low. Other possibilities let the RESET line go high and a flash programmed application will run for about 40ms before a debug mode sequence is started by the debugger. Application runaway can cause problems with debugger connecting to the MCU debug unit.

 

RESET drive mode:

•Open Drain - RESET pin is configured as an open drain output. This is the preferred configuration. winIDEA can also detect when the external circuit on the target activates the RESET pin.

•Push-Pull - RESET pin is configured as a push-pull output. Should be used with caution. The external circuit on the target must not actively drive the RESET pin, otherwise the debug adapter might get bricked.

•None - RESET pin is configured as read-only. The Latch target RESET functionality is not changed.

 

Not all RESET drive modes are available in all configurations, e.g., None mode is not supported by iC5000.

 

 

At Initialization

Disable watchdog

This option is checked by default on devices which have internal watchdog enabled by default. In the opposite case this option is greyed out.

 

Suspend peripherals while stopped

When this option is checked, selected peripheral functions (e.g., timers) are stopped when the application is stopped. Peripheral functions can be selected via the button . It is generally recommended that this option is checked, as this results in more predictable behavior of the debugged application when using these peripheral functions.

Refer to the microcontroller and architecture reference manuals for details.

 

 

 

Detect Watchdog reset

winIDEA detects whether a reset has occurred within a configurable time period after the reset has been released. Watchdog detection is checked only after Reset/Program/Attach is performed from a disconnected debugger (Debug / End Session) and not on every Reset/Program/Attach.

The detection feature is disabled by default. However, you can specify the time period (in milliseconds) for checking the target's reset. The Progress window displays the results, e.g. Detecting watchdog activity for 1000 milliseconds. Reset asserted, probably watchdog activity.

 

 

RAM Initialization

RH850 internal RAM is ECC protected. After reset, it needs to be initialized before it can be read and written – without returning error status. Normally, the RAM should be initialized by the startup code, but for easier debugging, you can use either Always or Auto (Download) option.

 

Never

Set the option to Never when it’s required to analyze a SoC state after reset. Use case would be to download the code to the flash with this option set. Next, power cycle the complete system and perform a debug reset only. At that point internal RAM is untouched by a debugger, and the microcontroller power-on state can be inspected.

 

Always

winIDEA initialize internal RAM after CPU reset and before download.

 

Auto (Download)

winIDEA initialize internal RAM before download.

 

When the initialize option is enabled, the debugger initializes internal RAM by writing zeros to RAM cells. RH850 families vary wildly in implemented RAM structures. For example, next to Local RAM there may also be Retention RAM and one or more Global RAM sections. Initialization of all structures is therefore not guaranteed. The user application must do it in any case to be able to run, when a debugger is not attached.

 

Local RAM initialization may be required by the debugger to be able to handle debugger access to device code and data flashes. Both device flashes are also ECC protected. So, if they have non-programmed areas, any data access to them will cause an ECC fault exception (severity depending on device family). Therefore, winIDEA loads into internal RAM specific UMI monitors that communicate with built-in Renesas flash libraries to check if the designated flash area is safe to read, for example. RAM content is restored after UMI operation is completed.

 

Note that when the code is run, winIDEA may start reading variables  in Rt.Watch before the RAM ECC has been initialized by the application, and that in turn may lead to FEINT/SYSERR trap handler. One solution could be an .ini file that turns ECC checking off after RESET.

 

 

Initialization

Primarily, initialization sequence is used on On-Chip Debug systems to initialize the CPU after reset to be able to download the code to the target (CPU or CPU external) memory.

Typically, there is no need to use the initialization sequence in case of the RH850. Initialization sequence may be required on some CPU families when it is required by the application being debugged. The debugger executes initialization immediately after reset and then downloads the code. Detailed information may be found in the Initialization Sequence help topic.

 

 

 

Cleanup before Detach

This call point extends the emulation detach and is called on:

•Disconnect (Debug / End Session)

•Detach procedure (Debug / Detach)

 

By default the script runs all cores.