A method for mute control of vehicle-mounted audio output based on software and hardware cooperation

Abstract

The application provides a method for mute control of vehicle audio output based on hardware-software cooperation, which comprises: monitoring the running state of the vehicle audio system according to the mute control trigger conditions corresponding to a plurality of control modes including a pure hardware mode, a hardware-triggered software cooperation mode and a pure software mode, and determining whether to trigger mute control; if it is determined to trigger mute control, determining the corresponding target control mode and target control strategy in the mode according to the monitored current mute control trigger condition; performing mute control operation according to the core control action and execution time sequence requirement specified in the target control strategy; and monitoring the running state of the vehicle audio system after the mute control operation is performed, and performing mode transfer when the mode switching condition corresponding to the target control mode is met. Thus, the audio mute control effect with high real-time performance, high reliability and full-scene adaptation can be effectively realized by the present scheme.

Description

Technical Field

[0001] This application relates to the field of vehicle audio control technology, and in particular to a method for mute control of vehicle audio output based on hardware and software collaboration. Background Technology

[0002] With the development of automotive intelligence and connectivity, in-vehicle audio systems have become a core human-machine interaction hub integrating navigation broadcasts, voice calls, online media, vehicle network warnings, and emergency calls. The quality and reliability of its audio output directly affect driving safety and the driving experience. In this scenario, audio mute control is a key technology to ensure system robustness. Its core challenge lies in simultaneously addressing two types of electrical problems: first, the transient electrical noise generated when the vehicle's power is switched on or off or when modes are changed. If this noise is not suppressed, it will transform into audible popping sounds, interfering with the driver's attention; second, the persistent background noise or ambient noise formed by various strong electromagnetic interferences coupled into the audio link from the complex electrical environment of the vehicle, which will seriously affect the accuracy of voice recognition and the entertainment experience. Summary of the Invention

[0003] In view of this, the purpose of this application is to provide a method for mute control of vehicle audio output based on software and hardware collaboration. Through multi-mode collaboration of software and hardware, dynamic triggering and mode transfer mechanism, it specifically solves the two core challenges of transient electrical noise and continuous electromagnetic interference faced by vehicle audio systems mentioned in the prior art. It can effectively achieve audio mute control effect with high real-time performance, high reliability and full-scenario adaptability.

[0004] This application provides a method for mute control of in-vehicle audio output based on hardware and software collaboration. The method includes: Based on the mute control trigger conditions corresponding to each of the multiple control modes, including pure hardware mode, hardware-triggered software collaborative mode, and pure software mode, the operating status of the vehicle audio system is monitored to determine whether to trigger mute control. If it is determined that mute control is triggered, the corresponding target control mode and the target control strategy under the target control mode are determined based on the current mute control trigger condition detected by the mute control trigger. In the target control mode, a mute control operation is performed in accordance with the core control actions and execution timing requirements specified in the target control strategy. The operating status of the vehicle audio system after the mute control operation is monitored, and a mode transition is performed when the mode switching conditions corresponding to the target control mode are met.

[0005] Optionally, based on the mute control trigger conditions corresponding to the pure hardware mode, the operating status of the in-vehicle audio system is monitored to determine whether to trigger mute control, including: The current power-on voltage and current power-off voltage of the vehicle power system are input into a comparator with power-on voltage thresholds and power-off voltage thresholds, and the comparator inputs two first-level signals into the AND circuit according to the comparison result. The hardware watchdog inputs a second-level signal determined by the software operation status in the vehicle system and its own power supply circuit, and a third-level signal determined by the current state of the power amplifier's error indicator pin, into the NAND circuit. If the output level signal of either the AND circuit or the NAND circuit is high, then the mute control is triggered. If the output level signals in both the AND and NAND circuits are low, then the mute control will not be triggered.

[0006] Optionally, based on the mute control trigger conditions corresponding to the hardware-triggered software collaborative mode, the operating status of the in-vehicle audio system is monitored to determine whether to trigger mute control, including: Identify whether a transient popping sound is generated or whether the SOC chip receives any of the following signals: a first signal determined by a low level output from the power amplifier's error indication pin, a second signal determined by a low level output from the comparator based on the current voltage value of the first power supply powering the power amplifier, and a third signal determined by a low level output from the voltage monitoring chip based on the current voltage value of the third power supply powering the SOC chip and the current voltage value of the second power supply powering the audio codec; If any signal is received or a transient popping sound is detected, the mute control is triggered; otherwise, the mute control is not triggered.

[0007] Optionally, based on the mute control trigger conditions corresponding to the pure software mode, the operating status of the in-vehicle audio system is monitored to determine whether to trigger mute control, including: Identify whether the SOC chip receives any of the following signals: audio source switching request signal, audio source playback signal, audio source pause signal, vehicle audio system wake-up signal, vehicle audio system sleep signal, and emergency audio cut-in request signal; If any signal is received, the mute control will be triggered; if no signal is received, the mute control will not be triggered.

[0008] Optionally, when the target control mode determined based on the current mute control triggering condition monitored by the mute control is a pure hardware mode, the target control strategy in the target control mode is: A high-level signal is simultaneously input to the first transistor, the first delay circuit, and the second delay circuit; wherein the delay duration of the first delay circuit is shorter than the delay duration of the second delay circuit. A low-level signal is input from the first transistor to the MUTE pin of the power amplifier; The first delay circuit inputs the delayed high-level signal to the second transistor, and the second transistor inputs a low-level signal to the first power supply control terminal of the power amplifier. The second delay circuit inputs the delayed high-level signal to the third transistor, and the third transistor inputs a low-level signal to the STB pin of the power amplifier.

[0009] Optionally, when the target control mode determined based on the current mute control triggering conditions monitored by the mute control is a hardware-triggered software-coordinated mode, the target control strategy under the target control mode is: When the current mute control trigger condition is that the SOC chip receives the first signal and / or the second signal and / or the third signal, the corresponding target control strategy is: The SOC chip performs mute configuration on the registers in the power amplifier via the I2C bus, sends a low-level signal to the MUTE pin of the power amplifier, sends a low-level signal to the STB pin of the power amplifier, and controls the power enable signal through the enable signal pin of the power amplifier.

[0010] Optionally, when the target control mode determined based on the current mute control triggering conditions monitored by the mute control is a hardware-triggered software-coordinated mode, the target control strategy under the target control mode is: When the current mute control trigger condition is based on the detection of a transient popping sound, the corresponding target control strategy is: The system sends a low-level signal to the MUTE pin of the power amplifier via hardware, and the SOC chip sequentially configures the audio codec and the power amplifier.

[0011] Optionally, when the target control mode determined based on the current mute control triggering condition monitored by the mute control is a pure software mode, the target control strategy under the target control mode is: When the current mute control trigger condition is based on the detection of a sound source switching request signal, the corresponding target control strategy is: Configure the registers in the power amplifier via the I2C bus, lower the MUTE pin level in the power amplifier, and raise the STB pin voltage of the power amplifier after the source switching is completed.

[0012] Optionally, when the target control mode determined based on the current mute control triggering condition monitored by the mute control is a pure software mode, the target control strategy under the target control mode is: When the current mute control trigger condition is based on the detection of an audio source playback signal, the corresponding target control strategy is: The STB pin voltage of the power amplifier is pulled high, and the MUTE pin voltage in the power amplifier is pulled high after a preset delay, and the audio output is started through the audio codec; When the current mute control trigger condition is based on the detection of a sound source pause signal, the corresponding target control strategy is: Configure the registers in the power amplifier and lower the MUTE pin level in the power amplifier via the I2C bus.

[0013] Optionally, when the target control mode determined based on the current mute control triggering condition monitored by the mute control is a pure software mode, the target control strategy under the target control mode is: When the current mute control trigger condition is based on the detection of a wake-up signal from the vehicle audio system, the corresponding target control strategy is: Power is supplied to the SOC chip, and after a first delay, power is supplied to the audio codec, and after a second delay, power is supplied to the power amplifier; After the power amplifier is ready, the voltage of the STB pin of the power amplifier is pulled low, and the voltage of the MUTE pin of the power amplifier is pulled high after the third delay, and the audio codec starts audio output; When the current mute control trigger condition is based on the detection of a sleep signal from the vehicle audio system, the corresponding target control strategy is: Pull the MUTE pin voltage of the power amplifier low, pull the STB pin voltage of the power amplifier low after the fourth delay, and turn off the power amplifier power supply after the fifth delay. After the sixth delay, the audio codec power is turned off, and after the audio codec power is turned off, the SOC chip power supply is turned off. When the current mute control trigger condition is based on the detection of an emergency audio cut-in request signal, the corresponding target control strategy is: The normal audio channel in the power amplifier is muted via the I2C bus, then the voltage of the MUTE pin of the power amplifier is pulled low, and finally the emergency audio channel is switched.

[0014] This application embodiment also provides a device for muting in-vehicle audio output based on hardware and software collaboration, the control device comprising: The first monitoring module is used to monitor the operation status of the vehicle audio system and determine whether to trigger the mute control based on the mute control trigger conditions corresponding to each of the multiple control modes, including pure hardware mode, hardware-triggered software collaborative mode, and pure software mode. The determination module is used to determine the corresponding target control mode and the target control strategy under the target control mode if it is determined that the mute control is triggered. The execution module is used to perform a mute control operation in the target control mode according to the core control actions and execution timing requirements specified in the target control strategy; The second monitoring module is used to monitor the operating status of the vehicle audio system after the mute control operation is completed, and to perform a mode transfer when the mode switching conditions corresponding to the target control mode are met.

[0015] This application also provides an electronic device, including: a processor, a memory, and a bus. The memory stores machine-readable instructions executable by the processor. When the electronic device is running, the processor communicates with the memory via the bus. When the machine-readable instructions are executed by the processor, the steps of the method described above are performed.

[0016] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, performs the steps of the method described above.

[0017] This application provides a method for muting in-vehicle audio output based on hardware and software collaboration. The method includes: monitoring the operating status of the in-vehicle audio system according to the muting control trigger conditions corresponding to multiple control modes, including pure hardware mode, hardware-triggered software collaboration mode, and pure software mode, to determine whether muting control is triggered; if muting control is triggered, determining the corresponding target control mode and target control strategy under the current muting control trigger conditions; executing a muting control operation according to the core control actions and execution timing requirements specified in the target control strategy under the target control mode; monitoring the operating status of the in-vehicle audio system after the muting control operation, and performing a mode transition when the mode switching conditions corresponding to the target control mode are met.

[0018] Thus, this application constructs an integrated mute control architecture encompassing three modes: pure hardware, pure software, and hardware-triggered software adaptive collaboration, creating complementary advantages. The pure hardware mode ensures mute safety under extreme conditions through an independent control link; the pure software mode enables flexible and intelligent control under normal circumstances; and the hardware-triggered software collaborative mode leverages the hardware's front-end to rapidly perceive and trigger deep software optimization, achieving closed-loop control of perception-decision-execution-feedback. This systematically solves various mute control challenges in automotive scenarios and effectively suppresses pop-up sounds and transient noise, improving audio switching smoothness based on specific mute control trigger conditions and corresponding control strategies. Furthermore, the hardware triggering mechanism can detect anomalies and initiate responses within microseconds, while the software collaborative decision-making is completed within milliseconds, balancing real-time performance and control precision.

[0019] To make the above-mentioned objectives, features and advantages of this application more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0020] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0021] Figure 1 A flowchart illustrating a method for mute control of in-vehicle audio output based on hardware and software collaboration, provided in an embodiment of this application. Figure 2 The diagram shows the principle block diagram of in-vehicle audio output; Figure 3 The schematic diagram of the signal processing logic of the hardware mute control circuit is shown. Figure 4 This is a schematic diagram of the hardware exception triggering logic in the hardware-triggered software collaborative mode. Figure 5 This is a schematic diagram of the fast power-on / off timing logic in pure software mode. Figure 6 This is a schematic diagram of the device for controlling the mute of in-vehicle audio output based on hardware and software collaboration, provided in an embodiment of this application. Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0022] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. The components of the embodiments of this application described and shown in the accompanying drawings can generally be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely represents selected embodiments of this application. Based on the embodiments of this application, every other embodiment obtained by those skilled in the art without inventive effort falls within the scope of protection of this application.

[0023] With the development of automotive intelligence and connectivity, in-vehicle audio systems have become a core human-machine interaction hub integrating navigation broadcasts, voice calls, online media, vehicle network warnings, and emergency calls. The quality and reliability of its audio output directly affect driving safety and the driving experience. In this scenario, audio mute control is a key technology to ensure system robustness. Its core challenge lies in simultaneously addressing two types of electrical problems: first, the transient electrical noise generated when the vehicle's power is switched on or off or when modes are changed. If this noise is not suppressed, it will transform into audible popping sounds, interfering with the driver's attention; second, the persistent background noise or ambient noise formed by various strong electromagnetic interferences coupled into the audio link from the complex electrical environment of the vehicle, which will seriously affect the accuracy of voice recognition and the entertainment experience.

[0024] To address these challenges, existing technologies primarily offer two independent solutions: The first type is a pure hardware-based mute solution. This solution achieves mute by setting up hardware circuits consisting of resistors, capacitors, inductors, or analog switches on the enable pin of the audio power amplifier or on the audio signal path. Its inherent disadvantages are: slow response and poor flexibility; the mute timing is determined by fixed hardware parameters, making it unable to adapt to the dynamic needs of different scenarios such as rapid system startup and emergency mute; and its function is limited, mainly targeting the power-on / off pop-up sound, and it is powerless against sudden and intermittent noises caused by electromagnetic interference during driving, lacking the ability to sense and dynamically respond to such noises.

[0025] The second type is the pure software mute solution. This solution involves the main control chip sending a mute command to the audio codec via general-purpose input / output ports or a bus, controlling the audio path at the software level. Its inherent drawbacks are: real-time performance cannot be guaranteed, and there is a mute blind spot. The software operation depends on the operating system's scheduling and initialization; in transient situations such as system startup, reset, or high-priority task blocking, the software may fail to start or respond in time. During the uncontrollable time window between hardware power-on and software takeover control, the audio path is highly susceptible to popping sounds. Furthermore, when strong electromagnetic interference causes the main control chip to reset or bus communication to be disrupted, software commands may be lost or delayed, resulting in weak anti-interference capabilities and reliability issues.

[0026] Therefore, the main drawback of this technology lies in the fact that hardware solutions are rigid and slow, while software solutions are fragile and outdated. Neither can provide a highly reliable audio mute control solution with real-time response, dynamic adaptation, and high reliability in the unique environment of automotive systems, characterized by high reliability, strong interference, and multiple scenarios. This directly leads to a decline in user experience and potential safety risks.

[0027] Based on this, the embodiments of this application provide a method for mute control of in-vehicle audio output based on hardware and software collaboration, achieving a high real-time, high reliability, and all-scenario adaptable audio mute control effect.

[0028] Please see Figure 1 , Figure 1 This is a flowchart illustrating a method for controlling the mute of in-vehicle audio output based on hardware and software collaboration, as provided in an embodiment of this application. Figure 1 As shown in the embodiments of this application, the method includes: S101. Based on the mute control trigger conditions corresponding to each of the multiple control modes, including pure hardware mode, hardware-triggered software-coordinated mode, and pure software mode, monitor the operation status of the vehicle audio system and determine whether to trigger mute control. S102. If it is determined that the mute control is triggered, determine the corresponding target control mode and the target control strategy under the target control mode according to the current mute control triggering condition monitored by the mute control trigger. S103. In the target control mode, execute the mute control operation according to the core control actions and execution timing requirements specified in the target control strategy; S104. Monitor the operating status of the vehicle audio system after performing the mute control operation, and perform mode transfer when the mode switching conditions corresponding to the target control mode are met.

[0029] The on-board output schematic diagram used in executing the above control method is as follows: Figure 2 As shown, Figure 2As shown, the in-vehicle audio output is mainly achieved through the coordinated operation of the SOC chip, audio codec, power amplifier, and speaker.

[0030] The SOC chip is the main control chip, which acts as the brain of the entire vehicle audio system, responsible for scheduling audio content, managing system status, and making mute strategy decisions.

[0031] The SOC chip connects to the audio codec via the I2S bus and to the audio codec and power amplifier via the I2C bus. The I2S bus is the integrated audio bus built into the integrated circuit, used to transmit digital audio data (PCM (Pulse Code Modulation) / DSP (Digital Signal Processing) audio stream) to the CODEC (audio codec), including bit clock (BCLK), word clock (LRCLK), data (SDATA) signals, to ensure synchronous and lossless transmission of audio data.

[0032] The I2C bus is an integrated circuit bus used to send configuration parameters (such as volume, sampling rate, and channel selection) to the CODEC (audio codec) and control commands (such as mute enable, gain adjustment, fault detection reset, etc.) to the Amplifier (audio power amplifier).

[0033] The SOC chip mainly generates a mute control signal (MUTE (mute pin)) based on the system status (such as power on / off, mode switching, software abnormality, external trigger), and sends it to the CODEC and Amplifier via I2C to realize the issuance of active mute commands at the software level.

[0034] The audio codec (CODEC) is used to perform digital-to-analog conversion (DAC (digital-to-analog converter)) and is a key conversion node in the audio link.

[0035] The input of the audio codec (CODEC) is the digital audio signal received from the SOC via the I2S bus. The output converts the digital audio into differential analog audio signals (AIN_P (positive terminal of the differential analog audio input pin), AIN_N (negative terminal of the differential analog audio input pin)) and outputs them to the Amplifier, effectively suppressing common-mode noise and improving audio fidelity.

[0036] The control input of the audio codec (CODEC) is: receiving control commands such as mute, gain, and filtering sent by the SOC via the I2C bus. The audio codec (CODEC) can independently receive the I2C mute command from the SOC, turn off the internal DAC (digital-to-analog converter) output, or set the impedance high to achieve CODEC-level mute.

[0037] Its output terminals (AIN_P / AIN_N) should be in a controllable state (such as zero level or high impedance) when in mute mode to avoid introducing noise by leaving them floating.

[0038] The power amplifier amplifies the analog audio signal output from the CODEC to drive the speaker and is the last stage of the audio output.

[0039] Power Amplifier Signal Interface: The input is: receiving the differential analog signals (AIN_P, AIN_N) output from the CODEC.

[0040] Output: The amplified differential signal (AOUT_P (positive terminal of differential analog audio output pin), AOUT_N (negative terminal of differential analog audio output pin)) drives the speaker.

[0041] Control input: I2C: Receives control commands from the SOC such as mute, gain, and protection.

[0042] STB (Standby) (Standby / Enable Pin): Low-power standby control signal used to shut down the power amplifier when the system is in sleep mode.

[0043] MUTE (Mute Pin): Mute control signal, used to quickly cut off audio output.

[0044] Hardware-level mute for power amplifiers involves directly controlling the amplifier output via the MUTE or STB pins, achieving millisecond-level response, rapidly cutting off audio output, and suppressing transient noise.

[0045] Software-level mute for power amplifiers involves receiving a mute command from the SOC via I2C and adjusting the internal gain or shutting down the output.

[0046] Power amplifier collaborative control: Supports hardware trigger + software confirmation mode. For example, in the event of a system malfunction, the hardware circuit first triggers mute, and then the SOC software performs subsequent processing.

[0047] A speaker converts the electrical signal output from a power amplifier into sound waves, thus producing the final sound output. It receives the differential signal (AOUT_P, AOUT_N) output from the amplifier and uses a coil to drive the diaphragm to produce sound.

[0048] A speaker passively receives signals and has no active control capability. Its sound output depends entirely on the output of the preamplifier.

[0049] The system consists of a main control SOC, an audio codec (CODEC), a power amplifier (Amplifier), and a speaker. The signal flow is as follows: the SOC sends digital audio signals to the CODEC via the I2S bus and control commands to the CODEC and Amplifier via the I2C bus. The CODEC converts the digital audio signals into differential analog signals (AIN_P, AIN_N) and outputs them to the Amplifier. The Amplifier amplifies the analog signals and outputs differential signals (AOUT_P, AOUT_N) to drive the speaker to produce sound.

[0050] The exemplary steps of the embodiments of this application are described below: Regarding step S101, the mute control trigger conditions are different for the pure hardware mode, the hardware-triggered software collaborative mode, and the pure software mode.

[0051] In one embodiment provided in this application, when monitoring the operating status of the vehicle audio system according to the mute control trigger condition corresponding to the pure hardware mode, and determining whether to trigger mute control, the method includes: S1011. Input the current power-on voltage and the current power-off voltage of the vehicle power system into a comparator that is set with power-on voltage threshold and power-off voltage threshold, and the comparator inputs two first level signals into the AND circuit according to the comparison result. S1012. Input the second level signal determined by the hardware watchdog based on the software operation status in the vehicle system and its own power supply circuit, and the third level signal determined based on the current state of the power amplifier's error indicator pin, into the NAND circuit. S1013. If the output level signal of either the AND circuit or the NAND circuit is high, then the mute control is triggered. S1014. If the output level signals in both the AND and NAND circuits are low, then it is determined that the mute control will not be triggered.

[0052] For steps S1011-S1014, the processing logic principle used to determine whether the pure hardware mode mute control is satisfied is detailed in the following section. Figure 3 , Figure 3 A schematic diagram of the signal processing logic for a hardware mute control circuit is shown. For example, the power-on voltage threshold can be set to 5.5V, and the power-off voltage threshold can be set to 8.5V. Thus, based on... Figure 3When the circuit diagram shown performs the hardware mode mute control judgment, it specifically includes: if the hardware detects that the power-on voltage is greater than 5.5V, the comparator LM2903 outputs a high level (H); if the power-off voltage is lower than 8.5V, the comparator LM2903 outputs a high level (H), which is then passed to the AND gate SN74LVC08ADR. Only when both conditions are met simultaneously, H and H, will the AND gate SN74LVC08ADR output H.

[0053] The hardware watchdog detects whether its own 3.3V power supply is abnormal, whether the software has a runaway bug, and whether the Amplifier-ERR pin is abnormally low (L). If the 3.3V power supply is abnormal or the software has a runaway bug, the hardware watchdog TPS3110 outputs a low level (L). Any of the above three abnormalities outputs H through the NAND gate SN74HC00DR.

[0054] It should be noted that this circuit diagram is designed to be compatible with PCB (printed circuit board) layout and routing. Analog signals are preferentially routed using differential routing. If hardware topology limitations prevent this, a quasi-differential design is used. Grounding protection is implemented throughout the routing process (analog ground isolation strips are laid on both sides and grounded at a single point). At the same time, the physical isolation between analog ground and digital ground and the single-point common ground strategy are strictly implemented to maximize the suppression of strong electromagnetic interference in the vehicle and ensure the purity of audio signals from the routing level.

[0055] In another embodiment provided in this application, when monitoring the operation status of the vehicle audio system according to the mute control triggering condition corresponding to the hardware-triggered software collaborative mode, and determining whether to trigger mute control, the method includes: Identify whether a transient popping sound is generated or whether the SOC chip receives any of the following signals: a first signal determined by a low level output from the power amplifier's error indication pin, a second signal determined by a low level output from the comparator based on the current voltage value of the first power supply powering the power amplifier, and a third signal determined by a low level output from the voltage monitoring chip based on the current voltage value of the third power supply powering the SOC chip and the current voltage value of the second power supply powering the audio codec; If any signal is received or a transient popping sound is detected, the mute control is triggered; otherwise, the mute control is not triggered.

[0056] In this embodiment, determining whether the SOC chip has received any of the three signals is actually determining whether the power amplifier itself is faulty, whether the power amplifier power supply is abnormal, and whether the core power supply is fluctuating abnormally.

[0057] For an example, please refer to Figure 4 , Figure 4 This is a schematic diagram illustrating the hardware exception triggering logic in a hardware-triggered software collaborative mode. For example... Figure 4As shown, three parallel hardware fault detection branches are set up to monitor various abnormal states in real time: The system directly acquires the Amplifier-ERR pin signal from the power amplifier. When an internal abnormality occurs in the power amplifier IC, this pin outputs a low-level fault signal and a low-level interrupt signal to the SOC. The LM2903 comparator monitors the current state of the power amplifier's first power supply. When the current voltage of the first power supply is below 8.8V, or when strong magnetic interference causes a power supply abnormality, a low-level interrupt signal is output to the SOC. The MAX811TEU voltage monitoring chip monitors the system's core power supply. When the monitored SOC chip's 3.3V system voltage is below 2.95V, the audio codec chip's 1.8V system voltage is below 1.65V, or strong magnetic interference causes fluctuations in the core power supply, a low-level interrupt signal is output to the SOC.

[0058] In another embodiment provided in this application, when monitoring the operation status of the vehicle audio system according to the mute control trigger condition corresponding to the pure software mode, and determining whether to trigger mute control, the process includes: identifying whether the SOC chip receives any of the following signals: audio source switching request signal, audio source playback signal, audio source pause signal, vehicle audio system wake-up signal, vehicle audio system sleep signal, and emergency audio cut-in request signal; if any signal is received, it is determined that mute control is triggered; if no signal is received, it is determined that mute control is not triggered.

[0059] For step S102, the target control strategies corresponding to different target control modes are not the same, and the target control strategies corresponding to the same target control mode determined based on different silence control trigger conditions are also not the same.

[0060] In one embodiment provided in this application, when the target control mode is determined to be a pure hardware mode based on the current mute control triggering condition monitored by the trigger mute control, the target control strategy in the target control mode is as follows: a high-level signal is simultaneously input to a first transistor, a first delay circuit, and a second delay circuit; wherein the delay duration of the first delay circuit is shorter than the delay duration of the second delay circuit; a low-level signal is input to the MUTE pin of the power amplifier from the first transistor; the delayed high-level signal is input to the second transistor from the first delay circuit, and a low-level signal is input to the first power control terminal of the power amplifier from the second transistor; the delayed high-level signal is input to the third transistor from the second delay circuit, and a low-level signal is input to the STB pin of the power amplifier from the third transistor.

[0061] Please continue reading. Figure 3 ,according to Figure 3As shown in the diagram and the example above, in pure hardware mute control, the subsequent NPN transistor circuit provides hierarchical control. MUTE mute is prioritized, and the RC (delay circuit) delays the NPN transistor to control the power amplifier's power supply and STB enable pin. Furthermore, the power amplifier's power supply is turned off before the STB. This achieves complete hardware-level mute. Only after power-on and power-off are complete, the program is normal, the power supply is normal, and there is no ERR (error feedback) feedback can the mute be released and audio played according to software requirements.

[0062] Specifically, this can be achieved by immediately pulling the MUTE pin low (hardware mute), shutting off the AP3 power supply within 2ms, and pulling the STB pin low within 3ms. Here, the MUTE trigger is at the microsecond level (<10μs), and the entire process is executed independently by hardware without software intervention.

[0063] Thus, the signal processing and output control logic diagram of the purely hardware-implemented Amplifier mute control circuit integrates multiple types of input signals (anomaly detection, power status, reset management, and analog input anti-interference design). Through the logical operations of hardware modules such as comparators, NAND gates, and hardware watchdogs, and after passing through an RC delay circuit, it ultimately controls the Amplifier's power, enable (STB), and mute (MUTE) pins, achieving safe and reliable fully hardware mute control. Through pure hardware logic, the amplifier's output is forcibly cut off or muted when the system powers on, powers off, experiences power abnormalities, or software abnormalities (such as software freezes), preventing pop-up sounds (the popping sound generated during power-on / off / switching) or other noises, ensuring driving quietness and safety. In another embodiment provided in this application, when the target control mode determined based on the current mute control triggering condition monitored by the mute control is a hardware-triggered software collaborative mode, the target control strategy under the target control mode is: When the current mute control trigger condition is that the SOC chip receives the first signal and / or the second signal and / or the third signal, the corresponding target control strategy is: the SOC chip configures the registers in the power amplifier to mute via the I2C bus, sends a low-level signal to the MUTE pin of the power amplifier, sends a low-level signal to the STB pin of the power amplifier, and performs power enable control via the enable signal pin of the power amplifier.

[0064] Here, when the SOC receives any hardware fault interrupt, it immediately executes the software strategy to implement multi-dimensional mute protection for the power amplifier through four control signals: software configuration of the power amplifier's internal registers via the I2C bus to achieve software-level mute; control of the power amplifier's enable pin via the GPIO_STB pin, pulling the signal low to force the power amplifier into sleep mode; direct control of the power amplifier's mute pin via the GPIO_MUTE pin, pulling the signal low to trigger hardware-level mute; and control of the power amplifier's power enable via the PWR_EN (power enable signal) pin, cutting off the power supply to the power amplifier in case of severe abnormality.

[0065] Specifically, the SOC chip uses the I2C bus to mute the registers in the power amplifier. This involves: configuring bit D5 or D6 of the external status register (0x06) to set the corresponding channel to mute mode; and configuring bit D1 or D2 of the external control register (0x0C) to set a specific channel to mute mode.

[0066] It should be noted that the hardware can be triggered within 50μs, and the software configuration can be completed within 2ms, with dual control throughout the process.

[0067] In another embodiment provided in this application, when the target control mode determined according to the current mute control triggering condition monitored by the trigger mute control is a hardware triggering software coordination mode, the target control strategy under the target control mode is as follows: when the current mute control triggering condition on which the trigger mute control is based is that a transient popping sound is detected, the corresponding target control strategy is: to send a low-level signal to the MUTE pin of the power amplifier through hardware, and the SOC chip sequentially performs audio codec configuration and power amplifier configuration.

[0068] Here, the identification of a situation that generates transient popping sounds may specifically include: when any of the following scenarios are identified, it is determined that a situation that generates transient popping sounds exists: system power-on / off, power supply step, and signal glitches.

[0069] The SOC chip sequentially configures the audio codec and power amplifier, specifically by optimizing the common-mode voltage and attenuation curve.

[0070] In another embodiment provided in this application, when the target control mode determined based on the current mute control triggering condition monitored by the mute control is a pure software mode, the target control strategy under the target control mode is: When the current mute control trigger condition is based on the detection of a source switching request signal, the corresponding target control strategy is: to configure the registers in the power amplifier via the I2C bus, to lower the MUTE pin level in the power amplifier, and to raise the STB pin voltage of the power amplifier after the source switching is completed.

[0071] In this way, the software command is issued in 1ms, and the switching process is completely silent with no audible abruptness.

[0072] In another embodiment provided in this application, when the current mute control trigger condition is based on the detection of an audio source playback signal, the corresponding target control strategy is: to raise the STB pin voltage of the power amplifier, and after a preset delay, to raise the MUTE pin voltage of the power amplifier, and to start audio output through the audio codec.

[0073] Here, the sequence of STB wake-up followed by MUTE de-mute is strictly followed to completely suppress pop sounds. The SOC first pulls GPIO_STB high to release the amplifier from sleep mode, putting it into a ready state. A preset delay (e.g., 1-2ms) is inserted, and after the amplifier is fully stable, GPIO_MUTE is pulled high to de-mute the hardware. Simultaneously, the amplifier registers are configured via I2C to restore the audio output gain, and finally, the CODEC starts audio playback. The core logic is to first make the amplifier hardware ready, then de-mute it, avoiding signal surges when the amplifier is not stable.

[0074] In another embodiment provided in this application, when the current mute control trigger condition is that a sound source pause signal is detected, the corresponding target control strategy is: to configure the registers in the power amplifier and reduce the MUTE pin level in the power amplifier via the I2C bus.

[0075] Here, the sequence of MUTE (mute) followed by STB (sleep) is strictly followed to block the impact noise at its source. The SOC first pulls GPIO_MUTE low to immediately trigger hardware mute and cut off the audio output; after inserting a preset delay (e.g., 1-2ms) and waiting for the mute to take full effect, GPIO_STB is pulled low to put the amplifier into sleep mode; simultaneously, the amplifier register is configured via I2C to set the mute state, completing the audio source switching pause operation. The logic of this strategy is: cut off the audio output first, then put the amplifier into sleep mode to avoid signal crosstalk during the power-down process.

[0076] In another embodiment provided in this application, when the target control mode determined according to the current mute control trigger condition monitored by the mute control is a pure software mode, the target control strategy in the target control mode is as follows: when the current mute control trigger condition is that the vehicle audio system wake-up signal is detected, the corresponding target control strategy is: power supply to the SOC chip, and power supply to the audio codec after a first delay, and power supply to the power amplifier after a second delay; after the power amplifier is ready, the power amplifier STB pin voltage is pulled low, and the power amplifier MUTE pin voltage is pulled high after a third delay, and the audio codec starts audio output.

[0077] When the current mute control trigger condition is based on the detection of the vehicle audio system sleep signal, the corresponding target control strategy is: pull down the MUTE pin voltage of the power amplifier, pull down the STB pin voltage of the power amplifier after the fourth delay, turn off the power amplifier power supply after the fifth delay, turn off the audio codec power supply after the sixth delay, and turn off the SOC chip power supply after turning off the audio codec power supply.

[0078] Here, the timing control of the mute control strategy executed in pure software mode during the sleep and wake-up of the in-vehicle audio system can be referenced. Figure 5 , Figure 5 This is a schematic diagram of the fast power-on / off timing logic in pure software mode.

[0079] like Figure 5 As shown, when the vehicle audio system is woken up, the corresponding control strategy can be as follows: the SOC power supply is powered on and stabilized first, and the main control is ready; after a 3ms delay, the CODEC power supply is enabled and the output is configured to be high impedance; after another 5ms delay (cumulative 8ms), the power amplifier power supply is enabled; after the power amplifier is ready, STB is first pulled low (active low, to unlock sleep mode), and after a 1ms delay, MUTE is pulled high (to unlock mute mode), and the CODEC starts audio output.

[0080] When the in-vehicle audio system is in sleep mode, the corresponding control strategy can be as follows: first, pull MUTE low (active low, triggers mute) to block audio output; after a 1ms delay, pull STB low (active low, enters sleep mode); after a 3ms delay, turn off the power amplifier; after another 5ms delay (cumulative 8ms), turn off the CODEC power supply, and finally turn off the SOC power supply.

[0081] Therefore, this timing sequence uses SOC→CODEC→power amplifier for tiered power-on and reverse tiered power-off, combined with STB sleep mode and MUTE mute dual control logic and precise delay, to completely eliminate the pop-up noise during power-on / off and sleep / wake-up of the vehicle audio system, ensuring a stable and reliable audio link.

[0082] In another embodiment provided in this application, when the current mute control triggering condition is based on the identification of an emergency audio switching request signal, the corresponding target control strategy is: to mute the normal audio channel in the power amplifier via the I2C bus, then pull down the MUTE pin voltage of the power amplifier, and finally switch to the emergency audio channel.

[0083] Here, the emergency switchover response time is less than 200μs, achieving seamless switching without affecting emergency audio broadcasting.

[0084] Regarding step S103, after determining the target control mode corresponding to the mute control and the target control strategy under that mode, the mute control operation is performed according to the core control actions and execution timing requirements specified in the target control strategy. See the example above for details.

[0085] Regarding step S104, the mode switching conditions corresponding to different target control modes are not necessarily the same, or even different; the mode switching conditions corresponding to the same target control mode under different triggering conditions are also not necessarily the same.

[0086] In one embodiment provided in this application, the mode switching condition corresponding to the pure hardware mode is as follows: lock the pure hardware mode until the system restarts / the power is turned on again; after restarting, perform a hardware self-test first, and if there is no abnormality, switch to the pure software mode.

[0087] The mode switching conditions corresponding to the hardware-triggered software collaborative mode determined by the SOC chip receiving the first and / or second and / or third signals are as follows: after the abnormality is cleared and lasts for 50ms, the software first pulls STB high (power amplifier ready), delays for 1ms and then pulls MUTE high (unmute), switches back to pure software mode, and writes the parameters into the policy library to optimize the default configuration.

[0088] Based on the identification of transient popping sounds, the mode switching conditions corresponding to the hardware-triggered software collaborative mode are as follows: after the MUTE holding time ends, the mute is immediately released; switch back to pure software mode, record the POP sound trigger conditions, and optimize the subsequent power-on and power-off timing delay parameters.

[0089] The mode switching conditions corresponding to the pure software mode determined by the detected audio source switching request signal are as follows: After the switching is completed, press STB to wake up first, then press MUTE to deactivate, delay for 1ms, and switch back to the pure software normal mode.

[0090] The mode switching conditions corresponding to the pure software mode, determined by the detection of the audio source playback signal / detection of the audio source pause signal, are as follows: maintain pure software mode throughout, record operation frequency, and optimize default delay parameters.

[0091] The mode switching conditions corresponding to the pure software mode determined by recognizing the vehicle audio system wake-up signal / recognizing the vehicle audio system sleep signal are as follows: after power-on / wake-up, maintain pure software mode; after power-off / sleep, lock the software to mute until the next wake-up.

[0092] The mode switching condition corresponding to the pure software mode determined by the detected emergency audio cut-in request signal is as follows: after the emergency audio ends, restore the original audio by pressing STB→MUTE sequence and maintain pure software mode.

[0093] Based on the same inventive concept, this application also provides an apparatus corresponding to the method. Since the principle of the apparatus in this application to solve the problem is similar to that of the method described above, the implementation of the apparatus can refer to the implementation of the method, and the repeated parts will not be described again.

[0094] Please see Figure 6 , Figure 6 This is a schematic diagram of the device for controlling the mute of in-vehicle audio output based on hardware and software collaboration, as provided in an embodiment of this application. Figure 6 As shown, the control device 600 includes: The first monitoring module 610 is used to monitor the operation status of the vehicle audio system according to the mute control trigger conditions corresponding to each of the multiple control modes, including pure hardware mode, hardware-triggered software collaborative mode, and pure software mode, and to determine whether to trigger mute control. The determination module 620 is used to determine, if it is determined that mute control is triggered, a corresponding target control mode and a target control strategy under the current mute control trigger condition monitored by the triggering mute control. The execution module 630 is used to perform a mute control operation in the target control mode according to the core control actions and execution timing requirements specified in the target control strategy. The second monitoring module 640 is used to monitor the operating status of the vehicle audio system after the mute control operation has been performed, and to perform a mode transfer when the mode switching conditions corresponding to the target control mode are met.

[0095] Optionally, when the first monitoring module 610 monitors the operating status of the vehicle audio system according to the mute control trigger condition corresponding to the pure hardware mode to determine whether to trigger mute control, the first monitoring module 610 is used to: The current power-on voltage and current power-off voltage of the vehicle power system are input into a comparator with power-on voltage thresholds and power-off voltage thresholds, and the comparator inputs two first-level signals into the AND circuit according to the comparison result. The hardware watchdog inputs a second-level signal determined by the software operation status in the vehicle system and its own power supply circuit, and a third-level signal determined by the current state of the power amplifier's error indicator pin, into the NAND circuit. If the output level signal of either the AND circuit or the NAND circuit is high, then the mute control is triggered. If the output level signals in both the AND and NAND circuits are low, then the mute control will not be triggered.

[0096] Optionally, when the first monitoring module 610 monitors the operating status of the vehicle audio system and determines whether to trigger mute control based on the mute control trigger condition corresponding to the hardware-triggered software collaborative mode, the first monitoring module 610 is used to: Identify whether a transient popping sound is generated or whether the SOC chip receives any of the following signals: a first signal determined by a low level output from the power amplifier's error indication pin, a second signal determined by a low level output from the comparator based on the current voltage value of the first power supply powering the power amplifier, and a third signal determined by a low level output from the voltage monitoring chip based on the current voltage value of the third power supply powering the SOC chip and the current voltage value of the second power supply powering the audio codec; If any signal is received or a transient popping sound is detected, the mute control is triggered; otherwise, the mute control is not triggered.

[0097] Optionally, when the first monitoring module 610 monitors the operating status of the vehicle audio system according to the mute control trigger condition corresponding to the pure software mode to determine whether to trigger mute control, the first monitoring module 610 is used to: Identify whether the SOC chip receives any of the following signals: audio source switching request signal, audio source playback signal, audio source pause signal, vehicle audio system wake-up signal, vehicle audio system sleep signal, and emergency audio cut-in request signal; If any signal is received, the mute control will be triggered; if no signal is received, the mute control will not be triggered.

[0098] Optionally, when the target control mode determined based on the current mute control triggering condition monitored by the mute control is a pure hardware mode, the target control strategy in the target control mode is: A high-level signal is simultaneously input to the first transistor, the first delay circuit, and the second delay circuit; wherein the delay duration of the first delay circuit is shorter than the delay duration of the second delay circuit. A low-level signal is input from the first transistor to the MUTE pin of the power amplifier; The first delay circuit inputs the delayed high-level signal to the second transistor, and the second transistor inputs a low-level signal to the first power supply control terminal of the power amplifier. The second delay circuit inputs the delayed high-level signal to the third transistor, and the third transistor inputs a low-level signal to the STB pin of the power amplifier.

[0099] Optionally, when the target control mode determined based on the current mute control triggering conditions monitored by the mute control is a hardware-triggered software-coordinated mode, the target control strategy under the target control mode is: When the current mute control trigger condition is that the SOC chip receives the first signal and / or the second signal and / or the third signal, the corresponding target control strategy is: The SOC chip performs mute configuration on the registers in the power amplifier via the I2C bus, sends a low-level signal to the MUTE pin of the power amplifier, sends a low-level signal to the STB pin of the power amplifier, and controls the power enable signal through the enable signal pin of the power amplifier.

[0100] Optionally, when the target control mode determined based on the current mute control triggering conditions monitored by the mute control is a hardware-triggered software-coordinated mode, the target control strategy under the target control mode is: When the current mute control trigger condition is based on the detection of a transient popping sound, the corresponding target control strategy is: The system sends a low-level signal to the MUTE pin of the power amplifier via hardware, and the SOC chip sequentially configures the audio codec and the power amplifier.

[0101] Optionally, when the target control mode determined based on the current mute control triggering condition monitored by the mute control is a pure software mode, the target control strategy under the target control mode is: When the current mute control trigger condition is based on the detection of a sound source switching request signal, the corresponding target control strategy is: Configure the registers in the power amplifier via the I2C bus, lower the MUTE pin level in the power amplifier, and raise the STB pin voltage of the power amplifier after the source switching is completed.

[0102] Optionally, when the target control mode determined based on the current mute control triggering condition monitored by the mute control is a pure software mode, the target control strategy under the target control mode is: When the current mute control trigger condition is based on the detection of an audio source playback signal, the corresponding target control strategy is: The STB pin voltage of the power amplifier is pulled high, and the MUTE pin voltage in the power amplifier is pulled high after a preset delay, and the audio output is started through the audio codec; When the current mute control trigger condition is based on the detection of a sound source pause signal, the corresponding target control strategy is: Configure the registers in the power amplifier and lower the MUTE pin level in the power amplifier via the I2C bus.

[0103] Optionally, when the target control mode determined based on the current mute control triggering condition monitored by the mute control is a pure software mode, the target control strategy under the target control mode is: When the current mute control trigger condition is based on the detection of a wake-up signal from the vehicle audio system, the corresponding target control strategy is: Power is supplied to the SOC chip, and after a first delay, power is supplied to the audio codec, and after a second delay, power is supplied to the power amplifier; After the power amplifier is ready, the voltage of the STB pin of the power amplifier is pulled low, and the voltage of the MUTE pin of the power amplifier is pulled high after the third delay, and the audio codec starts audio output; When the current mute control trigger condition is based on the detection of a sleep signal from the vehicle audio system, the corresponding target control strategy is: Pull the MUTE pin voltage of the power amplifier low, pull the STB pin voltage of the power amplifier low after the fourth delay, and turn off the power amplifier power supply after the fifth delay. After the sixth delay, the audio codec power is turned off, and after the audio codec power is turned off, the SOC chip power supply is turned off. When the current mute control trigger condition is based on the detection of an emergency audio cut-in request signal, the corresponding target control strategy is: The normal audio channel in the power amplifier is muted via the I2C bus, then the voltage of the MUTE pin of the power amplifier is pulled low, and finally the emergency audio channel is switched.

[0104] Please see Figure 7 , Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 7 As shown, the electronic device 700 includes a processor 710, a memory 720, and a bus 730.

[0105] The memory 720 stores machine-readable instructions executable by the processor 710. When the electronic device 700 is running, the processor 710 communicates with the memory 720 via the bus 730. When the machine-readable instructions are executed by the processor 710, they can perform the operations described above. Figure 1 The steps in the method embodiment shown are specifically implemented in the method embodiment and will not be repeated here.

[0106] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, can perform the above-described actions. Figure 1 The steps in the method embodiment shown are specifically implemented in the method embodiment and will not be repeated here.

[0107] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0108] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. The apparatus embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. Furthermore, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Additionally, the shown or discussed mutual couplings, direct couplings, or communication connections may be through some communication interfaces; indirect couplings or communication connections between devices or units may be electrical, mechanical, or other forms.

[0109] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0110] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0111] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a processor-executable, non-volatile, computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0112] Finally, it should be noted that the above-described embodiments are merely specific implementations of this application, used to illustrate the technical solutions of this application, and not to limit them. The scope of protection of this application is not limited thereto. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can still modify or easily conceive of changes to the technical solutions described in the foregoing embodiments, or make equivalent substitutions for some of the technical features, within the scope of the technology disclosed in this application. Such modifications, changes, or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be covered within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for controlling the mute of in-vehicle audio output based on hardware and software collaboration, characterized in that, The method includes: Based on the mute control trigger conditions corresponding to each of the multiple control modes, including pure hardware mode, hardware-triggered software collaborative mode, and pure software mode, the operating status of the vehicle audio system is monitored to determine whether to trigger mute control. If it is determined that mute control is triggered, the corresponding target control mode and the target control strategy under the target control mode are determined based on the current mute control trigger condition detected by the mute control trigger. In the target control mode, a mute control operation is performed in accordance with the core control actions and execution timing requirements specified in the target control strategy. The operating status of the vehicle audio system after the mute control operation is monitored, and a mode transition is performed when the mode switching conditions corresponding to the target control mode are met.

2. The method according to claim 1, characterized in that, When monitoring the operation of the in-vehicle audio system based on the mute control trigger conditions corresponding to the pure hardware mode, it is determined whether to trigger mute control, including: The current power-on voltage and current power-off voltage of the vehicle power system are input into a comparator with power-on voltage thresholds and power-off voltage thresholds, and the comparator inputs two first-level signals into the AND circuit according to the comparison result. The hardware watchdog inputs a second-level signal determined by the software operation status in the vehicle system and its own power supply circuit, and a third-level signal determined by the current state of the power amplifier's error indicator pin, into the NAND circuit. If the output level signal of either the AND circuit or the NAND circuit is high, then the mute control is triggered. If the output level signals in both the AND and NAND circuits are low, then the mute control will not be triggered.

3. The method according to claim 1, characterized in that, When the mute control trigger conditions corresponding to the hardware-triggered software collaborative mode are used, the operating status of the vehicle audio system is monitored to determine whether to trigger mute control, including: Identify whether a transient popping sound is generated or whether the SOC chip receives any of the following signals: a first signal determined by a low level output from the power amplifier's error indication pin, a second signal determined by a low level output from the comparator based on the current voltage value of the first power supply powering the power amplifier, and a third signal determined by a low level output from the voltage monitoring chip based on the current voltage value of the third power supply powering the SOC chip and the current voltage value of the second power supply powering the audio codec; If any signal is received or a transient popping sound is detected, the mute control is triggered; otherwise, the mute control is not triggered.

4. The method according to claim 1, characterized in that, When monitoring the operation of the in-vehicle audio system based on the mute control trigger conditions corresponding to the pure software mode, it is determined whether to trigger mute control, including: Identify whether the SOC chip receives any of the following signals: audio source switching request signal, audio source playback signal, audio source pause signal, vehicle audio system wake-up signal, vehicle audio system sleep signal, and emergency audio cut-in request signal; If any signal is received, the mute control will be triggered; if no signal is received, the mute control will not be triggered.

5. The method according to claim 2, characterized in that, When the target control mode determined based on the current mute control trigger condition monitored by the trigger mute control is a pure hardware mode, the target control strategy under the target control mode is as follows: A high-level signal is simultaneously input to the first transistor, the first delay circuit, and the second delay circuit; wherein the delay duration of the first delay circuit is shorter than the delay duration of the second delay circuit. A low-level signal is input from the first transistor to the MUTE pin of the power amplifier; The first delay circuit inputs the delayed high-level signal to the second transistor, and the second transistor inputs a low-level signal to the first power supply control terminal of the power amplifier. The second delay circuit inputs the delayed high-level signal to the third transistor, and the third transistor inputs a low-level signal to the STB pin of the power amplifier.

6. The method according to claim 3, characterized in that, When the target control mode determined based on the current mute control triggering conditions monitored by the trigger mute control is a hardware-triggered software collaborative mode, the target control strategy under the target control mode is as follows: When the current mute control trigger condition is that the SOC chip receives the first signal and / or the second signal and / or the third signal, the corresponding target control strategy is: The SOC chip performs mute configuration on the registers in the power amplifier via the I2C bus, sends a low-level signal to the MUTE pin of the power amplifier, sends a low-level signal to the STB pin of the power amplifier, and controls the power enable signal through the enable signal pin of the power amplifier.

7. The method according to claim 3, characterized in that, When the target control mode determined based on the current mute control triggering conditions monitored by the trigger mute control is a hardware-triggered software collaborative mode, the target control strategy under the target control mode is as follows: When the current mute control trigger condition is based on the detection of a transient popping sound, the corresponding target control strategy is: The system sends a low-level signal to the MUTE pin of the power amplifier via hardware, and the SOC chip sequentially configures the audio codec and the power amplifier.

8. The method according to claim 4, characterized in that, When the target control mode determined based on the current mute control trigger condition monitored by the mute control is pure software mode, the target control strategy under the target control mode is: When the current mute control trigger condition is based on the detection of a sound source switching request signal, the corresponding target control strategy is: Configure the registers in the power amplifier via the I2C bus, lower the MUTE pin level in the power amplifier, and raise the STB pin voltage of the power amplifier after the source switching is completed.

9. The method according to claim 4, characterized in that, When the target control mode determined based on the current mute control trigger condition monitored by the mute control is pure software mode, the target control strategy under the target control mode is: When the current mute control trigger condition is based on the detection of an audio source playback signal, the corresponding target control strategy is: The STB pin voltage of the power amplifier is pulled high, and the MUTE pin voltage in the power amplifier is pulled high after a preset delay, and the audio output is started through the audio codec; When the current mute control trigger condition is based on the detection of a sound source pause signal, the corresponding target control strategy is: Configure the registers in the power amplifier and lower the MUTE pin level in the power amplifier via the I2C bus.

10. The method according to claim 4, characterized in that, When the target control mode determined based on the current mute control trigger condition monitored by the mute control is pure software mode, the target control strategy under the target control mode is: When the current mute control trigger condition is based on the detection of a wake-up signal from the vehicle audio system, the corresponding target control strategy is: Power is supplied to the SOC chip, and after a first delay, power is supplied to the audio codec, and after a second delay, power is supplied to the power amplifier; After the power amplifier is ready, the voltage of the STB pin of the power amplifier is pulled low, and the voltage of the MUTE pin of the power amplifier is pulled high after the third delay, and the audio codec starts audio output; When the current mute control trigger condition is based on the detection of a sleep signal from the vehicle audio system, the corresponding target control strategy is: Pull the MUTE pin voltage of the power amplifier low, pull the STB pin voltage of the power amplifier low after the fourth delay, and turn off the power amplifier power supply after the fifth delay. After the sixth delay, the audio codec power is turned off, and after the audio codec power is turned off, the SOC chip power supply is turned off. When the current mute control trigger condition is based on the detection of an emergency audio cut-in request signal, the corresponding target control strategy is: The normal audio channel in the power amplifier is muted via the I2C bus, then the voltage of the MUTE pin of the power amplifier is pulled low, and finally the emergency audio channel is switched.

Images