@@ -12,12 +12,12 @@ Obtain **hdc\_std** from the **prebuilt** directory at [developtools\_hdc\_stand
...
@@ -12,12 +12,12 @@ Obtain **hdc\_std** from the **prebuilt** directory at [developtools\_hdc\_stand
**Example:**
**Example:**
To obtain hdc\_std on Windows, obtain the executable file **hdc\_std.exe** from **prebuilt/windows** and place it in a directory on the disk.
To obtain hdc\_std on Windows, obtain the executable file **hdc\_std.exe** from **prebuilt/windows** and place it in a directory on the disk.
## Important Notes<a name="section19543134915210"></a>
## Important Notes<a name="section19543134915210"></a>
- If an exception occurs when you are using hdc\_std, run the **hdc\_std kill** command to kill the hdc\_std service or run the **hdc\_std start -r** command to restart the service process.
- If an exception occurs when you are using hdc\_std, run the **hdc\_std kill** command to kill the hdc\_std service or run the **hdc\_std start -r** command to restart the service process.
- If no device information is obtained after **hdc\_std list targets** is executed, use the task manager to check whether the **hdc.exe** process exists. If it exists, kill the process.
- If no device information is obtained after **hdc\_std list targets** is executed, use the task manager to check whether the **hdc.exe** process exists. If it exists, kill the process.
<tdclass="cellrowborder"valign="top"width="50%"><pid="p135611718111618"><aname="p135611718111618"></a><aname="p135611718111618"></a>hdc help or version information</p>
</td>
</tr>
</tbody>
</table>
Examples:
Examples:
...
@@ -53,43 +43,23 @@ hdc\_std -v / hdc\_std version
...
@@ -53,43 +43,23 @@ hdc\_std -v / hdc\_std version
| 1. error: device '***' not found<br/>2. Nothing to do... | 1. The device does not exist<br>2. The command appended to **-t key** does not exist. |
<tdclass="cellrowborder"valign="top"width="50%"><pid="p26051123547"><aname="p26051123547"></a><aname="p26051123547"></a>Key that identifies the device. The value is in the <emid="i15978153415214"><aname="i15978153415214"></a><aname="i15978153415214"></a>IP address:Port number</em> format or is a USB serial number.</p>
<trid="row1760531211546"><tdclass="cellrowborder"valign="top"width="50%"><pid="p232481834"><aname="p232481834"></a><aname="p232481834"></a>1. error: device '***' not found</p>
<pid="p12191171320"><aname="p12191171320"></a><aname="p12191171320"></a>②Nothing to do...</p>
</td>
<tdclass="cellrowborder"valign="top"width="50%"><pid="p85527328314"><aname="p85527328314"></a><aname="p85527328314"></a>1. The device does not exist.</p>
<pid="p10343124416277"><aname="p10343124416277"></a><aname="p10343124416277"></a>2. The command appended to <strongid="b18734194624117"><aname="b18734194624117"></a><aname="b18734194624117"></a>-t key</strong> does not exist.</p>
</td>
</tr>
</tbody>
</table>
Examples:
Examples:
This option must be used together with a specific operation command. The following uses the shell command as an example:
This option must be used together with a specific operation command. The following uses the shell command as an example:
**hdc\_std list targets**\(obtain device information\)
**hdc\_std list targets**\(obtain device information\)
**hdc\_std -t _key_ shell**\(replace _key_ with the device information obtained\)
**hdc\_std -t _key_ shell**\(replace _key_ with the device information obtained\)
>You can connect to multiple devices from the device you use for development. Each device has a unique key. The key can be _IP address:Port number_ for a device connected through a network or the serial number for a device connected through USB.
>You can connect to multiple devices from the device you use for development. Each device has a unique key. The key can be _IP address:Port number_ for a device connected through a network or the serial number for a device connected through USB.
## Querying the Device List<a name="section174891132104218"></a>
## Querying the Device List<a name="section174891132104218"></a>
...
@@ -100,33 +70,13 @@ The following command is used to query the device list:
...
@@ -100,33 +70,13 @@ The following command is used to query the device list:
<tdclass="cellrowborder"valign="top"width="50%"><pid="p6334859174310"><aname="p6334859174310"></a><aname="p6334859174310"></a>1. A list of connected devices</p>
<pid="p57581926125318"><aname="p57581926125318"></a><aname="p57581926125318"></a>2. No device information is found.</p>
</td>
</tr>
</tbody>
</table>
Examples:
Examples:
...
@@ -140,35 +90,15 @@ The following commands are available:
...
@@ -140,35 +90,15 @@ The following commands are available:
| 1. Mount finish<br/>2. Returned information | 1. Information returned when the operation is successful.<br/>2. Information returned when the operation fails. |
<pid="p43471519204114"><aname="p43471519204114"></a><aname="p43471519204114"></a>2. Returned information</p>
</td>
<tdclass="cellrowborder"valign="top"width="50%"><pid="p1551336123011"><aname="p1551336123011"></a><aname="p1551336123011"></a>1. Information returned when the operation is successful.</p>
<pid="p2034731984115"><aname="p2034731984115"></a><aname="p2034731984115"></a>2. Information returned when the operation fails.</p>
<tdclass="cellrowborder"valign="top"width="50%"><pid="p18405337142911"><aname="p18405337142911"></a><aname="p18405337142911"></a>Triggers the service restart.</p>
<trid="row15405163702915"><tdclass="cellrowborder"valign="top"width="50%"><pid="p0976152811311"><aname="p0976152811311"></a><aname="p0976152811311"></a>①Kill server finish</p>
<tdclass="cellrowborder"valign="top"width="50%"><pid="p10405123732915"><aname="p10405123732915"></a><aname="p10405123732915"></a>1. Information returned when the operation is successful.</p>
<pid="p19405337152916"><aname="p19405337152916"></a><aname="p19405337152916"></a>2. The operation fails.</p>
<tdclass="cellrowborder"valign="top"width="50%"><pid="p1860525413414"><aname="p1860525413414"></a><aname="p1860525413414"></a>Restarts the service process if it has started.</p>
<tdclass="cellrowborder"valign="top"width="50%"><pid="p14129038443"><aname="p14129038443"></a><aname="p14129038443"></a>IP address and port number of the device to be connected</p>
<tdclass="cellrowborder"valign="top"width="50%"><pid="p24693194612"><aname="p24693194612"></a><aname="p24693194612"></a>Disconnects from the specified device.</p>
<tdclass="cellrowborder"valign="top"width="50%"><pid="p1353282314492"><aname="p1353282314492"></a><aname="p1353282314492"></a>1. The operation fails.</p>
<pid="p053312316491"><aname="p053312316491"></a><aname="p053312316491"></a>2. The operation is successful.</p>
<tdclass="cellrowborder"valign="top"width="50%"><pid="p81911527145413"><aname="p81911527145413"></a><aname="p81911527145413"></a>1. The operation fails.</p>
<pid="p4191192720546"><aname="p4191192720546"></a><aname="p4191192720546"></a>2. The operation is successful.</p>
</td>
</tr>
</tbody>
</table>
Example:
Example:
...
@@ -339,40 +187,20 @@ hdc\_std tmode usb
...
@@ -339,40 +187,20 @@ hdc\_std tmode usb
Restarts the daemon process and connects to the device over TCP.
Restarts the daemon process and connects to the device over TCP.
<tdclass="cellrowborder"valign="top"width="50%"><pid="p18198921171715"><aname="p18198921171715"></a><aname="p18198921171715"></a>Port number used to connect to the device</p>
<tdclass="cellrowborder"valign="top"width="50%"><pid="p17426133416542"><aname="p17426133416542"></a><aname="p17426133416542"></a>1. The operation fails.</p>
<pid="p20426834195419"><aname="p20426834195419"></a><aname="p20426834195419"></a>2. The operation is successful.</p>
>After this command is executed, the remote daemon process exits and restarts, and the TCP connection is enabled by default. If you do not include **port-number** in this command, a random port will be used to connect to the device.
>After this command is executed, the remote daemon process exits and restarts, and the TCP connection is enabled by default. If you do not include **port-number** in this command, a random port will be used to connect to the device.
<tdclass="cellrowborder"valign="top"width="50%"><pid="p176225193115"><aname="p176225193115"></a><aname="p176225193115"></a>Path of the file to send</p>
<tdclass="cellrowborder"valign="top"width="50%"><pid="p1634515316"><aname="p1634515316"></a><aname="p1634515316"></a>Destination path on the remote device</p>
<pid="p0550151385512"><aname="p0550151385512"></a><aname="p0550151385512"></a>2. File transfer result</p>
</td>
<tdclass="cellrowborder"valign="top"width="50%"><pid="p1955091315517"><aname="p1955091315517"></a><aname="p1955091315517"></a>1. The operation fails.</p>
<pid="p1555041375519"><aname="p1555041375519"></a><aname="p1555041375519"></a>2. The operation is successful.</p>
<tdclass="cellrowborder"valign="top"width="50%"><pid="p1783912455333"><aname="p1783912455333"></a><aname="p1783912455333"></a>Path on the local device to receive the file</p>
<tdclass="cellrowborder"valign="top"width="50%"><pid="p179411118193416"><aname="p179411118193416"></a><aname="p179411118193416"></a>File path on the remote device</p>
<tdclass="cellrowborder"valign="top"width="50%"><pid="p117511052144218"><aname="p117511052144218"></a><aname="p117511052144218"></a>Replaces an existing application.</p>
<tdclass="cellrowborder"valign="top"width="50%"><pid="p16720113145610"><aname="p16720113145610"></a><aname="p16720113145610"></a>1. The operation fails.</p>
<pid="p8720031185611"><aname="p8720031185611"></a><aname="p8720031185611"></a>2. The operation is successful.</p>
<tdclass="cellrowborder"valign="top"width="50%"><pid="p167181136125610"><aname="p167181136125610"></a><aname="p167181136125610"></a>1. The operation fails.</p>
<pid="p1371811369562"><aname="p1371811369562"></a><aname="p1371811369562"></a>2. The operation is successful.</p>
</td>
</tr>
</tbody>
</table>
Example:
Example:
...
@@ -569,31 +289,13 @@ The following commands are available:
...
@@ -569,31 +289,13 @@ The following commands are available:
<tdclass="cellrowborder"valign="top"width="50%"><pid="p2481349195711"><aname="p2481349195711"></a><aname="p2481349195711"></a>Execution result of the command</p>
</td>
</tr>
</tbody>
</table>
Examples:
Examples:
...
@@ -637,31 +321,31 @@ hdc\_std shell
...
@@ -637,31 +321,31 @@ hdc\_std shell
### hdc\_std Fails to Connect to a Device<a name="section74019384588"></a>
### hdc\_std Fails to Connect to a Device<a name="section74019384588"></a>
-**Symptom**
-**Symptom**
**\[Empty\]** is displayed in the output after the **hdc\_std list targets** command is executed.
**\[Empty\]** is displayed in the output after the **hdc\_std list targets** command is executed.
-**Solutions**
-**Solutions**
1. The device cannot be identified.
1. The device cannot be identified.
Check whether **HDC Device** exists in the universal serial bus device of the device manager. If **HDC Device** does not exist, the device cannot be connected. In this case, remove and then insert the device or burn the latest image for the device.
Check whether **HDC Device** exists in the universal serial bus device of the device manager. If **HDC Device** does not exist, the device cannot be connected. In this case, remove and then insert the device or burn the latest image for the device.
2. hdc\_std works improperly.
2. hdc\_std works improperly.
Run the **hdc kill** or **hdc start -r** command to kill or restart the hdc service. Then, run the **hdc list targets** command to check whether device information can be obtained.
Run the **hdc kill** or **hdc start -r** command to kill or restart the hdc service. Then, run the **hdc list targets** command to check whether device information can be obtained.
3. hdc\_std does not match the device.
3. hdc\_std does not match the device.
If the latest image is burnt on the device, the latest hdc\_std version must be used. As hdc\_std is updated continuously, obtain hdc\_std of the latest version from the **developtools\_hdc\_standard** repository in the **prebuilt** directory.
If the latest image is burnt on the device, the latest hdc\_std version must be used. As hdc\_std is updated continuously, obtain hdc\_std of the latest version from the **developtools\_hdc\_standard** repository in the **prebuilt** directory.
## hdc\_std Fails to Run<a name="section6825095917"></a>
## hdc\_std Fails to Run<a name="section6825095917"></a>
-**Symptom**
-**Symptom**
The **hdc\_std.exe** file does not run after being clicked.
The **hdc\_std.exe** file does not run after being clicked.
-**Solutions**
-**Solutions**
**hdc\_std.exe** requires no installation. It can be directly used on a disk or added to environment variables. Open the cmd window and run the **hdc\_std** command to use **hdc\_std.exe**.
**hdc\_std.exe** requires no installation. It can be directly used on a disk or added to environment variables. Open the cmd window and run the **hdc\_std** command to use**hdc\_std.exe**.