update zh-en

2025-10-10 10:09:04 +08:00
parent 3f8a2404bc
commit 1be4d9ae62
447 changed files with 20605 additions and 5432 deletions
--- a/en/docs/dev_doc/faq/technical_faq/a316_firmware_dev_faq.md
+++ b/en/docs/dev_doc/faq/technical_faq/a316_firmware_dev_faq.md
@@ -1,7 +1,7 @@
 ---
 title: A316 Series Product Firmware Development FAQ
-description: This document provides common issues and solutions encountered during A316 series product firmware development, including XU316 communication issues, device power supply problems, etc., helping developers quickly resolve development challenges.
-keywords: A316 firmware development, XU316 communication issues, USB device power supply, firmware development FAQ, device recognition problems
+description: This document provides common questions and solutions encountered during A316 series firmware development, including XU316 communication issues and device power supply problems, helping developers quickly resolve development challenges.
+keywords: A316 firmware development, XU316 communication issues, USB device power supply, firmware development FAQ, device recognition issues
 ---

 --8<-- "common/phaten_xmos_support_img.md"
@@ -10,123 +10,122 @@ keywords: A316 firmware development, XU316 communication issues, USB device powe

 !!! Note
    1. The solutions provided in this document are based on the A316-HF-DAC development board. Other A316 series products may have different communication issues and solutions.
-    2. The following problem solutions use A316-HF-DAC as an example. Other A316 series products may need adjustments based on actual conditions.
+    2. The following solutions use the A316-HF-DAC as an example. Other A316 series products may require adjustments based on actual conditions.

 ## Communication Issues

-### Q1: XU316 cannot send/receive data when connected to PC or MCU via serial port, and logic analyzer cannot capture data
+### Q1: XU316 cannot send or receive data when connected to PC or MCU via serial port, and logic analyzer cannot capture data

 <div class="grid" markdown>

-=== "Problem Symptoms"
-    - XU316 cannot send/receive data when connected to PC via serial port
+=== "Problem Description"
+    - XU316 cannot send or receive data when connected to PC via serial port
    - Logic analyzer cannot capture communication data
-    - Cannot receive messages sent by XU316
+    - Unable to receive messages sent by XU316

 === "Possible Causes"
    1. Insufficient MCU response speed
-          - MCU is processing other initialization tasks while XU316 has already completed initialization
+        - While the MCU is processing other initialization tasks, XU316 has already completed initialization
    2. Power supply issues
-          - MCU is not providing power to XU316
+        - MCU has not provided power to XU316

 === "Problem Analysis"
-    1. Initialization timing issues
-          - XU316 sends 4 power-on commands (0x00) after power-up
-          - 300ms interval between each command
-          - If initialization is not completed or no response is given before the 4 commands are sent, communication fails
+    1. Initialization timing issue
+        - XU316 sends power-on command (0x00) 4 times after power-up
+        - 300ms interval between each command
+        - If initialization is not completed or no response is received before the 4 commands are sent, communication will fail
    2. Power supply issues
-          - Insufficient power supply to XU316 will cause startup failure
+        - Insufficient power supply to XU316 will cause startup failure

-=== "Solutions"
+=== "Solution"
    1. Optimize initialization process
-          - Prioritize XU316 configuration
-          - Ensure initialization is completed before XU316 sends power-on commands
+        - Prioritize XU316 configuration
+        - Ensure initialization is completed before XU316 sends power-on commands
    2. Check power supply design
-          - Check hardware design
-          - Perform hardware modifications if necessary (flying wires, short circuits, etc.)
+        - Check hardware design
+        - Perform hardware modifications if necessary (wire jumpers, short circuits, etc.)

 </div>

-### Q2: Sending IIS in command is ineffective when WiFi is in slave mode
+### Q2: When WiFi is in slave mode, sending IIS in command is ineffective

 <div class="grid" markdown>

-=== "Problem Symptoms"
-    1. After normal connection and power-up, current mode shows USB, but sending IIS in command has no effect
+=== "Problem Description"
+    1. After normal connection and power-on, current mode is USB. Sending IIS in command has no effect

 === "Possible Causes"
-    1. Firmware function limitations
-          - Current firmware does not support mode switching from WiFi (IIS slave) to XMOS (IIS master)
+    1. Firmware function limitation
+        - Current firmware does not support mode switching from WiFi (IIS slave) to XMOS (IIS master)

 === "Problem Analysis"
    1. Communication status
-          - Commands can communicate normally
-          - But mode switching function does not take effect
-    2. Function limitations
-          - Firmware has not implemented the conversion function from WiFi slave mode to XMOS master mode
+        - Commands can communicate normally
+        - But mode switching function does not take effect
+    2. Function limitation
+        - Firmware has not implemented the conversion function from WiFi slave mode to XMOS master mode

-=== "Solutions"
+=== "Solution"
    1. Modify connection method
-          - Mount WiFi module to Bluetooth module
-          - Implement mode switching function through Bluetooth module
+        - Mount WiFi module to Bluetooth module
+        - Implement mode switching function through Bluetooth module

 </div>

 ## Device Recognition Issues

-### Q1: Device is recognized and plays normally on PC, but mobile phone cannot recognize the device
+### Q1: Device is recognized and plays normally on PC, but phone cannot recognize the device

 <div class="grid" markdown>

-=== "Problem Symptoms"
+=== "Problem Description"
    1. Device can be recognized and play normally on PC
-    2. Cannot recognize device when connected to mobile phone
+    2. Device cannot be recognized after connecting to phone

 === "Possible Causes"
-    1. Power supply mode issues
-          - When mobile phone acts as output device, it should provide power to the device
+    1. Power supply mode issue
+        - When phone is used as output device, the phone should supply power to the device

 === "Problem Analysis"
    1. Power supply mode conflict
-          - Mobile phone shows charging status when connected to device
-          - Causes mobile phone to fail to output audio normally
+        - Phone displays charging status when connected to device
+        - This prevents the phone from outputting audio normally

-=== "Solutions"
+=== "Solution"
    1. Modify device power supply design
-          - Check and optimize device power supply section
-          - Adjust discharge section design
-          - Ensure device can correctly receive power when connected to mobile phone
+        - Check and optimize device power supply section
+        - Adjust discharge section design
+        - Ensure device can correctly receive power when connected to phone

 </div>

-<!-- Structured data markup -->
-<script type="application/ld+json">
-{
-"@context": "https://schema.org",
-"@type": "FAQPage",
-"mainEntity": [{
-"@type": "Question",
-"name": "XU316 cannot send/receive data when connected to PC via serial port, and logic analyzer cannot capture data",
-"acceptedAnswer": {
-"@type": "Answer",
-"text": "Possible causes: 1. Insufficient MCU response speed, MCU is processing other initialization tasks while XU316 has already completed initialization; 2. MCU is not providing power to XU316. Solutions: 1. Optimize initialization process, prioritize XU316 configuration; 2. Check power supply design, perform hardware modifications if necessary."
-}
-}, {
-"@type": "Question",
-"name": "Device is recognized and plays normally on PC, but mobile phone cannot recognize the device",
-"acceptedAnswer": {
-"@type": "Answer",
-"text": "Possible cause: Power supply mode issues, when mobile phone acts as output device, it should provide power to the device. Solution: Modify device power supply design, check and optimize device power supply section, adjust discharge section design."
-}
-}]
-}
-</script>
-
 ## Consultation and Feedback
-
 <details>
-<summary>Click to expand consultation feedback form</summary>
+<summary>Click to expand consultation and feedback form</summary>

 --8<-- "common/customer_form.md"

 </details>
+<!-- Structured data markup -->
+<script type="application/ld+json">
+{
+  "@context": "https://schema.org",
+  "@type": "FAQPage",
+  "mainEntity": [{
+    "@type": "Question",
+    "name": "XU316 cannot send or receive data when connected to PC via serial port, and logic analyzer cannot capture data",
+    "acceptedAnswer": {
+      "@type": "Answer",
+      "text": "Possible causes: 1. Insufficient MCU response speed, while processing other initialization tasks, XU316 has already completed initialization; 2. MCU has not provided power to XU316. Solutions: 1. Optimize initialization process, prioritize XU316 configuration; 2. Check power supply design, perform hardware modifications if necessary."
+    }
+  }, {
+    "@type": "Question",
+    "name": "Device is recognized and plays normally on PC, but phone cannot recognize the device",
+    "acceptedAnswer": {
+      "@type": "Answer",
+      "text": "Possible cause: Power supply mode issue, when phone is used as output device, the phone should supply power to the device. Solution: Modify device power supply design, check and optimize device power supply section, adjust discharge section design."
+    }
+  }]
+}
+</script>
+