update
update
This commit is contained in:
PhatenIoT-yan
@@ -1,54 +1,12 @@
|
||||
---
|
||||
title: Frequently Asked Questions
|
||||
---
|
||||
|
||||
# Frequently Asked Questions
|
||||
|
||||
--8<-- "common/phaten_xmos_support_img.md"
|
||||
|
||||
|
||||
|
||||
# FT1710DAFV1 Module Pin Definition Table - Updated 0925
|
||||
|
||||
| Pin | Symbol | Function Description |
|
||||
|-----|------|----------|
|
||||
| 1 | GND | Ground |
|
||||
| 2 | RFIO | 2.4&5G Wi-Fi/BLE External Antenna Interface |
|
||||
| 3 | GND | Ground |
|
||||
| 4 | NC | NC |
|
||||
| 5 | PB20 | GPIO or WAKEUP HOST (IO Voltage always 3.3V) |
|
||||
| 6 | PA27 | GPIO |
|
||||
| 7 | PB21 | GPIO or WAKEUP HOST (IO Voltage always 3.3V)|
|
||||
| 8 | ADC2(PB17)/NC | GPIO(WAKEUP HOST) OR ADC2(PB17 SDIO_4Bit_Mode) / NC(SDIO_1Bit_Mode) |
|
||||
| 9 | VCC | 3.3V supply |
|
||||
| 10 | USB_DM(PA28) | USB_DM OR GPIO |
|
||||
| 11 | USB_DP(PA29) | USB_DP OR GPIO |
|
||||
| 12 | WIFI_EN | Chip_EN High: Enables the chip<br>Low: Module power off. |
|
||||
| 13 | PB30 | GPIO OR WAKEUP HOST (IO Voltage always 3.3V)|
|
||||
| 14 | SDIO_D2(PA13)/ADC2(PB17) | SDIO_D2(PA13 SDIO_4Bit_Mode)/GPIO(WAKEUP HOST) OR ADC2(PB17 SDIO_1Bit_Mode) |
|
||||
| 15 | SDIO_D3(PA14)/ADC1(PB18) | SDIO_D3(PA14 SDIO_4Bit_Mode)/GPIO(WAKEUP HOST) OR ADC1(PB18 SDIO_1Bit_Mode) |
|
||||
| 16 | SDIO_CMD(PA15) | SDIO command |
|
||||
| 17 | SDIO_CLK(PA16) | SDIO clock |
|
||||
| 18 | SDIO_D0(PA17) | SDIO_D0 |
|
||||
| 19 | SDIO_D1(PA18) | SDIO_D1 OR GPIO |
|
||||
| 20 | GND | Ground |
|
||||
| 21 | BAT_MEAS | BAT_MEAS(0-5V) |
|
||||
| 22 | VDDIO | I/O Voltage supply. NC (Internal 1.8V supply) / External 3.3V/1.8V supply |
|
||||
| 23 | NC | NC |
|
||||
| 24 | NC | NC |
|
||||
| 25 | ADC1(PB18)/NC | GPIO(WAKEUP HOST) OR ADC1(PB18 SDIO_4Bit_Mode) / NC(SDIO_1Bit_Mode) |
|
||||
| 26 | PA26 | GPIO |
|
||||
| 27 | PA12 | GPIO |
|
||||
| 28 | PA8 | GPIO |
|
||||
| 29 | NC | NC |
|
||||
| 30 | NC | NC |
|
||||
| 31 | GND | Ground |
|
||||
| 32 | NC | NC |
|
||||
| 33 | GND | Ground |
|
||||
| 34 | NC | NC |
|
||||
| 35 | NC | NC |
|
||||
| 36 | GND | Ground |
|
||||
| 37 | UART_LOG_TXD(PB5) | UART_LOG_TXD<br>For firmware download (IO Voltage always 3.3V) |
|
||||
| 38 | UART_LOG_RXD(PB4) | UART_LOG_RXD<br>For firmware download (IO Voltage always 3.3V) |
|
||||
| 39 | WiFi_FACTORY_RST(PB19) | GPIO(WIFI Factor Reset) or ADC0 |
|
||||
| 40 | PB31 | GPIO or WAKEUP HOST (IO Voltage always 3.3V)|
|
||||
| 41 | NC | NC |
|
||||
| 42 | PA30 | GPIO or WAKEUP HOST |
|
||||
| 43 | PA31 | GPIO or WAKEUP HOST |
|
||||
| 44 | NC | NC |
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,37 +1,37 @@
|
||||
---
|
||||
title: Driver Recognition and Device Recognition Exception Issues
|
||||
title: Driver Recognition and Device Exception Issues
|
||||
---
|
||||
--8<-- "common/phaten_xmos_support_img.md"
|
||||
|
||||
## **Q1**: Driver Recognition and Device Recognition Exception Issues
|
||||
## **Q1**: Driver Recognition and Device Exception Issues
|
||||
|
||||
### Problem Description
|
||||
During development or debugging, when using firmware with different configurations or different channel numbers, device recognition exceptions may occur, or the device cannot be used normally after recognition exceptions.
|
||||
When using firmware with different configurations or channel counts during development or debugging, device recognition exceptions may occur, or the device may fail to function properly after recognition exceptions.
|
||||
|
||||
### Cause Analysis
|
||||
After modifying the recording channel number, the new configuration is inconsistent with the configuration cached by the Windows system, causing the system to fail to correctly recognize the current device status. In this case, cached data needs to be cleared and device recognition needs to be performed again.
|
||||
### Root Cause Analysis
|
||||
When the recording channel count is modified, the new configuration does not match the configuration cached by the Windows system, causing the system to fail to correctly recognize the current device state. In such cases, it is necessary to clear the cached data and re-recognize the device.
|
||||
|
||||
### Solution
|
||||
### Solutions
|
||||
{width=500}
|
||||
=== "Solution 1: Simple Uninstall"
|
||||
1. Connect the device to the computer
|
||||
2. Open Device Manager
|
||||
3. Find the "Sound, video and game controllers" category
|
||||
4. Right-click the related audio device
|
||||
3. Locate the "Sound, video and game controllers" category
|
||||
4. Right-click on the relevant audio device
|
||||
5. Select "Uninstall device"
|
||||
|
||||
=== "Solution 2: Complete Uninstall (Recommended)"
|
||||
1. Connect the device to the computer
|
||||
2. Open Device Manager
|
||||
3. Find the "Sound, video and game controllers" category
|
||||
4. Right-click the related audio device
|
||||
3. Locate the "Sound, video and game controllers" category
|
||||
4. Right-click on the relevant audio device
|
||||
5. Select "Uninstall device" and check "Delete the driver software for this device"
|
||||
6. Reinstall the driver
|
||||
6. Reinstall the driver software
|
||||
7. Reconnect the device and wait for successful system recognition
|
||||
|
||||
## Consultation and Feedback
|
||||
## Contact and Feedback
|
||||
<details>
|
||||
<summary>Click to expand consultation and feedback form</summary>
|
||||
<summary>Click to expand contact and feedback form</summary>
|
||||
|
||||
--8<-- "common/customer_form.md"
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: A316 Series Product Firmware Development FAQ
|
||||
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.
|
||||
description: This document provides common questions 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 issues
|
||||
---
|
||||
|
||||
@@ -8,9 +8,9 @@ keywords: A316 firmware development, XU316 communication issues, USB device powe
|
||||
|
||||
# A316 Series Product Firmware Development FAQ
|
||||
|
||||
!!! Note
|
||||
!!! 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 solutions use the A316-HF-DAC as an example. Other A316 series products may require 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 circumstances.
|
||||
|
||||
## Communication Issues
|
||||
|
||||
@@ -18,54 +18,54 @@ keywords: A316 firmware development, XU316 communication issues, USB device powe
|
||||
|
||||
<div class="grid" markdown>
|
||||
|
||||
=== "Problem Description"
|
||||
=== "Problem Symptoms"
|
||||
- XU316 cannot send or receive data when connected to PC via serial port
|
||||
- Logic analyzer cannot capture communication data
|
||||
- Unable to receive messages sent by XU316
|
||||
- Messages sent by XU316 are not received
|
||||
|
||||
=== "Possible Causes"
|
||||
1. Insufficient MCU response speed
|
||||
- While the MCU is processing other initialization tasks, XU316 has already completed initialization
|
||||
- MCU is processing other initialization tasks when XU316 has already completed initialization
|
||||
2. Power supply issues
|
||||
- MCU has not provided power to XU316
|
||||
- MCU does not provide power to XU316
|
||||
|
||||
=== "Problem Analysis"
|
||||
1. Initialization timing issue
|
||||
1. Initialization timing issues
|
||||
- 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
|
||||
- Communication fails if initialization is not completed or no reply is received before the 4 commands finish
|
||||
2. Power supply issues
|
||||
- Insufficient power supply to XU316 will cause startup failure
|
||||
|
||||
=== "Solution"
|
||||
=== "Solutions"
|
||||
1. Optimize initialization process
|
||||
- Prioritize XU316 configuration
|
||||
- Ensure initialization is completed before XU316 sends power-on commands
|
||||
2. Check power supply design
|
||||
- Check hardware design
|
||||
- Inspect hardware design
|
||||
- Perform hardware modifications if necessary (wire jumpers, short circuits, etc.)
|
||||
|
||||
</div>
|
||||
|
||||
### Q2: When WiFi is in slave mode, sending IIS in command is ineffective
|
||||
### Q2: Sending I2S IN command is ineffective when WiFi is in slave mode
|
||||
|
||||
<div class="grid" markdown>
|
||||
|
||||
=== "Problem Description"
|
||||
1. After normal connection and power-on, current mode is USB. Sending IIS in command has no effect
|
||||
=== "Problem Symptoms"
|
||||
1. After normal wiring and power-up, current mode shows USB, but sending I2S IN command has no effect
|
||||
|
||||
=== "Possible Causes"
|
||||
1. Firmware function limitation
|
||||
- Current firmware does not support mode switching from WiFi (IIS slave) to XMOS (IIS master)
|
||||
1. Firmware function limitations
|
||||
- Current firmware does not support mode switching from WiFi (I2S slave) to XMOS (I2S master)
|
||||
|
||||
=== "Problem Analysis"
|
||||
1. Communication status
|
||||
- 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
|
||||
2. Function limitations
|
||||
- Firmware has not implemented conversion function from WiFi slave mode to XMOS master mode
|
||||
|
||||
=== "Solution"
|
||||
=== "Solutions"
|
||||
1. Modify connection method
|
||||
- Mount WiFi module to Bluetooth module
|
||||
- Implement mode switching function through Bluetooth module
|
||||
@@ -74,39 +74,39 @@ keywords: A316 firmware development, XU316 communication issues, USB device powe
|
||||
|
||||
## Device Recognition Issues
|
||||
|
||||
### Q1: Device is recognized and plays normally on PC, but phone cannot recognize the device
|
||||
### Q1: Device is recognized and plays normally on PC, but mobile phone cannot recognize device
|
||||
|
||||
<div class="grid" markdown>
|
||||
|
||||
=== "Problem Description"
|
||||
1. Device can be recognized and play normally on PC
|
||||
2. Device cannot be recognized after connecting to phone
|
||||
=== "Problem Symptoms"
|
||||
1. Device can be recognized and plays normally on PC
|
||||
2. Device cannot be recognized after connecting to mobile phone
|
||||
|
||||
=== "Possible Causes"
|
||||
1. Power supply mode issue
|
||||
- When phone is used as output device, the phone should supply power to the device
|
||||
1. Power supply mode issues
|
||||
- When mobile phone acts as output device, it should supply power to the device
|
||||
|
||||
=== "Problem Analysis"
|
||||
1. Power supply mode conflict
|
||||
- Phone displays charging status when connected to device
|
||||
- This prevents the phone from outputting audio normally
|
||||
- Mobile phone shows charging status when connected to device
|
||||
- Causes mobile phone to fail to output audio normally
|
||||
|
||||
=== "Solution"
|
||||
=== "Solutions"
|
||||
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 phone
|
||||
- Ensure device can correctly receive power when connected to mobile phone
|
||||
|
||||
</div>
|
||||
|
||||
## Consultation and Feedback
|
||||
## Contact and Feedback
|
||||
<details>
|
||||
<summary>Click to expand consultation and feedback form</summary>
|
||||
<summary>Click to expand contact and feedback form</summary>
|
||||
|
||||
--8<-- "common/customer_form.md"
|
||||
|
||||
</details>
|
||||
<!-- Structured data markup -->
|
||||
<!-- Structured Data Markup -->
|
||||
<script type="application/ld+json">
|
||||
{
|
||||
"@context": "https://schema.org",
|
||||
@@ -116,16 +116,15 @@ keywords: A316 firmware development, XU316 communication issues, USB device powe
|
||||
"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."
|
||||
"text": "Possible causes: 1. Insufficient MCU response speed, MCU is processing other initialization tasks when XU316 has already completed initialization; 2. MCU does not provide 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",
|
||||
"name": "Device is recognized and plays normally on PC, but mobile phone cannot recognize 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."
|
||||
"text": "Possible cause: Power supply mode issues, when mobile phone acts as output device, it should supply power to the device. Solution: Modify device power supply design, check and optimize device power supply section, adjust discharge section design."
|
||||
}
|
||||
}]
|
||||
}
|
||||
</script>
|
||||
|
||||
|
||||
@@ -1,87 +1,97 @@
|
||||
---
|
||||
title: Common Questions and Answers for WiFi Audio + Bluetooth Modules
|
||||
description: This document summarizes common technical questions and answers regarding wireless WiFi modules and Bluetooth modules, including IR remote decoding, power consumption, chip architecture, TX/RX switching, Bluetooth TWS, etc., to help developers quickly locate and solve problems.
|
||||
keywords: 8711, wireless speaker, IR remote, module power consumption, WIFI BT chip, TX RX switching, Bluetooth TWS, technical FAQ
|
||||
title: WiFi Audio Speaker + Bluetooth Module FAQ
|
||||
description: This document compiles common technical questions and answers regarding wireless WiFi modules and Bluetooth modules in areas such as infrared remote control, power consumption, chip architecture, TX/RX conversion, Bluetooth TWS, etc., helping developers quickly locate and resolve issues.
|
||||
keywords: 8711, wireless speakers, infrared remote control, module power consumption, WiFi BT chip, TX RX conversion, Bluetooth TWS, technical FAQ
|
||||
---
|
||||
|
||||
--8<-- "common/phaten_xmos_support_img.md"
|
||||
|
||||
# Technical FAQ for WiFi Audio + Bluetooth Modules
|
||||
# WiFi Audio Speaker + Bluetooth Module Technical FAQ
|
||||
|
||||
## Q1: Does the module support IR remote decoding?
|
||||
## Q1: Does the module support infrared remote control decoding?
|
||||
|
||||
**IR remote decoding is supported.**
|
||||
**Yes, infrared decoding functionality is supported.**
|
||||
|
||||
---
|
||||
|
||||
## Q2: Power consumption during module operation and standby
|
||||
## Q2: Module power consumption during operation and standby
|
||||
|
||||
=== "Sleep Mode 1"
|
||||
- **Operating state**: Both TX/RX are in sleep, WiFi is off, TX and RX BLE are working
|
||||
- **How to enter sleep**:
|
||||
- The application actively calls the Sleep interface
|
||||
- Automatically enters after detecting no I2S data for a period of time
|
||||
- **Wake-up method**:
|
||||
- UART/GPIO interrupt wakes up TX → TX wakes up RX
|
||||
- UART/GPIO interrupt wakes up RX → RX wakes up TX (bi-directional wake-up)
|
||||
- **Current**:
|
||||
- **Operating State**: TX/RX both sleep, WiFi off, TX and RX BLE operational
|
||||
- **Sleep Entry Method**:
|
||||
- Application actively calls Sleep interface
|
||||
- Automatically enters after detecting no I2S data for a period
|
||||
- **Wake-up Method**:
|
||||
- UART/GPIO interrupt wakes TX → TX wakes RX
|
||||
- UART/GPIO interrupt wakes RX → RX wakes TX (bidirectional wake-up)
|
||||
- **Current Draw**:
|
||||
- Unidirectional wake-up: TX ≤1mA, RX ≤3mA
|
||||
- Bidirectional wake-up: TX ≤3mA, RX ≤3mA
|
||||
|
||||
|
||||
=== "Sleep Mode 2"
|
||||
- **Operating state**: TX WiFi does not sleep, RX WiFi sleeps, TX/RX BLE are off
|
||||
- **How to enter sleep**:
|
||||
- The application actively calls the Sleep interface
|
||||
- Automatically enters after detecting no I2S data for a period of time
|
||||
- **Wake-up method**:
|
||||
- The application calls the playback interface (TX automatically wakes up RX)
|
||||
- RX is automatically woken up when I2S data is detected
|
||||
- **Current**: RX ≤1mA
|
||||
- **Operating State**: TX WiFi does not sleep, RX WiFi sleeps, TX/RX BLE off
|
||||
- **Sleep Entry Method**:
|
||||
- Application actively calls Sleep interface
|
||||
- Automatically enters after detecting no I2S data for a period
|
||||
- **Wake-up Method**:
|
||||
- Application calls playback interface (TX automatically wakes RX)
|
||||
- Automatically wakes RX when I2S data is detected
|
||||
- **Current Draw**: RX ≤1mA
|
||||
|
||||
---
|
||||
|
||||
## Q3: What is the WIFI and BT chip architecture of the module?
|
||||
## Q3: Module WiFi and BT chip architecture
|
||||
|
||||
A single SoC integrates both WIFI and BT functions.
|
||||
Uses a single SoC chip integrating WiFi and BT functionality.
|
||||
|
||||
---
|
||||
|
||||
## Q4: Does it support online TX/RX switching?
|
||||
## Q4: Does it support online TX/RX conversion?
|
||||
|
||||
### Support status:
|
||||
- Supports online TX/RX switching in WIFI mode
|
||||
### Support Status:
|
||||
- Supports TX/RX online conversion in WiFi mode
|
||||
- BT mode limitations:
|
||||
- SoC only supports BLE5.0
|
||||
- Does not support Classic BT
|
||||
- Cannot transmit audio via mobile phone Bluetooth
|
||||
- SoC only supports BLE 5.0
|
||||
- Does not support Classic BT
|
||||
- Cannot transmit audio via mobile phone Bluetooth
|
||||
|
||||
### Working mode description:
|
||||
### Operating Mode Description:
|
||||
|
||||
=== "**TV Mode**:"
|
||||
- The transmitter box is WIFI TX
|
||||
- The receiving speakers are dual RX (left/right channels)
|
||||
- Transmitter box is WiFi TX
|
||||
- Receiver speakers are dual RX (left/right channels)
|
||||
|
||||
|
||||
|
||||
|
||||
=== "**BT Mode**:"
|
||||
- Left speaker:
|
||||
* Receives mobile phone signal via BT
|
||||
* Simultaneously acts as WIFI TX to transmit to the right speaker
|
||||
- Right speaker: pure WIFI RX mode
|
||||
- Acts as BT receiver for mobile phone signal
|
||||
- Simultaneously acts as WiFi TX to transmit to right speaker
|
||||
- Right speaker: Pure WiFi RX mode
|
||||
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
## Q5: Bluetooth TWS function implementation
|
||||
|
||||
- **Native Bluetooth TWS is not supported**
|
||||
- **Alternative solution**:
|
||||
- In BT mode, the left speaker (with IR receiver) acts as TX
|
||||
- Transmits the right channel to the right speaker via TWS
|
||||
- The right speaker (without IR receiver) acts as RX to receive the TWS signal
|
||||
- **Does not support** native Bluetooth TWS functionality
|
||||
- **Alternative Solution**:
|
||||
- Left speaker (with remote control receiver) acts as TX in BT mode
|
||||
- Transmits right channel to right speaker via TWS method
|
||||
- Right speaker (without remote control receiver) acts as RX to receive TWS signal
|
||||
|
||||
|
||||
|
||||
|
||||
## Contact and Feedback
|
||||
<details>
|
||||
<summary>Click to expand contact and feedback form</summary>
|
||||
|
||||
--8<-- "common/customer_form.md"
|
||||
|
||||
</details>
|
||||
|
||||
|
||||
|
||||
<!-- Structured Data Markup -->
|
||||
<script type="application/ld+json">
|
||||
@@ -91,53 +101,44 @@ A single SoC integrates both WIFI and BT functions.
|
||||
"mainEntity": [
|
||||
{
|
||||
"@type": "Question",
|
||||
"name": "Does the module support IR remote decoding?",
|
||||
"name": "Does the module support infrared remote control decoding?",
|
||||
"acceptedAnswer": {
|
||||
"@type": "Answer",
|
||||
"text": "IR remote decoding is supported."
|
||||
"text": "Yes, infrared decoding functionality is supported."
|
||||
}
|
||||
},
|
||||
{
|
||||
"@type": "Question",
|
||||
"name": "What is the power consumption during module operation and standby?",
|
||||
"name": "What is the module power consumption during operation and standby?",
|
||||
"acceptedAnswer": {
|
||||
"@type": "Answer",
|
||||
"text": "Sleep Mode 1: Both TX/RX are in sleep, WiFi is off, TX and RX BLE are working. Unidirectional wake-up: TX≤1mA, RX≤3mA; Bidirectional wake-up: TX≤3mA, RX≤3mA. Sleep Mode 2: TX WiFi does not sleep, RX WiFi sleeps, TX/RX BLE are off, RX≤1mA."
|
||||
"text": "Sleep Mode 1: TX/RX both sleep, WiFi off, TX and RX BLE operational, unidirectional wake-up TX≤1mA, RX≤3mA, bidirectional wake-up TX≤3mA, RX≤3mA. Sleep Mode 2: TX WiFi does not sleep, RX WiFi sleeps, TX/RX BLE off, RX≤1mA."
|
||||
}
|
||||
},
|
||||
{
|
||||
"@type": "Question",
|
||||
"name": "What is the WIFI and BT chip architecture of the module?",
|
||||
"name": "What is the module's WiFi and BT chip architecture?",
|
||||
"acceptedAnswer": {
|
||||
"@type": "Answer",
|
||||
"text": "A single SoC integrates both WIFI and BT functions."
|
||||
"text": "Uses a single SoC chip integrating WiFi and BT functionality."
|
||||
}
|
||||
},
|
||||
{
|
||||
"@type": "Question",
|
||||
"name": "Does it support online TX/RX switching?",
|
||||
"name": "Does it support online TX/RX conversion?",
|
||||
"acceptedAnswer": {
|
||||
"@type": "Answer",
|
||||
"text": "Supports online TX/RX switching in WIFI mode. BT mode only supports BLE5.0, does not support Classic BT, and cannot transmit audio via mobile phone Bluetooth."
|
||||
"text": "Supports TX/RX online conversion in WiFi mode. BT mode only supports BLE 5.0, does not support Classic BT, and cannot transmit audio via mobile phone Bluetooth."
|
||||
}
|
||||
},
|
||||
{
|
||||
"@type": "Question",
|
||||
"name": "How is the Bluetooth TWS function implemented?",
|
||||
"name": "How is Bluetooth TWS functionality implemented?",
|
||||
"acceptedAnswer": {
|
||||
"@type": "Answer",
|
||||
"text": "Native Bluetooth TWS is not supported. In BT mode, the left speaker acts as TX and transmits the right channel to the right speaker via TWS. The right speaker acts as RX to receive the TWS signal."
|
||||
"text": "Does not support native Bluetooth TWS functionality. Can be implemented by having the left speaker act as TX in BT mode and transmitting the right channel to the right speaker via TWS method."
|
||||
}
|
||||
}
|
||||
]
|
||||
}
|
||||
</script>
|
||||
|
||||
## Consultation and Feedback
|
||||
|
||||
<details>
|
||||
<summary>Click to expand consultation feedback form</summary>
|
||||
|
||||
--8<-- "common/customer_form.md"
|
||||
|
||||
</details>
|
||||
@@ -1,108 +1,109 @@
|
||||
---
|
||||
login: true
|
||||
---
|
||||
|
||||
# 固件升级指南：XU316系列产品DFU更新操作手册
|
||||
|
||||
--8<-- "common/checklogin_form.md"
|
||||
|
||||
## 概述
|
||||
|
||||
本文档详细说明如何在Windows操作系统环境下，使用DFU（Device Firmware Update）方式对XU316系列产品进行固件更新。若您使用其他操作系统，请参考XMOS官方文档：[XMOS DFU官方指南](https://www.xmos.com/documentation/XM-014926-PC-1/html/doc/programming_guide/tutorials/freertos/examples/dfu.html#dfu)。
|
||||
|
||||
## 系统要求
|
||||
|
||||
- Windows操作系统（Windows 7或更高版本，推荐使用最新版本以获得最佳兼容性）
|
||||
- USB数据线
|
||||
- 可正常连接的XU316系列设备
|
||||
|
||||
## 所需工具
|
||||
|
||||
在开始升级过程前，请确保您已下载并准备好以下工具：
|
||||
|
||||
1. **Zadig驱动安装工具**：<a href="javascript:void(0);" onclick="checkLogin('/assets/download/tools_software/zadig-2.8.exe')">下载zadig-2.8.exe</a>
|
||||
2. **DFU实用程序**：<a href="javascript:void(0);" onclick="checkLogin('/assets/download/tools_software/dfu-util-0.11-binaries.tar.xz')">下载dfu-util-0.11</a>
|
||||
|
||||
## 升级流程
|
||||
|
||||
### 步骤一：安装驱动
|
||||
|
||||
1. 使用USB数据线将XU316设备连接至计算机
|
||||
2. 运行Zadig工具（zadig-2.8.exe）
|
||||
3. 在Zadig界面中进行如下配置：
|
||||
|
||||
4. 点击"Reinstall Driver"按钮
|
||||
5. 等待系统提示驱动安装成功
|
||||
|
||||
### 步骤二：执行固件更新
|
||||
|
||||
1. 解压下载的dfu-util-0.11软件包
|
||||
2. 根据您的Windows系统版本，进入相应目录：
|
||||
- 64位系统：`dfu-util-0.11-binaries\win64`
|
||||
- 32位系统：`dfu-util-0.11-binaries\win32`
|
||||
3. 在该目录下打开命令提示符（按住Shift键+鼠标右键，选择"在此处打开命令窗口"）
|
||||
4. 输入以下命令验证DFU工具是否可用：
|
||||
```
|
||||
dfu-prefix.exe --version
|
||||
```
|
||||
如果看到包含"please report bugs to http://sourceforge.net/p/dfu-util/tickets/"的提示信息，说明工具可正常使用
|
||||
|
||||
5. 将要升级的固件文件（例如：example_ffva_ua_adec_upgrade.bin）复制到当前目录
|
||||
6. 执行升级命令：
|
||||
```
|
||||
dfu-util -e -d 4000 -a 1 -D 您的固件文件名.bin
|
||||
```
|
||||
**注意**：请将"您的固件文件名.bin"替换为实际的固件文件名
|
||||
|
||||
### 步骤三：确认升级结果
|
||||
|
||||
升级成功时，终端将显示类似如下信息：
|
||||
|
||||
```
|
||||
dfu-util 0.11
|
||||
|
||||
Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
|
||||
Copyright 2010-2021 Tormod Volden and Stefan Schmidt
|
||||
This program is Free Software and has ABSOLUTELY NO WARRANTY
|
||||
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/
|
||||
|
||||
Warning: Invalid DFU suffix signature
|
||||
A valid DFU suffix will be required in a future dfu-util release
|
||||
Opening DFU capable USB device...
|
||||
Device ID 20b1:4001
|
||||
Run-Time device DFU version 0101
|
||||
Claiming USB DFU Interface...
|
||||
Setting Alternate Interface #1 ...
|
||||
Determining device status...
|
||||
DFU state(2) = dfuIDLE, status(0) = No error condition is present
|
||||
DFU mode device DFU version 0101
|
||||
Device returned transfer size 4096
|
||||
Copying data from PC to DFU device
|
||||
Download [=========================] 100% 331776 bytes
|
||||
Download done.
|
||||
DFU state(7) = dfuMANIFEST, status(0) = No error condition is present
|
||||
DFU state(2) = dfuIDLE, status(0) = No error condition is present
|
||||
Done!
|
||||
```
|
||||
|
||||
当您看到"Done!"提示时，表示固件已成功更新。
|
||||
|
||||
## 常见问题
|
||||
|
||||
- 如果设备无法被识别，请尝试重新插拔USB连接线
|
||||
- 确保您使用的是原装或高质量的USB线缆
|
||||
- 若升级过程中断，请重新开始整个升级流程
|
||||
|
||||
## 技术支持
|
||||
|
||||
如遇到任何问题，请联系我们的技术支持团队获取帮助。
|
||||
|
||||
## Consultation and Feedback
|
||||
|
||||
<details>
|
||||
<summary>Click to expand consultation feedback form</summary>
|
||||
|
||||
--8<-- "common/customer_form.md"
|
||||
|
||||
</details>
|
||||
|
||||
---
|
||||
title: XU316 Firmware Upgrade
|
||||
login: true
|
||||
---
|
||||
|
||||
--8<-- "common/phaten_xmos_support_img.md"
|
||||
|
||||
# Firmware Upgrade Guide: XU316 Series Product DFU Update Operation Manual
|
||||
|
||||
--8<-- "common/checklogin_form.md"
|
||||
|
||||
## Overview
|
||||
|
||||
This document provides detailed instructions on how to perform firmware updates for XU316 series products using the DFU (Device Firmware Update) method in Windows operating system environments. If you are using other operating systems, please refer to the official XMOS documentation: [XMOS DFU Official Guide](https://www.xmos.com/documentation/XM-014926-PC-1/html/doc/programming_guide/tutorials/freertos/examples/dfu.html#dfu).
|
||||
|
||||
## System Requirements
|
||||
|
||||
- Windows operating system (Windows 7 or higher, latest version recommended for best compatibility)
|
||||
- USB data cable
|
||||
- XU316 series device with normal connectivity
|
||||
|
||||
## Required Tools
|
||||
|
||||
Before starting the upgrade process, ensure you have downloaded and prepared the following tools:
|
||||
|
||||
1. **Zadig Driver Installation Tool**: <a href="javascript:void(0);" onclick="checkLogin('/assets/download/tools_software/zadig-2.8.exe')">Download zadig-2.8.exe</a>
|
||||
2. **DFU Utility**: <a href="javascript:void(0);" onclick="checkLogin('/assets/download/tools_software/dfu-util-0.11-binaries.tar.xz')">Download dfu-util-0.11</a>
|
||||
|
||||
## Upgrade Process
|
||||
|
||||
### Step 1: Install Driver
|
||||
|
||||
1. Connect the XU316 device to the computer using a USB data cable
|
||||
2. Run the Zadig tool (zadig-2.8.exe)
|
||||
3. Configure the following settings in the Zadig interface:
|
||||
|
||||
4. Click the "Reinstall Driver" button
|
||||
5. Wait for the system prompt indicating successful driver installation
|
||||
|
||||
### Step 2: Execute Firmware Update
|
||||
|
||||
1. Extract the downloaded dfu-util-0.11 software package
|
||||
2. Navigate to the appropriate directory based on your Windows system version:
|
||||
- 64-bit system: `dfu-util-0.11-binaries\win64`
|
||||
- 32-bit system: `dfu-util-0.11-binaries\win32`
|
||||
3. Open Command Prompt in this directory (hold Shift + right-click mouse, select "Open command window here")
|
||||
4. Enter the following command to verify the DFU tool is available:
|
||||
```
|
||||
dfu-prefix.exe --version
|
||||
```
|
||||
If you see a message containing "please report bugs to http://sourceforge.net/p/dfu-util/tickets/", the tool is functioning properly
|
||||
|
||||
5. Copy the firmware file to be upgraded (e.g., example_ffva_ua_adec_upgrade.bin) to the current directory
|
||||
6. Execute the upgrade command:
|
||||
```
|
||||
dfu-util -e -d 4000 -a 1 -D your_firmware_filename.bin
|
||||
```
|
||||
**Note**: Replace "your_firmware_filename.bin" with the actual firmware filename
|
||||
|
||||
### Step 3: Confirm Upgrade Results
|
||||
|
||||
Upon successful upgrade, the terminal will display information similar to the following:
|
||||
|
||||
```
|
||||
dfu-util 0.11
|
||||
|
||||
Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
|
||||
Copyright 2010-2021 Tormod Volden and Stefan Schmidt
|
||||
This program is Free Software and has ABSOLUTELY NO WARRANTY
|
||||
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/
|
||||
|
||||
Warning: Invalid DFU suffix signature
|
||||
A valid DFU suffix will be required in a future dfu-util release
|
||||
Opening DFU capable USB device...
|
||||
Device ID 20b1:4001
|
||||
Run-Time device DFU version 0101
|
||||
Claiming USB DFU Interface...
|
||||
Setting Alternate Interface #1 ...
|
||||
Determining device status...
|
||||
DFU state(2) = dfuIDLE, status(0) = No error condition is present
|
||||
DFU mode device DFU version 0101
|
||||
Device returned transfer size 4096
|
||||
Copying data from PC to DFU device
|
||||
Download [=========================] 100% 331776 bytes
|
||||
Download done.
|
||||
DFU state(7) = dfuMANIFEST, status(0) = No error condition is present
|
||||
DFU state(2) = dfuIDLE, status(0) = No error condition is present
|
||||
Done!
|
||||
```
|
||||
|
||||
When you see the "Done!" prompt, the firmware has been successfully updated.
|
||||
|
||||
## Common Issues
|
||||
|
||||
- If the device cannot be recognized, try reconnecting the USB cable
|
||||
- Ensure you are using an original or high-quality USB cable
|
||||
- If the upgrade process is interrupted, restart the entire upgrade procedure
|
||||
|
||||
## Technical Support
|
||||
|
||||
If you encounter any problems, please contact our technical support team for assistance.
|
||||
|
||||
## Contact and Feedback
|
||||
<details>
|
||||
<summary>Click to expand contact and feedback form</summary>
|
||||
|
||||
--8<-- "common/customer_form.md"
|
||||
|
||||
</details>
|
||||
|
||||
@@ -1,78 +1,80 @@
|
||||
---
|
||||
title: XMOS USB Audio Driver Technical Guide
|
||||
login: true
|
||||
---
|
||||
|
||||
# XMOS USB HiFi音频驱动技术指南
|
||||
--8<-- "common/phaten_xmos_support_img.md"
|
||||
|
||||
# XMOS USB HiFi Audio Driver Technical Guide
|
||||
|
||||
--8<-- "common/checklogin_form.md"
|
||||
|
||||
## 引言
|
||||
在设计基于XMOS芯片的产品时，理解USB音频驱动的工作原理至关重要。XMOS解决方案采用USB UAC2.0协议传输音频数据，本文将详细介绍相关驱动技术及应用注意事项，帮助开发者更好地实现USB音频设备。
|
||||
## Introduction
|
||||
When designing products based on XMOS chips, understanding the working principles of USB audio drivers is crucial. XMOS solutions use the USB UAC 2.0 protocol to transmit audio data. This document provides detailed information on related driver technologies and application considerations to help developers better implement USB audio devices.
|
||||
|
||||
本指南主要提供XMOS USB音频驱动的基础技术概述。关于详细的安装配置、故障排除及应用案例等内容，将在后续技术文档中提供。
|
||||
This guide primarily provides a foundational technical overview of XMOS USB audio drivers. Detailed installation configuration, troubleshooting, and application case studies will be provided in subsequent technical documentation.
|
||||
|
||||
## USB音频类标准概述
|
||||
XMOS技术方案支持两种USB音频标准：
|
||||
## USB Audio Class Standard Overview
|
||||
XMOS technical solutions support two USB audio standards:
|
||||
|
||||
- **USB Audio Class 1.0 (UAC 1.0)** - 基本音频传输协议
|
||||
- **USB Audio Class 2.0 (UAC 2.0)** - 高级音频传输协议
|
||||
- **USB Audio Class 1.0 (UAC 1.0)** - Basic audio transmission protocol
|
||||
- **USB Audio Class 2.0 (UAC 2.0)** - Advanced audio transmission protocol
|
||||
|
||||
这两种协议均遵循USB国际联盟(USB-IF)制定的标准规范，确保了产品的兼容性与稳定性。
|
||||
Both protocols comply with standard specifications established by the USB Implementers Forum (USB-IF), ensuring product compatibility and stability.
|
||||
|
||||
## UAC 1.0与UAC 2.0技术对比
|
||||
## UAC 1.0 vs UAC 2.0 Technical Comparison
|
||||
|
||||
了解两种协议的差异对选择合适的方案至关重要：
|
||||
Understanding the differences between the two protocols is crucial for selecting the appropriate solution:
|
||||
|
||||
### 传输性能对比
|
||||
- UAC 1.0: 传输速率上限为12Mbit/s
|
||||
- UAC 2.0: 传输速率最高可达480Mbit/s
|
||||
### Transmission Performance Comparison
|
||||
- UAC 1.0: Transfer rate limit of 12Mbit/s
|
||||
- UAC 2.0: Transfer rate up to 480Mbit/s
|
||||
|
||||
### 功能特性对比
|
||||
### Feature Comparison
|
||||
|
||||
| 技术指标 | UAC 1.0 | UAC 2.0 |
|
||||
| Technical Specification | UAC 1.0 | UAC 2.0 |
|
||||
|---------|---------|---------|
|
||||
| 适用场景 | 简易音频设备，基础立体声应用 | 高端HiFi设备，专业多通道音频系统 |
|
||||
| 操作系统支持(macOS/Linux/iOS/Android) | 原生支持，无需额外驱动 | 原生支持，无需额外驱动 |
|
||||
| Windows系统支持 | 原生支持，即插即用 | 采样率≤384kHz时原生支持；>384kHz时需安装专用驱动 |
|
||||
| 音频规格 | 最高支持PCM 96kHz/16bit | 最高支持PCM 768kHz/32bit及DSD Native512 |
|
||||
| Application Scenarios | Simple audio devices, basic stereo applications | High-end HiFi devices, professional multi-channel audio systems |
|
||||
| Operating System Support (macOS/Linux/iOS/Android) | Native support, no additional drivers required | Native support, no additional drivers required |
|
||||
| Windows System Support | Native support, plug and play | Native support for sample rates ≤384kHz; dedicated driver required for >384kHz |
|
||||
| Audio Specifications | Up to PCM 96kHz/16bit | Up to PCM 768kHz/32bit and DSD Native512 |
|
||||
|
||||
## Windows平台UAC 2.0驱动解决方案
|
||||
## Windows Platform UAC 2.0 Driver Solutions
|
||||
|
||||
根据XMOS官方文档 [USB Audio 2.0 Driver for Windows - Overview](https://www.xmos.ai/download/USB-Audio-2.0-Driver-for-Windows---Overview(3.34.0).pdf) 的说明，在Windows系统中使用采样率高于384kHz的XMOS UAC 2.0设备时，需要安装专用驱动程序。
|
||||
According to XMOS official documentation [USB Audio 2.0 Driver for Windows - Overview](https://www.xmos.ai/download/USB-Audio-2.0-Driver-for-Windows---Overview(3.34.0).pdf), when using XMOS UAC 2.0 devices with sample rates higher than 384kHz on Windows systems, a dedicated driver must be installed.
|
||||
|
||||
### 评估版驱动详情
|
||||
对于开发测试阶段，可使用评估版驱动进行功能验证。该驱动支持多通道音频、SPDIF、MIDI及高采样率PCM和DSD传输，但存在使用限制：设备持续工作一小时后，系统会每隔五分钟发出提示音，提醒用户这是非商用授权驱动。
|
||||
### Evaluation Driver Details
|
||||
For the development and testing phase, an evaluation driver can be used for functional verification. This driver supports multi-channel audio, SPDIF, MIDI, and high sample rate PCM and DSD transmission, but has usage limitations: after the device operates continuously for one hour, the system will emit a notification sound every five minutes to remind users that this is a non-commercial licensed driver.
|
||||
|
||||
开发者可通过以下链接获取评估版驱动：
|
||||
Developers can obtain the evaluation driver through the following link:
|
||||
<a href="javascript:void(0);" onclick="checkLogin('/assets/download/Thesycon-USB-Audio-Class-2_0-Evaluation-Driver-for-Windows_5_58_0.zip')">Thesycon 5.58 Eva Driver for Windows</a>
|
||||
|
||||
### Thesycon商业驱动
|
||||
对于正式商业产品，建议采购Thesycon商业授权驱动。在完成产品评估后，可直接与Thesycon公司联系，协商功能需求和授权费用事宜。我们不参与此类商务谈判，用户需自行与驱动供应商建立商务合作关系。
|
||||
### Thesycon Commercial Driver
|
||||
For formal commercial products, it is recommended to purchase a Thesycon commercial licensed driver. After completing product evaluation, you can contact Thesycon directly to negotiate functional requirements and licensing fees. We do not participate in such business negotiations; users must establish business relationships with the driver supplier independently.
|
||||
|
||||
如需获取商业授权或咨询价格，请访问Thesycon官方联系页面： [Contact Thesycon](https://www.thesycon.de/eng/cont.shtml)
|
||||
To obtain commercial licensing or inquire about pricing, please visit the Thesycon official contact page: [Contact Thesycon](https://www.thesycon.de/eng/cont.shtml)
|
||||
|
||||
## USB设备识别码管理
|
||||
## USB Device Identification Code Management
|
||||
|
||||
USB设备通过VID(厂商识别码)和PID(产品识别码)进行唯一标识，这些编码由USB-IF组织分配管理。
|
||||
USB devices are uniquely identified through VID (Vendor ID) and PID (Product ID), which are assigned and managed by the USB-IF organization.
|
||||
|
||||
在开发XMOS USB音频产品时，可选择：
|
||||
- 使用Thesycon预分配的VID/PID组合
|
||||
- 使用自有的VID/PID（需在USB-IF注册并获得授权证书）
|
||||
When developing XMOS USB audio products, you can choose to:
|
||||
- Use Thesycon pre-assigned VID/PID combinations
|
||||
- Use your own VID/PID (requires registration with USB-IF and obtaining an authorization certificate)
|
||||
|
||||
对于定制产品方案，我们将与客户直接沟通VID/PID配置事宜。客户使用我们的标准固件产品时，可根据协议进行相应配置。正确的VID/PID配置对确保产品与驱动程序的兼容性至关重要。
|
||||
For custom product solutions, we will communicate VID/PID configuration matters directly with customers. When customers use our standard firmware products, configuration can be performed according to the agreement. Correct VID/PID configuration is crucial for ensuring product compatibility with driver software.
|
||||
|
||||
选择合适的识别码策略，有助于产品在市场中建立独特身份标识，并确保与现有驱动程序的兼容性。
|
||||
Selecting an appropriate identification code strategy helps establish a unique identity for products in the market and ensures compatibility with existing drivers.
|
||||
|
||||
## 结论
|
||||
选择合适的XMOS USB音频驱动方案，需综合考虑产品定位、技术需求和成本因素。UAC 2.0技术为高端音频设备提供了卓越的性能和扩展性，而合适的驱动程序选择则确保了产品在各操作系统平台的稳定运行。
|
||||
## Conclusion
|
||||
Selecting the appropriate XMOS USB audio driver solution requires comprehensive consideration of product positioning, technical requirements, and cost factors. UAC 2.0 technology provides excellent performance and scalability for high-end audio devices, while appropriate driver selection ensures stable product operation across various operating system platforms.
|
||||
|
||||
如需更多技术支持，请联系我们的技术服务部门。
|
||||
|
||||
## Consultation and Feedback
|
||||
For additional technical support, please contact our technical service department.
|
||||
|
||||
## Contact and Feedback
|
||||
<details>
|
||||
<summary>Click to expand consultation feedback form</summary>
|
||||
<summary>Click to expand contact and feedback form</summary>
|
||||
|
||||
--8<-- "common/customer_form.md"
|
||||
|
||||
</details>
|
||||
</details>
|
||||
|
||||
Reference in New Issue
Block a user