Method, device, equipment and medium for compatibility of system-on-chip and screen

Abstract

The invention relates to the technical field of intelligent cabins, and discloses a method, a device, equipment and a medium for compatibility of a system-on-chip and a screen, and the method comprises the steps: configuring a deserializer arranged at a screen end to be in a first link state; under the condition that the deserializer is in the first link state, communication connection in the first link state is established between the deserializer and a serializer arranged at a system-on-chip end, and a first equipment address of an existing screen end stored in a memory is read through the system-on-chip end; under the communication connection in the first link state, a configuration file is traversed based on the system-level chip side, the configuration file comprises the device address of at least one deserializer, a second device address which can be accessed in the configuration file is obtained, and if the first device address is the same as the second device address, the screen side is initialized based on the first device address. Therefore, the in-vehicle machine chip can be automatically compatible with various screens, the workload of technicians is reduced, the in-vehicle machine screen does not need to be replaced, and the research and development and after-sales costs are reduced.

Description

Technical Field

[0001] The present invention relates to the field of smart cockpit technology, and in particular to a method, device, equipment and medium for compatibility between a system-level chip and a screen. Background Art

[0002] With the development of society, users have higher and higher requirements for vehicle intelligence, and the development of smart cockpits is inseparable from various screens, including the central control instrument, etc. However, in the process of production or after-sales service of vehicles, different batches or different configurations of models often use different screens from different suppliers. Since the parameters of different screens are different, the initialization process of the vehicle cockpit system-on-chip (SoC) for the screen is also different.

[0003] For the above situation, the relevant technology uses hardware to distinguish, and different hardware is adapted through different software, which will generate a relatively large workload. For vehicles that have already been put on the market for after-sales, the only solution is to replace the car screen. The above coping strategies have caused a waste of manpower and material resources. Summary of the invention

[0004] In view of this, the present invention provides a method, device, equipment and medium for system-level chip and screen compatibility to solve the problem of wasting human and material resources by adapting different car screens through different software.

[0005] In a first aspect, the present invention provides a method for making a system-level chip compatible with a screen, the method comprising: configuring a deserializer provided at a screen end to be in a first link state; when the deserializer is in the first link state, establishing a communication connection under the first link state between the deserializer and a serializer provided at the system-level chip end, and reading a first device address of an existing screen end stored in a memory through the system-level chip end; under the communication connection under the first link state, traversing a configuration file based on the system-level chip end, the configuration file including at least one device address of a deserializer, obtaining a second device address that can be accessed in the configuration file, and if the first device address is the same as the second device address, initializing the screen end based on the first device address.

[0006] In an optional embodiment, the aforementioned method for making the system-level chip compatible with the screen also includes: if the first device address is different from the second device address, writing the second device address into the memory, restarting the system-level chip end, and initializing the screen end based on the second device address.

[0007] In an optional embodiment, the aforementioned method for making the system-level chip compatible with the screen also includes: if the memory does not store the first device address; under the communication connection in the first link state, traversing the configuration file based on the system-level chip end, obtaining the second device address that can be accessed in the configuration file, writing the second device address into the memory, restarting the system-level chip end, and initializing the screen end based on the second device address.

[0008] In an optional embodiment, the aforementioned method for making the system-level chip compatible with the screen also includes: after a preset time interval, switching the deserializer to a second link state, and establishing a communication connection with the serializer in the second link state when the deserializer is in the second link state.

[0009] In an optional implementation, the aforementioned method for making the system-level chip compatible with the screen further includes: obtaining configuration information of a preset type of deserializer, and writing the configuration information of the preset type of deserializer into the configuration file.

[0010] In a second aspect, the present invention provides a device for compatibility between a system-level chip and a screen, the device comprising: a configuration module, used to configure a deserializer provided on the screen end to be in a first link state; a link module, used to establish a communication connection between the deserializer and a serializer provided on the system-level chip end in the first link state when the deserializer is in the first link state; an initialization module, used to obtain a first device address of the screen end through the communication connection of the system-level chip end in the first link state, the system-level chip end reads a second device address of the existing screen end stored in the memory, and if the first device address is the same as the second device address, the system-level chip end initializes the screen end based on the second device address.

[0011] In a third aspect, the present invention provides a vehicle intelligent cockpit, comprising: a memory and a processor, the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the method for system-level chip and screen compatibility of the above-mentioned first aspect or any corresponding embodiment thereof by executing the computer instructions.

[0012] In a fourth aspect, the present invention provides a vehicle, comprising the aforementioned vehicle intelligent cockpit.

[0013] In a fifth aspect, the present invention provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to enable a computer to execute the method for system-level chip compatibility with a screen according to the first aspect or any corresponding embodiment thereof.

[0014] In a sixth aspect, the present invention provides a computer program product, comprising computer instructions for causing a computer to execute the method for system-on-chip compatibility with a screen according to the first aspect or any corresponding embodiment thereof.

[0015] After the deserializer set on the screen side and the serializer set on the system-level chip side establish a communication connection in a single link state, the serializer traverses the configuration information to obtain the device address of the accessible deserializer. The serializer initializes the screen side with the deserializer based on the obtained device address information of the deserializer, which can solve the problem that some system-level chips do not support mapping the address of the other end, so that the car computer chip can be automatically compatible with multiple screens, reducing the workload of technicians, and there is no need to replace the car computer screen, reducing R&D and after-sales costs, and saving resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the specific embodiments of the present invention or the technical solutions in the related technologies, the drawings required for use in the specific embodiments or the related technical descriptions will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0017] Figure 1 A schematic flow chart of a method for achieving compatibility between a system-level chip and a screen provided by an embodiment of the present invention is shown;

[0018] Figure 2 A schematic flow chart of another method for achieving compatibility between a system-level chip and a screen provided by an embodiment of the present invention is shown;

[0019] Figure 3 A schematic diagram showing the structure of a device for system-on-chip compatibility with a screen provided by an embodiment of the present invention;

[0020] Figure 4 A schematic diagram of the hardware structure of a vehicle intelligent cockpit according to an embodiment of the present invention is shown. DETAILED DESCRIPTION

[0021] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0022] According to an embodiment of the present invention, a method embodiment for system-level chip compatibility with a screen is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0023] In this embodiment, a method for making a system-level chip compatible with a screen is provided, which can be used in a smart cockpit or a system provided with a serializer and a deserializer. Figure 1 A schematic diagram of a process for making a system-level chip compatible with a screen provided by an embodiment of the present invention is shown. Figure 1 As shown, the process includes the following steps:

[0024] Step S101: configure a deserializer disposed at a screen end to be in a first link state.

[0025] Serializer and deserializer is a high-speed serial data transmission technology that can transfer data from one location in the car to another, such as transferring the contents of the main control chip to the display screen at the driver's seat for display. The serializer splits multiple parallel data signals into smaller data blocks and transmits them in serial mode. After receiving the aforementioned data blocks, the deserializer reassembles the data blocks into complete parallel data. The setting of the serializer and deserializer can reduce wiring conflicts and has the advantages of strong noise and interference resistance.

[0026] In this step, the screen connected to the smart cockpit is equipped with a deserializer, which needs to communicate with the host end with Android and embedded operating system (qnx). After the deserializer set on the screen end is powered on, the initialization parameters of the vehicle screen are initialized in the early stage, and the link type is initialized so that the screen end and the system-level chip end set on the host can communicate. The deserializer is configured to be in the first link state, and the first link state is a single link state, that is, the serializer and the deserializer are connected using a link (lane).

[0027] Step S102, when the deserializer is in the first link state, establish a communication connection between the deserializer and the serializer provided at the system-on-chip end in the first link state, and read the first device address of the existing screen end stored in the memory through the system-on-chip end.

[0028] In this step, the serializer set at the system-level chip end is powered on, the serializer is in the first link state, and the serializer reads the register of the deserializer. If it can be read, the serializer can establish a communication connection with the deserializer in the first link state, that is, a single link connection. In this way, the method can be adapted to chips with both single-link and dual-link modes on the market, and can ensure that the serializer and the deserializer establish a communication connection during actual application.

[0029] Step S103, under the communication connection in the first link state, traverse the configuration file based on the system-level chip side, the configuration file includes at least one device address of the deserializer, obtain the second device address that can be accessed in the configuration file, if the first device address is the same as the second device address, initialize the screen side based on the first device address.

[0030] In this step, the serializer set at the system-level chip end can access the deserializer at the screen end based on the communication connection in the first link state, so that the serialization and deserialization chips at the screen end and the host end can perform basic communication. A configuration file can be set in the memory, and the information of the deserializer of the screen that needs to be compatible is written into the configuration file. The deserializer information may include the device address of the deserializer and the version information of the deserializer. The system-level chip end traverses the configuration file. If there is an accessible device address of the target deserializer in the configuration file, the device address of the target deserializer is the device address of the currently used screen.

[0031] If the first device address and the second device address obtained by the system-level chip are the same, the vehicle screen is initialized based on the read first device address. The system-level chip is a control chip that can run the vehicle operating system, which can be a Qualcomm 8155 chip, 8295 chip, Maxim or Texas Instruments chip. The deserializer chip can be a Maxim or Texas Instruments chip.

[0032] The method for making the system chip compatible with the screen provided in this embodiment is that after the deserializer arranged on the screen end and the serializer arranged on the system chip end establish a communication connection in a single link state, the serializer traverses the configuration information to obtain the device address of the accessible deserializer, and the serializer initializes the screen end provided with the deserializer based on the obtained device address information of the deserializer, which can solve the problem that some system chips do not support mapping the address of the opposite end, so that the vehicle computer chip can be automatically compatible with multiple screens, reducing the workload of technicians, and there is no need to replace the vehicle computer screen, thereby reducing R&D and after-sales costs and saving resources.

[0033] In some optional implementations, the aforementioned method for making the system-level chip compatible with the screen further includes: if the first device address is different from the second device address, writing the second device address into the memory, restarting the system-level chip end, and initializing the screen end based on the second device address.

[0034] In this embodiment, the first device address read by the system-level chip from the memory is different from the second device address stored in the configuration file, which means that the screen connected to the system-level chip is not the screen device stored in the memory. The information of the currently connected screen device can be written into the memory and the smart cockpit system can be restarted.

[0035] In this way, when the screen of the car computer is replaced, the system-level chip can correctly identify and access the replaced screen, thereby achieving automatic compatibility between the car computer and the replaced screen device.

[0036] In some optional embodiments, the aforementioned method for making the system-level chip compatible with the screen also includes: if the first device address is not stored in the memory, under the communication connection in the first link state, traversing the configuration file based on the system-level chip side, obtaining the second device address that can be accessed in the configuration file, writing the second device address into the memory, restarting the system-level chip side, and initializing the screen side based on the second device address.

[0037] In this step, for the situation where the first device address is not stored in the memory, it may be the first time that the vehicle computer starts the system, and no screen information is stored in the system memory. The system memory is empty. A single link communication connection can be established between the vehicle computer system-level chip and the screen. By traversing the address content of the configuration file, the second device address that can be accessed in the configuration file is obtained, the second device address is written into the memory, and the system is restarted to initialize the screen based on the second device address.

[0038] In this way, when the vehicle configuration is initialized before leaving the factory, automatic compatibility between the vehicle system-level chip and the vehicle screen can be achieved for various types of screens in various types of vehicles, saving a lot of resources.

[0039] In some optional embodiments, the aforementioned method for making the system-level chip compatible with the screen also includes: after a preset time interval, switching the deserializer to a second link state, and establishing a communication connection with the serializer in the second link state when the deserializer is in the second link state.

[0040] In this embodiment, after a preset time interval, both the deserializer and the serializer switch to the second link state, and the second link state is a dual-link communication connection, that is, the serializer and the deserializer are connected through two links, which can provide higher data transmission bandwidth and efficiency. Among them, the preset time interval can be set to 500 milliseconds, and those skilled in the art can also determine the preset time interval according to actual needs.

[0041] After the serializer and the deserializer establish a communication connection in the second link state, the dual link state can be monitored to ensure normal transmission of parallel data between the serializer and the deserializer.

[0042] In this way, after the car system-level chip initializes the screen, the serializer set in the system-level chip and the deserializer set in the screen switch to dual-link mode, which can achieve the matching of link modes between the serializer and the deserializer, and can also meet the needs of high-speed and large data volume transmission application scenarios, such as the transmission needs of in-vehicle high-definition video.

[0043] In some optional embodiments, the aforementioned method for making the system-level chip compatible with the screen also includes: a configuration file is stored in the memory, and the configuration file includes: a device address of at least one deserializer; the system-level chip side traverses the configuration file, and if there is an accessible device address of the target deserializer in the configuration file, the device address of the target deserializer is the second device address.

[0044] In this implementation, a configuration file may be set in the memory, and the information of the deserializer of the screen that needs to be compatible may be written into the configuration file. The deserializer information may include the device address of the deserializer and the version information of the deserializer. The system-level chip traverses the configuration file. If the device address of the target deserializer that can be accessed exists in the configuration file, the device address of the target deserializer is the device address of the currently used screen.

[0045] In this way, by storing the device address of the deserializer in the memory, the problem that some system-level chips do not support mapping the address of the other end can be solved. At the same time, the system-level chip set in the car computer can be adapted to a variety of different known types of screen equipment.

[0046] In some optional implementations, for a screen end having a preset type deserializer that is not stored in the configuration information, the aforementioned method for making the system-level chip compatible with the screen further includes: obtaining the configuration information of the preset type deserializer, and writing the configuration information of the preset type deserializer into the configuration file. In this implementation, the device addresses in the configuration file are not accessible, the configuration information of the preset type deserializer can be obtained, and the configuration information of the preset type deserializer can be written into the configuration file.

[0047] In this way, the system-level chip can be compatible with screen devices that are not stored in the configuration information, thereby enhancing the scalability of the method.

[0048] Another flowchart of a method for making a system-on-chip compatible with a screen is also provided in an embodiment of the present invention. Figure 2 FIG. 2 is a flow chart showing another method for making a system-level chip compatible with a screen provided by an embodiment of the present invention. Figure 2 As shown, the aforementioned another method for making the system-level chip compatible with the screen also includes:

[0049] Step S201, the smart cockpit system is started;

[0050] Step S202, power-on stage, the serializer of the system-level chip end is powered on, and the screen end is powered on. After the serializer and the deserializer are linked, the serializer reads the first device address in the memory, and the serializer also reads the configuration file stored in the memory, the configuration file stores multiple initial device addresses representing the screen address, and traverses the configuration file. If there is an accessible target device address in the configuration file, the target device address is the device address of the current screen, that is, the second device address;

[0051] Step S203, determining whether the first device address is the same as the second device address, if the first device address is the same as the second device address, proceeding to step S204; if the first device address is different from the second device address, the current screen is not the screen device stored in the memory, proceeding to step S205;

[0052] Step S204, initializing the current screen according to the first device address. After the current screen is initialized, specific parameters of the current screen are transmitted to the serializer. The specific parameters of the current screen include line and field synchronization signals or screen resolution information. After the current screen is initialized, video data can be transmitted.

[0053] Step S205, writing the second device address into the memory, and proceeding to step S201 to restart the smart cockpit system;

[0054] Step S206, monitoring the link status between the serializer and the deserializer, to ensure the normal connection of the data path.

[0055] In some optional implementations, a plurality of screen terminals may be provided in the smart cockpit system, and each screen terminal may be automatically compatible with the system-level chip based on the present method.

[0056] In this embodiment, a device for system-level chip compatibility with a screen is also provided, which is used to implement the above embodiments and preferred implementations, and will not be repeated for what has been described. As used below, the term "module" can implement a combination of software and / or hardware for a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0057] This embodiment provides a device for making a system-on-chip compatible with a screen. Figure 3 FIG. 1 shows a schematic diagram of a structure of a device for system-level chip and screen compatibility provided by an embodiment of the present invention, such as Figure 3 As shown, including:

[0058] The configuration module 301 is used to configure the deserializer provided at the screen end to be in a first link state.

[0059] The reading module 302 is used to establish a communication connection between the deserializer and the serializer set at the system-level chip end in the first link state when the deserializer is in the first link state, and read the first device address of the existing screen end stored in the memory through the system-level chip end.

[0060] The initialization module 303 is used to traverse the configuration file based on the system-level chip side under the communication connection in the first link state, the configuration file includes the device address of at least one deserializer, obtain the second device address that can be accessed in the configuration file, and if the first device address is the same as the second device address, initialize the screen side based on the first device address.

[0061] In some optional embodiments, the aforementioned device for system-level chip compatibility with the screen also includes: a first module, used to write the second device address into the memory, restart the system-level chip end, and initialize the screen end based on the second device address if the first device address is different from the second device address.

[0062] In some optional embodiments, the aforementioned device for making the system-level chip compatible with the screen also includes: a second module, which is used to, if the first device address is not stored in the memory; under the communication connection under the first link state, traverse the configuration file based on the system-level chip side, obtain the second device address that can be accessed in the configuration file, write the second device address into the memory, restart the system-level chip side, and initialize the screen side based on the second device address.

[0063] In some optional embodiments, the aforementioned device for making the system-level chip compatible with the screen further includes: a third module, which is used to switch the deserializer to the second link state after a preset time interval, and establish a communication connection with the serializer in the second link state when the deserializer is in the second link state.

[0064] In some optional embodiments, the aforementioned device for making the system-level chip compatible with the screen also includes: a fourth module, which is used to store a configuration file in the memory, and the configuration file includes: a device address of at least one deserializer; the system-level chip side traverses the configuration file, and if there is an accessible device address of the target deserializer in the configuration file, the device address of the target deserializer is the second device address.

[0065] In some optional implementations, the aforementioned device for making the system-level chip compatible with the screen further includes: a fifth module, used to obtain configuration information of a preset type deserializer, and write the configuration information of the preset type deserializer into a configuration file.

[0066] The further functional description of each of the above modules and units is the same as that of the above corresponding embodiments and will not be repeated here.

[0067] The device for system-level chip compatibility with the screen in this embodiment is presented in the form of a functional unit, where the unit refers to an application specific integrated circuit (ASIC) circuit, a processor and memory that executes one or more software or fixed programs, and / or other devices that can provide the above functions.

[0068] An embodiment of the present invention provides a device for compatibility between a system-level chip and a screen. After a deserializer arranged on the screen end and a serializer arranged on the system-level chip end establish a communication connection in a single link state, the serializer obtains the device address information of the deserializer. The serializer initializes the screen end provided with the deserializer based on the obtained device address information of the deserializer, so that the vehicle-computer chip can be automatically compatible with various screens, reducing the workload of technicians, and there is no need to replace the vehicle-computer screen, thereby reducing R&D and after-sales costs and saving resources.

[0069] The embodiment of the present invention also provides a vehicle intelligent cockpit, having the above Figure 3 The device shown is used for system-level chip and screen compatibility.

[0070] See also Figure 4 , Figure 4 is a structural schematic diagram of a vehicle intelligent cockpit provided by an optional embodiment of the present invention, such as Figure 4As shown, the vehicle intelligent cockpit includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. The various components are connected to each other using different buses for communication, and can be installed on a common motherboard or installed in other ways as needed. The processor can process instructions executed in a computer device, including instructions stored in or on a memory to display graphical information of a graphical user interface on an external input / output device (such as a display device coupled to an interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple computer devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Figure 4 A processor 10 is taken as an example.

[0071] The processor 10 may be a central processing unit, a network processor or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be a dedicated integrated circuit, a programmable logic device or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic or any combination thereof.

[0072] The aforementioned memory 20 stores instructions executable by at least one processor 10, so that the aforementioned at least one processor 10 executes the method shown in the above embodiment.

[0073] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the computer device, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely arranged relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0074] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive; the memory 20 may also include a combination of the above types of memory.

[0075] The computer device also includes an input device 30 and an output device 40. The processor 10, the memory 20, the input device 30 and the output device 40 may be connected via a bus or other means. Figure 4 The example of connecting through bus is taken in the following.

[0076] The input device 30 can receive input digital or character information, and generate key signal input related to the user settings and function control of the computer device, such as a touch screen, a keypad, a mouse, a track pad, a touch pad, an indicator rod, one or more mouse buttons, a trackball, a joystick, etc. The output device 40 may include a display device, an auxiliary lighting device (such as a light emitting diode) and a tactile feedback device (such as a vibration motor), etc. The above-mentioned display device includes but is not limited to a liquid crystal display, a light emitting diode, a display and a plasma display. In some optional embodiments, the display device can be a touch screen.

[0077] An embodiment of the present invention further provides a vehicle, comprising the aforementioned vehicle intelligent cockpit.

[0078] The embodiment of the present invention also provides a computer-readable storage medium. The method according to the embodiment of the present invention can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium through a network download, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state hard disk, etc.; further, the storage medium can also include a combination of the above types of memories. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor, or hardware, the method shown in the above embodiment is implemented.

[0079] A part of the present invention may be applied as a computer program product, such as a computer program instruction, which, when executed by a computer, can call or provide the method and / or technical solution according to the present invention through the operation of the computer. Those skilled in the art should understand that the existence of the computer program instruction in a computer-readable medium includes, but is not limited to, a source file, an executable file, an installation package file, etc., and accordingly, the way in which the computer program instruction is executed by the computer includes, but is not limited to: the computer directly executes the instruction, or the computer compiles the instruction and then executes the corresponding compiled program, or the computer reads and executes the instruction, or the computer reads and installs the instruction and then executes the corresponding installed program. Here, the computer-readable medium may be any available computer-readable storage medium or communication medium accessible to the computer.

[0080] Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A method for making a system-level chip compatible with a screen, characterized in that: The method comprises: Configuring the deserializer disposed at the screen end to be in a first link state; When the deserializer is in the first link state, the deserializer is connected to a serializer provided at a system-on-chip end in the first link state, and a first device address of an existing screen end stored in a memory is read through the system-on-chip end; Under the communication connection in the first link state, based on the system-level chip side traversal configuration file, the configuration file includes at least one device address of a deserializer, obtain the second device address that can be accessed in the configuration file, if the first device address is the same as the second device address, initialize the screen side based on the first device address.

2. The method according to claim 1, characterized in that The method further comprises: If the first device address is different from the second device address, the second device address is written into the memory, the system-on-chip end is restarted, and the screen end is initialized based on the second device address.

3. The method according to claim 1 or 2, characterized in that: The method further comprises: If the memory does not store the first device address; Under the communication connection in the first link state, the configuration file is traversed based on the system-on-chip side, a second device address that can be accessed in the configuration file is obtained, the second device address is written into the memory, the system-on-chip side is restarted, and the screen side is initialized based on the second device address.

4. The method according to claim 1, characterized in that: The method further comprises: After a preset time interval, the deserializer is switched to a second link state, and when the deserializer is in the second link state, a communication connection in the second link state is established with the serializer.

5. The method according to claim 1, characterized in that: The method further comprises: The configuration information of the preset type deserializer is obtained, and the configuration information of the preset type deserializer is written into the configuration file.

6. A device for system-level chip and screen compatibility, characterized in that: The device comprises: A configuration module, used for configuring a deserializer provided at the screen end to be in a first link state; a reading module, configured to establish a communication connection between the deserializer and a serializer provided at a system-on-chip end in the first link state when the deserializer is in the first link state, and read a first device address of an existing screen end stored in a memory through the system-on-chip end; An initialization module is used to traverse a configuration file based on the system-level chip side under the communication connection in the first link state, the configuration file includes a device address of at least one deserializer, obtain a second device address that can be accessed in the configuration file, and if the first device address is the same as the second device address, initialize the screen side based on the first device address.

7. A vehicle intelligent cockpit, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the method for system-level chip compatibility with a screen as described in any one of claims 1 to 5 by executing the computer instructions.

8. A vehicle, characterized in that: The vehicle includes the vehicle intelligent cockpit as described in claim 7.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the method for making a system-on-chip compatible with a screen according to any one of claims 1 to 5.

10. A computer program product, characterized in that The method comprises computer instructions for causing a computer to execute the method for making a system-level chip compatible with a screen according to any one of claims 1 to 5.

Images