BLE Voice

Introduction GPIO configuration seems simple, but there are plenty of cases where things go wrong. If the drive strength isn't set correctly, an LED might be too dim or not light at all. Without proper pull-up/pull-down configuration, button detection can be erratic. The most troublesome is the USB pin—it might default to a regular GPIO, and if you forget to switch its function, your PC won't recognize the device. The JL JieLi AC696N's GPIOs are quite versatile, with three drive strength levels (normal, strong, super strong) and various APIs. However, these functions are scattered throughout the documentation, and you often have to search for a while when using them. I've gone through the common GPIO configurations on the AC696N development board and organized them into a table, so you can quickly look them up when writing drivers. I. GPIO Operating Modes Input Mode: Can be configured as floating, pull-up, pull-down, or analog (for ADC). In input mode, output is disab...

  Introduction The serial port is truly the "eyes" of a developer – that statement is no exaggeration. In embedded debugging, if you can't get logs out, it's like working blindfolded. The UART configuration on the JL Jieli AC696N is quite flexible. The debug print pin can be mapped arbitrarily, and the baud rate can be pushed up to 1M, making debugging very smooth. However, many beginners overlook one point: the serial port can not only output logs, but also connect to a PC tool for online tuning of audio effects. Parameters like EQ and DRC can be adjusted in real time without recompiling and flashing – you can hear the effect immediately. After tinkering with the AC696N development board, I've sorted out the configuration for both functions so I don't have to dig through the code every time. I. Configuring Serial Print In the board-level configuration header file (e.g., board_ac696x_demo_cfg.h), locate the UART0 configuration. Modify the following macros: #d...

  Introduction Timers seem simple, but using them in the wrong place either increases power consumption or causes timing inaccuracies—and debugging can be quite troublesome. The JL JieLi AC696N SDK provides two sets of timers: sys_timer and usr_timer. When first getting started, it's easy to get confused—when to use which? Why does my timer become inaccurate after entering sleep? Can I perform work in the callback? I encountered all these issues while debugging low-power solutions on the AC696N development board. Here's a summary of the differences and selection logic, so you can directly reference it when writing code. Chip Product Introduction I. System Timer (sys_timer) – "Software Timer" Features: Managed by the systimer thread, synchronous interface. The callback executes in the same thread where the timer was added. Low Power: System can sleep; the timer will wake the system when it expires, without losing ticks. Use Case: Suitable for general tasks that ...