Skip to end of banner
Go to start of banner

Unexpected resets when debugging netX 90 with netX Studio - how to fix this?

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Q

When debugging a netX 90 application with netX Studio, we observe that the netX 90 gets reset several times while the debug session is started. A "hidden" reset is performed even when the debug settings mode is set to 'Attach', which is completely unexpected. Is that intended? Is there a workaround?

A

This behavior is not intended. The expected behavior depending on the debug settings mode is this:

  • Run mode - attach to the running CPU, perform a reset and then halt the CPU at the first instruction
  • Attach mode - attach to the running CPU and halt it at the current instruction

Currently, the netX Studio debugger performs some unexpected resets in both modes:

  • Run mode - the CPU is reset more than once before the debug session is started, which results in unwanted executions of the program currently residing in the application internal flash
  • Attach mode - the CPU is reset once before the debugger attaches, which makes it impossible to debug an application which was already running for some time (so far observed only with the NXHX 90-JTAG and NXHX 90-MC evaluation boards when using the on-board FTDI chip)

These are known issues that will be fixed in upcoming versions of netX Studio.

Part of these issues are related to the OpenOCD reset configuration which is currently configured to use a hardware reset. Until this is resolved, the workaround is to switch to a software reset. If using a software reset is not an issue for you, then you can patch your existing netX Studio installation as described below.


How to apply the patch?

  1. Download and unzip the patch to a temporary location:
  2. Run the batch script inside to apply the patch:
    netxstudio_netx90_reset_config_patch.bat


What does the patch do?

The patch updates some of the existing OpenOCD configuration files which are located inside the BuildTools folder:

C:\ProgramData\Hilscher GmbH\netX Studio CDT\BuildTools\openocd\config

After applying the patch, netX Studio will switch to using a software instead of a hardware reset when debugging netX 90.

After running the flasher or auto-flasher, a reset has to be performed in order to be able to debug the application side. Before the patch, netX Studio would always perform a reset before starting a debug session in 'Run' mode, and this would ensure that the application CPU is started. After the patch, this extra reset is removed, and the netX needs to be reset manually when required.

See also...

  • No labels