Domain controller and configuration method thereof, vehicle, program product and storage medium

By integrating functional modules of multiple implementation methods in the domain controller and dynamically configuring configuration information, the high design and manufacturing cost problems caused by the differences in demand for different vehicle models are solved, and a standardized and customized domain controller design is realized. Reduced production costs and resource utilization.

CN118372754BActive Publication Date: 2024-12-06上海适宇智能科技有限公司
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202410596488.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-05-14
Publication Date
2024-12-06
Estimated Expiration
2044-05-14

AI Technical Summary

Technical Problem

Due to the differences in software and hardware configurations of different vehicle models, domain controller suppliers need to customize each vehicle model, which increases design and manufacturing costs.

Method used

Design a domain controller, integrating communication module, control module and multiple functional modules, each functional module contains multiple implementation methods. Through the implementation of configuration information dynamic configuration module, domain controller suppliers can design according to standardized methods. And manufacturing, users can customize the configuration according to their needs.

Benefits of technology

It reduces the production cost of domain controllers, improves configuration efficiency, reduces resource usage, and supports the standardization and customization of the hardware and software modules of domain controllers.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118372754B_ABST
    Figure CN118372754B_ABST
Patent Text Reader

Abstract

The present application relates to the field of automobile technology, and provides a domain controller and its configuration method, vehicle, program product and storage medium. Among them, the domain controller is applied to the vehicle, including a communication module, a control module and multiple functional modules, the functional module is a hardware module or a software module, each functional module is used to implement a function of the domain controller, and the functional module integrates multiple implementation methods of its function; the communication module is used to receive configuration information; the control module is used to put the implementation method indicated by the configuration information in the functional module into an effective state. The above-mentioned domain controller can realize standardized production, and there is no need to design and manufacture the domain controller separately for each model, which significantly reduces the production cost.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of automobile technology, and in particular to a domain controller and a configuration method thereof, a vehicle, a program product and a storage medium. Background Art

[0002] The emergence of the Domain Control Unit (DCU) stems from a series of problems such as the lengthening of the bus caused by the increase in the number of Electronic Control Units (ECUs) in the development of automobiles. The scattered ECUs are divided according to functional domains, integrated and upgraded into domain controllers with stronger computing power. Different vehicle manufacturers have their own design concepts for the specific division of functional domains. For example, some manufacturers divide them according to the power domain, chassis domain, cockpit domain, autonomous driving domain, and body domain.

[0003] The domain controllers required for different vehicle models have significant differences in software and hardware configurations. Therefore, domain controller suppliers need to customize domain controllers for each model based on the needs of vehicle manufacturers, resulting in high design and manufacturing costs for domain controllers. Summary of the invention

[0004] The purpose of the embodiments of the present application is to provide a domain controller and its configuration method, vehicle, program product and storage medium to improve the above-mentioned technical problems.

[0005] To achieve the above objectives, this application provides the following technical solutions:

[0006] In a first aspect, an embodiment of the present application provides a domain controller for use in a vehicle, wherein the domain controller comprises: a communication module, a control module, and multiple functional modules; wherein the functional modules are hardware modules or software modules, each functional module is used to implement a function of the domain controller, and the functional modules integrate multiple implementation methods of the functions; the communication module is used to receive configuration information; and the control module is used to configure the implementation method indicated by the configuration information in the functional module to an effective state.

[0007] Different users (for example, vehicle manufacturers) have different requirements for the implementation of the same function in the domain controller. The above domain controller integrates these different implementation requirements into the same functional module, so that the domain controller supplier can design and manufacture the domain controller in a standardized way, and at the same time open the dynamic configuration capability of the domain controller to users, so that after obtaining the domain controller, the user can customize its function implementation according to their own needs through software configuration. In this way, the domain controller supplier no longer needs to design and manufacture the domain controller for each model separately, which significantly reduces the production cost.

[0008] In an implementation of the first aspect, the functional module is a hardware module, which includes a switching element and multiple circuit structures corresponding to multiple implementation methods of its function, and the multiple circuit structures are coupled to each other through the switching element; the control module is used to control the conduction state of the switching element according to the configuration information so that the circuit structure indicated by the configuration information in the functional module is in an effective state.

[0009] In the above implementation, the conduction state of the switch element is changed by dynamic configuration, thereby taking into account different circuit structures inside the hardware module, which well supports the standardization and customization of the domain controller hardware module.

[0010] In an implementation of the first aspect, if the functional module is an analog to digital conversion (ADC) sampling circuit, the circuit structure includes a resistance signal sampling circuit, a current signal sampling circuit, and a voltage signal sampling circuit; if the functional module is a controller area network (CAN) communication circuit, the circuit structure includes a CAN communication circuit with terminal resistors and a CAN communication circuit without terminal resistors; if the functional module is a low-side drive circuit, the circuit structure includes a low-side drive circuit whose output pin has a pull-up function and a low-side drive circuit whose output pin does not have a pull-up function.

[0011] In the above implementation, several cases of hardware module standardization are listed. For example, in a standardized domain controller, both a CAN communication circuit with a terminal resistor and a CAN communication circuit without a terminal resistor are provided. Users can configure the conduction state of the switch element according to their own needs, so that the CAN communication circuit in the domain controller works either with a terminal resistor or without a terminal resistor.

[0012] In an implementation of the first aspect, the domain controller further includes a substrate, on which pads are provided for supporting selection and pasting of different circuit elements.

[0013] In the above implementation, by reserving pads on the substrate to support the selection of circuit components, on the one hand, standardization of substrate design and manufacturing is achieved, and on the other hand, it can easily support users to customize circuit components in the domain controller.

[0014] In an implementation of the first aspect, the domain controller further includes a substrate, the functional module is a hardware module, and a standardized detachable connection structure is provided on the substrate, and the connection structure is used to connect the substrate and the functional module.

[0015] The above implementation method is a modular design idea, which decouples the baseboard and the hardware functional module through a standardized detachable connection structure, so that different hardware modules can be selected according to user needs, and it is also convenient to replace or remove the hardware module for maintenance when a failure occurs.

[0016] In an implementation of the first aspect, the functional module is a software module, and the functional module includes software codes corresponding to multiple implementation methods of its functions; the control module is used to configure the parameters in the functional module according to the configuration information so that the code logic corresponding to the parameters in the software code is in an effective state.

[0017] In the above implementation, the parameters in the software code are changed by dynamic configuration, so as to take effect different code logics inside the software module, which well supports the standardization and customization of the domain controller software module.

[0018] In an implementation of the first aspect, if the functional module is sampling software, the parameters include at least one of the sampling rate, sampling accuracy and sampling period of the ADC; if the functional module is Ethernet driver software, the parameters include at least one of the clock frequency, Media Access Control (MAC) address and Internet Protocol (IP) address of the Ethernet; if the functional module is CAN communication software, the parameters include the transceiver rate and / or arbitration domain interval of CAN communication; if the functional module is Local Interconnect Network (LIN) communication software, the parameters include the transceiver rate of LIN communication; if the functional module is power management software, the parameters include the sleep state and / or sleep condition of the power supply; if the functional module is input / output (IO) control software, the parameters include the working mode of the IO port; if the functional module is pulse width modulation (Pulse Width Modulation) software, the parameters include the working mode of the IO port; If the functional module is a half-bridge driver software, the parameters include the operating mode and / or operating parameters of the half-bridge driver; if the functional module is a low-side driver software, the parameters include the operating mode of the low-side driver.

[0019] In the above implementation, several cases of software module standardization are listed. For example, in a standardized domain controller, the half-bridge driver software provides both the code for motor driving and the code for PWM control. Users can configure the working mode parameters of the half-bridge driver software according to their own needs, so that the code logic in the half-bridge driver software can work as either the motor driving code or the PWM control code.

[0020] In an implementation manner of the first aspect, if the functional module is protocol stack software, the parameter includes a function switch of the protocol stack software.

[0021] In the above implementation, the domain controller can store complete protocol stack software codes, and users can configure the function switches of these protocol stack software according to their own needs, thereby turning on or off specific functions in the software, so that the protocol stack software can work according to the required function combination.

[0022] In an implementation of the first aspect, the configuration information includes data to be configured and a storage address of the data to be configured, the data to be configured includes indication information of an implementation method adopted by the functional module, and the control module is further used to write the data to be configured into the Read Only Memory (ROM) of the domain controller according to the storage address of the data to be configured in the configuration information and make the data to be configured effective.

[0023] In the above implementation, the storage address of the data to be configured in the ROM has been planned in the configuration information, so that after receiving the configuration information, the domain controller can directly write the data to be configured to the appropriate location in the ROM based on the address therein, thereby completing the configuration update without recompiling the entire project file. This significantly simplifies the configuration process of the domain controller, improves configuration efficiency, and provides better support for dynamic configuration.

[0024] In a second aspect, an embodiment of the present application provides a domain controller for use in a vehicle, wherein the domain controller is obtained by cutting out the domain controller provided by the first aspect or any one implementation of the first aspect, and cutting out refers to retaining only one implementation of the functions of the functional modules of the domain controller provided by the first aspect or any one implementation of the first aspect, and shielding other implementations.

[0025] The domain controller in the first aspect (and its possible implementation methods) is mainly used in the development stage. In the mass production stage of the domain controller, the specific implementation method of each functional module has been determined, and the remaining implementation methods are not needed by users, so they can be blocked, which reduces the production cost of the domain controller and reduces resource usage.

[0026] In a third aspect, an embodiment of the present application provides a vehicle, comprising a domain controller provided by the first aspect, the second aspect, or any one of the implementations of these two aspects.

[0027] In a fourth aspect, an embodiment of the present application provides a method for configuring a domain controller, wherein the domain controller is applied in a vehicle, and the domain controller includes a communication module, a control module, and multiple functional modules, wherein the functional modules are hardware modules or software modules, and each functional module is used to implement a function of the domain controller, and the functional module integrates multiple implementation methods of its function; the method includes: receiving configuration information through the communication module; and configuring the implementation method indicated by the configuration information in the functional module to be in effect through the control module.

[0028] In a fifth aspect, an embodiment of the present application provides a computer program product, including computer program instructions, which, when read and executed by a domain controller, execute the method provided in the fourth aspect or any one of the implementations of the fourth aspect.

[0029] In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium, on which computer program instructions are stored. When the computer program instructions are read and run by a domain controller, the method provided by the fourth aspect or any one of the implementations of the fourth aspect is executed. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments of the present application will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0031] Figure 1 A possible structure of a domain controller provided in an embodiment of the present application is shown;

[0032] Figure 2 Another possible structure of the domain controller provided in the embodiment of the present application is shown;

[0033] Figure 3 A domain controller standardization solution provided by an embodiment of the present application is shown;

[0034] Figure 4 A possible structure of an unstandardized ADC sampling circuit is shown;

[0035] Figure 5 A possible structure of a standardized ADC sampling circuit is shown;

[0036] Figure 6 A possible structure of a standardized CAN communication circuit is shown;

[0037] Figure 7 A possible structure of a standardized low-side driver circuit is shown;

[0038] Figure 8 Another possible structure of a standardized ADC sampling circuit is shown;

[0039] Fig. 9 It is shown that the embodiment of the present application provides a modular solution. DETAILED DESCRIPTION

[0040] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. It should be noted that similar reference numerals and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in the subsequent drawings.

[0041] The terms "comprises," "comprising," or any other variation thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes the element.

[0042] Figure 1 A possible structure of a domain controller provided in an embodiment of the present application is shown. The domain controller is a domain controller used in a vehicle. The domain controller can be installed in the vehicle or in a simulation test environment. The specific type of the domain controller is not limited. For example, it can be a domain controller of a body domain, a domain controller of a chassis domain, and so on.

[0043] Reference Figure 1 The domain controller 10 at least includes a communication module 100, a control module 110 and a plurality of functional modules 120. Of course, the domain controller 10 may also include other components, such as a substrate, a housing or a storage module.

[0044] Among them, the functional module 120 is a hardware module or a software module. If the functional module 120 is a hardware module, it corresponds to a hardware circuit, and if the functional module 120 is a software module, it corresponds to a software code. Each functional module 120 is used to implement a function of the domain controller 10, and the functional module 120 integrates multiple implementation methods 122 of the functions to be implemented. The functions here can be signal acquisition, communication, input and output, control, drive, management, etc. If the functional module 120 is a hardware module, the multiple implementation methods 122 here can be understood as multiple circuit structures. If the functional module 120 is a software module, the multiple implementation methods 122 here can be understood as multiple code logics.

[0045] Which implementations 122 are included in a functional module 120 depends on user needs. Figure 1 In the domain controller 10, a total of n functional modules 120 (n>1) are shown. Taking the functional module k as an example, the functional module k is used to implement the function k of the domain controller 10. The supplier of the domain controller 10 can collect the user's implementation requirements for the function k in advance. Assuming that a total of mk user requirements are collected, each requirement corresponds to an implementation method 122 of the function k, so that when manufacturing the domain controller 10, these mk implementation methods 122 can be integrated into the functional module k. If the functional module k is a hardware module, mk circuit structures are integrated into the functional module k. If the functional module k is a software module, mk code logics are integrated into the functional module k. In this way, the functional module k is compatible with all users' implementation requirements for the function k.

[0046] Therefore, when manufacturing the functional module k, it is only necessary to manufacture it in a fixed manner and integrate mk implementation methods 122, without having to worry about which specific implementation method 122 the user wants to adopt, that is, its manufacturing process is standardized. If the functional module k is a hardware module, the above "manufacturing" can be understood as circuit manufacturing, and if the functional module k is a software module, the above "manufacturing" can be understood as code generation. If the functional module k is extended to all functional modules 120, the manufacturing process of the domain controller 10 is also standardized, and the resulting domain controller 10 can be called a standardized domain controller.

[0047] Note that a function module 120 similar to function module k that is compatible with multiple function implementations 122 is called a standardized function module. If a function module 120 only includes one function implementation 122, and this implementation 122 is only for a specific user requirement, then this function module 120 is called a non-standardized function module (especially, if a function module 120 only includes one function implementation 122, and this implementation 122 meets the needs of all users, then this function module 120 can also be considered a standardized function module). The domain controller 10 provided in the embodiment of the present application may only include standardized function modules, or may include both standardized function modules and non-standardized function modules. However, in order to facilitate the explanation of the main innovation of the present application, the non-standardized function modules can be temporarily ignored, that is, whenever the function module 120 is mentioned, unless otherwise specified, it is understood as a standardized function module.

[0048] In addition, in the present application scheme, only the hardware of the domain controller 10 can be standardized, in which case the standardized functional modules 120 are all hardware modules, or only the software of the domain controller 10 can be standardized, in which case the standardized functional modules 120 are all software modules, or both the hardware of the domain controller 10 and the software of the domain controller 10 can be standardized at the same time, in which case the standardized functional modules 120 include both hardware modules and software modules.

[0049] The communication module 100 is used for the domain controller 10 to communicate with external software or equipment, for example Figure 1 The configuration tool 20 may be a software and / or hardware tool for collecting user configuration information and transmitting the configuration information to the domain controller 10.

[0050] For example, the configuration tool 20 may include configuration software and a host computer, wherein the host computer is installed on the domain controller 10 and is detachable, and the host computer can exchange data with the domain controller 10 through a specific interface, such as an Ethernet interface, a CAN interface, a serial interface, etc. There are different deployment methods for the configuration software, such as:

[0051] Method 1:

[0052] The configuration software is deployed on a remote server (relative to the domain controller 10), and the server and the host computer exchange data through a network, for example, the network can be the Internet. The configuration software can provide an interface (such as a web page) or an interface for users to create, import or edit configuration information, and send the configuration information to the host computer. The host computer is located between the configuration software and the domain controller 10, and it mainly plays the role of communication transfer, responsible for forwarding the received configuration information to the domain controller 10. Of course, it is not ruled out that the host computer will process the configuration information in the process of forwarding the configuration information. It should be understood that although the host computer is a hardware device, it also runs software on it, which is responsible for cooperating with the hardware to complete the transfer of configuration information.

[0053] Method 1 is mainly for the situation where the server and the host computer can communicate with each other through the network. The configuration software can realize the remote configuration of the domain controller through the host computer, so that users do not have to go to the site to configure the domain controller, which significantly reduces the operation and maintenance burden.

[0054] Method 2

[0055] The configuration software is directly deployed on the host computer, and the host computer is installed on the domain controller 10 and is detachable. The host computer can exchange data with the domain controller 10 through a specific interface. The rest of the process is similar to the above example and will not be repeated. The configuration software can provide an interface (such as a web page) or an interface for users to create, import or edit configuration information, and send the configuration information to the domain controller 10.

[0056] Method 2 is mainly for situations where the server and the host computer cannot communicate through the network (or there is no Internet environment). The configuration software deployed on the host computer can realize the local configuration of the domain controller. Of course, at this time, the user needs to arrive at the site and access the configuration software through the local area network or direct connection with the host computer to complete the input of configuration information.

[0057] Method 3

[0058] Method 3 can be regarded as a combination of Method 1 and Method 2, that is, the configuration software deploys an instance on the server and the host computer respectively, and the functions of these two instances are basically the same. When the server and the host computer are interconnected, the configuration software instance deployed on the server is mainly used for remote configuration. When the server cannot be interconnected with the host computer network, the configuration software instance deployed on the host computer is used for local configuration. That is, the configuration of the domain controller 10 can be realized in different scenarios.

[0059] The communication module 100 may be used to receive configuration information sent from the outside to the domain controller 10 and pass it to the control module 110 for further processing, or store the configuration information first and then read and process it by the control module 110 later.

[0060] The configuration information includes the implementation mode 122 selected by the user for each functional module 120. For example, for functional module k, the user selects the implementation mode sk. Optionally, the configuration information may specify the implementation mode 122 only for some functional modules 120 of the domain controller 10, and the remaining functional modules 120 that do not specify the implementation mode 122 may default to one implementation mode 122.

[0061] The communication module 100 can be understood as a combination of hardware and software used for external communication of the domain controller 10: for example, the communication module 100 can be a combination of an Ethernet card and its driver; for another example, the communication module 100 can be a combination of a CAN communication circuit and its driver, etc. The communication module 100 itself can also be a functional module 120.

[0062] The control module 110 can be used to control the behavior of each component (communication module 100, functional module 120, etc.) of the domain controller 10, and can also be used for information processing and analysis, etc. After obtaining the configuration information, the control module 110 can parse the content of the configuration information, and configure the implementation method 122 indicated by the configuration information in the functional module 120 to be in effect, and the remaining implementation methods 122 to be ineffective. For example, the control module 110 parses the configuration information and determines that the implementation method for the functional module k is sk, then the functional module k is configured to be effective in the implementation method sk, and the remaining implementation methods are ineffective. After the configuration is completed, the functional module k will run according to the implementation method sk. If the functional module k is a hardware module, it will work according to the circuit structure corresponding to sk. If the functional module k is a software module, it will execute according to the code logic corresponding to sk.

[0063] The configuration process can be actively initiated by the user using the configuration tool 20. After the configuration is completed, each functional module 120 of the domain controller 10 operates in accordance with the user's expected implementation method 122, that is, the user's customized needs are realized on the basis of the standardized domain controller 10, so that the domain controller 10 can be adapted to a specific vehicle model.

[0064] The configuration process can be initiated at different times, for example, when the domain controller 10 is not running, or during the operation of the domain controller 10. In an optional solution, the user is allowed to repeatedly use the configuration tool 20 to modify the configuration. Depending on the implementation 122, the domain controller 10 may or may not need to be restarted after each configuration. Since the configuration information of the domain controller 10 is not fixed in it, but can be modified by the user, this configuration process is dynamic.

[0065] The control module 110 may be implemented as an integrated circuit chip with a computing control function, such as a microcontroller unit (MCU), etc. The number of such chips may be one or more.

[0066] To summarize briefly, different users have different requirements for the implementation of the same function in the domain controller 10. The above-mentioned domain controller 10 integrates these different implementation requirements into the same functional module 120, so that the domain controller supplier can design and manufacture the domain controller 10 in a standardized manner, and at the same time open the dynamic configuration capability of the domain controller 10 to the user, so that after obtaining the domain controller 10, the user can customize its function implementation according to his own needs through software configuration.

[0067] In this way, domain controller suppliers no longer need to design and manufacture domain controllers for each model separately, and can provide standardized domain controllers 10 for different users in a unified manner, thereby significantly reducing the production cost of domain controllers. Especially for some niche models, the number of domain controllers required is very small, and the cost of designing and manufacturing them separately is very high. For users, there is no need to customize the domain controller software and hardware. They only need to configure the existing software and hardware of the domain controller to quickly obtain a domain controller that meets their needs, thereby speeding up the progress of domain controller development and verification.

[0068] The above mainly involves the domain controller development stage. After the development work based on the domain controller is completed, the domain controller will be mass-produced. In the mass production stage of the domain controller, the specific implementation method 122 of each functional module 120 has been determined, and the remaining implementation methods 122 are not required by the user. Therefore, these redundant implementation methods 122 can be trimmed during mass production, that is, for each functional module 120 of the standardized domain controller 10, only one implementation method 122 of its function is retained, and other implementation methods 122 are shielded, and the trimmed domain controller is then used for mass production. This is conducive to reducing the production cost of the domain controller and reducing resource usage.

[0069] Among them, "shielding" is not equivalent to removing other implementation methods 122, but making other implementation methods 122 in an ineffective state (and can no longer be configured by users to be effective). Because removing other implementation methods 122 may change the design of the functional module 120, it will require the domain controller to be redesigned and verified during the mass production stage, which is not what the domain controller supplier expects.

[0070] Figure 2Another possible structure of the domain controller provided by the embodiment of the present application is shown, that is, the structure of the domain controller 10 after trimming. Taking the function module k as an example, in the mass production stage, the user has selected to manufacture the function module k according to the implementation method sk, so the other implementation methods in the function module k are unnecessary and can be shielded. Figure 2 It is no longer shown in the figure. For different functional modules k, the shielding method may be different, as shown in the examples below.

[0071] It should be understood that before mass production of the domain controller 10, in addition to tailoring the functional module 120, other optimization measures for mass production may also be taken, such as optimizing the power consumption of hardware modules, optimizing the execution efficiency and resource usage of software modules, etc.

[0072] Next, based on the above embodiments, more solutions for standardizing domain controller hardware and domain controller software are respectively given. Note that these solutions are not limited to the above solution for achieving standardization in combination with dynamic configuration.

[0073] Standardization measures for domain controller hardware

[0074] (1) Adding switching elements

[0075] In the case where the functional module is a hardware module, the functional module may include a switch element and a plurality of circuit structures corresponding to the various implementations of its function (each implementation corresponds to a circuit structure). The number of the switch elements may be one or more, and the switch element may be a photocoupler, a relay, a triode, a metal-oxide-semiconductor field-effect transistor (Metal-Oxide-Semiconductor Field-Effect Transistor, referred to as MOSFET, also generally referred to as MOS tube), a multiplex switch chip, etc. The switch element is connected to the control module circuit (directly or indirectly), so that the control module can control the conduction state of the switch element.

[0076] The above-mentioned multiple circuit structures are coupled to each other through switch elements, and the control module can control the conduction state of the switch elements according to the configuration information, so that the circuit structure indicated by the configuration information in the functional module is in an effective state, and the remaining circuit structures are in an ineffective state. The effectiveness of the circuit structure can be understood as an electrical signal passing through the circuit, so that the function of the circuit structure can be realized. Figure 3 A domain controller standardization solution provided by an embodiment of the present application is shown. Figure 3 The hardware standardization in the system is achieved through measure (1), which includes the standardization of ADC sampling circuit, CAN communication circuit and low-side driver circuit (these circuits are all hardware functional modules). They are introduced below:

[0077] (1.1) ADC sampling circuit

[0078] The ADC sampling circuit is used to collect signals from sensors. These sensors can be divided into three categories according to the type of output signals: resistance signal sensors (for example, temperature sensors), voltage signal sensors (for example, pressure sensors, damper motors), and current signal sensors (for example, light sensors). In the prior art, different circuit structures need to be designed for these three types of sensors for collection. For details, please refer to Figure 4 . Figure 4 The upper left corner shows the circuit structure for collecting resistance signals. RSensor1 represents the resistance signal sensor, and ADC_Collect1 represents the collected signal. Figure 4 The upper right corner shows the circuit structure for collecting current signals. ISensor3 represents the current signal sensor, and ADC_Collect3 represents the collected signal. Figure 4 The following is the circuit structure for collecting voltage signals. VSensor2 represents the voltage signal sensor, and ADC_Collect2 represents the collected signal.

[0079] When the ADC sampling circuit is not standardized, the supplier will communicate with users before manufacturing the domain controller. For example, if there are three users who need the ADC sampling circuit to collect resistance signals, current signals, and voltage signals respectively, the domain controller supplier needs to design and manufacture three domain controllers. The ADC sampling circuit in each domain controller uses Figure 4 A circuit structure in the embodiment is implemented, and its production cost is relatively high.

[0080] Figure 5 A possible structure of a standardized ADC sampling circuit is shown. Figure 5 , Figure 4 The three circuit structures in the figure are coupled together through the switch element SW1. If SW1 connects terminals 1 and 2, the ADC sampling circuit is a resistance signal sampling circuit for collecting resistance signals (with Figure 4 The circuit structure in the upper left corner is equivalent), the input end of the circuit can be connected to RSensor; if SW1 is connected to terminals 2 and 3, then the ADC sampling circuit is a current signal sampling circuit, which is used to collect current signals (with Figure 4 The circuit structure in the upper right corner is equivalent), the input end of the circuit can be connected to ISensor; if SW1 is disconnected (terminals 1 and 2 are not connected, and terminals 2 and 3 are not connected), then the ADC sampling circuit is a voltage signal sampling circuit, which is used to collect voltage signals (with Figure 4The circuit structure on the lower left is equivalent), and the input end of the circuit can be connected to VSensor. The above three connection states of SW1 are controlled by the control module based on the configuration information.

[0081] For example, there are three users who need ADC sampling circuits to collect resistance signals, current signals, and voltage signals respectively. The domain controller supplier can provide them with the same domain controller, in which the ADC sampling circuit is as follows: Figure 5 As shown, the ADC sampling circuit can be connected to any type of sensor, and each user can configure the ADC sampling circuit to a desired state through a configuration tool.

[0082] For another example, originally SW1 connects terminals 1 and 2 (collecting resistance signals), and later the user may indicate through configuration information that a voltage signal should be collected. Then the control module may control SW1 to be in a disconnected state according to the configuration information, that is, the signal object collected by the ADC sampling circuit may be flexibly changed.

[0083] In the mass production stage of the domain controller, since the user needs have been determined, it is necessary to cut when manufacturing the ADC sampling circuit in the domain controller. For example, if the user has determined that the resistance signal should be collected, the switch element SW1 can be replaced with a 0Ω resistance line, which is fixedly connected to terminals 1 and 2, so that in the mass-produced domain controller, only the resistance signal sampling circuit is effective, and the current signal sampling circuit and the voltage signal sampling circuit are shielded. Of course, the shielded circuit is not removed from the domain controller, because removing these circuits may require redesigning and verifying the domain controller, which is costly, but it cannot be ruled out that in some implementations, the circuit structure that is no longer used will be removed during mass production. In addition, replacing SW1 with a resistance line also reduces its manufacturing cost, making it more suitable for mass production. For another example, if the user has determined that the current signal should be collected, the switch element SW1 can be replaced with a 0Ω resistance line, which is fixedly connected to terminals 2 and 3. For another example, if the user has determined that the voltage signal should be collected, SW1 can be directly not welded.

[0084] (1.2) CAN communication circuit

[0085] The CAN communication circuit can be used to implement CAN communication. Figure 6 A possible structure of a standardized CAN communication circuit is shown. Figure 6 ,The CAN communication circuit includes two circuit structures, a CAN communication circuit with terminal resistors and a CAN communication circuit without terminal resistors, and the two circuit structures are coupled together through the switch element SW1. Among them, the terminal resistor R1 can reduce signal reflection and improve signal quality. CAN_H represents the high data line in CAN communication, and CAN_L represents the low data line in CAN communication.

[0086] If SW1 connects terminals 1 and 2, the CAN communication circuit has R1; if SW1 is disconnected, the CAN communication circuit does not have R1. The above two connection states of SW1 are controlled by the control module based on the configuration information.

[0087] In the mass production stage of the domain controller, for example, if the user has determined that the CAN communication circuit needs to have a terminal resistor, the switch element SW1 can be replaced with a 0Ω resistor wire, which is fixedly connected to terminals 1 and 2. For another example, if the user has determined that the CAN communication circuit does not need to have a terminal resistor, SW1 can be directly not welded, and R1 can also be not welded.

[0088] (1.3) Low-side drive circuit

[0089] The low-side driver circuit can be used to implement switching control of the load. Figure 7 A possible structure of a standardized low-side driver circuit is shown. Figure 7 The low-side driving circuit includes two circuit structures, a low-side driving circuit with a pull-up function for the output pin and a low-side driving circuit without a pull-up function for the output pin, and the two circuit structures are coupled together through a switch element SW. Among them, OutPutControl represents the output control signal of the low-side driving circuit, and Output represents the output signal of the low-side driving circuit, corresponding to the output pin.

[0090] If SW connects terminals 1 and 2, the output pin of the low-side driver circuit has a pull-up function (connected to the power supply voltage VCC_BAT); if SW connects terminals 2 and 3, the output pin of the low-side driver circuit does not have a pull-up function (not connected to the power supply voltage VCC_BAT). The above two connection states of SW are controlled by the control module based on the configuration information.

[0091] In the mass production stage of the domain controller, for example, if the user has determined that the output pin of the low-side driver circuit needs to have a pull-up function, the switch element SW can be replaced with a 0Ω resistor line, which is fixedly connected to terminals 1 and 2. For another example, if the user has determined that the output pin of the low-side driver circuit does not need to have a pull-up function, SW can be directly not welded, or the switch element SW can be replaced with a 0Ω resistor line, which is fixedly connected to terminals 2 and 3.

[0092] The solutions of the above examples (1.1) to (1.3) can be understood by reference to each other, and it should be noted that the hardware standardization of the domain controller is not limited to the above examples (1.1) to (1.3).

[0093] The coupling mode of the circuit structures corresponding to different functional implementation modes in Examples (1.1) to (1.3) can be summarized as follows: the unique part of each circuit structure is coupled to the common part of each circuit structure through a switching element.

[0094] For example, for example (1.1), refer to Figure 4 For the circuit structure of collecting resistance signals, VCC and R1 are its unique parts, and the circuit at the output end of RSensor1 (i.e. the horizontal line below) is the common part; for the circuit structure of collecting current signals, the ground terminal and R3 are its unique parts, and the circuit at the output end of ISensor3 (i.e. the horizontal line below) is the common part; for the circuit structure of collecting voltage signals, its unique part is empty, and the circuit at the output end of VSensor2 (i.e. the horizontal line below) is the common part. Continue to refer to Figure 5 , the circuit at the output of R / I / VSensor (i.e. the horizontal line below) is Figure 4 The common part of the three circuit structures, Figure 4 The private parts of the three circuits are coupled to the common part through the switch element SW1. This coupling mode allows the common part circuit to be reused in different circuit structures, which is beneficial to reduce the manufacturing cost of the circuit and reduce the circuit volume. For examples (1.2) and (1.3), similar analysis can be carried out and will not be repeated.

[0095] Of course, there are other coupling modes for each circuit structure. Figure 8 Another possible structure of a standardized ADC sampling circuit is shown. Figure 8 , Figure 4 The three circuit structures are independent of each other, and are only coupled to each other through switch element SW1 at the input end and through switch element SW2 at the output end. For example, if SW1 connects terminals 1 and 2, and SW2 connects terminals 5 and 8, then the ADC sampling circuit is equivalent to Figure 4 The resistance signal sampling circuit in.

[0096] In measure (1), the conduction state of the switch element is changed by dynamic configuration, thereby taking into account different circuit structures inside the hardware module, which well supports the standardization and customization of the domain controller hardware module.

[0097] (2) Use short-circuit cap

[0098] A short-circuit cap is also called a jumper cap. It is usually in the shape of a small plastic cap with metal pins or lines inside. It can be inserted or flipped to connect or disconnect nodes in the circuit. The short-circuit cap can be used to replace the switch element in measure (1) and play a similar role. Of course, the connection state of the short-circuit cap needs to be manually configured (including manual configuration or configuration using mechanical equipment) rather than software configuration.

[0099] For example, after obtaining a standardized domain controller, the user can manually install a short-circuit cap to realize dynamic configuration of the circuit structure and achieve a customized domain controller.

[0100] (3) Reserved solder pads

[0101] Optionally, the domain controller further includes a substrate, which may be a printed circuit board (PCB). Various circuit elements in the domain controller may be mounted on the substrate and interconnected through the circuit on the substrate. The circuit elements here may include resistors, capacitors, inductors, jumpers, triodes, MOS tubes, amplifiers, chips, switch elements, etc., and the hardware module in the domain controller may include one or more circuit elements.

[0102] A pad is a metallized area on a substrate, which is mainly used to connect the pins of circuit components. The so-called "reserved pad" refers to a pad designed and manufactured in advance on the substrate that is sufficient to support the selection and pasting of different circuit components. For example, a type A resistor includes 2 pins, and a type B resistor includes 3 pins. In order to support the selection and pasting of different types of resistors according to user needs, 3 pads can be reserved on the substrate. If the user selects a type A resistor, only 2 of the 3 pads are used to weld the resistor when manufacturing the domain controller. If the user selects a type B resistor, all 3 pads are used to weld the resistor when manufacturing the domain controller. In this way, different user needs are met through a fixed number of pads (3), that is, standardization is achieved. For another example, the chip has different packaging methods and different numbers of pins. In order to support users to select different types of chips according to their needs, the pads corresponding to the chip on the substrate need to be compatible with the number of pins and pin positions of different chips.

[0103] In summary, measure (3) reserves pads on the substrate to support the selection of circuit components. On the one hand, it realizes the standardization of substrate design and manufacturing, and on the other hand, it can easily support users to customize the circuit components in the domain controller.

[0104] (4) Modular design

[0105] Optionally, the domain controller further includes a substrate, which may be a PCB board. A detachable connection structure is provided on the substrate, and the functional module (here, the hardware module) is not directly soldered on the substrate, but is connected to the substrate through these connection structures, and can be easily disassembled when needed. The connection structure here includes a gold finger, a stamp hole, or a board-to-board connector, etc.

[0106] There are many situations where functional modules need to be disassembled: for example, if a functional module fails, it can be removed for maintenance or replacement. For example, power modules usually have a relatively high probability of failure. For another example, if a functional module is upgraded, it can be removed and replaced with an upgraded functional module. For another example, modules of the same function but different models can be installed according to project requirements to test specific functions. For example, modules of different powers can be installed according to project requirements, and so on.

[0107] Measure (4) includes several key points in its implementation:

[0108] First, the functions of the domain controller should be modularized, that is, the relevant circuits of a certain function should be integrated into a hardware module, so that it can be easily connected to or disassembled from the substrate as a whole. Fig. 9 It shows that the embodiment of the present application provides a modular solution, referring to Fig. 9 ,The hardware functional modules of the domain controller can be divided into two categories: the power part, which is mainly used to realize the ,power conversion and power control of the domain controller, including the bridge driver module, the high and low side driver module, the ,power module, etc.; the logic part, which is mainly used to realize the data ,acquisition and logic control of the domain controller, including the ADC sampling module, the signal driver module, the ,data communication module, etc.

[0109] Secondly, the connection structure should be detachable on the one hand and standardized on the other hand, so that any functional module that meets the standards can be connected to the substrate, which facilitates the development and manufacture of the functional modules.

[0110] In summary, measure (4) decouples the baseboard and the hardware functional module through a standardized detachable connection structure, so that the design and manufacture of the baseboard can be standardized. Users can select different hardware modules according to their needs to customize the domain controller. It is also convenient to replace or remove the hardware module of the domain controller for maintenance when a failure occurs, which is conducive to improving maintenance efficiency and reducing maintenance costs.

[0111] It should be understood that in a domain controller, the above four hardware standardization measures may be implemented simultaneously, or only part of them may be implemented.

[0112] Standardization measures for domain controller software

[0113] The standardization of domain controller software is mainly aimed at the driver software of the domain controller (that is, the software that directly interacts with the hardware of the domain controller). The upper-level software usually has quite different user requirements, which makes it difficult to standardize. Of course, it does not rule out the possibility of standardizing some common components (for example, middleware).

[0114] In the case where the functional module is a software module, the functional module may include software codes (referring to executable codes) corresponding to multiple implementation methods of its functions, and the software code contains one or more configurable parameters. The control module may configure the values ​​of these parameters according to the configuration information, so that the code logic corresponding to the configured parameter values ​​in the software code is in effect, and the code logic corresponding to other parameter values ​​is in an ineffective state. The effectiveness of the code logic can be understood as the code corresponding to this logic will be executed when the functional module is running.

[0115] In the mass production stage of the domain controller, since the user needs have been determined, the software function modules in the domain controller can be code trimmed. Code trimming can be done by removing the code logic that will not be executed (that is, the "shielding" mentioned above can be understood as removal here) to reduce the code volume and improve execution efficiency. This removal can be based on the source code or the executable code. If it is based on the source code, it may be necessary to recompile the function module. Of course, if the domain controller hardware performance is sufficient, it is also possible not to perform code trimming.

[0116] Continue to refer to Figure 3 , Figure 3 It also gives several examples of software standardization (these software are software function modules), which are introduced below:

[0117] (1) ADC sampling software

[0118] The configurable parameters include but are not limited to at least one of the ADC sampling rate, sampling accuracy, and sampling period. For example, the sampling rate of an ADC sampling circuit can be 50Hz, 100Hz, or 200Hz. If the user specifies 50Hz through configuration information, the subsequent ADC sampling software will perform signal sampling according to the code logic corresponding to 50Hz, while the sampling code logic corresponding to 100Hz and 200Hz will not be executed although it is included in the ADC sampling software.

[0119] During the development phase of the domain controller, 50Hz, 100Hz, and 200Hz are all configurable by the user. During the mass production phase of the domain controller, assuming that the ADC sampling rate is determined to be 100Hz, 100Hz can be fixedly written into the code of the ADC sampling software (or the configuration file used by the code), and it can no longer be configured to 100Hz or 200Hz (at least ordinary users are not allowed to modify it at will).

[0120] (2) Ethernet driver software

[0121] The configurable parameters include but are not limited to at least one of Ethernet clock frequency, MAC address and IP address.

[0122] (3) CAN communication software

[0123] The configurable parameters include but are not limited to the CAN communication receiving and sending rate or arbitration domain interval.

[0124] (4)LIN communication software

[0125] The configurable parameters include but are not limited to the sending and receiving rates of LIN communication.

[0126] (5) Power management software

[0127] The configurable parameters include but are not limited to the power supply sleep state and / or sleep conditions. The sleep state is such as whether the power supply supports sleep, and the sleep condition is such as what conditions are met to enter sleep mode if sleep mode is supported.

[0128] (6)IO control software

[0129] The configurable parameters include but are not limited to the working mode of the IO port, which may include input mode or output mode. If it is output mode, it may further include subdivision modes such as pull-up output, pull-down output, open-drain output or push-pull output.

[0130] (7) PWM control software

[0131] The configurable parameters include but are not limited to the period and / or duty cycle of the PWM output.

[0132] (8) Half-bridge driver software

[0133] Its configurable parameters include the working mode and / or operating parameters of the half-bridge drive. The working mode may include a drive mode or a PWM control mode. The operating parameters may be operating parameters under a specific mode. For example, the operating parameters under the PWM control mode may be the period and / or duty cycle of the PWM output.

[0134] For example, the half-bridge driver chip can be used as a motor driver, or it can output PWM waves to control certain in-vehicle devices (such as fans), and the half-bridge driver software is the driver software corresponding to the half-bridge driver chip. In the prior art, if the user requires the half-bridge driver chip to work in a motor drive mode, the half-bridge driver software deployed to the domain controller only contains code logic related to the motor drive, and does not contain code logic related to PWM control. In the solution of the present application, (at least in the domain controller development stage) the half-bridge driver software simultaneously contains code logic related to the motor drive and code logic related to the PWM control, so that the user can use the configuration information to select the corresponding working mode, so that the half-bridge driver software controls the half-bridge driver chip to work in a specified mode, so that the needs of different users can be met.

[0135] Of course, during the mass production stage of the domain controller, if it has been determined that the half-bridge driver chip works in the motor drive mode, the code logic related to PWM control in the half-bridge driver software can be shielded, for example, this part of the code can be removed from the software to reduce the code size and improve execution efficiency.

[0136] (9) Low-side driver software

[0137] Its configurable parameters include the operating mode of the low-side driver, which may include turning the low-side driver on or off.

[0138] (10) Protocol stack software

[0139] Its configurable parameters include the function switch of the protocol stack software. The software protocol stack here may include middleware such as the diagnostic protocol stack and the communication protocol stack. The complete code of the diagnostic protocol stack is written into the domain controller in advance. The diagnostic protocol stack includes multiple functions. Each function or several related functions corresponds to a function switch (which can be implemented as a field). Therefore, the user can turn on or off each function in the diagnostic protocol stack by configuring the function switch, so that the code of the diagnostic protocol stack is organized in the form expected by the user, so as to provide the fault diagnosis service expected by the user.

[0140] For example, the diagnostic protocol stack of Unified Diagnostic Services (UDS) mainly includes the following three functions:

[0141] A: Diagnostic Event Manager (DEM): responsible for processing diagnostic events and storing diagnostic events and data related to diagnostic events. DEM also includes sub-function modules such as diagnostic data identification (DID) and diagnostic trouble code (DTC).

[0142] B: Diagnostic Communication Manager (DCM): Responsible for processing diagnostic requests from external diagnostic instruments. The data of the diagnostic request may be a DID value or a DTC status word. After receiving the diagnostic request, the DCM performs a specific inspection and performs a specific service action (may need to obtain DTC related Info from the DEM), and then sends a positive response or a specific NRC (Negative Response Code) negative response. The DCM also includes sub-functions such as the Diagnostic Session Layer (DSL), the Diagnostic Session Layer (DSD), and the Diagnostic Service Processing (DSP).

[0143] C: Fault Mitigation Manager (FIM): Disables specific functions of software components based on Event Status. FIM has no sub-functions.

[0144] The domain controller can enable or disable relevant functions (including sub-functions) in the diagnostic protocol stack based on the function switch in the configuration information, thereby achieving the effect of dynamically generating the diagnostic protocol stack and avoiding the tedious operation of generating the diagnostic protocol stack by recompiling.

[0145] Optionally, each of the above software may provide parameter configuration interfaces to the outside during implementation, so that the control module may call these interfaces to implement parameter configuration.

[0146] The solutions of the above examples (1) to (10) can be understood with reference to each other, and it should be noted that the software standardization of the domain controller is not limited to the above examples (1) to (10).

[0147] The above software standardization solution changes the parameters in the software code by means of dynamic configuration, thereby taking into account different code logics within the software module, and well supports the standardization and customization of the domain controller software module.

[0148] Based on the above embodiments, possible ways of writing configuration information into a domain controller are further described below:

[0149] The control module of the domain controller can be implemented by a chip, which may be called a main control chip, such as the MCU mentioned above. The main control chip is provided with a ROM inside to store the data and / or computer program instructions required for the operation of the domain controller. The main control chip can read these instructions and data and execute them to achieve the corresponding functions. The ROM here is erasable, for example, it can be a programmable read-only memory (Programmable Read-Only Memory, referred to as PROM), an erasable programmable read-only memory (Erasable Programmable Read-Only Memory, referred to as EPROM), an electrically erasable programmable read-only memory (Electric Erasable Programmable Read-Only Memory, referred to as EEPROM), a flash memory, etc. Optionally, the ROM can also be located outside the main control chip, but can be accessed by the main control chip, so the ROM can also be called the ROM of the domain controller.

[0150] In one implementation, the configuration information includes one or more data to be configured, the data to be configured includes information indicating the implementation method adopted by the functional module, the data to be configured is the data that needs to be written into the ROM of the domain controller, and the data to be configured has been described in the previous text. In addition, the configuration information also includes the storage address of each data to be configured, and the storage address here refers to the storage address in the ROM of the domain controller. The storage address of each data to be configured is pre-planned when the configuration information is generated, that is, the configuration tool will plan the storage layout of the data in the ROM.

[0151] After the control module obtains the configuration information, it will write the data to be configured into the ROM of the domain controller according to the storage address of the data to be configured in the configuration information and make the data to be configured effective. Making the data to be configured effective means making the data to be configured written into the ROM available. The effective data to be configured can be further read by the domain controller and used to configure the implementation mode of the functional modules in the domain controller.

[0152] For example, the domain controller can be restarted based on the storage area in the ROM where the data to be configured is written, so as to make the data to be configured effective. Restarting the domain controller can mean powering on the entire domain controller, but it can also mean restarting only some components of the domain controller, such as the main control chip. For another example, in the case where only a small number of parameters are changed during the configuration process, it is also possible to simply re-execute the initialization program in the domain controller to make these parameters effective. For example, if the baud rate parameters of the CAN communication software in the domain controller are modified, the modified baud rate can be made effective by restarting the initialization program of the CAN communication software.

[0153] In the above implementation, the storage address of the data to be configured in the ROM has been planned in the configuration information, so that after receiving the configuration information, the domain controller can directly write the data to be configured to the appropriate location in the ROM based on the address therein, thereby completing the configuration update without recompiling the entire project file. This significantly simplifies the configuration process of the domain controller, improves configuration efficiency, and provides better support for dynamic configuration.

[0154] Optionally, the ROM of the domain controller includes a first partition and a second partition (of course, other partitions may also be included, but the other partitions are not used to store the data to be configured), and only one of the two partitions is in operation at the same time, and the operation status of the partition is marked by a startup flag, which itself may also be stored in the ROM. A partition is currently in operation, which can be understood as the domain controller currently running based on the computer program instructions and data stored in the partition.

[0155] For example, there are two startup flags A and B in total. Startup flag A indicates the running status of the first partition. Startup flag A=0 indicates that the first partition is not in the running state. Startup flag A=1 indicates that the first partition is in the running state, that is, the computer program instructions and data corresponding to the operation logic currently executed by the domain controller are stored in the first partition; startup flag B indicates the running status of the first partition. Startup flag B=0 indicates that the second partition is not in the running state. Startup flag B=1 indicates that the second partition is in the running state, that is, the computer program instructions and data corresponding to the operation logic currently executed by the domain controller are stored in the second partition; at the same time, at most only one of the startup flag A and the startup flag B has a value of 1.

[0156] If the domain controller determines that the boot flag currently indicates that the first partition is running, for example, the boot flag A=1 (the boot flag B=0 at this time), then the data to be configured is written into the second partition according to the storage address of the data to be configured in the configuration file. After writing, the domain controller will set the boot flag to indicate that the second partition is running, for example, the boot flag B=1 (the boot flag A=0 at this time); if the domain controller determines that the boot flag currently indicates that the second partition is running, for example, the boot flag B=1 (the boot flag A=0 at this time), then the data to be configured is written into the first partition according to the storage address of the data to be configured in the configuration file. After writing, the domain controller will set the boot flag to indicate that the first partition is running, for example, the boot flag A=1 (the boot flag B=0 at this time). Optionally, in the case where the ROM includes the first partition and the second partition, the storage address of the data to be configured in the configuration information can be a relative address within each partition (relative to the starting address of the partition).

[0157] After modifying the boot flag, the domain controller can restart based on the partition indicated by the boot flag to take effect on the newly configured data to be configured. For example, if the boot flag is set to indicate the operation of the second partition, the restart is based on the second partition, that is, after the restart, the domain controller runs based on the computer program instructions and data stored in the second partition; if the boot flag is set to indicate the operation of the first partition, the restart is based on the first partition, that is, after the restart, the domain controller runs based on the computer program instructions and data stored in the first partition. In this way, by setting the boot flag, the smooth switching of the ROM running partition is completed, and the data to be configured written into the ROM is effective.

[0158] Furthermore, if the domain controller fails to restart the partition indicated by the boot flag, it can try to restart based on the partition again, but if the number of consecutive failures exceeds a threshold (the threshold can be an integer greater than or equal to 1), the boot flag can be set to indicate the running of another partition of the two partitions (referring to the first partition and the second partition), and restart based on the other partition. For example, if the domain controller modifies the boot flag to indicate the running of the second partition, it will restart based on the second partition, and if the restart fails for 4 consecutive times (the threshold is 3 times), the boot flag will be set to indicate the running of the first partition, and restart based on the first partition. Since the domain controller is running based on the first partition before restarting the MCU based on the second partition, restarting the MCU based on the first partition is likely to succeed.

[0159] In the above optional scheme, since the ROM of the domain controller includes two partitions, and the data to be configured is always written to the partition that is not currently running, the behavior of writing the data to be configured into the ROM will not affect the normal operation of the current partition, and the domain controller can be restarted at an appropriate time to switch the running partition, so that the configuration update process can be carried out safely and smoothly. Furthermore, if the domain controller fails to restart continuously based on the partition after the configuration update, it can be changed to run based on the partition before the configuration update, thereby avoiding the situation where the domain controller is unavailable due to configuration update errors, and improving the security of the configuration process. If each configuration update is regarded as a functional upgrade of the domain controller, then this scheme can also be understood as returning to the version before the upgrade after the upgrade fails to continue running, so that the domain controller can at least work before troubleshooting, thereby improving the reliability and security of the configuration process. If the ROM of the domain controller includes more partitions, it can be analyzed with reference to the situation of two partitions, and no further elaboration is given.

[0160] The embodiment of the present application also provides a vehicle, including any domain controller provided by the embodiment of the present application. For example, if it is a test vehicle, the domain controller it contains may be the domain controller in the development stage mentioned above, and if it is a mass-produced vehicle, the domain controller it contains may be the domain controller in the mass-production stage mentioned above. Since the domain controller is standardized, it is also conducive to reducing the production cost of the vehicle and improving the development efficiency of new models.

[0161] The embodiment of the present application also provides a configuration method of a domain controller, wherein the domain controller is applied to a vehicle, and the domain controller includes at least a communication module, a control module, and multiple functional modules, wherein the functional module is a hardware module or a software module, and each functional module is used to implement a function of the domain controller, and the functional module integrates multiple implementation methods of its function. The configuration method can be implemented by a computer program deployed in the domain controller, and the steps include: receiving configuration information through the communication module; configuring the implementation method indicated by the configuration information in the functional module to an effective state through the control module.

[0162] The configuration method of the domain controller provided in the embodiment of the present application, its implementation principle and the technical effects produced have been introduced in the aforementioned embodiment of the domain controller. For the sake of brief description, for matters not mentioned in the method embodiment, reference may be made to the corresponding content in the domain controller embodiment.

[0163] The embodiment of the present application also provides a computer program product, which includes computer program instructions. When these computer program instructions are read and run by the domain controller, the configuration method of the domain controller provided by the embodiment of the present application is executed. For example, the computer program product can be stored in a storage module of the domain controller and read and run by a control module of the domain controller. Of course, the computer program product can also be stored in a storage medium independent of the domain controller, such as a hard disk, a CD, or a USB flash drive.

[0164] The embodiment of the present application also provides a computer-readable storage medium, on which computer program instructions are stored. When these computer program instructions are read and run by the domain controller, the configuration method of the domain controller provided by the embodiment of the present application is executed. For example, the computer-readable storage medium can be implemented as a read-only memory or a rewritable memory in the domain controller. Of course, the computer-readable storage medium can also be independent of the domain controller, such as a hard disk, an optical disk, a USB flash drive, and other media.

[0165] The above description is only an embodiment of the present application and is not intended to limit the scope of protection of the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, scheme combination, improvement, etc. made within the spirit and principle of the present application shall be included in the scope of protection of the present application.

Claims

1. A domain controller, characterized in that: Applied in a vehicle, the domain controller is used in the domain controller development stage and is customizable, and the domain controller includes: a communication module, a control module, and multiple functional modules; Wherein, the functional module is a hardware module or a software module, each functional module is used to implement a function of the domain controller, and the functional module integrates multiple implementation methods of its function; The communication module is used to receive configuration information; The control module is used to configure the implementation mode indicated by the configuration information in the functional module to be in a valid state; The configuration information includes the data to be configured and the storage address of the data to be configured, the data to be configured includes indication information of the implementation method adopted by the functional module, and the control module is also used to write the data to be configured into the ROM of the domain controller and make the data to be configured effective according to the storage address of the data to be configured in the configuration information.

2. The domain controller according to claim 1, characterized in that: The functional module is a hardware module, and the functional module includes a switch element and a plurality of circuit structures corresponding to various implementation modes of its function, and the plurality of circuit structures are coupled to each other through the switch element; The control module is used to control the conduction state of the switch element according to the configuration information, so that the circuit structure indicated by the configuration information in the functional module is in an effective state.

3. The domain controller according to claim 2, characterized in that: If the functional module is an ADC sampling circuit, the circuit structure includes a resistance signal sampling circuit, a current signal sampling circuit and a voltage signal sampling circuit; If the functional module is a CAN communication circuit, the circuit structure includes a CAN communication circuit with a terminal resistor and a CAN communication circuit without a terminal resistor; If the functional module is a low-side driving circuit, the circuit structure includes a low-side driving circuit whose output pin has a pull-up function and a low-side driving circuit whose output pin does not have a pull-up function.

4. The domain controller according to claim 1, characterized in that: The domain controller also includes a substrate, on which pads are provided for supporting the selection and pasting of different circuit elements.

5. The domain controller according to claim 1, characterized in that: The domain controller further includes a substrate, the functional module is a hardware module, and a standardized detachable connection structure is provided on the substrate, and the connection structure is used to connect the substrate and the functional module.

6. The domain controller according to claim 1, characterized in that: The functional module is a software module, and the functional module includes software codes corresponding to multiple implementation modes of its functions; The control module is used to configure the parameters in the functional module according to the configuration information, so that the code logic corresponding to the parameters in the software code is in an effective state.

7. The domain controller according to claim 6, characterized in that: If the functional module is ADC sampling software, the parameter includes at least one of the sampling rate, sampling accuracy and sampling period of the ADC; If the functional module is Ethernet driver software, the parameter includes at least one of a clock frequency, a MAC address, and an IP address of the Ethernet; If the functional module is CAN communication software, the parameters include the transceiver rate and / or arbitration domain interval of CAN communication; If the functional module is LIN communication software, the parameters include the sending and receiving rate of LIN communication; If the functional module is power management software, the parameters include the sleep state and / or sleep condition of the power supply; If the functional module is IO control software, the parameters include the working mode of the IO port; If the functional module is PWM control software, the parameters include the period and / or duty cycle of the PWM output; If the functional module is half-bridge driver software, the parameters include the operating mode and / or operating parameters of the half-bridge driver; If the functional module is low-side driver software, the parameter includes the working mode of the low-side driver.

8. The domain controller according to claim 7, characterized in that: If the functional module is a protocol stack software, the parameter includes a function switch of the protocol stack software.

9. A domain controller, characterized in that: Applied in a vehicle, the domain controller is obtained by cutting out the domain controller according to any one of claims 1 to 8, and cutting out means that the functional module of the domain controller according to any one of claims 1 to 8 retains only one implementation mode of its function and shields other implementation modes.

10. A vehicle, characterized in that: The method comprises a domain controller as claimed in any one of claims 1 to 9.

11. A method for configuring a domain controller, characterized in that: The domain controller is applied to a vehicle. The domain controller is used in the development stage of the domain controller and is customizable. The domain controller includes a communication module, a control module, and multiple functional modules. The functional modules are hardware modules or software modules. Each functional module is used to implement a function of the domain controller. The functional module integrates multiple implementation modes of its function. The method includes: receiving configuration information through the communication module; configuring the implementation mode indicated by the configuration information in the functional module to be in an effective state through the control module; The configuration information includes the data to be configured and the storage address of the data to be configured, the data to be configured includes indication information of the implementation method adopted by the functional module, and the control module writes the data to be configured into the ROM of the domain controller and makes the data to be configured effective according to the storage address of the data to be configured in the configuration information.

12. A computer program product, characterized in that The method comprises computer program instructions, and when the computer program instructions are read and executed by a domain controller, the method according to claim 11 is executed.

13. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer program instructions, and when the computer program instructions are read and executed by the domain controller, the method according to claim 11 is executed.

Citation Information

Patent Citations

  • Vehicle power domain control system based on multi-core controller

    CN116661423A

  • Multifunctional differentiated configuration method and system based on automobile domain controller software

    CN117395298A