- Tip & Tech
- Code Snippet
- Tizen Projects
- Tip & Tech
- Code Snippet
- Tizen Projects
The Smart Development Bridge (SDB) is a command line tool that communicates with a connected target device (it can be an emulator instance or a real Tizen device).
The SDB is a client-server program that consists of a client, daemon, and server:
sdbcommand at the prompt.
You can find the SDB tools in the
The SDB can communicate with a target over a USB or Wi-Fi connection. To use the SDB over USB, open the system settings of the target device, and enable the USB debugging mode in Settings > More system settings > Developer options (the location can vary depending on the device).
Run the SDB with a shell using the following command:
> sdb [option] <command> [parameters]
You can specify a target of
<command> by entering the following in the
-d: Sends the
<command>to a connected device and returns an error if there are other devices.
-e: Sends the
<command>to a running emulator instance and returns an error if there are other instances.
-s <serial number>: Sends the
<command>to a target through
For more information on commands and parameters, see the following table.
Table: SDB commands
||Lists all connected target instances.|
||Connects to a target through TCP/IP.|
||Disconnects from a TCP/IP device.
By default, the port 26101 is used if there is no specified port number. If you use this command with no additional arguments, all connected TCP/IP devices are disconnected.
||Copies a file or directory recursively from the host computer to the target.|
||Copies a file or directory recursively from the target to the host computer.|
||Launches the shell on the target instance if the
||Uninstalls the application from the device by using its
||Sets up requests' arbitrary port forwarding from the host's local port to the target's remote port.|
||Monitors the content of the device log buffers.|
||Starts the server.
||Stops the running server.|
||Prints the connection status with the target device:
||Prints the serial number for connecting the target device.|
||Prints the connection status for a specified device continuously.|
||Switches between the root and developer account mode.
||Shows the version number.|
||Shows the help message.|
Before issuing SDB commands, it is helpful to know which target instances are connected to the SDB server. In response to the
devices command option, the SDB prints the serial number (a string created by the SDB to uniquely identify a target instance) and connection status for each connected device. The connection status can be
offline (the instance is not connected to the SDB or is not responding) or
device (the instance is connected to the SDB server).
The output format for each instance is the following:
[serialNumber] [state] [targetName]
The following snippet shows an example of the command output:
> sdb devices List of devices attached emulator-26100 device myemulator1 emulator-26200 device myemulator2
By specifying the
[serialNumber] in the command, you can execute SDB commands on a specific target device. If you execute a command without specifying the target instance while multiple devices are available, the SDB generates an error.
You can use the
push command options to copy files to and from the target instance. These options let you copy arbitrary directories and files to any location in the target instance, if you have the right permissions:
> sdb pull <remote> [<local>]
> sdb push <local> <remote> [-with-utf8]
[-with-utf8] parameter creates the remote file with the UTF-8 character encoding.
In both commands, the
<remote> parameters refer to the paths to the target files and directory on your computer (local) and on the target instance (remote). For example:
> sdb push foo.txt /tmp/foo.txt
You can use the
shell command option to issue target shell commands, with or without entering the SDB remote shell on the target. To issue a single command without entering a remote shell:
> sdb shell <shell_command>
You can also enter a remote shell on an emulator or device:
> sdb shell
To exit from the remote shell, press the Ctrl + D key or use the
exit command to end the remote shell.
You can use all shell commands, such as the following, if you have the right permissions:
ls, rm, mv, cd, cp, mkdir, touch, echo, tar, grep, cat, chmod, rpm, find, uname, netstat
You can use the SDB to install and uninstall the Tizen package file on the target instance:
installcommand option pushes the package file to the target and installs it. The
<path_to_tpk>parameter defines the path to the TPK file. The following command shows an example:
> sdb install /home/tizen/ko983dw33q-1.0.0-i386.tpk
uninstallcommand option kills the application, if running, and removes the package from the target. The
<pkg-id>is a unique 10-digit identifier for the application. The following command shows an example:
> sdb uninstall ko983dw33q
You can set up arbitrary port forwarding of requests from a specific host port to a specific remote port on a target instance.
The format for the
<remote> parameters is
tcp:<port>. The following example shows how to forward requests from the host port 26102 to the device port 9999:
> sdb forward tcp:26102 tcp:9999
After setting up port forwarding, development tools between the device and host can work remotely. For example, GDB (the GNU Project debugger) on a host/gdbserver on a device, and gdbserver on a device opened with the tcp:9999 port:
> sdb shell gdbserver:9999 hellotizen
GDB in a host connects to localhost:26102:
> gdb hellotizen ... (gdb) target remote localhost:26102
You can see the target log messages using the SDB. To see the log output in your computer or from a remote SDB shell, use the
sdb dlog or
dlogutil command, respectively:
> sdb dlog [option] [<filter>]
The following table shows some options for the
sdb dlog and
Table: Log output options
||Writes the log to the
||Rotates the log file every
||Sets the maximum number of rotated logs to
||Sets the output format for log messages.
You can define which metadata fields are included in log messages by setting one of the following output formats:
[<filter>] parameter defines the tag of interest (the system component from which the message originates) and the minimum level of priority to report for that tag. The format is
<tag>:<priority>, and multiple filters must be separated with a space. The available priorities (from lowest to highest) are V (Verbose), D (Debug), I (Info), W (Warning), E (Error), and F (Fatal).
For example, to view all log messages of the error and fatal priority in addition to the MyApp tag messages of the debug priority (and higher), use the following command:
> sdb dlog MyApp:D *:E