SCT Scout SC4415 User manual

6815 –8 Street NE, Suite 295
Calgary, AB T2E7H7 Canada
www.signalcraft.com
This document contains proprietary information and shall not be disclosed, in whole or in part, to any party
without the expressed and written consent of an authorized representative of SignalCraft Technologies Inc. ©2013
User Manual
SC4415 - Scout
Number: SCT-UM026Fvc
Date: 2019-08-23

Document# SCT-UM026FVC Page 2 of 46 Confidential
Revision History
Revision
Date
Author
Description
1.0
2017-11-03
K. Sumlak
Initial Release
1.1
2019-02-20
K. Sumlak
Update for release version 1980
1.2
2019-08-23
K. Sumlak
Update for release version 2030

Document# SCT-UM026FVC Page 3 of 46 Confidential
Table of Contents
Revision History............................................................................................................................................................2
Table of Contents..........................................................................................................................................................3
1. Overview...............................................................................................................................................................7
1.1 Device Details......................................................................................................................................................7
1.2 Symbols ...............................................................................................................................................................7
2. Hardware ..............................................................................................................................................................8
2.1 Overview .............................................................................................................................................................8
2.2 Power ..................................................................................................................................................................9
2.3 USB ......................................................................................................................................................................9
2.3.1 Driver Installation ...........................................................................................................................................9
2.4 Ethernet ............................................................................................................................................................10
2.5 IO Interface .......................................................................................................................................................10
2.5.1 Pin Map.........................................................................................................................................................11
2.5.2 IO Details.......................................................................................................................................................12
2.5.3 VIO ................................................................................................................................................................12
2.6 Status LED..........................................................................................................................................................13
2.7 Physical Details..................................................................................................................................................13
3. Programming ...................................................................................................................................................... 14
3.1 Overview ...........................................................................................................................................................14
3.2 Command Interface ..........................................................................................................................................14
3.2.1 Prompts ........................................................................................................................................................14
3.2.2 Formatting ....................................................................................................................................................14
3.2.3 Help System ..................................................................................................................................................15
3.2.4 Command Queue..........................................................................................................................................15
3.2.4.1 Immediate Mode .................................................................................................................................15
3.2.4.2 Buffer Mode .........................................................................................................................................15
3.2.5 Data Queue...................................................................................................................................................16
3.2.6 Events ...........................................................................................................................................................17
3.3 Application Modes ............................................................................................................................................18
3.3.1 Boot Mode ....................................................................................................................................................18
3.3.2 MIPI-RFFE Mode ...........................................................................................................................................19
3.3.2.1 Summary ..............................................................................................................................................19
3.3.2.2 Details ..................................................................................................................................................19
3.3.3 SPI Mode.......................................................................................................................................................20

Document# SCT-UM026FVC Page 4 of 46 Confidential
3.3.3.1 Summary ..............................................................................................................................................20
3.3.3.2 Details ..................................................................................................................................................20
3.3.4 MIPI-I3C Mode ..............................................................................................................................................22
3.3.4.1 Summary ..............................................................................................................................................22
3.3.4.2 Details ..................................................................................................................................................22
4. Maintenance .......................................................................................................................................................25
4.1 License...............................................................................................................................................................25
4.2 System Firmware...............................................................................................................................................26
5. Reference............................................................................................................................................................ 27
5.1 General Commands...........................................................................................................................................27
5.1.1 version ..........................................................................................................................................................27
5.1.2 update...........................................................................................................................................................27
5.1.3 license ...........................................................................................................................................................27
5.1.4 mode.............................................................................................................................................................27
5.1.5 vio .................................................................................................................................................................27
5.1.6 led .................................................................................................................................................................28
5.1.7 status ............................................................................................................................................................28
5.1.8 read...............................................................................................................................................................28
5.1.9 buffer ............................................................................................................................................................28
5.1.10 trigger_in ..................................................................................................................................................29
5.1.11 trigger_out................................................................................................................................................29
5.1.12 clear..........................................................................................................................................................29
5.1.13 delay .........................................................................................................................................................30
5.1.14 gdw ...........................................................................................................................................................30
5.1.15 gdr ............................................................................................................................................................30
5.1.16 gpw ...........................................................................................................................................................30
5.1.17 gpr ............................................................................................................................................................31
5.2 RFFE Commands................................................................................................................................................31
5.2.1 clock ..............................................................................................................................................................31
5.2.2 hsdr ...............................................................................................................................................................31
5.2.3 rr ...................................................................................................................................................................31
5.2.4 err .................................................................................................................................................................32
5.2.5 erl..................................................................................................................................................................32
5.2.6 rzw ................................................................................................................................................................32
5.2.7 rw..................................................................................................................................................................32
5.2.8 erw ................................................................................................................................................................33
5.2.9 ewl ................................................................................................................................................................33

Document# SCT-UM026FVC Page 5 of 46 Confidential
5.2.10 mrw ..........................................................................................................................................................34
5.3 SPI Commands...................................................................................................................................................34
5.3.1 clock ..............................................................................................................................................................34
5.3.2 config ............................................................................................................................................................34
5.3.3 select.............................................................................................................................................................34
5.3.4 polarity..........................................................................................................................................................35
5.3.5 protocol ........................................................................................................................................................35
5.3.6 w_command .................................................................................................................................................35
5.3.7 w_address.....................................................................................................................................................35
5.3.8 w_write.........................................................................................................................................................36
5.3.9 w_read ..........................................................................................................................................................36
5.3.10 wait_read .................................................................................................................................................36
5.3.11 s_write......................................................................................................................................................36
5.3.12 s_read.......................................................................................................................................................37
5.4 I3C Commands ..................................................................................................................................................37
5.4.1 clkset.............................................................................................................................................................37
5.4.2 pullup ............................................................................................................................................................38
5.4.3 err_msg.........................................................................................................................................................38
5.4.4 init.................................................................................................................................................................38
5.4.5 view...............................................................................................................................................................38
5.4.6 add ................................................................................................................................................................39
5.4.7 remove..........................................................................................................................................................39
5.4.8 new_da .........................................................................................................................................................39
5.4.9 hot_join.........................................................................................................................................................40
5.4.10 ccc_write ..................................................................................................................................................40
5.4.11 ccc_read ...................................................................................................................................................40
5.4.12 vendor_write ............................................................................................................................................41
5.4.13 vendor_read .............................................................................................................................................41
5.4.14 ibi_read.....................................................................................................................................................42
5.4.15 legacy_write .............................................................................................................................................42
5.4.16 legacy_read ..............................................................................................................................................42
5.4.17 sdr_write ..................................................................................................................................................43
5.4.18 sdr_read ...................................................................................................................................................43
5.4.19 sdr_rsvd ....................................................................................................................................................44
5.4.20 ddr_write..................................................................................................................................................44
5.4.21 ddr_read...................................................................................................................................................44
6. Additional Information........................................................................................................................................ 46

Document# SCT-UM026FVC Page 6 of 46 Confidential
6.1 Support..............................................................................................................................................................46
6.2 Regulatory .........................................................................................................................................................46
6.2.1 FCC Compliance ............................................................................................................................................46

Document# SCT-UM026FVC Page 7 of 46 Confidential
1. Overview
This document is a complete reference guide for the SC4415 and includes information such as hardware specifications
and operating instructions.
1.1 Device Details
The SC4415 Scout is a flexible multi-protocol Serial Bus Controller capable of generating various serial protocol
communications. Currently, the supported protocols include MIPI-RFFE, MIPI-I3C, and SPI. Additionally, Scout offers
multiple General-Purpose-IOs which can further expand the control and monitoring capabilities for any application. For
more details about the physical and electrical characteristics, refer to Section 2.
Determinism, flexibility, and efficiency have been key design principles for the SC4415. This enables users to perform
various operations with guaranteed and predictable timing making Scout ideal for manufacturing and development
applications. Section 3 describes the unique feature set of the SC4415 such as configurable IO voltage levels, bus clock
rates, operation sequence control, and protocol specific functionality.
1.2 Symbols
Below are the document symbols which appear in this manual.
Important Note
Programming Example

Document# SCT-UM026FVC Page 8 of 46 Confidential
2. Hardware
This section describes the SC4415 hardware features and specifications in detail.
2.1 Overview
The SC4415 is contained within a compact enclosure with all required interfaces exposed at either end. The product
label located on the top of the enclosure provides model information along with a pin map for quick reference. Figure
2.1-1 provides an illustration of the enclosure. Dimensions and other specifications can be found in Section 2.7.
Figure 2.1-1 –SC4415 Scout
The exposed interfaces on the ends of the enclosure are shown below in Figure 2.1-2 and 2.1-3.
Figure 2.1-2 –Power and Data Connections
Figure 2.1-3 –Device Interface
Detail about each interface can be found by referencing the item number, shown in red, against Table 2.1-1.
Item
Description
Section
1
External 5VDC Input (optional)
2.2
2
Status LED
2.6
3
USB Device Port
2.3
4
Ethernet Connector
2.4
5
SMA Trigger Connector
2.5
6
IO Interface Connector
2.5
Table 2.1-1 –Device Interface Details

Document# SCT-UM026FVC Page 9 of 46 Confidential
2.2 Power
Scout can be powered by using either USB Bus power or the external power input. The external power input may be
required in cases where the USB host is unable to reliably provide enough current to supply Scout. This can be a
common issue with USB hubs that are not able to guarantee 500mA on all ports simultaneously.
The power requires for the SC4415 are shown below in Table 2.2-1.
Description
Value
Input Voltage
4.4 Vdc –5.25Vdc
Input Current (Min)
500mA
Table 2.2-1 –Power Requirements
2.3 USB
The USB interface is the primary programming interface used for Scout. In order for Scout to properly operate with a
host computer, the device drivers must be installed as described in Section 2.3.1. The USB interface is USB2.0
compatible and makes use of a Type-B connector. To connect Scout to a host computer, typically a USB Type-A to USB
Type-B cable is required.
Once the device drivers for Scout have been installed, Scout will instantiate itself as a virtual com-port device when
plugged into the host machine. The programming interface can be accessed using simple serial communication
functions which are built into the majority of programming languages.
For a more interactive experience, a simple terminal emulator application, such as Tera Term or PuTTY, can be used to
establish a serial connection to Scout. For the best experience, ensure that the terminal emulator is set to a
monospaced font such as Lucidia Console or Consolas.
The Serial configuration required to communicate with Scout is shown in Table 2.3-1.
Description
Value
Baud Rate
9600 –921600 (emulated)
Data
8bit
Parity
None
Stop
1bit
Flow Control
None
Table 2.3-1 –Serial Configuration
For more details about the Scout’s application programming interface, refer to Section 3.
2.3.1 Driver Installation
In order for Scout to properly communicate with a computer system using USB, the device drivers must be installed.
This section describes the procedure to acquire and install the Scout device driver.
Do not connect the Scout hardware to the PC until the USB device driver has been installed.
The current version of the Scout device driver can be obtained from the Scout support portal. To access the Scout
support portal, refer to the link in Section 6.1. The Scout installation files are contained in a .zip archive. Once
downloaded, extract the archive to a known location such as the Desktop.
As a result of extracting the archive, two files can now be observed sct_scout.cat and sct_scout.inf. To install the
driver, right click the sct_scout.inf file and select install as shown in Figure 2.3.1-1.

Document# SCT-UM026FVC Page 10 of 46 Confidential
Figure 2.3.1-1 –Scout Driver Installation
A Windows Security prompt, shown in Figure 2.3.1-2, will display showing information about the device driver. Confirm
that the Publisher is indicated as SignalCraft Technologies Inc. Select Install to complete the driver installation process.
Figure 2.3.1-2 –Windows Security Prompt
Once the installation is complete, connect the Scout device using the USB port. In Windows Device Manager, Scout will
be identified under the Ports list as SC4415 Scout.
2.4 Ethernet
The Ethernet interface is non-functional at this time. A future firmware version may enable the Ethernet interface as an
alternative programming interface.
Do not make any connections to the Ethernet connector at this time as this may cause undesirable
behavior.
2.5 IO Interface
Scout has been designed with flexibility in mind. For this reason, the SC4415 utilizes a 30-pin 0.100” male header for
the IO Interface. Table 2.5-1 provides the details about the IO interface connector.
Description
Value
Manufacture
Samtec
Part Number
TSS-115-04-G-D-RA
Table 2.5-1 –IO Connector Details
This connector provides a high degree of compatibility with various connector mates such as board to board, female
sockets, and individual test leads. Using the information in Table 2.5-1, the mechanical details of the IO Interface
connector can be determined which will assist in choosing a mating connector for a custom application. Additional
connector accessories are available from SignalCraft Technologies for the SC4415.

Document# SCT-UM026FVC Page 11 of 46 Confidential
Also included as part of the IO interface is a standard SMA female connector for a trigger signal. The SMA trigger
provides a compatible connection to other test equipment which makes use of similar coaxial connectors for trigger or
synchronization IO.
2.5.1 Pin Map
The IO Interface pin map can be observed in Figure 2.5.1-1 as well as on the product label of the SC4415. Table 2.5.1-1
provides a brief functional description of each of the pin types.
Figure 2.5.1-1 –IO Interface Pin Map
Type
Description
VIO
IO Voltage Reference. Can be internally generated
or externally supplied to establish a common IO
voltage between Scout and the connected
devices.
APIO
Application Specific IO. These pins are dedicated
for application specific purposes which are mode
dependent and are not available for general
purpose.
GPIO
General Purpose Input-Output. These pins are for
general purpose use and are available in any
application mode.
TRIG
Hardware Trigger. Used for triggering and
synchronization.
GND
Signal ground reference.
Table 2.5.1-1 –IO Pin Descriptions

Document# SCT-UM026FVC Page 12 of 46 Confidential
2.5.2 IO Details
There are three main IO groups that are available on the IO Interface, APIO, GPIO, and TRIG. Each of the IO groups is
explained in detail below.
APIO:
The APIO pins refer to Application Specific Input-Output. These pins are under control of the
selected software application and perform dedicated functions. The user does not have direct
control over the state or function of the APIO pins. Refer to Section 3.3 for more details about the
function of the APIO pins for each application mode.
GPIO:
The GPIO pins refer to General Purpose Input-Output. These pins are available to the user at all
times and each pin can be configured using the programming interface as either an input or an
output. As an output, pins can be set to either a logic high or a logic low state. As an input, the
current logical state present on the pin can be read. Refer to Section 5.1 for information on the
software interface for the GPIO pins.
TRIG:
The TRIG pins refer to Trigger Input-Output. The direction and function of each trigger pin is
described in Table 2.5.2-1 below.
PIN
Description
Section
TRIG1
Input trigger, logical OR with TRIG2
Section 3.2.4 and 5.1.10
TRIG2
Input trigger, logical OR with TRIG1
Section 3.2.4 and 5.1.10
TRIG3
Output Trigger
Section 5.1.11
Table 2.5.2-1 - TRIG IO Functionality
All of the IO Interface pins have built in protection to ensure that the SC4415 is protected against accidental voltage
surges such as Electrostatic Discharge (ESD). Table 2.5.2-2 lists the electrical specifications for the IO Interface.
Description
Value
Condition
Operating range
0V –VIO
Absolute limit
-0.5V min, 4.6V max
Typical capacitance
5.0pF
Input transition rate
5ns/V max
Output current, per IO
±8mA, ±20mA
VIO = 1.2V, VIO = 3.3V
Output current, all IO
100mA max
VIO Internal (VIO > 0)
Output current, all IO
20mA max
VIO External (VIO = 0)
Table 2.5.2-2 –IO Electrical Specifications
Applying a voltage greater than the VIO reference for an extended period of time can cause
permanent damage to the device.
2.5.3 VIO
The IO Voltage reference pins, VIO, are used to establish an IO reference between the Scout and the connected
devices. VIO can be configured as either an input (supplied externally) or an output (generated internally) using the
programming interface and the VIO command.
When VIO is configured as an output, the on board voltage generation is enabled and provides the user with the ability
to set VIO to 1.2V, 1.8V, 2.5V or 3.3V. Alternatively, VIO can be configured as an input to accept an externally provided
voltage which may be generated from other equipment. Table 2.5.3-1 provides the electrical specifications for VIO.
Description
Value
Input Operating range
0.8V –3.5V
Output set-points
1.2V, 1.8V, 2.5V, 3.3V

Document# SCT-UM026FVC Page 13 of 46 Confidential
Output current (Max)
20mA
Table 2.5.3-1 –VIO Electrical Specifications
2.6 Status LED
When Scout is first powered up, the status LED provides an indication that the unit has booted and is ready for use.
Once the LED is illuminated, Scout is in a responsive state and will accept connections via the programming interface.
The status LED can also be manually controlled using the programming interface and the LED command. This may
prove to be useful to help identify a specific Scout unit in a circumstance where multiple units may be connected to a
single host computer and the relationship between the programming interfaces and the physical devices is unknown.
2.7 Physical Details
The physical dimensions of the SC4415 are detailed in Figure 2.7-1.
Figure 2.7-1 –Product Dimensions
Additional specifications such as environmental, weight, and ESD protection are listed in Table 2.7-1.
Description
Value
Operating
Temperature
0°C to 70°C
Storage Temperature
-40°C to 85°C
Humidity
5% to 85% non-condensing
ESD Protection
HBM JESD22-A114E Class 3B exceeds 8000V
MM JESD22-A115-A exceeds 200V
CDM JESD22-C101C exceeds 1000V
Table 2.7-1 –Additional Product Specifications

Document# SCT-UM026FVC Page 14 of 46 Confidential
3. Programming
3.1 Overview
For the purposes of this manual, all descriptions and examples will be from the perspective of a terminal emulator
connected to the Scout hardware as described in Section 2.3.
The application programming interface for the SC4415 is a simple command and response type of interface similar to
that of terminal applications. Commands are defined for each application mode and are made up of a combination of
configuration and operational command types. The user can invoke the defined commands by sending the command
name followed by the required arguments. Additional details about command formats are discussed in Section 3.2.2.
3.2 Command Interface
This section describes the features and the usage of the SC4415 Command Interface.
3.2.1 Prompts
Once a connection has been established with the SC4415, the command prompt will become visible. The command
prompt indicates that Scout is ready to accept a new command. The types of command prompts are shown in Table
3.2.1-1.
Type
Prompt
Section
Standard Prompt
->
3.2.4.1
Primary queue
B>
3.2.4.2
Secondary queue
b>
3.2.4.2
Event Message
E>
3.2.6
Table 3.2.1-1 –Command Prompt Types
As general good practice, it is important for automated applications to always wait to receive the command prompt
prior to sending a new command. Failure to do so can result in a potential data overflow which may cause the
programming interface to become unresponsive. Programming examples which follow this practice can be obtained by
referring to Section 6.1 and visiting the Scout Support Portal.
If the command prompt is not visible upon connecting to Scout, pressing the enter key will re-
print the current command prompt.
3.2.2 Formatting
Any numerical arguments may be represented as either decimal or hexadecimal values provided the hexadecimal value
is prefixed by the characters ‘0x’. For example, if a command argument is provided using the decimal value of ‘10’, the
hexadecimal equivalent would be entered as ‘0xA’.
Commands are described using a specific notation in order communicate the proper usage of a command and its
arguments. Table 3.2.2-1 provides some examples for how a command and its syntax is described. The synopsis and
details for each command can be obtained using Scout’s built-in help system as described in Section 3.2.3.
Definition
Details
CMD1
The Command CMD1 does not require any arguments
CMD2 <ARG1> <ARG2>
The Command CMD2 has two mandatory numeric arguments, ARG1
and ARG2
CMD3 <ARG1> [<ARG2>]
The Command CMD3 has one mandatory numeric argument, ARG1,
and one optional numerical argument, ARG2.

Document# SCT-UM026FVC Page 15 of 46 Confidential
CMD4 [<ARG1>[<ARG2>]]
The Command CMD4 has two optional numeric arguments,
however, ARG2 cannot be specified without first providing ARG1.
CMD5 ‘STRING’| <ARG1>
The Command CMD5 has one mandatory argument which can be
either a string value of ‘STRING’ or a numeric value defined for
ARG1.
CMD6 <ARG1=’1’> [<ARG2>]
CMD6 <ARG1=’2’>
The Command CMD6 has one mandatory numeric argument ARG1.
When ARG1 is set to the value of 1, ARG2 can optionally be
specified. When ARG1 is set to the value of 2, ARG2 cannot be
specified.
Table 3.2.2-1 –Command Notation
3.2.3 Help System
Scout has a built-in help system which allows users to view the list of available commands as well as obtain detailed
help information for the command specified. The available command list can be retrieved at any time by executing the
‘help’ command without providing any additional arguments.
->help
...
Detailed help for a specific command can be obtained by executing the ‘help’ command followed by the name of the
command or its abbreviated form. As a result, the command synopsis and details are returned as shown below with the
example ‘help version’.
->help version
NAME
version
SYNOPSIS
version
DESCRIPTION
Get the system information
DETAIL
Display the serial number and version information
3.2.4 Command Queue
The Command Queue is the mechanism that stores and processes specific commands received from the Programming
Interface. The commands that make use of the Command Queue are identified in Section 4 by the ‘Queue’ field.
The behavior of the Command Queue can be modified in a number of ways to suit a specific application. Some of the
available options include command sequencing, inter-command delay control, and various triggering source selections.
The Command Queue behavior can be returned to its defaults at any time by executing the Clear command.
3.2.4.1 Immediate Mode
By default, the Command Queue is configured for Immediate Mode. Any command executed from the Programming
Interface will not be stored in the Queue and will be processed immediately. Immediate Mode is indicated by use of
the Standard Prompt as indicated by Table 3.2.1-1.
3.2.4.2 Buffer Mode
Buffer Mode allows for commands to be stored into one of two Command Queues until a trigger signal is received.
Doing so enables commands to be sequenced and executed in a deterministic fashion. The Inter-command delay can
be tightly controlled by inserting Delay commands. The additional delay, specified in terms of clock cycles, helps to
ensure the required command timing can be achieved.

Document# SCT-UM026FVC Page 16 of 46 Confidential
The selection of the Command Queue can be made when Buffer Mode is enabled using the Buffer command. The
enabled Command Queue is indicated by Primary Queue prompt or the Secondary Queue prompt as shown in Table
3.2.1-1. The execution behavior of the Primary and Secondary Command Queue largely depends on the configuration
of the trigger signal which can be set using the trigger_in command. The trigger sources can be configured to either
execute the Command Queue in a one-shot fashion or in a repeated mode. The repeated mode allows for the content
of the Command Queue to persist between the received trigger signals.
The Command Queues has limited space to store commands. The majority of commands require only a single unit of
space while others may require up to 8 units. The free space available in the Command Queues can be observed by
executing the Status command.
In the example below, the primary buffer is selected and the prompt changes from the Standard Prompt to the Primary
Queue Prompt. Following this, two commands are queued into the Primary Command Queue. The trigger is then
configured as a software source with the repeat option enabled. Once the trigger is configured, the prompt returns to
the Standard Prompt and the Command Queue can be executed multiple times by invoking the software trigger.
# Enable Buffer Mode (Primary).
->buffer 1
# Queue two GPIO operations.
B>gpw 0x01 0x01
B>gdr
# Enable a Repeated Software Trigger.
B>trigger_in 1 1
# Execute Software Trigger twice.
->trigger_in 1
->trigger_in 1
3.2.5 Data Queue
The Data Queue is a temporary storage mechanism which holds the data which has been returned by various
commands. Depending on the type of command and its configuration, the amount of data returned will vary. When
accessing the Data Queue, the data order is maintained such that the bytes received first are the first to be returned
when read.
The data stored in the Data Queue is retained until it is read using the Read command. Depending on the arguments
provided with the Read command, a portion or all of the available data may be returned. When data is read or
dequeued, it is effectively shifted out of the queue meaning that it is only available to be read once.
The Data Queue manages its queue data differently depending on the current Command Mode. In Immediate Mode,
only the data received from the most recent command is retained in the queue. When Buffer Mode is enabled, the
Data Queue will retain all data received until the queue is read or the maximum storage capacity is exceeded.
Similar to the Command Queue, the Data Queue has limited storage space. The Status command can be used to obtain
the number of bytes available as well as a flag which indicates if the Data Queue is full. If the Data Queue becomes full,
the oldest data will be preserved while any new data will not be stored.
In the example below, two SPI Read commands are executed in Buffer Mode. In this case, the SPI Read Width has been
configured as one byte, therefore, each SPI read will return 5 bytes of data. The queued commands are then triggered
using the Trigger_in command which results in the execution of the two commands. Using the Status command, the
state of the Data Queue is observed to have 10 bytes are available. The Read command is then used to selectively
return only the first 5 bytes, formatted as Stream Format. The updated status of the Data Queue now indicates that 5
bytes of data remain in the queue. The remaining data bytes can be returned with subsequent reads.
# Enable Buffer Mode (Primary).
->buffer 1
# Queue two SPI Read operations.
B>s_read 5 0x1 0x30
B>s_read 5 0x1 0x40
# Execute a Single Software Trigger to

Document# SCT-UM026FVC Page 17 of 46 Confidential
# execute the Queued commands and exit Buffer Mode.
B>trigger_in 1
# Prompt returns to the Standard Prompt.
# 10 Bytes of data are available in the Data Queue.
->status
...
Data Queue
Queue Full : False
Bytes Queued : 10
# Read 5 Bytes, using stream formatting, from Data Queue.
# Data returned is 0x01FF348900.
->read 5 1
Data: 01FF348900
# 5 Bytes of data remain in the Data Queue.
->status
...
Data Queue
Queue Full : False
Bytes Queued : 5
3.2.6 Events
An Event is the occurrence of an action that is not a direct result of a user’s interaction with the Programming
Interface. Such events may occur in order to communicate protocol related bus errors, protocol interrupts, or
unexpected system related errors or warnings. The types of events that may occur largely depend on the protocol
Mode enabled.
Events are only communicated to the Programming Interface during idle time when a command is not being processed.
An Event is identified by the use of the Event Prompt as indicated by Table 3.2.1-1.
Due to the non-deterministic nature of Events, care must be taken to ensure that automated applications are able to
appropriately handle the occurrence of an event. In most cases, event messages can be disabled from being reported
to the Programming Interface. Refer to Section 3.3 for additional detail and about mode specific event and how to
configure them.

Document# SCT-UM026FVC Page 18 of 46 Confidential
3.3 Application Modes
The SC4415 is a serial bus controller capable of performing multiple serial protocols. In order to support multiple
protocols, the SC4415’s functionality has been broken up into several logical application modes. Table 3.3-1 provides
details about each of the application modes.
Mode
Description
Type
Section
Boot
Initial mode on power-up
Standard
3.3.1
RFFE
RF Front-End
Licensed
3.3.2
SPI
Serial Peripheral Interface
Standard
3.3.3
I3C
Improved Inter Integrated Circuit
Licensed
3.3.4
Table 3.3-1 –Application Modes
Applications modes are either standard or licensed. Standard modes are available for all devices whereas licensed
modes are available with the purchase of a license key. For more information about license keys and applying them to
an SC4415 device, refer to Section 5.1.3.
Each application mode enables a unique command set. In addition to the unique command set, a set of general
commands are also available in every mode. The general commands provide access to base functionalities of the Scout
such as command mode selection, trigger configuration, and GPIO functions. Table 3.3-2 lists the general commands
available.
Command
Description
Section
version
Get the system information
5.1.1
update
Update system components such as firmware or license
5.1.2
license
Get the licensed feature available
5.1.3
mode
Set the application operation mode
5.1.4
vio
Set the VIO voltage reference level or source
5.1.5
led
Set the front panel LED state
5.1.6
status
Get the system status and queue information
5.1.7
read
Return and display the data contained in the Data Queue
5.1.8
buffer
Enable Buffered Mode and select the active Command Queue
5.1.9
trigger_in
Trigger the execution of commands queued
5.1.10
trigger_out
Manually pulse the trigger output pin
5.1.11
clear
Exits Buffer Mode and aborts any pending triggers
5.1.12
delay
Wait for the specified number of clock cycles
5.1.13
gdw
Set the direction of the GPIO pins
5.1.14
gdr
Get the direction of the GPIO pins
5.1.15
gpw
Set the state of the GPIO pins
5.1.16
gpr
Get the state of the GPIO pins
5.1.17
Table 3.3-2 –General Commands
3.3.1 Boot Mode
The Boot mode is the mode of operation that is enabled upon power-up. The Boot mode has limited functionality as it
is primarily intended as a consistent starting point. The Boot mode is required as some devices may have a different
selection of available modes of operation depending on which features have been licensed for a specified device. The
available commands in this mode are Version, Update, License, and Mode. In most cases the only required action after
first booting Scout is to select the desired application mode.
The example below shows the user querying the mode of operation after Scout has been booted. The current
operating mode is listed as 0 which indicates the current mode as BOOT. The next operation shows the selection of the
desired operating Mode, in this case, it is SPI mode.

Document# SCT-UM026FVC Page 19 of 46 Confidential
->mode
Application Mode: 0
->mode 2
...
3.3.2 MIPI-RFFE Mode
When enabled, MIPI-RFFE mode enables the SC4415 to behave as an RFFE Master device.
3.3.2.1 Summary
The RFFE application mode is based on the MIPI-RFFE protocol specification v2.0, designed and maintained by the MIPI
Alliance. This document does not include RFFE protocol specific information such as protocol message formats or
timing information. For further detail about the RFFE specification, refer to mipi.org.
All rights reserved. This material is reprinted with the permission of the MIPI Alliance, Inc. No
part(s) of this material may be disclosed, reproduced or used for any purpose other than as
needed to support the use of the products of SignalCraft Technologies Inc.
There are two signals required for the RFFE application mode SCLK and SDATA. The SCLK signal is the serial clock signal
driven by the master and the SDATA is the bidirectional data line used to exchange data between master and slave.
The APIO pin functions for RFFE mode are shown in Table 3.3.2.1-1. For more information about the APIO pins refer to
Section 2.5.1.
APIO1
APIO2
APIO3
APIO4
APIO5
APIO6
APIO7
APIO8
SCLK
SDATA
Table 3.3.2.1-1 - APIO Pin Mapping for RFFE Mode
3.3.2.2 Details
The following features are available in this mode:
Register Read and Write
Extended Register Read and Write
Extended Register Long Read and Write
Masked Register Write
Half Speed Data Response (HSDR)
Configurable SCLK frequency from 100kHz up to 52MHz
The available commands specific to RFFE Mode are listed in Table 3.3.2.2-1. Details about the command and its usage
can be found by referring to the relevant section for the command in Section 5.2.
Command
Description
Section
clock
Set the RFFE SCLK rate
5.2.1
hsdr
Set the RFFE half speed data response
5.2.2
rr
Perform an RFFE Register Read operation
5.2.3
err
Perform an RFFE Extended Register Read operation
5.2.4
erl
Perform an RFFE Extended Register Read Long operation
5.2.5
rzw
Perform an RFFE Register Zero Write operation
5.2.6
rw
Perform an RFFE Register Write operation
5.2.7
erw
Perform an RFFE Extended Register Write operation
5.2.8
ewl
Perform an RFFE Extended Register Write Long operation
5.2.9
mrw
Perform an RFFE Masked Register Write operation
5.2.10
Table 3.3.2.2-1 –RFFE Command List

Document# SCT-UM026FVC Page 20 of 46 Confidential
3.3.3 SPI Mode
When enabled, SPI mode enables the SC4415 to behave as an SPI Master device.
3.3.3.1 Summary
The SPI application mode is based on the common Serial Peripheral Interface used by many devices and products.
There are four signals required to communicate with a slave device using the SPI application mode, CLK, MOSI, MISO,
and SS.
The CLK Signal is the serial clock and is always driven by the master device. The MOSI and MISO signals are the
unidirectional data lines used to exchange data between the master and slaves. The direction of the MOSI and MISO
signals differ with respect to a master versus a slave device and can be determined by understanding the naming
convention. MOSI stands for Master-Out-Slave-In, which indicates that the signal is driven by the master and received
by the slave(s). MISO stands for Master-In-Slave-Out, which indicates that the signal is driven by a slave and received by
the master device.
SPI allows for multiple slave devices to share a single SPI interface. In order to do so, slave devices must be explicitly
enabled to become active on the bus. This is achieved by asserting the Slave Select (SSn) line connected to each
individual slave device. The SC4415 supports three individual Slave-Select lines, SS1-SS3.
The APIO pin functions for SPI mode are shown in Table 3.3.3.1-1. For more information about the APIO pins refer to
Section 2.5.1.
APIO1
APIO2
APIO3
APIO4
APIO5
APIO6
APIO7
APIO8
CLK
MOSI
MISO
SS1
SS2
SS3
Table 3.3.3.1-1 –APIO Pin Mapping for SPI Mode
3.3.3.2 Details
The following features are available in this mode:
Standard SPI Read and Write operations
On-the-fly bus reconfiguration
Support for SPI Mode 0, 1, 2 and 3 (CPOL and CPHA)
Positive and negative Slave Select polarity
Configurable word widths for Command, Address, and Data
Configurable SCLK frequency from 50kHz up to 26MHz
The available commands specific to SPI Mode are listed in Table 3.3.3.2-1. Details about the command and its usage
can be found by referring to the relevant section for the command in Section 5.2.10.
Command
Description
Section
clock
Set the SPI Clock rate
5.3.1
config
Set the SPI interface full configuration
5.3.2
select
Set the active Slave Select line
5.3.3
polarity
Set the Slave Select line Polarity
5.3.4
protocol
Set the SPI protocol mode
5.3.5
w_command
Set the Command Width
5.3.6
w_address
Set the Address Width
5.3.7
w_write
Set the Write Data Width
5.3.8
w_read
Set the Read Data Width
5.3.9
wait_read
Set the number of wait cycles before the read data
5.3.10
s_write
Perform an SPI Write operation
5.3.11
s_read
Perform an SPI Read operation
5.3.12
Table 3.3.3.2-1 –SPI Command List