Screen control method and apparatus for intelligent cabin system, device, and medium

Abstract

Disclosed are a screen control method and apparatus for an intelligent cabin system, a device, and a medium. The intelligent cabin system comprises a processing chip and a screen end. The screen control method comprises: when startup of the intelligent cabin system is detected, acquiring a first display screen ID from a display screen partition of the processing chip, multiple display screen IDs being pre-stored in the display screen partition, and the first display screen ID being an ID of a historical display screen connected to and used by the intelligent cabin system; acquiring a second display screen ID of a target display screen of the screen end by means of a mapping relationship corresponding to the first display screen ID; if the second display screen ID is the same as the first display screen ID, acquiring a first initialization file corresponding to the first display screen ID; and initializing the target display screen by using the first initialization file, such that the target display screen operates normally.

Description

Screen control method, device and equipment of intelligent cockpit system and medium

[0001] Reference of Related Applications

[0002] The present disclosure claims the entire right of the Chinese invention patent application with the application number 202410687124.5 and the invention name "Screen control method, device and equipment of intelligent cockpit system and medium" submitted to the State Intellectual Property Office of the People's Republic of China on May 29, 2024, and the entire content thereof is incorporated by reference into the present disclosure.

[0003] Field

[0004] The present disclosure generally relates to the field of intelligent cockpit technology, and more particularly to a screen control method, device and equipment of intelligent cockpit system and medium.

[0005] BACKGROUND

[0006] At present, with the development of intelligent cockpit experience, users no longer only focus on mechanical performance such as power back feeling, but pursue more delicate and comfortable intelligent cockpit environment and interactive experience. In order to meet the interactive experience of users, various screens of different models appear, but the screen IC (Integrated Circuit) used by screens of different models is different, and the parameters are different, so different screens need to be configured with different initialization parameters. When the software of the same version of cockpit platform is adapted to screens of different models, the correct screen ID (Identity document) is obtained through enumeration at startup, and then the corresponding parameters are found to initialize the screen, but this will increase the startup time of the system. Especially when the system is compatible with a large number of display screen models, finding the model of the connected screen through enumeration will result in too long startup time, which will waste time cost and affect user experience.

[0007] SUMMARY

[0008] In one aspect, the present disclosure provides a screen control method of an intelligent cockpit system, the intelligent cockpit system comprising a processing chip and a screen end, the method comprising: obtaining a first display screen ID from a display screen partition of the processing chip when it is detected that the intelligent cockpit system is started, wherein a plurality of display screen IDs are pre-stored in the display screen partition, and the first display screen ID is an ID of a historical display screen connected to the intelligent cockpit system and used; obtaining a second display screen ID of a target display screen of the screen end through a mapping relationship corresponding to the first display screen ID; in the case that the second display screen ID is the same as the first display screen ID, obtaining a first initialization file corresponding to the first display screen ID; and initializing the target display screen by using the first initialization file, so that the target display screen operates normally.

[0009] In some embodiments, obtaining the second display screen ID of the target display screen at the screen end through the mapping relationship corresponding to the first display screen ID comprises: obtaining a storage address corresponding to the mapping relationship of the first display screen ID; locating a storage unit of the target display screen according to the storage address; and reading the second display screen ID of the target display screen from the storage unit if the storage unit is successfully located.

[0010] In some embodiments, after locating the storage unit of the target display screen according to the storage address, the method further comprises: determining that the target display screen is different from the historical display screen if the storage unit fails to be located; and determining that the target display screen is different from the historical display screen if the storage unit is successfully located and the second display screen ID obtained from the storage unit is different from the first display screen ID.

[0011] In some embodiments, initializing the target display screen through the first initialization file comprises: merging the first initialization file and a common file of a device tree to obtain the device tree, wherein the first initialization file is in a binary format of the device tree, and the first initialization file is obtained by compiling configuration parameters corresponding to the first display screen ID in advance; parsing the device tree by traversing each node of the device tree to obtain the configuration parameters; and initializing the target display screen through the configuration parameters.

[0012] In some embodiments, after initializing the target display screen through the first initialization file, the method further comprises: generating a target node, wherein the target node comprises the second display screen ID of the target display screen; reading the second display screen ID on the target node through a preset loading service and loading a touch screen module corresponding to the second display screen ID, wherein the display screen ID and the touch screen module are pre-mapped and stored, and the touch screen module is obtained by compiling touch screen drivers of various models; and initializing a touch screen device to enable the touch screen device to operate normally.

[0013] In some embodiments, after obtaining the second display screen ID at the screen end, the method further comprises: obtaining an ID list if the first display screen ID is different from the second display screen ID, wherein the ID list comprises a plurality of display screen IDs pre-established in the mapping relationship; finding a third display screen ID identical to the second display screen ID from the ID list and storing the second display screen ID to a display screen partition of a processing chip; and obtaining a second initialization file corresponding to the third display screen ID through the mapping relationship and initializing the target display screen through the second initialization file.

[0014] In some embodiments, after the positioning of the storage unit fails, the method further comprises: obtaining an ID list and each storage address corresponding to each display screen ID in the ID list; sequentially positioning the storage unit of the target display screen according to the storage addresses of each display screen ID until a fourth display screen ID is found, wherein the storage address corresponding to the fourth display screen ID is used to successfully position the storage unit of the target display screen, and the fourth display screen ID is the same as the fifth display screen ID obtained from the storage unit; storing the fourth display screen ID to the display screen partition of the processing chip; and obtaining a third initialization file corresponding to the fourth display screen ID, and initializing the target display screen by using the third initialization file.

[0015] In another aspect, the present disclosure provides a screen control device of an intelligent cockpit system, the intelligent cockpit system comprising a processing chip and a screen end, the device comprising: a first obtaining module configured to obtain a first display screen ID from a display screen partition of the processing chip when it is detected that the intelligent cockpit system is powered on, wherein a plurality of display screen IDs are pre-stored in the display screen partition, and the first display screen ID is an ID of a historical display screen connected to the intelligent cockpit system and used; a second obtaining module configured to obtain a second display screen ID of a target display screen of the screen end through a mapping relationship corresponding to the first display screen ID; a third obtaining module configured to obtain a first initialization file corresponding to the first display screen ID in a case where the second display screen ID is the same as the first display screen ID; and an initialization module configured to initialize the target display screen by using the first initialization file, so that the target display screen normally operates.

[0016] In yet another aspect, the present disclosure provides an electronic device comprising a memory, a processor, a communication interface and a communication bus, the memory storing a computer program executable on the processor, the memory, the processor and the communication interface communicating through the communication bus, and the processor executing the computer program to implement the screen control method of the intelligent cockpit system.

[0017] In still another aspect, the present disclosure further provides a computer readable medium having a non-volatile program code executable by a processor, the program code causing the processor to execute the screen control method of the intelligent cockpit system.

[0018] In some embodiments, by obtaining the first display screen ID used before from the display screen partition, it is only necessary to compare the first display screen ID with the ID of the currently connected screen, and if they are the same, the initialization file corresponding to the first display screen ID can be directly obtained to configure the display screen, without spending a lot of time for enumeration, thereby solving the problem that the enumeration to find the model of the connected screen of the system leads to too long boot time.

[0019] BRIEF DESCRIPTION OF DRAWINGS

[0020] The accompanying drawings, which are incorporated herein and constitute part of the specification, illustrate embodiments consistent with the present disclosure and, together with the description, further serve to explain the principles of the present disclosure.

[0021] In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings required to be used by the embodiments will be briefly introduced as follows. Obviously, for those of ordinary skill in the art, other drawings can also be obtained based on these drawings without any creative effort.

[0022] FIG. 1 is a flowchart of a screen control method of an intelligent cockpit system according to an embodiment of the present disclosure;

[0023] FIG. 2 is an architecture diagram of an intelligent cockpit system according to an embodiment of the present disclosure;

[0024] FIG. 3 is a block diagram of a screen control device of an intelligent cockpit system according to an embodiment of the present disclosure; and

[0025] FIG. 4 is a structural schematic diagram of an electronic device according to an embodiment of the present disclosure.

[0026] Detailed description

[0027] In order to make the objects, technical solutions and advantages of the embodiments of the present disclosure clearer, the technical solutions in the embodiments of the present disclosure will be described clearly and completely below with reference to the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are only a part of the embodiments of the present disclosure, rather than all the embodiments of the present disclosure. Based on the embodiments in the present disclosure, all other embodiments obtained by those of ordinary skill in the art without any creative effort fall within the scope of protection of the present disclosure.

[0028] In the subsequent description, the suffixes such as "module", "part" or "unit" used to represent elements are only for the convenience of the description of the present disclosure, and have no specific meaning in itself. Therefore, "module" and "part" can be used interchangeably.

[0029] Currently, with the development of intelligence of cockpit experience, the user's requirements no longer stop at mechanical performance such as power back feeling, but pursue more delicate and comfortable intelligent cockpit environment and interactive experience. In order to meet the user's more interactive experience, various screens of different models appear, but different models of screens use different screen ICs and different parameters, so different screens need to be configured with different initialization parameters. When the software of the same version of cockpit platform is adapted to different models of screens, the correct screen ID is obtained through enumeration at startup, and then the corresponding parameters are found to initialize the screen. However, this will increase the system startup time, especially when the system is compatible with a large number of display screen models, finding the type of the connected screen through enumeration will cause the boot time to be too long, which will waste time cost and affect user experience.

[0030] In one aspect, the present disclosure provides a screen control method of an intelligent cockpit system, the intelligent cockpit system comprising a processing chip and a screen end, as shown in FIG. 1, the method comprising:

[0031] Step 101, when it is detected that the intelligent cockpit system is started, obtaining a first display screen ID from a display screen partition of the processing chip, wherein a plurality of display screen IDs are pre-stored in the display screen partition, and the first display screen ID is an ID of a historical display screen connected with the intelligent cockpit system and used;

[0032] Step 103, obtaining a second display screen ID of a target display screen of the screen end through a mapping relationship corresponding to the first display screen ID;

[0033] Step 105, in the case that the second display screen ID is the same as the first display screen ID, obtaining a first initialization file corresponding to the first display screen ID; and

[0034] Step 107, initializing the target display screen by using the first initialization file, so that the target display screen normally runs.

[0035] The scheme provided by the present disclosure needs to store screen related data in the screen end before startup, and store screen related data with mapping relationship in the firmware, and store the IDs of each display screen connected with the intelligent cockpit system and used in the display screen partition of the processing chip.

[0036] The present disclosure preferentially takes the ID of the historical display screen connected with the intelligent cockpit system and used last time as the first display screen ID.

[0037] Figure 2 is an architecture diagram of an intelligent cockpit system according to an embodiment of the present disclosure. The SOC (System on a Chip) and the serializer in the figure belong to the processing chip part (which can also be understood as the intelligent cockpit body part), the deserializer, EEPROM (Electrically Erasable Programmable Read-Only Memory), LCD (Liquid Crystal Display), and TP (Touch Panel) belong to the screen end part (screen A in the figure), I2C is a serial communication bus used for data transmission, and MIPI DSI is a serial interface applied to display technology. In some embodiments, the SOC is connected to the serializer through MIPI DSI and I2C, the serializer and the deserializer are connected through GMSL (Gigabit Multimedia Serial Link), the deserializer is connected to the EEPROM through I2C, connected to the LCD through LVDS (Low Voltage Differential Signaling), and connected to the TP through I2C.

[0038] In some embodiments, storing screen-related data at the screen end includes storing information such as the current screen ID, screen manufacturer, display screen resolution, and display screen size in the storage unit at each screen end. The screen ID is mainly used in the present disclosure. By adding a storage unit at the screen end to save screen-related information, different screens can be distinguished.

[0039] In some embodiments, screen-related data of the same model needs to be mapped and saved to the firmware, and can be stored in the form of a structure array. The firmware stores screen-related data with a mapping relationship, including storing the display screen ID, configuration parameters corresponding to the display screen, storage addresses corresponding to the display screen, initialization files corresponding to the display screen, and touch screen modules of the touch screen matched with the display screen. By establishing a mapping relationship, one data can be used to quickly extract other related data when needed.

[0040] In some embodiments, the firmware stores initialization parameters (i.e., configuration parameters) corresponding to each screen and the serial deserializer. The initialization parameters are mainly determined by the display screen hardware, and can be configured according to the hardware principle of the display screen. After the configuration parameters are configured, they are stored. When the configuration parameters are used to initialize the target display screen, the initialization of the serial deserializer is also involved.

[0041] In some embodiments, the configuration parameters are present in the xml file of UEFI (Unified Extensible Firmware Interface) and the device tree of kernel, wherein the configuration parameters in the device tree are compiled into the initialization file (DISP DTBO) in the binary format of the device tree by using DTC (Device Tree Compiler), and each model of display screen corresponds to an initialization file, such as DISP DTBO A for A screen and DISP DTBO B for B screen. The initialization parameters are obtained from the xml file and the device tree by the subsequent serial deserializer driver, so that one serial deserializer driver can be compatible with all serial deserializer.

[0042] The configuration parameters of each display screen are pre-compiled into the initialization file, which can achieve the purpose of minimum change and compilation, and save the compilation time during debugging.

[0043] In some embodiments, it is also necessary to compile the drivers of touch screens of different models into corresponding touch screen modules ko, such as tp_a.ko for a model of touch screen and tp_b.ko for b model of touch screen.

[0044] In some embodiments, the display screen partition is also added in the SOC of the intelligent cockpit platform, which is used to store the ID of the display screen connected and used by the intelligent cockpit and the serial deserializer information. The serial deserializer information is saved through the display screen partition, and if it is not the first time to connect the screen and start or change the screen, the serial deserializer does not need to be enumerated, thereby saving the start time.

[0045] In some embodiments, the purpose is to quickly find the initialization parameters matched with the connected screen to initialize the connected screen when the intelligent cockpit system starts, instead of directly using the time-consuming enumeration method to find the corresponding display screen ID or display screen model, which can save the start time and improve the user experience.

[0046] In some embodiments, the second display screen ID of the target display screen of the screen end is obtained through the mapping relationship corresponding to the first display screen ID, including: obtaining the storage address corresponding to the mapping relationship of the first display screen ID; locating the storage unit of the target display screen according to the storage address; if the storage unit is successfully located, reading the second display screen ID of the target display screen from the storage unit.

[0047] In the UEFI boot stage, the first display screen ID of the last used display screen is read from the display screen partition, including: using the existing interface to directly read the string from the display screen partition, and the first display screen ID saved in the partition can be obtained by parsing the string; then the storage address corresponding to the mapping relationship of the first display screen ID is obtained.

[0048] In some embodiments, the storage address corresponding to the first display screen ID is obtained according to the mapping relationship, and the storage address includes an I2C address of the EEPROM and an EEPROM register address. The I2C address is used to uniquely identify a device on an I2C bus, and the EEPROM register address is used to locate specific data or configuration in the EEPROM.

[0049] Locating the storage unit of the target display screen according to the storage address includes: locating the display screen device on the bus through the I2C address, then locating the storage unit inside the device through the EEPROM register address, and further obtaining the second display screen ID of the target display screen.

[0050] In some embodiments, after locating the storage unit of the target display screen according to the storage address, the method further includes: if the storage unit fails to be located, determining that the target display screen is different from the historical display screen; and if the storage unit is successfully located and the second display screen ID obtained from the storage unit is different from the first display screen ID, determining that the target display screen is different from the historical display screen.

[0051] If the storage unit fails to be read, it means that the storage unit cannot be located according to the storage address, that is, the historical display screen is different from the model of the currently connected display screen.

[0052] Generally, the I2C address of the EEPROM and the EEPROM register address of the display screen of the same model are the same, but there is a possibility that the supplier repeats the address configuration, so there is a possibility that the display screens of different models correspond to the same storage address.

[0053] If the storage unit is successfully read, but the second display screen ID obtained from the storage unit is different from the first display screen ID, it still means that the historical display screen is different from the model of the currently connected display screen.

[0054] The data of the mapping relationship can be stored in an array of structure bodies.

[0055] In some embodiments, the array of panel_list structure bodies sequentially stores the mapping relationship of the I2C address of the EEPROM, the EEPROM register address, the display screen ID (in the partition), and the display screen model. An example of the array of panel_list structure bodies is provided in the disclosure as follows:

[0056] {0x58, 0x02, 0x20, “a.xml”}, / / panel_list[0] model A screen;

[0057] {0x58, 0x03, 0x30, “b.xml”}, / / panel_list[1] model B screen;

[0058] {0x52, 0x04, 0x40, "c.xml"}, / / panel_list[2] model C screen.

[0059] Taking the model A screen as an example, 0x58 is the I2C address, 0x02 is the EEPROM register address, 0x20 is the screen ID, "a.xml" is the xml file, and panel_list[0] indicates that the screen-related data of the model A screen is the first element of the structure array.

[0060] The first display screen ID obtained from the display screen partition is 0x30, so according to the mapping relationship, it can be known that the display screen partition saves the screen ID of the B display screen, and the B display screen belongs to the data of panel_list[1]. The storage address in panel_list[1] is used to obtain the second display screen ID saved in the storage unit at the screen end. If the second display screen ID is successfully obtained and is 0x30, it means that the last screen is still used, and the display screen is directly initialized using b.xml. If the obtained second display screen ID is not successful or is not 0x30, it means that the connected is not the B display screen, and it is necessary to find out which model of display screen is actually connected to the intelligent cockpit.

[0061] In some embodiments, the target display screen is initialized by using the first initialization file, including: merging the first initialization file and a common file of a device tree to obtain a device tree, wherein the first initialization file is in a device tree binary format, and the first initialization file is obtained by pre-compiling configuration parameters corresponding to the first display screen ID; the device tree is parsed by traversing each node of the device tree to obtain the configuration parameters; and the target display screen is initialized by using the configuration parameters.

[0062] The first initialization file is obtained by pre-compiling the configuration parameters of the display screen using a DTC tool, and the format is a device tree binary format.

[0063] If the screen IDs of the two display screens are the same, the first initialization files of the two screens are also the same.

[0064] The common file of the device tree includes DTB and DTBO. The DTB is passed to the kernel by the bootloader when the kernel is started, and it contains the basic structure of the device tree. The DTBO is loaded when the system is running, and it allows some configurations to be added or covered on the original device tree structure. The first initialization file is combined with the DTB and the DTBO as an added configuration to become a complete device tree, and the display screen configuration in the device tree will be updated to correspond to the configuration defined in the loaded first initialization file (DISP_DTBO file).

[0065] The bootloader (e.g., abl or U-Boot) loads the configuration parameters in the device tree, and then passes the configuration parameters to the kernel, which uses the configuration parameters to initialize and configure the target display screen connected to the system, including setting the resolution, refresh rate, brightness, and other parameters of the target display screen, to ensure that the display screen can work normally.

[0066] In some embodiments, after the target display screen is initialized using the first initialization file, the method further includes: generating a target node, wherein the target node includes a second display screen ID of the target display screen; reading the second display screen ID on the target node by a preset loading service, and loading a touch screen module corresponding to the second display screen ID, wherein the display screen ID and the touch screen module are pre-mapped and stored, and the touch screen module is obtained by compiling touch screen drivers of various models; and initializing the touch screen device to make the touch screen device run normally.

[0067] After the kernel initializes the display screen, a panel_id node (i.e., a target node) is generated, which contains the ID of the connected target display screen, and the panel_id node is located at a specific location in the device tree for the upper application program to obtain. The upper application program can obtain the second display screen ID of the target display screen by reading the target node in the device tree.

[0068] In some embodiments, the preset loading service is a module_load service, which can obtain the second display screen ID of the target display screen by parsing the target node, and then load the touch screen module corresponding to the second display screen ID, which includes the driver and functions related to the current model of touch screen.

[0069] After loading the touch screen module, the touch screen device connected to the system is initialized, and the touch screen device can normally run to receive user input.

[0070] The preset loading service loads the corresponding touch screen module according to the target node in the device tree, so that the system can automatically load the corresponding touch screen driver according to the connected target display screen, realizing dynamic adaptation and support for different models of touch screens.

[0071] In some embodiments, the related information of the display screen, the touch screen, and the serial deserializer are all stored on the firmware, which can simultaneously consider the compatibility of the display screen, the touch screen, and the serial deserializer.

[0072] In some embodiments, after obtaining the second display screen ID of the screen terminal, the method further comprises: if the first display screen ID is different from the second display screen ID, obtaining an ID list, wherein the ID list comprises a plurality of display screen IDs with which a mapping relationship is established in advance; finding a third display screen ID identical to the second display screen ID from the ID list, and storing the second display screen ID to the display screen partition of the processing chip; obtaining a second initialization file corresponding to the third display screen ID according to the mapping relationship, and initializing the target display screen by using the second initialization file.

[0073] The display screen IDs in the ID list are the display screen IDs in the structure array mentioned above, and the structure array can also be regarded as the ID list.

[0074] Since the second display screen ID of the screen terminal has been obtained, the mapping data corresponding to the second display screen ID in the ID list can be directly found. If the ID list contains a third display screen ID identical to the second display screen ID, the second initialization file can be directly obtained according to the mapping relationship, and the target display screen can be initialized by using the second initialization file. The specific initialization steps have been described above, and thus will not be described here.

[0075] In some embodiments, the second display screen ID needs to be stored to the display screen partition of the processing chip. In this way, the display screen ID obtained from the display screen partition at the next boot is the second display screen ID.

[0076] In some embodiments, after the storage unit fails to be located, the method further comprises: obtaining an ID list and a storage address corresponding to each display screen ID in the ID list; locating the storage unit of the target display screen according to the storage addresses of the display screen IDs in sequence until a fourth display screen ID is found, wherein the storage address corresponding to the fourth display screen ID is used to successfully locate the storage unit of the target display screen, and the fourth display screen ID is identical to a fifth display screen ID obtained from the storage unit; storing the fourth display screen ID to the display screen partition of the processing chip; obtaining a third initialization file corresponding to the fourth display screen ID, and initializing the target display screen by using the third initialization file.

[0077] Locating the storage unit of the target display screen according to the storage addresses of the display screen IDs is to locate the display screen device on the bus through the I2C address, and then locate the storage unit in the device through the EEPROM register address. If the location fails, the I2C address and the EEPROM register address of the next display screen ID are obtained to continue the location until the location succeeds.

[0078] If the storage unit of the target display screen is successfully positioned, the display screen ID stored in the storage unit is read, and it is determined whether the display screen ID being verified is the same as the display screen ID stored in the storage unit. If they are the same, the display screen ID being verified is determined as the fourth display screen ID. If they are not the same, the next I2C address and EEPROM register address of the display screen ID are acquired for positioning.

[0079] The third initialization file corresponding to the fourth display screen ID is acquired, and the target display screen is initialized by using the third initialization file. The specific initialization steps have been described above, and thus will not be described here.

[0080] If the compatible screens in the ID list are N, the number of verification times is 1 to N. For example, if the connected screen is the Mth screen in the list (M≤N), the screen ID needs to be read M times.

[0081] In some embodiments, by acquiring the first display screen ID used last time from the display screen partition, the first display screen ID only needs to be compared with the ID of the currently connected screen. If they are the same, the initialization file corresponding to the first display screen ID can be directly acquired to configure the display screen, without spending a lot of time for enumeration, thereby solving the problem that the boot time is too long due to enumeration to find the model of the connected screen of the system.

[0082] On the other hand, the present disclosure provides a screen control device of an intelligent cockpit system, the intelligent cockpit system including a processing chip and a screen end. As shown in FIG. 3, the device includes:

[0083] The first acquisition module 302 is configured to acquire a first display screen ID from a display screen partition of the processing chip when it is detected that the intelligent cockpit system is booted, wherein a plurality of display screen IDs are pre-stored in the display screen partition, and the first display screen ID is an ID of a historical display screen connected to the intelligent cockpit system and used;

[0084] The second acquisition module 304 is configured to acquire a second display screen ID of a target display screen of the screen end through a mapping relationship corresponding to the first display screen ID;

[0085] The third acquisition module 306 is configured to acquire a first initialization file corresponding to the first display screen ID in a case where the second display screen ID is the same as the first display screen ID; and

[0086] The initialization module 308 is configured to initialize the target display screen by using the first initialization file, so that the target display screen normally operates.

[0087] It should be noted that the first obtaining module 302 in the embodiment can be configured to perform step 101 in the embodiments of the present disclosure, the second obtaining module 304 in the embodiment can be configured to perform step 103 in the embodiments of the present disclosure, the third obtaining module 306 in the embodiment can be configured to perform step 105 in the embodiments of the present disclosure, and the initialization module 308 in the embodiment can be configured to perform step 107 in the embodiments of the present disclosure.

[0088] In some embodiments, the second obtaining module 304 is further configured to obtain a storage address corresponding to the first display screen ID; locate a storage unit of the target display screen according to the storage address; and if the storage unit is located successfully, read the second display screen ID of the target display screen from the storage unit.

[0089] In some embodiments, the second obtaining module 304 is further configured to, after locating the storage unit of the target display screen according to the storage address, determine that the target display screen is different from the historical display screen if the storage unit fails to be located; and determine that the target display screen is different from the historical display screen if the storage unit is located successfully and the second display screen ID obtained from the storage unit is different from the first display screen ID.

[0090] In some embodiments, the initialization module 308 is further configured to merge the first initialization file and a common file of the device tree to obtain the device tree, wherein the first initialization file is in a device tree binary format, and the first initialization file is obtained by compiling the configuration parameters corresponding to the first display screen ID in advance; parse the device tree by traversing each node of the device tree to obtain the configuration parameters; and initialize the target display screen by using the configuration parameters.

[0091] In some embodiments, the apparatus further comprises a first processing module configured to, after initializing the target display screen by using the first initialization file, generate a target node, wherein the target node comprises the second display screen ID of the target display screen; read the second display screen ID on the target node by using a preset loading service, and load a touch screen module corresponding to the second display screen ID, wherein the display screen ID and the touch screen module are pre-stored in a mapping manner, and the touch screen module is obtained by compiling touch screen drivers of various models; and initialize the touch screen device to enable the touch screen device to operate normally.

[0092] In some embodiments, the device further comprises a second processing module configured to, after obtaining the second display screen ID of the acquisition terminal, if the first display screen ID is different from the second display screen ID, obtain an ID list, wherein the ID list comprises a plurality of display screen IDs having a pre-established mapping relationship; find a third display screen ID identical to the second display screen ID from the ID list, and store the second display screen ID to the display screen partition of the processing chip; obtain a second initialization file corresponding to the third display screen ID according to the mapping relationship, and initialize the target display screen by using the second initialization file.

[0093] In some embodiments, the device further comprises a second processing module configured to, after failing to locate the storage unit, obtain an ID list and a plurality of storage addresses having a mapping relationship with each display screen ID in the ID list; locate the storage unit of the target display screen according to the storage addresses of the display screen IDs in sequence until a fourth display screen ID is found, wherein the storage address corresponding to the fourth display screen ID is used to successfully locate the storage unit of the target display screen, and the fourth display screen ID is identical to a fifth display screen ID obtained from the storage unit; store the fourth display screen ID to the display screen partition of the processing chip; obtain a third initialization file corresponding to the fourth display screen ID, and initialize the target display screen by using the third initialization file.

[0094] It should be noted that the above modules and corresponding steps achieve the same examples and application scenarios as the above embodiments, but are not limited to the contents disclosed in the above embodiments.

[0095] In another aspect, the present disclosure provides an electronic device as shown in FIG. 4, which comprises a memory 401, a processor 403, a communication interface 405, and a communication bus 407, the memory 401 stores a computer program executable on the processor 403, the memory 401 and the processor 403 communicate through the communication interface 405 and the communication bus 407, and the processor 403 executes the computer program to implement the screen control method of the intelligent cockpit system described in the present disclosure.

[0096] In some embodiments, the memory, the processor in the above electronic device communicate through the communication bus and the communication interface. The communication bus can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The communication bus can be divided into an address bus, a data bus, a control bus, etc.

[0097] In some embodiments, the memory can include a Random Access Memory (RAM) and can also include a non-volatile memory, such as at least one disk storage. In some embodiments, the memory can also be at least one storage device remotely located from the aforementioned processor(s).

[0098] In some embodiments, the aforementioned processor(s) can be a general processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc. It can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components.

[0099] In another aspect, the present disclosure also provides a computer readable medium having non-volatile program codes executable by a processor.

[0100] In some embodiments, the specific examples in the present embodiment can refer to the examples described in the above embodiments, which will not be repeated here.

[0101] When the present embodiment is implemented, it can refer to the above embodiments and have corresponding technical effects.

[0102] It can be understood that the embodiments described herein can be implemented in hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing units can be implemented within one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field-Programmable Gate Arrays (FPGAs), general-purpose processors, controllers, micro-controllers, microprocessors, other electronic units configured to perform the functions described in the present disclosure, or a combination thereof.

[0103] For software implementation, the techniques described herein can be implemented with a combination of hardware and software. The software code can be stored in a memory and executed by a processor.

[0104] Those skilled in the art can clearly understand that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be realized by electronic hardware or a combination of computer software and electronic hardware. Whether the functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. A person skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present disclosure.

[0105] Those skilled in the art can clearly understand that, for the convenience and brevity of the description, the specific working processes of the above-described system, device and unit can refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

[0106] In the embodiments provided by the present disclosure, it should be understood that the disclosed apparatus and method can be implemented in other ways. For example, the above-described device embodiments are merely schematic, and the division of the modules is merely a logical function division. In actual implementation, another division mode can be used, for example, a plurality of modules or components can be combined or integrated into another system, or some features can be omitted or not executed. In addition, the coupling or direct coupling or communication connection between the displayed or discussed units can be indirect coupling or communication connection through some interfaces, devices or units, and can be electrical, mechanical or other forms.

[0107] The units described as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, i.e. can be located in one place, or can be distributed on a plurality of network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment.

[0108] In addition, each functional unit in each embodiment of the present disclosure can be integrated in one processing unit, or each unit can be physically present separately, or two or more units can be integrated in one unit.

[0109] If the functions are implemented in the form of software function units and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the embodiments of the disclosure essentially contribute to or part of the technical solutions can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to make a computer device (which can be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the disclosure. The aforementioned storage medium includes: U disk, mobile hard disk, ROM, RAM, magnetic disk or optical disk, and various other program code storage media. It should be noted that in this paper, relationship terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between the entities or operations. Moreover, the terms "include", "contain" or any other variants thereof are intended to cover non-exclusive inclusion, so that the processes, methods, articles or devices including a series of elements not only include those elements, but also include other elements not explicitly listed or inherent to such processes, methods, articles or devices. Without more limitations, the element defined by the statement "including a" does not exclude the presence of other identical elements in the process, method, article or device including the element.

[0110] The above description is only a specific implementation of the disclosure, so that those skilled in the art can understand or implement the disclosure. Various modifications of these embodiments will be apparent to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the disclosure. Therefore, the disclosure will not be limited to these embodiments shown herein, but will conform to the widest range consistent with the principles and novel features disclosed herein.

Claims

1. A method for screen control of an intelligent cockpit system, the intelligent cockpit system comprising a processing chip and a screen terminal, the method comprising: obtaining a first display ID from a display partition of the processing chip when it is detected that the intelligent cockpit system is powered on, wherein a plurality of display IDs are pre-stored in the display partition, and the first display ID is an ID of a historical display connected to the intelligent cockpit system and used; obtaining a second display ID of a target display of the screen terminal through a mapping relationship corresponding to the first display ID; obtaining a first initialization file corresponding to the first display ID in a case where the second display ID is the same as the first display ID; and initializing the target display using the first initialization file to enable the target display to operate normally. 2.The method of claim 1, wherein the obtaining the second display ID of the target display of the screen terminal through the mapping relationship corresponding to the first display ID comprises: obtaining a storage address having the mapping relationship with the first display ID; locating a storage unit of the target display according to the storage address; and reading the second display ID of the target display from the storage unit if the storage unit is located successfully. 3.The method of claim 2, wherein after the locating the storage unit of the target display according to the storage address, the method further comprises: determining that the target display is different from the historical display if the storage unit fails to be located; and determining that the target display is different from the historical display if the storage unit is located successfully and the second display ID obtained from the storage unit is different from the first display ID. 4.The method of any one of claims 1 to 3, wherein the initializing the target display using the first initialization file comprises: merging the first initialization file and a common file of a device tree to obtain the device tree, wherein the first initialization file is in a device tree binary format, and the first initialization file is obtained by compiling configuration parameters corresponding to the first display ID in advance; parsing the device tree by traversing each node of the device tree to obtain the configuration parameters; and initializing the target display using the configuration parameters. 5.The method of any one of claims 1 to 4, wherein after the initializing the target display using the first initialization file, the method further comprises: generating a target node, wherein the target node comprises the second display ID of the target display; reading the second display ID on the target node through a preset loading service, and loading a touch screen module corresponding to the second display ID, wherein a corresponding display ID and a touch screen module are pre-mapped and stored, and the touch screen module is obtained by compiling touch screen drivers of various models; and ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ Initialize a touch screen device to make the touch screen device run normally.

6. The method of any one of claims 1 to 5, wherein after obtaining the second display ID of the screen terminal, the method further comprises: if the first display ID is different from the second display ID, obtaining an ID list, wherein the ID list includes a plurality of display IDs for which the mapping relationship is established in advance; finding a third display ID from the ID list that is the same as the second display ID, and storing the second display ID to a display partition of the processing chip; obtaining a second initialization file corresponding to the third display ID according to the mapping relationship, and initializing the target display using the second initialization file.

7. The method of claim 3, wherein after failing to locate the storage unit, the method further comprises: obtaining an ID list and each storage address of each display ID in the ID list for which the mapping relationship exists; locating the storage unit of the target display in order according to the storage addresses of the display IDs until a fourth display ID is found, wherein the storage address corresponding to the fourth display ID is used to successfully locate the storage unit of the target display, and the fourth display ID is the same as a fifth display ID obtained from the storage unit; storing the fourth display ID to the display partition of the processing chip; obtaining a third initialization file corresponding to the fourth display ID, and initializing the target display using the third initialization file.

8. A screen control device of an intelligent cockpit system, the intelligent cockpit system comprising a processing chip and a screen terminal, the device comprising: a first obtaining module configured to obtain a first display ID from a display partition of the processing chip when detecting that the intelligent cockpit system is powered on, wherein a plurality of display IDs are pre-stored in the display partition, and the first display ID is an ID of a historical display connected to and used by the intelligent cockpit system; a second obtaining module configured to obtain a second display ID of a target display of the screen terminal through a mapping relationship corresponding to the first display ID; a third obtaining module configured to obtain a first initialization file corresponding to the first display ID in a case where the second display ID is the same as the first display ID; an initialization module configured to initialize the target display using the first initialization file to make the target display run normally.

9. An electronic device comprising a memory, a processor, a communication interface, and a communication bus, wherein the memory stores a computer program capable of running on the processor, the memory, the processor, the communication interface, and the communication bus are in communication, and the processor implements the screen control method of the intelligent cockpit system according to any one of claims 1 to 7 when executing the computer program. 10.A computer readable medium having non-transitory program code executable by a processor, wherein the program code causes the processor to perform the screen control method of the intelligent cockpit system of any one of claims 1 to 7.

Images