A316 Series Product Firmware Development FAQ¶
Note
- 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.
- The following solutions use the A316-HF-DAC as an example. Other A316 series products may require adjustments based on actual circumstances.
Communication Issues¶
Q1: XU316 cannot send or receive data when connected to PC or MCU via serial port, and logic analyzer cannot capture data¶
- XU316 cannot send or receive data when connected to PC via serial port
- Logic analyzer cannot capture communication data
- Messages sent by XU316 are not received
- Insufficient MCU response speed
- MCU is processing other initialization tasks when XU316 has already completed initialization
- Power supply issues
- MCU does not provide power to XU316
- Initialization timing issues
- XU316 sends power-on command (0x00) 4 times after power-up
- 300ms interval between each command
- Communication fails if initialization is not completed or no reply is received before the 4 commands finish
- Power supply issues
- Insufficient power supply to XU316 will cause startup failure
- Optimize initialization process
- Prioritize XU316 configuration
- Ensure initialization is completed before XU316 sends power-on commands
- Check power supply design
- Inspect hardware design
- Perform hardware modifications if necessary (wire jumpers, short circuits, etc.)
Q2: Sending I2S IN command is ineffective when WiFi is in slave mode¶
- After normal wiring and power-up, current mode shows USB, but sending I2S IN command has no effect
- Firmware function limitations
- Current firmware does not support mode switching from WiFi (I2S slave) to XMOS (I2S master)
- Communication status
- Commands can communicate normally
- But mode switching function does not take effect
- Function limitations
- Firmware has not implemented conversion function from WiFi slave mode to XMOS master mode
- Modify connection method
- Mount WiFi module to Bluetooth module
- Implement mode switching function through Bluetooth module
Device Recognition Issues¶
Q1: Device is recognized and plays normally on PC, but mobile phone cannot recognize device¶
- Device can be recognized and plays normally on PC
- Device cannot be recognized after connecting to mobile phone
- Power supply mode issues
- When mobile phone acts as output device, it should supply power to the device
- Power supply mode conflict
- Mobile phone shows charging status when connected to device
- Causes mobile phone to fail to output audio normally
- 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
Contact and Feedback¶
Click to expand contact and feedback form
×