Please enable JavaScript to view this site.

winIDEA Help

Version: 9.21.246


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





Configured boot core

Selected the boot core according to your application design.



Note that this option does not change the boot core on SoC, but only informs winIDEA about which core is being used as a boot core.




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).


Stop after target RESET

CPU can be optionally stopped after the CPU reset is detected and handled. If the option is unchecked, the application is resumed upon reset release.


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

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 ThreeDots. 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.



This option, including its peripherals list, is available for specific microcontrollers only. If not supported, the option is greyed out.




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 RL78. 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.



Hot Attach function cannot be used for any flash programming or code download!


Copyright © 2024 TASKING Germany GmbH