The Debug-interface
Deutschmann Automation GmbH & Co. KG
17
UNIGATE
®
fieldbus gateway UNIGATE
®
EL - DeviceNet
™
V. 1.0
22.6.17
6
The Debug-interface
6.1 Overview of the Debug-interface
The UNIGATE
®
IC features a Debug-interface, that allows a step-by-step processing of a Script.
Normally this interface is only required for the development of a Script.
6.2 Starting in the Debug-mode
When applying power to the UNIGATE
®
(power up) the firmware will output the binary character
0 (0x00) after a self-test was carried out on this interface. If the UNIGATE
®
receives an
acknowledgement via this interface within 500 ms, it is in the Debug-mode. The
acknowledgement is the ASCII-character O (0x4F).
With the start in the Debug-mode the further execution of Script commands will be put to a stop.
6.3 Communication parameter for the Debug-interface
The Debug-interface is always operating with 9600 baud, no parity, 8 data bit, 1 stop bit. It is not
possible to change this parameter in the PROTOCOL DEVELOPER. Please consider the fact
that these settings have to be in accordance with those of the PC-COM-interface and that the
flow control (protocol) has to be set on „none“ there.
6.4 Possibilities with the Debug-interface
Usually the PROTOCOL DEVELOPER is connected to the Debug-interface. With it a
step-by-step processing of a Script, monitoring jumps and decisions and looking at memory
areas is possible. Moreover breakpoints can be set. It basically possesses all characteristics a
software-development tool is typically supposed to have. However, it is also possible to carry out
a Scrip-update via this interface.
From Script version [27] on you can also output data with the Script command
"
SerialOutputToDebugInterface
". Please also pay attention to the remark in the manual
’
PROTOCOL DEVELOPER
’.
6.5 Commands of the Debug-interface
The commands for the use of the Debug-interface are described in the instruction manual
PROTOCOL DEVELOPER.
Restriction:
•
Script commands that make a data exchange with the Ext. Card are not supported in Debug
mode.
•
The command
„SerialOutputToDebugInterface“
, referred to in chapter 6.4, as well as
the command
„SerialInDebugInterface“
, is not supported.
•
Redirection of the Debug interface to the Application interface (X1).
With the script command
„ScriptStartBehaviour(DbgOverApl);“
debugging to con-
nector X1 of the application is possible again, so that the commands for the Ext. Cards are
supported.
Note:
The script command
„ScriptStartBehaviour(DbgOverApl);“
must be placed
directly after the script info.
First, the script must be loaded, because only after a reboot it is possible to debug via the appli-
cation interface. If the command is taken out, the script has to be started once before you can
debug on the Debug interface.