Q (A Generic Error)

OpenOCD shows an error. Those errors are often cryptic and it is not possible to derive a solution out of the message. This page collects the possible issues behind.

A (Application Core not Running)

The most common issue of OpenOCD error messages originates from the fact, that the application core is not started. The text visible in the OpenOCD console is as follows:

Info : netx90.app: hardware has 0 breakpoints, 0 watchpoints
Info : netx90.comm: hardware has 6 breakpoints, 4 watchpoints

OR:

Info : netx90.app: hardware has 0 breakpoints, 0 watchpoints
Error: timed out while waiting for target halted

The issue, that the application core seems to have 0 breakpoints arises from the fact, that it is was not provided with a core clock signal.

Solution:

Console mode or Alternative Boot Mode is active. The dip switches S400.5 and S400.6 should be in OFF position.
The device has to be flashed properly with a set of binary images that match together. Usually the device has to have the following images flashed.
HWC, FDL, NXI, NAI
The HWC has an option under General Configuration where one is able to enable and disable the Application Core.
The DC19XX and DC18XX chips need different HWCs.
Optional device files are MWC, MXI, NXE, NAE

A (Device not reachable)

S701.1 Should be in the correct position. In OFF for JTAG via FTDI to USB or in ON for the MIPI20 Connector.

Error: Invalid ACK (7) in DAP response
Error: JTAG-DP STICKY ERROR
Error: Could not initialize the debug port
Error: An error occurred while setting up the scan chain
shutdown command invoked

JTAG connection can be checked via the Flasher tool of netX Studio. If the interface name romloader_jtag_netX90_COM@HXHX_90-JTAG is visible, the board is available.

If there is something readable wit (*MPW*) please contact hilscher support immediately.

A (Reset not working)

The debugger output contains the following line:

Failed to run the reset code: -4

This indicates that the reset is not working.

Please review your wiring following this FAQ: JTAG connectors and signals

A (No Binary or *.elf available)

Error in final launch sequence

Error in final launch sequence
Failed to execute MI command:
load "C:\\Users\\YourName\\Desktop\\V2 Project\\netXStudio_PNSV5_simpleConfig\\build\\debug\\Targets\\netx90_sdram.elf"
Error message from debugger back end:
Load failed
Load failed

Info : accepting 'gdb' connection on tcp/3333
Error: JTAG-DP STICKY ERROR
Error: Failed to write memory at 0x10000004
Error: JTAG-DP STICKY ERROR
Error: Failed to write memory at 0x10000204
Info : dropped 'gdb' connection

Solution: Build the project first.

See also...

Page:

A Raspberry Pi supports multiple SPI signals, which ones are used for communication between RPi and netHAT?
Page:

Can other expansion HAT boards be used in combination with the netHAT?
Page:

Is other protocol fimware than PROFINET, EtherCAT and EtherNet/IP available for netHAT?
Page:

The SYS LED of netHAT flashing alternately yellow and green, is this normal?
Page:

How fast can be the data update cycle with an application running above netHAT?
Page:

Where can I find API documentation about the netHAT supported protocols?
Page:

Is there a 3D CAD model of the netHAT available?
Page:

A netX52 chip could support multiple communication channels at a time, does the netHAT support more than one channel?
Page:

Can I use netHAT with more than 32 bytes inputs or outputs?
Page:

Which operating systems does the netHAT support?
Page:

Which SD card size do I require?
Page:

Whom should I contact if I have technical questions relating to the netHAT?
Page:

Which power supply unit do I require?
Page:

Where can I find documentation and further information of the netHAT module?
Page:

Supported Flash Types netX100/500

Browser not supported