update docs

Signed-off-by: NAnnie_wang <annie.wangli@huawei.com>

en/application-dev/reference/apis/Readme-EN.md

@@ -301,6 +301,7 @@
   - [@ohos.nfc.controller (Standard NFC)](js-apis-nfcController.md)
   - [@ohos.nfc.tag (Standard NFC Tags)](js-apis-nfcTag.md)
   - [@ohos.rpc (RPC)](js-apis-rpc.md)
+  - [@ohos.secureElement (SE Channel Management)](js-apis-secureElement.md)
   - [@ohos.wifiManager (WLAN) (Recommended)](js-apis-wifiManager.md)
   - [@ohos.wifiManagerExt (WLAN Extension) (Recommended)](js-apis-wifiManagerExt.md)
   - [@ohos.wifi (WLAN) (To Be Deprecated Soon)](js-apis-wifi.md)

en/application-dev/reference/errorcodes/Readme-EN.md

@@ -60,6 +60,7 @@
   - [Bluetooth Error Codes](errorcode-bluetoothManager.md)
   - [Wi-Fi Error Codes](errorcode-wifi.md)  
   - [NFC Error Codes](errorcode-nfc.md)
+  - [SE Error Codes](errorcode-se.md)
   - [RPC Error Codes](errorcode-rpc.md)
  - Basic Features
   - [Accessibility Error Codes](errorcode-accessibility.md)

en/application-dev/reference/errorcodes/errorcode-se.md

+# SE Error Codes
+
+> **NOTE**
+>
+> This topic describes only module-specific error codes. For details about universal error codes, see [Universal Error Codes](errorcode-universal.md).
+
+## 3300101 Abnormal SE Service Status
+
+**Error Message**
+
+Illegal service state exception.
+
+**Description**
+
+The SecureElement (SE) service is abnormal.
+
+**Possible Causes**
+
+1. The SE service is disconnected.
+
+**Solution**
+
+1. Close the SE service.
+
+2. Set up a connection with the SE service again.
+
+## 3300102 No Such SE
+
+**Error Message**
+
+No such element exception.
+
+**Description**
+
+The SE is unavailable.
+
+**Possible Causes**
+
+1. Communication with the SE service is abnormal.
+2. Communication of the SE chip is abnormal.
+
+**Solution**
+
+1. Close the SE service and set up a connection with the SE service again.
+2. Restart the device.
+
+## 3300103 Failed to Obtain the Access Rule
+
+**Error Message**
+
+Illegal access rule exception.
+
+**Description**
+
+The access rule cannot be obtained.
+
+**Possible Causes**
+
+1. There is no access rule for the application on the SE.
+
+**Solution**
+
+1. Write correct access rules to the SE.
+2. Close the SE service and set up a connection with the SE service again.
+
+## 3300104 SE Chip I/O Exception
+
+**Error Message**
+
+Secure element IO exception.
+
+**Description**
+
+The I/O of the SE chip is abnormal.
+
+**Possible Causes**
+
+1. The communication with the SE chip is abnormal.
+2. The SE chip is abnormal.
+
+**Solution**
+
+1. Close the SE service and set up a connection with the SE service again.
+
+2. Restart the device.