BLE Voice

1.4 DAC Anti-Interference Circuit Description AC695N and AC696N support DACL/DACR differential mode and DACL/DACR/VCOMO stereo mode. Schematic is as follows: (1) It is recommended to reserve anti-interference circuits for the DAC section; if space is limited, only L4/L5/L6 can be reserved. (2) For strict noise requirements, it is suggested to place  AGND  copper pour (or no pour) on both sides around the DAC circuit and solder points.  Do not pour "digital GND"  and  keep away from "digital GND" to effectively eliminate high-frequency noise. (3) L4/L5 should be fixed at 100nH or 120nH to effectively remove high-frequency TDD noise generated when a mobile phone is near the device during Bluetooth calls; L6 should be fixed at 220nH or 330nH to effectively remove high-frequency noise during music playback (try this method if LAYOUT is not optimal). Note: The reserved noise handling circuit on the DAC side increases cost. If the design is reasonable enough and n...

During the development of Bluetooth smart speakers using Jieli's AC696N series SoCs, developers may encounter several common issues. This article summarizes these problems and provides corresponding solutions to help streamline the development process. 1. AC696N V1.7.0: Unable to Display SDK Version Number via Test Box When TWS is Enabled Problem Description: After enabling TWS (True Wireless Stereo) in AC696N V1.7.0 SDK, the test box cannot display the SDK version number. Solution: Register a new callback function to handle the SDK version information request. // Re-register a callback function bt_testbox_ex_info_get_handle_register(TESTBOX_INFO_SDK_VERSION, user_bt_get_sdk_ver_info); // Callback function example: u8 user_bt_get_sdk_ver_info(u8 len) { y_printf("Getting version number\n"); const char *p = sdk_version_info_get(); if (len) { *len = strlen(p); } log_info("sdk_ver:%s %x\n", p, *len); return (u8 *)p; } After Modification: The SDK version numb...

Debugging is a crucial part of embedded development. For AC696N series SoCs, the SDK provides a flexible and layered print output control system. This guide will walk you through the key configuration options for managing debug prints. 1. Print Control a. Global Print Switch The master switch for all debug output is located in app_config.h . // app_config.h #ifndef CONFIG_DEBUG_ENABLE // Control global debug output here #endif b. Library Debug Output (LIB_DEBUG) Library-specific debug prints can be controlled separately in app_config.h . // app_config.h #ifdef CONFIG_RELEASE_ENABLE #define LIB_DEBUG 1 #else #define LIB_DEBUG 1 #endif c. Logging System & Level Control The logging module ( log.h ) supports multiple severity levels. Level Definitions (0–6): // log.h #define __LOG_VERB 0 // Verbose #define __LOG_DEBUG 1 // Debug #define __LOG_INFO 2 // Info #define __LOG_WARN 3 // Warning #define __LOG_ERROR 4 // Error #define __LOG_CHAR 5 // Character output Level Filter:...