update
This commit is contained in:
PhatenIoT-yan
123
en/docs/dev_doc/faq/technical_faq/a316_firmware_dev_faq.md
Normal file
123
en/docs/dev_doc/faq/technical_faq/a316_firmware_dev_faq.md
Normal file
@@ -0,0 +1,123 @@
|
||||
---
|
||||
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
|
||||
---
|
||||
|
||||
--8<-- "common/phaten_xmos_support_img.md"
|
||||
|
||||
# A316 Series Product Firmware Development FAQ
|
||||
|
||||
!!! 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.
|
||||
|
||||
## Communication Issues
|
||||
|
||||
### Q1: XU316 cannot send/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
|
||||
- Logic analyzer cannot capture communication data
|
||||
- Cannot receive messages sent by XU316
|
||||
|
||||
=== "Possible Causes"
|
||||
1. Insufficient MCU response speed
|
||||
- MCU is processing other initialization tasks while XU316 has already completed initialization
|
||||
2. Power supply issues
|
||||
- MCU is not providing 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
|
||||
2. Power supply issues
|
||||
- Insufficient power supply to XU316 will cause startup failure
|
||||
|
||||
=== "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
|
||||
- Perform hardware modifications if necessary (flying wires, short circuits, etc.)
|
||||
|
||||
</div>
|
||||
|
||||
### Q2: Sending IIS in command is ineffective when WiFi is in slave mode
|
||||
|
||||
<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
|
||||
|
||||
=== "Possible Causes"
|
||||
1. Firmware function limitations
|
||||
- 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
|
||||
|
||||
=== "Solutions"
|
||||
1. Modify connection method
|
||||
- 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
|
||||
|
||||
<div class="grid" markdown>
|
||||
|
||||
=== "Problem Symptoms"
|
||||
1. Device can be recognized and play normally on PC
|
||||
2. Cannot recognize device when connected to mobile phone
|
||||
|
||||
=== "Possible Causes"
|
||||
1. Power supply mode issues
|
||||
- When mobile phone acts as output device, it should provide 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
|
||||
|
||||
=== "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 mobile 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>
|
||||
134
en/docs/dev_doc/faq/technical_faq/technical_faq.md
Normal file
134
en/docs/dev_doc/faq/technical_faq/technical_faq.md
Normal file
@@ -0,0 +1,134 @@
|
||||
---
|
||||
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
|
||||
---
|
||||
|
||||
--8<-- "common/phaten_xmos_support_img.md"
|
||||
|
||||
# Technical FAQ for WiFi Audio + Bluetooth Modules
|
||||
|
||||
## Q1: Does the module support IR remote decoding?
|
||||
|
||||
**IR remote decoding is supported.**
|
||||
|
||||
---
|
||||
|
||||
## Q2: Power consumption during module 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**:
|
||||
- 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
|
||||
|
||||
---
|
||||
|
||||
## Q3: What is the WIFI and BT chip architecture of the module?
|
||||
|
||||
A single SoC integrates both WIFI and BT functions.
|
||||
|
||||
---
|
||||
|
||||
## Q4: Does it support online TX/RX switching?
|
||||
|
||||
### Support status:
|
||||
- Supports online TX/RX switching in WIFI mode
|
||||
- BT mode limitations:
|
||||
- SoC only supports BLE5.0
|
||||
- Does not support Classic BT
|
||||
- Cannot transmit audio via mobile phone Bluetooth
|
||||
|
||||
### Working mode description:
|
||||
|
||||
=== "**TV Mode**:"
|
||||
- The transmitter box is WIFI TX
|
||||
- The receiving 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
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
## 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
|
||||
|
||||
|
||||
|
||||
<!-- Structured Data Markup -->
|
||||
<script type="application/ld+json">
|
||||
{
|
||||
"@context": "https://schema.org",
|
||||
"@type": "FAQPage",
|
||||
"mainEntity": [
|
||||
{
|
||||
"@type": "Question",
|
||||
"name": "Does the module support IR remote decoding?",
|
||||
"acceptedAnswer": {
|
||||
"@type": "Answer",
|
||||
"text": "IR remote decoding is supported."
|
||||
}
|
||||
},
|
||||
{
|
||||
"@type": "Question",
|
||||
"name": "What is the power consumption during module 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."
|
||||
}
|
||||
},
|
||||
{
|
||||
"@type": "Question",
|
||||
"name": "What is the WIFI and BT chip architecture of the module?",
|
||||
"acceptedAnswer": {
|
||||
"@type": "Answer",
|
||||
"text": "A single SoC integrates both WIFI and BT functions."
|
||||
}
|
||||
},
|
||||
{
|
||||
"@type": "Question",
|
||||
"name": "Does it support online TX/RX switching?",
|
||||
"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."
|
||||
}
|
||||
},
|
||||
{
|
||||
"@type": "Question",
|
||||
"name": "How is the Bluetooth TWS function 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."
|
||||
}
|
||||
}
|
||||
]
|
||||
}
|
||||
</script>
|
||||
Reference in New Issue
Block a user