59
CHAPTER 8
ASCII command interface
8.3 ASCII command interface
8.3.1 Introduction
Once set up using J-Flash, the Flasher ATE can be driven by any application or just a simple
terminal using ASCII commands.
Every known command is acknowledged by the Flasher ATE and then executed. After com-
mand execution, the Flasher ATE sends an ASCII reply message.
Note
There are situations where the execution of a known command is rejected with
#NACK:ERRxxx if Flasher ATE is currently busy and the received command is not al-
lowed to be sent while Flasher ATE is busy
8.3.2 General command and reply message format
• Any ASCII command has to start with the start delimiter
#
.
• Any ASCII command has to end with simple carriage return (’\r’, ASCII code 13).
• Commands can be sent upper or lower case.
8.3.3 General usage
Reply messages must be considered in each case. In general, a new command must not be
sent before a reply for the last one has been received. The least the “#ACK” needs to be
received by the controlling application before sending a new command for a flash module
not yet executing a command.
For the Flasher ATE, all commands triggering a flash programming function (
#AUTO, #CAN-
CEL, #ERASE, #PROGRAM, #VERIFY
) may be used for other modules, before the current op-
eration has been finished. Please note that in this case the overall finish indicator “#DONE”
will be sent when all commands have been executed.
8.3.4 Settings for ASCII interface via RS232
Flasher is driven via a RS232 serial port with the following initial interface settings:
• 9600 baud
• 8 data bits
• no parity
• 1 stop bit
The baud rate can be changed by using the
#BAUDRATE
command.
8.3.5 Settings for ASCII interface via Telnet
A client application can connect to the Flasher ATE via Telnet on port 23. Find below a
screenshot of Flasher which is remote controlled via Telnet:
Flasher ATE User Guide (UM08035)
© 2017-2018 SEGGER Microcontroller GmbH
