Skip to content

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 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 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
  • Unable to receive messages sent by XU316
  1. Insufficient MCU response speed
    • While the MCU is processing other initialization tasks, XU316 has already completed initialization
  2. Power supply issues
    • MCU has not provided power to XU316
  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
  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 (wire jumpers, short circuits, etc.)

Q2: When WiFi is in slave mode, sending IIS in command is ineffective

  1. After normal connection and power-on, current mode is USB. Sending IIS in command has no effect
  1. Firmware function limitation
    • Current firmware does not support mode switching from WiFi (IIS slave) to XMOS (IIS master)
  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
  1. 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 phone cannot recognize the device

  1. Device can be recognized and play normally on PC
  2. Device cannot be recognized after connecting to phone
  1. Power supply mode issue
    • When phone is used as output device, the phone should supply power to the device
  1. Power supply mode conflict
    • Phone displays charging status when connected to device
    • This prevents the phone from outputting audio normally
  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

Consultation and Feedback

Click to expand consultation and feedback form
×

Notice

Company Name:

Email Address:

Subject:

Message: