> 4.4.1 | Module States

> The module can exist in the following six states in relation to a Java application, the serial interfaces, GPIO and I2C/SPI. See [1] for information about the AT commands referenced. A state transition diagram is shown in Figure 11.
> This section shows how Java applications must share AT parsers, GPIO pins and I2C/SPI resources. DAC, ADC and DAI are not discussed here.
> Color legend for the following figures:

> 4.4.1.1 | State 1: Default – No Java Running

> This is the default state. The Java application is inactive and there is an AT interface with CSD on ASC0 as well as ASC1. The initial state of the pins is according to [4].
> Figure 8: Module State 1

> 4.4.1.2 | State 2: No Java Running, General Purpose I/O and I2C/SPI

> The Java application is inactive. There is an AT parser with CSD on ASC0 as well as ASC1. Up to ten I/O pins are used as general purpose I/O plus a I2C/SPI interface. The pins are configured by AT^SCPIN and AT^SSPI (refer [1]).
> Figure 9: Module State 2

> 4.4.1.3 | State 4: Default – Java Application Active

> The Java application is active and ASC0 and ASC1 are used as System.out and/or CommConnection. Java instances of AT commands are connected to the available AT parsers. The Java application is activated with AT^SJRA (refer to [1]) or autostart.
> Figure 10: Module State 4

> 4.4.1.4 | State 5: Java Application Active, General Purpose I/O and I2C/SPI

> The Java application is active and ASC0 and ASC1 are used as System.out and/or CommConnection. The Java application is activated with AT^SJRA. The I/O pins are configured with AT^SCPIN, the I2C/SPI interface with AT^SSPI. Refer to [1] for AT command details.
> Figure 11: Module State 5