Java User’s Guide
5.9 System Out
49
s
wm_java_usersguide_v12
Page 41 of 123
2008-02-25
Confidential / Released
5.8.5
Java Commands
There is a small set of special Java AT commands:
•
AT^SJRA, start a Java application
•
AT^SJNET, configuration of Java networking connections
•
AT^SJOTAP, start and configuration of over the air provisioning
•
AT^SJSEC, security configuration
Refer to the AT command Set
[1]
.
5.8.6
AutoExec Function
Under Java, the AutoExec function’s AT command execution has some restrictions (see
[1]
for
details on the AutoExec function). If an AT command is executed, neither URC nor command
response are indicated to the Java application. Therefore, it is recommended to use the
AutoExec function under Java only with commands that shut down the module, e.g., with
AT+CFUN=0,1, as a watch dog. Any other AT command execution should be implemented with
Java means and the ATCommand class.
5.9
System Out
Any output printed to the System.out stream by a Java application can be redirected to one of
the serial interfaces, a file, a "NULL" device (i.e. the output will be discarded) or a UDP socket
for using the debugger from an IDE. The configuration can be done at any time using the AT
command AT^SCFG (see
[1]
for details) and is non-volatile.
5.9.1
Serial interfaces
System.out can be written to any of the serial interfaces ASC0, ASC1 or USB. If System.out is
redirected to one of the interfaces used for the Java CommConnection, the interface will be
shared between System.out and the CommConnection. This will result in mixed output, if data
is written to the CommConnections OutputStream and something is printed via System.out at
the same time.
Using System.out and CommConnection on the same serial interface may be done if a device
connected to the serial port is only transmitting data to the module. It is recommended to
ensure already in the HW design that output from the module cannot be transferred to a con-
nected device.
