Vehicle machine function configuration method and device, electronic equipment and storage medium

Abstract

The embodiment of the invention relates to the technical field of vehicles, and discloses a vehicle machine function configuration method and device, electronic equipment and a storage medium. The method comprises the following steps of: dividing oemcfg partitions in a specified format in a flash memory to store vehicle machine function configuration; setting a shared memory space corresponding to the AMSS side and the QNX side, and writing full data of the oemcfg partition into a shared memory for the QNX side to read and use; the QNX side is used for reading total data, the total data is written into a memory starting parameter cmdline, and the cmdline is at least transmitted to the Android side; and analyzing the cmdline by using the Android side according to the specified configuration table to obtain the function configuration of the vehicle-mounted terminal, and completing the configuration of the functions of the vehicle-mounted terminal according to the functions of the vehicle-mounted terminal. According to the invention, flexible flashing of vehicle machine function configuration can be realized, and the maintenance cost is reduced.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of vehicles, in particular to a car machine function configuration method and device, electronic equipment and storage medium. BACKGROUND

[0002] At present, vehicle enterprises often have multiple models of cars, and the same model of car often has high, medium and low configurations. These different models and different configurations of cars also have great differences in function configuration. Therefore, vehicle enterprises usually use configuration word systems for unified management.

[0003] However, the existing vehicle model configuration system scheme usually has the following disadvantages:

[0004] (1) Poor configuration flexibility, a large number of storage partitions are predefined for different vehicle models, resulting in serious storage fragmentation; independent firmware versions are maintained for each vehicle model, version management is complex, and the flashing efficiency is low;

[0005] (2) Insufficient cross-system compatibility, the existing scheme is usually adapted to a single operating system, and lacks a unified cross-platform synchronization mechanism.

[0006] (3) High development and maintenance cost, business modules need to directly operate the underlying address or firmware interface, the code is redundant and has high coupling degree; configuration changes need to recompile the firmware or adjust the storage layout, and the response speed is slow. SUMMARY

[0007] The purpose of the present application is to provide a car machine function configuration method, device, electronic equipment and storage medium, to at least solve the problems of poor configuration flexibility, insufficient compatibility and high maintenance cost of the existing vehicle model configuration system scheme, and to improve the configuration flexibility, improve the configuration compatibility and reduce the maintenance cost.

[0008] In order to solve the above technical problems, in a first aspect, the present application provides a car machine function configuration method, at least comprising:

[0009] Dividing an oemcfg partition of a specified format in the flash memory to store the car machine function configuration;

[0010] Setting up a shared memory space corresponding to the AMSS side and the QNX side, and writing the full data of the oemcfg partition into the shared memory for reading and using by the QNX side;

[0011] Reading the full data by the QNX side, and writing the full data into the memory start parameter cmdline, to at least pass the cmdline to the Android side;

[0012] The Android side parses the cmdline according to a specified configuration table to obtain the car machine function configuration, and configures the car machine function according to the car machine function.

[0013] Optionally, the oemcfg partition in the specified format at least includes a partition header, an index area, and a data area.

[0014] The partition header is used to verify whether the oemcfg partition is valid.

[0015] The index area at least includes a plurality of index items for indexing data areas of the data area.

[0016] The data area is divided into the data areas according to the index items, and is used to store the car machine function configuration.

[0017] Optionally, the AMSS side and the QNX side are set up to correspond to a shared memory space, and full data of the oemcfg partition is written into the shared memory for reading and use by the QNX side, and specifically includes:

[0018] The AMSS side and the QNX side are set up to correspond to the shared memory space.

[0019] An initialization function is called, and the initialization function is used to read the full data of the oemcfg partition in the flash memory through a specified interface;

[0020] The full data is written into the shared memory space for reading and use by the QNX side.

[0021] Optionally, the QNX side reads the full data and writes the full data into a memory startup parameter cmdline to at least pass the cmdline to the Android side, and specifically includes:

[0022] The QNX side maps the shared memory through a preset function to directly read the full data of the shared memory space.

[0023] The full data is preprocessed through a preset function, and the preprocessed full data is written into the cmdline to at least pass the cmdline to the Android side.

[0024] Optionally, the specified configuration table at least includes a flag bit, a data start bit, a data length, a parsing type, and a parsing bit number.

[0025] The flag bit is used to associate the index area.

[0026] Optionally, the Android side parses the cmdline according to a specified configuration table to obtain the configuration of the car machine function, and configures the car machine function according to the car machine function.

[0027] The Android side converts the cmdline into a standard startup parameter in a preset format through a preset function.

[0028] According to the flag bit, the function configuration data in the corresponding area of the standard startup parameter is read in sequence.

[0029] According to the data start bit and the data length, the data content of the function configuration data is read.

[0030] According to the parsing type and the parsing bit number, the data content is parsed to obtain the corresponding car machine function configuration, and the update of the car machine function is completed.

[0031] In a second aspect, the present application further provides a car machine function configuration device, which at least comprises:

[0032] The memory partition module is used for partitioning an oemcfg partition in a specified format in the flash memory to store the configuration of the car machine function.

[0033] The shared memory module is used for setting up a shared memory space corresponding to the AMSS side and the QNX side, and writing the full data of the oemcfg partition into the shared memory for reading and using by the QNX side.

[0034] The data transmission module is used for reading the full data by the QNX side, and writing the full data into the memory startup parameter cmdline, so as to at least transmit the cmdline to the Android side.

[0035] The parsing update module is used for parsing the cmdline by the Android side according to a specified configuration table to obtain the configuration of the car machine function, and configuring the car machine function according to the car machine function.

[0036] Optionally, it further comprises:

[0037] The oemcfg partition in the specified format at least comprises a partition header, an index area and a data area.

[0038] The partition header is used for verifying whether the oemcfg partition is valid.

[0039] The index area at least comprises a plurality of index items, which are used for indexing the data area of the data area.

[0040] The data area is divided according to the index item, and the data area is used to store the car machine function configuration.

[0041] In a third aspect, the present application provides an electronic device, comprising a memory and a processor, wherein the memory stores a computer program which can be run on the processor, and when the processor executes the program, the steps of the car machine function configuration method in any one of the first aspect are implemented.

[0042] In a fourth aspect, the present application provides a computer readable storage medium, which stores a computer program, and when the processor executes the computer program, the steps of the car machine function configuration method in any one of the first aspect are implemented.

[0043] The technical scheme provided by the embodiment of the present application first divides the oemcfg partition of the specified format in the flash memory to store the car machine function configuration, then sets up the shared memory space corresponding to the AMSS side and the QNX side, and writes the full data of the oemcfg partition into the shared memory for the QNX side to read and use, then reads the full data by the QNX side and writes the full data into the memory start parameter cmdline to at least pass the cmdline to the Android side, and finally parses the cmdline according to the specified configuration table by the Android side to obtain the car machine function configuration and complete the configuration of the car machine function according to the car machine function.

[0044] Therefore, the embodiment of the present application can directly update the car machine function configuration by only changing the storage data of the oemcfg partition when updating the car machine function configuration for different vehicle models, so as to realize the flexible flashing of the car machine function configuration and reduce the maintenance cost. On the other hand, the embodiment of the present application parses the cmdline according to the specified configuration table to obtain the car machine function configuration, which can read the car machine function configuration according to the function module, and the specified configuration table can support defining multiple access interfaces to improve the configuration compatibility and meet various development requirements. BRIEF DESCRIPTION OF DRAWINGS

[0045] Figure 1 is a flowchart of a car machine function configuration method provided by the embodiment of the present application;

[0046] Figure 2 is a flowchart of another car machine function configuration method provided by the embodiment of the present application;

[0047] Figure 3 is a structural schematic diagram of a car machine function configuration device provided by the embodiment of the present application;

[0048] Figure 4is a structural schematic diagram of an electronic device provided by an embodiment of the present application.

[0049] Figure 5 is a system architecture diagram of a car-machine function configuration device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0050] For the purposes of the present application, the technical solutions and advantages, the present application will be described in further detail below with reference to the drawings. Obviously, the described embodiments are only some of the embodiments of the present application, but not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the scope of the present application.

[0051] The terms used in the embodiments of the present application are only for the purpose of describing the specific embodiments, and are not intended to limit the present application. The singular forms "a", "an" and "the" used in the embodiments of the present application and the appended claims are also intended to include the plural forms, unless the context clearly indicates otherwise. "Multiple" generally includes at least two.

[0052] It should be understood that the term "and / or" used herein is only to describe the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B, which can represent the three cases of A alone, A and B together, and B alone. In addition, the character " / " in this paper generally represents that the front and rear associated objects are a "or" relationship.

[0053] It should be understood that although the terms first, second, third, etc. can be used in the embodiments of the present application, these descriptions should not be limited to these terms. These terms are only used to distinguish the description. For example, without departing from the scope of the embodiments of the present application, the first can also be called the second, and similarly, the second can also be called the first.

[0054] Depending on the context, the word "if" as used herein can be interpreted as "when" or "upon" or "in response to determining" or "in response to detecting". Similarly, depending on the context, the phrase "if it is determined" or "if (a stated condition or event) is detected" can be interpreted as "when it is determined" or "in response to determining" or "when (a stated condition or event) is detected" or "in response to detecting (a stated condition or event)".

[0055] It is also important to note that the terms "comprises" and / or "comprising", or "includes" and / or "including" when used in this specification, specify the presence of stated features, integers, steps, operations, elements, or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, or groups thereof.

[0056] In particular, it should be noted that symbols and / or numbers present in the description, if not marked in the description of the drawings, are not drawing references.

[0057] Figure 1 is a flowchart of a vehicle-machine function configuration method provided by an embodiment of the present application. The embodiment is applicable to at least the function configuration scenarios of various vehicles / vehicle models. The vehicle-machine function configuration method can be executed by a vehicle-machine function configuration device in the embodiment of the present application as an execution subject, and the execution subject can be implemented in the form of software and / or hardware. As shown in the figure, the vehicle-machine function configuration method at least includes the following steps: Figure 1

[0058] S1, dividing an oemcfg partition of a specified format in a flash memory to store vehicle-machine function configurations.

[0059] In the embodiment, the oemcfg partition can be a special partition for storing vehicle-machine function configurations. In a specific implementation, optionally, the specified format of the oemcfg partition at least includes a partition header, an index area, and a data area.

[0060] It is known that the partition header is used to verify whether the oemcfg partition is valid; the index area at least includes a plurality of index items, which are used to index the data areas of the data area; and the data area at least divides the data areas according to the index items, which are used to store vehicle-machine function configurations. Each data area can correspond to a vehicle-machine function configuration. The vehicle-machine function configuration can be a configuration related to vehicle functions such as seat heating, automatic parking, navigation, intelligent driving, central control, and instrument.

[0061] ​Understandably, the oemcfg partition size can be 1024 bytes. The partition header length can be 48 bytes, with the first 4 bytes being the magic number "OEM" used to optimize the calculation process and improve code execution efficiency. The index area length can be 208 bytes, containing 52 index entries (each index entry occupies 4 bytes). The first two bytes of each index entry are used to identify the starting address of the data area, and the last two bytes are used to identify the length of the data area (for example, 01a0 0040 indicates that the data area starts at 0x01A0 and has a length of 64 bytes). The data area length can be 768 bytes, and the data area can be divided into multiple data regions according to multiple index entries. The index entries can correspond to flag bits in the specified configuration table, meaning that the region corresponding to each flag bit can store a portion of the functional configuration (such as the central control / instrument configuration). Therefore, as shown in this embodiment, the oemcfg partition can support bit-level addressing storage (for example, a certain configuration occupies 12 bits starting from the 6th bit of the 3rd byte), which is beneficial for improving the flexibility of the vehicle's functional configuration.

[0062] S2. Establish shared memory spaces for AMSS and QNX sides, and write the full data of the oemcfg partition to the shared memory for QNX side to read and use.

[0063] AMSS can include a suite of software ranging from a real-time operating system to a user interface module, supporting multi-mode applications and switching methods. QNX is a real-time operating system. Shared memory space can be created by allocating a 1024-byte dedicated oemcfg partition on a storage device, declaring this partition as the shared memory address SMEM_OEMCFG_DATA, and initializing the pointer oemcfg_table_info. This pointer is used to transfer data from this dedicated partition between different boot stages, such as XBL (Extensible Bootloader) and SBL (Extensible Bootloader). It is known that before declaring the shared memory address, the partition's coldplug_guid can be configured to the preset identifier oem_config_image_partition_id to ensure that QNX can correctly identify the partition attributes.

[0064] S3. Use the QNX side to read the full data and write the full data to the memory startup parameter cmdline, so as to at least pass cmdline to the Android side.

[0065] In this case, cmdline can be passed to the Android side as a parameter in androidboot.op.

[0066] S4. Use the Android side to parse the cmdline according to the specified configuration table to obtain the vehicle infotainment system function configuration, and complete the configuration of the vehicle infotainment system function according to the vehicle infotainment system function.

[0067] On the Android side, when the init process starts, Android sets the parsed vehicle infotainment system configuration attributes as Android system attributes by calling InitPropertySet. Furthermore, applications can read Android system attributes to access the vehicle's configuration. In one specific implementation, optionally, the specified configuration table includes at least a flag bit, a data start bit, a data length, a parsing type, and a parsing bit length; the flag bit is used to associate the index area. It is understood that the specified configuration table also includes the target system attribute name, used to obtain information such as the attribute name and attribute value under the Android system.

[0068] The technical solution provided in this embodiment firstly divides the flash memory into oemcfg partitions of a specified format to store the vehicle infotainment system function configuration; secondly, it establishes shared memory spaces corresponding to the AMSS side and the QNX side, and writes the full data of the oemcfg partitions into the shared memory for the QNX side to read and use; then, it uses the QNX side to read the full data and writes the full data into the memory startup parameter cmdline, so as to at least pass the cmdline to the Android side; finally, it uses the Android side to parse the cmdline according to the specified configuration table to obtain the vehicle infotainment system function configuration, and completes the configuration of the vehicle infotainment system functions according to the vehicle infotainment system functions.

[0069] Therefore, this embodiment demonstrates two advantages. First, by dividing the vehicle infotainment system's function configuration into a specified format OEMCFG partition, it allows for flexible updating of the system configuration by simply modifying the stored data in the OEMCFG partition when updating the system configuration for different vehicle models. This enables flexible flashing of the system configuration and reduces maintenance costs. Second, this embodiment parses the CMDline based on a specified configuration table to obtain the vehicle infotainment system's function configuration. It can read the system configuration according to functional modules, and the specified configuration table supports defining multiple access interfaces to improve configuration compatibility and meet various development needs.

[0070] Based on the above embodiments or implementation methods Figure 2 This is a flowchart of another vehicle infotainment system function configuration method provided by an embodiment of the present invention. This embodiment is based on the above embodiment with additions. Figure 2 As shown, the vehicle infotainment system configuration method includes at least the following steps:

[0071] S1. Divide the flash memory into oemcfg partitions of a specified format to store the vehicle infotainment system configuration.

[0072] S21. Establish shared memory spaces for the AMSS side and the QNX side.

[0073] S22. Call the initialization function and use the initialization function to read the full data of the oemcfg partition from the flash memory through the specified interface.

[0074] The initialization function can be `boot_oemconfig_data_table_init`, which reads the full data of the `oemcfg` partition from the flash device through the `boot_update_oemconfig_data_table` interface (i.e., the specified interface) and caches the full data in the memory space pointed to by `oemcfg_table_info` (such as shared memory space) for direct reference during the SBL (Secondary Boot Load) stage. This configuration, as in this embodiment, enables data synchronization between multiple system kernels.

[0075] S23. Write all data to the shared memory space for QNX side to read and use.

[0076] S31. Use the QNX side to map shared memory through preset functions to directly read the full data of the shared memory space.

[0077] The preset function can be the `mem_mmap_get_addr` function, which directly reads data by mapping shared memory `SMEM_OEMCFG_DATA`. In another specific implementation, the `pread` function can also be used to directly access preset path system nodes, such as the ` / dev / disk / oemcfg` device node, to obtain raw data. To facilitate access to vehicle configuration by various service modules, this embodiment also provides read / write interfaces based on tags and offsets, including `read / write_oemcfg_by_tag` and `read / write_oemcfg_by_offset`, so that each service module can directly read the required data and meet the underlying development needs.

[0078] S32. Preprocess the full data using a preset function and write the preprocessed full data into cmdline, so as to at least pass cmdline to the Android side.

[0079] The default function can be a libz function. Preprocessing can involve compressing the 1024-byte oemcfg partition data, converting the compressed data format to the required string type, and finally writing it to the cmdline.

[0080] S41. Utilize the Android side to convert cmdline into standard startup parameters in a preset format using a preset function.

[0081] The default function here is the same as in step S32, which is the libz function. The default format can be to convert the decompressed cmdline string into hex format.

[0082] S42. Read the function configuration data of the corresponding area in the standard startup parameters in sequence according to the flag bits.

[0083] S43. Read the data content of the function configuration data according to the data start bit and data length.

[0084] S44. Parse the data content according to the parsing type and parsing bit width to obtain the corresponding vehicle infotainment function configuration and complete the vehicle infotainment function update.

[0085] Steps S42-S44 involve parsing the cmdline using a specified configuration table. The specific steps of S42-S44 are as follows:

[0086] First, the configuration entries in the specified configuration table are read sequentially, and the `read_by_tag` function is called to read the corresponding area within the cmdline according to the tag (flag) field of the configuration entry. Further, the data content is read according to `bit_offset` (starting bit) and `bit_size` (data length, i.e., number of bits). Then, the read data content is parsed according to `property_type` (parsing type, such as bit, string, etc.) and `property_size` (parsing bit length) to obtain the corresponding vehicle infotainment system configuration. Finally, the Android side updates the vehicle infotainment system functions based on the vehicle infotainment system configuration.

[0087] In another specific implementation, the configuration entry is: 1,ro.devoption.clusterposition,0x38,1,bit,1. This configuration entry indicates that the first bit starting from bit 0x38 of the tag1 data area is set to the Android system attribute ro.devoption.clusterposition.

[0088] The technical solution provided in this embodiment firstly divides the flash memory into an oemcfg partition of a specified format to store the vehicle infotainment system's function configuration. Further, it establishes shared memory spaces corresponding to the AMSS and QNX sides. Further, it calls an initialization function and uses this function to read the full data of the oemcfg partition from the flash memory through a specified interface. Further, it writes the full data into the shared memory space for the QNX side to read. Further, it uses a preset function on the QNX side to map the shared memory and directly read the full data from the shared memory space. Further, it preprocesses the full data using a preset function and writes the preprocessed full data into the cmdline to at least transmit the cmdline to the Android side. Further, it uses a preset function on the Android side to convert the cmdline into standard startup parameters of a preset format. Further, it reads the function configuration data of the corresponding area within the standard startup parameters sequentially according to the flag bits. Further, it reads the data content of the function configuration data according to the data start bit and data length. Finally, it parses the data content according to the parsing type and parsing bit length to obtain the corresponding vehicle infotainment system function configuration and completes the vehicle infotainment system function update.

[0089] Therefore, this embodiment demonstrates several advantages. First, by dividing the vehicle infotainment system into a dedicated configuration partition of fixed size, which employs an index and data storage structure, it supports bit-level addressing and multi-type data storage. When updating the vehicle infotainment system configuration for different vehicle models, only the stored data in the oemcfg partition needs to be changed to directly update the configuration. This supports flashing the image to install the vehicle configuration, enabling flexible flashing of the system configuration and reducing maintenance costs. Second, this embodiment parses the cmdline based on a specified configuration table, enabling precise extraction of bit-level data from the cmdline. After obtaining the vehicle infotainment system configuration, it can be read according to functional modules, greatly improving the compatibility of the configuration. Third, the specified configuration table in this embodiment supports defining multiple access interfaces to meet various development needs, and the compressed data transmission scheme of the cmdline effectively ensures data transmission efficiency.

[0090] Figure 3 This is a schematic diagram of the structure of a vehicle infotainment system configuration device provided in an embodiment of the present invention. Figure 5 This is a system architecture diagram of the vehicle infotainment function configuration device provided in this embodiment of the invention. This embodiment is applicable to function configuration scenarios for at least various types of vehicles / models. The vehicle infotainment function configuration device can be implemented using software and / or hardware. Figure 3 and Figure 5 As shown, the vehicle infotainment system configuration device includes at least the following:

[0091] The memory partitioning module 110 is used to partition the flash memory into oemcfg partitions of a specified format to store the vehicle infotainment system function configuration.

[0092] The shared memory module 120 is used to establish shared memory spaces corresponding to the AMSS side and the QNX side, and to write the full data of the oemcfg partition into the shared memory for the QNX side to read and use.

[0093] The data transmission module 130 is used to read all the data from the QNX side and write all the data into the memory startup parameter cmdline, so as to at least transmit cmdline to the Android side.

[0094] The parsing update module 140 is used to parse the cmdline according to the specified configuration table on the Android side to obtain the vehicle infotainment system function configuration and complete the configuration of the vehicle infotainment system function according to the vehicle infotainment system function.

[0095] Optionally, the oemcfg partition of the specified format includes at least a partition header, an index area, and a data area.

[0096] The partition header is used to verify whether the oemcfg partition is valid.

[0097] The index area includes at least several index entries, which are used to index the data area of ​​the data area.

[0098] The data area is divided into data regions based at least on the index entries, and is used to store the vehicle infotainment system's function configurations.

[0099] Optionally, the shared memory module 120 is specifically used for:

[0100] Establish shared memory spaces for AMSS and QNX sides; call the initialization function and use the initialization function to read the full data of the oemcfg partition from the flash memory through the specified interface; and write the full data to the shared memory space for the QNX side to read and use.

[0101] Optionally, the data transmission module 130 is specifically used for:

[0102] The QNX side uses a preset function to map shared memory to directly read the full data of the shared memory space; and the preset function preprocesses the full data and writes the preprocessed full data to cmdline so that cmdline is at least passed to the Android side.

[0103] Optionally, the configuration table may include at least a flag bit, a data start bit, a data length, a parsing type, and a parsing bit length; the flag bit is used to associate the index area.

[0104] Optionally, the parsing update module 140 is specifically used for:

[0105] The system utilizes a preset function on the Android side to convert the cmdline into a standard startup parameter in a preset format; it also reads the function configuration data of the corresponding area within the standard startup parameter according to the flag bit; it reads the data content of the function configuration data according to the data start bit and data length; and it parses the data content according to the parsing type and parsing bit length to obtain the corresponding vehicle system function configuration and complete the vehicle system function update.

[0106] The technical solution provided in this embodiment firstly divides the flash memory into oemcfg partitions of a specified format to store the vehicle infotainment system function configuration. Further, a shared memory module establishes corresponding shared memory spaces for the AMSS and QNX sides and writes the full data of the oemcfg partitions into the shared memory for the QNX side to read and use. Further, a data transmission module uses the QNX side to read the full data and writes the full data into the memory startup parameter cmdline, ensuring that the cmdline is at least transmitted to the Android side. Finally, a parsing and updating module uses the Android side to parse the cmdline according to a specified configuration table to obtain the vehicle infotainment system function configuration and completes the configuration of the vehicle infotainment system functions accordingly.

[0107] Therefore, this embodiment demonstrates two advantages. First, by dividing the vehicle infotainment system's function configuration into a specified format OEMCFG partition, it allows for flexible updating of the system configuration by simply modifying the stored data in the OEMCFG partition when updating the system configuration for different vehicle models. This enables flexible flashing of the system configuration and reduces maintenance costs. Second, this embodiment parses the CMDline based on a specified configuration table to obtain the vehicle infotainment system's function configuration. It can read the system configuration according to functional modules, and the specified configuration table supports defining multiple access interfaces to improve configuration compatibility and meet various development needs.

[0108] This embodiment provides an electronic device. Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. See also: Figure 4The electronic device 1000 includes a processor 1001 and a memory 1002. The memory 1002 stores computer-readable instructions. When the computer-readable instructions are executed by the processor 1001, the steps in any of the vehicle infotainment system function configuration methods described above are performed. Through the above technical solution, the processor 1001 and the memory 1002 are interconnected and communicate with each other through a communication bus and / or other forms of connection mechanism (not shown). The memory 1002 stores a computer program that can be executed by the processor. When the electronic device 1000 is running, the processor 1001 executes the computer program to execute the vehicle function configuration method in any optional implementation of the above embodiments, so as to at least achieve the following functions: partitioning an oemcfg partition of a specified format in the flash memory to store the vehicle function configuration; establishing a shared memory space corresponding to the AMSS side and the QNX side, and writing the full data of the oemcfg partition into the shared memory for the QNX side to read and use; using the QNX side to read the full data and writing the full data into the memory startup parameter cmdline, so as to at least pass the cmdline to the Android side; using the Android side to parse the cmdline according to the specified configuration table to obtain the vehicle function configuration, and completing the configuration of the vehicle function according to the vehicle function.

[0109] This embodiment provides a computer-readable storage medium storing a computer program. When executed by a processor, the program implements the vehicle infotainment system (VMS) function configuration method provided in all embodiments of this application: partitioning a specified format oemcfg partition in flash memory to store VMS function configuration; establishing shared memory spaces corresponding to the AMSS side and QNX side, and writing the full data of the oemcfg partition into the shared memory for the QNX side to read and use; using the QNX side to read the full data and write the full data into the memory startup parameter cmdline, so as to at least transmit cmdline to the Android side; using the Android side to parse cmdline according to a specified configuration table to obtain the VMS function configuration, and completing the VMS function configuration according to the VMS functions.

[0110] Any combination of one or more computer-readable media may be used. A computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. A computer-readable storage medium can be, for example—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of computer-readable storage media include: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this document, a computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in connection with an instruction execution system, apparatus, or device.

[0111] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including—but not limited to—electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, capable of transmitting, propagating, or transmitting programs for use by or in connection with an instruction execution system, apparatus, or device.

[0112] The program code contained on a computer-readable medium may be transmitted using any suitable medium, including—but not limited to—wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0113] Computer program code for performing the operations of this invention can be written in one or more programming languages ​​or a combination thereof. Programming languages ​​include object-oriented programming languages—such as Java, Smalltalk, and C++—as well as conventional procedural programming languages—such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0114] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for configuring vehicle infotainment system functions, characterized in that, At least including: Divide the flash memory into oemcfg partitions of a specified format to store the vehicle infotainment system configuration; Establish a shared memory space corresponding to the AMSS side and the QNX side, and write the full data of the oemcfg partition into the shared memory for the QNX side to read and use; The full data is read using the QNX side and written into the memory startup parameter cmdline, so as to at least pass cmdline to the Android side; The Android side parses the cmdline according to the specified configuration table to obtain the vehicle infotainment system function configuration, and completes the configuration of the vehicle infotainment system function based on the vehicle infotainment system function.

2. The vehicle infotainment system configuration method according to claim 1, characterized in that, The specified format oemcfg partition includes at least a partition header, an index area, and a data area; The partition header is used to verify whether the oemcfg partition is valid; The index area includes at least a number of index entries for indexing the data area of ​​the data area; The data area is divided at least according to the index item and is used to store the vehicle system function configuration.

3. The vehicle infotainment system configuration method according to claim 1, characterized in that, The step of establishing shared memory spaces corresponding to the AMSS side and the QNX side, and writing all the data of the oemcfg partition into the shared memory for the QNX side to read and use, specifically includes: Establish the shared memory space corresponding to the AMSS side and the QNX side; The initialization function is invoked, and the full data of the oemcfg partition is read from the flash memory through the specified interface using the initialization function; The full amount of data is written to the shared memory space for the QNX side to read and use.

4. The vehicle infotainment system configuration method according to claim 1, characterized in that, The step of reading the full data using the QNX side and writing the full data into the memory startup parameter cmdline, so as to at least pass cmdline to the Android side, specifically includes: The shared memory is mapped using a preset function on the QNX side to directly read the full data in the shared memory space; The full data is preprocessed using a preset function, and the preprocessed full data is written into the cmdline, so as to at least transmit the cmdline to the Android side.

5. The vehicle infotainment system configuration method according to claim 2, characterized in that, The specified configuration table includes at least the flag bit, the data start bit, the data length, the parsing type, and the parsing bit length; The flag bit is used to associate the index area.

6. The vehicle infotainment system configuration method according to claim 5, characterized in that, The process of using the Android side to parse the cmdline according to a specified configuration table to obtain the vehicle infotainment system function configuration, and completing the configuration of the vehicle infotainment system functions based on the vehicle infotainment system functions, specifically includes: The Android side uses a preset function to convert the cmdline into standard startup parameters in a preset format. Read the function configuration data of the corresponding area in the standard startup parameters sequentially according to the flag bit; Read the data content of the function configuration data according to the data start bit and the data length; The data content is parsed according to the parsing type and the parsing bit length to obtain the corresponding vehicle infotainment function configuration and complete the update of the vehicle infotainment function.

7. A vehicle infotainment system configuration device, characterized in that, At least including: The memory partitioning module is used to partition the flash memory into oemcfg partitions of a specified format to store the vehicle infotainment system's function configurations; A shared memory module is used to establish shared memory spaces corresponding to the AMSS side and the QNX side, and to write the full data of the oemcfg partition into the shared memory for the QNX side to read and use. The data transmission module is used to read the full data using the QNX side and write the full data into the memory startup parameter cmdline, so as to at least transmit cmdline to the Android side; The parsing and updating module is used to parse the cmdline according to the specified configuration table on the Android side to obtain the vehicle system function configuration and complete the configuration of the vehicle system function according to the vehicle system function.

8. The vehicle infotainment system configuration device according to claim 7, characterized in that, A specified format oemcfg partition must include at least a partition header, an index area, and a data area; The partition header is used to verify whether the oemcfg partition is valid; The index area includes at least a number of index entries for indexing the data area of ​​the data area; The data area is divided at least according to the index item and is used to store the vehicle system function configuration.

9. An electronic device comprising a memory and a processor, the memory storing a computer program executable on the processor, characterized in that, When the processor executes the program, it implements the steps in the vehicle infotainment function configuration method according to any one of claims 1 to 6.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps in the vehicle infotainment function configuration method according to any one of claims 1 to 6.

Images