CN112256350A - Vehicle-mounted system starting method and device, vehicle-mounted device, vehicle and storage medium - Google Patents
Vehicle-mounted system starting method and device, vehicle-mounted device, vehicle and storage medium Download PDFInfo
- Publication number
- CN112256350A CN112256350A CN202011159317.1A CN202011159317A CN112256350A CN 112256350 A CN112256350 A CN 112256350A CN 202011159317 A CN202011159317 A CN 202011159317A CN 112256350 A CN112256350 A CN 112256350A
- Authority
- CN
- China
- Prior art keywords
- vehicle
- core
- slave
- slave core
- started
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F15/00—Digital computers in general; Data processing equipment in general
- G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
- G06F15/163—Interprocessor communication
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides a vehicle-mounted system starting method, which comprises a U-Boot stage and a kernel stage; the U-Boot stage comprises the following steps: determining a slave core to be started; executing a first preprocessing flow according to the slave core to be started; acquiring a first address of the slave core and updating the first address into a first page table of the U-Boot; initiating a boot to perform a boot of the master core and an early boot of at least one of the plurality of slave cores; the kernel phase includes: updating a first address of an early-booted slave core into a second page table of the kernel; executing a second preprocessing flow; performing addressing based on the second page table; establishing a communication connection; performing a late attach of the early-booted slave core to establish communication between the slave core and the master core. By the method, the starting time can be reduced, and part of the preset vehicle-mounted functions are performed in advance. The invention also provides a vehicle-mounted system starting device, a vehicle-mounted device, a vehicle and a readable storage medium.
Description
Technical Field
The invention relates to the technical field of vehicle-mounted system starting, in particular to a linux-based vehicle-mounted system starting method and device, a vehicle-mounted device, a vehicle and a storage medium.
Background
The Linux operating system has the characteristics of free openness, strong kernel vehicle-mounted functions, low requirement on hardware resources, multi-platform support, more developers and the like, so that the Linux operating system is widely applied to various fields, particularly the vehicle-mounted control field.
In order to improve the operation efficiency of a vehicle-mounted system, a multi-core scheme is usually adopted, and other cores are often used for realizing auxiliary vehicle-mounted functions such as display of the vehicle-mounted system, when the vehicle-mounted system is started, a kernel (operating system kernel) is mostly guided to be started by uboot (Universal Boot Loader, an open source code item following a GPL term), and then other cores are started, however, in the process of realizing the present invention, the inventor finds that at least the following problems exist in the prior art: because other cores need to start loading and starting after the completion of the starting of the inner core, the multi-core scheme causes the starting time of the vehicle-mounted system to be longer, and the user experience is influenced.
Disclosure of Invention
In view of the above, it is necessary to provide an in-vehicle system starting method, an in-vehicle system starting device, an in-vehicle device, a vehicle and a readable storage medium to solve the above problems.
The embodiment of the application provides a linux-based vehicle-mounted system starting method, wherein the vehicle-mounted system is applied to a vehicle and comprises a main core and a plurality of auxiliary cores, and the method comprises a U-Boot stage and a kernel stage;
the U-Boot stage comprises:
determining a slave core to be started;
executing a first preprocessing flow according to the slave core to be started;
acquiring a first address of the slave core and updating the first address into a first page table;
initiating a boot to perform a boot of the master core and an early boot of at least one of the slave cores;
the kernel phase includes:
updating a first address of the slave core into a second page table;
executing a second preprocessing flow;
performing addressing based on the second page table;
establishing a communication connection;
performing a late attach of an early booted slave core to establish communication between the slave core and the master core.
Therefore, the plurality of slave cores to be started are started in the phase from U-Boot in advance, so that the corresponding vehicle-mounted functions of the plurality of slave cores take effect in advance, and the communication between the plurality of slave cores and the kernel is established after the plurality of slave cores are started. By the method, the starting time of the plurality of slave cores can be integrally advanced, and the plurality of slave cores and the kernel are synchronously started, so that the starting time is reduced, and the realization of the vehicle-mounted function preset by a user is advanced.
In some embodiments, the determining the slave core to be started specifically includes:
acquiring a control instruction input by a user;
matching the control instruction with the corresponding vehicle-mounted function to determine the vehicle-mounted function selected by the user;
and matching the vehicle-mounted function with a plurality of slave cores to determine the slave core executing the vehicle-mounted function.
In this way, the slave core to be started is determined according to the control instruction input by the user, and further, the slave core started each time the vehicle-mounted system is started can be determined according to the user requirement.
In some embodiments, executing the first preprocessing flow according to the slave core to be started specifically includes:
acquiring a second address and sending a control command to place the compressed file of the slave core to be started at the second address;
and distributing corresponding storage space according to the compressed file, wherein the storage space is used for storing the compressed file and the decompressed file.
Therefore, the compressed file of the slave core is placed in the address of the U-Boot, so that the U-Boot can be conveniently loaded, and meanwhile, a corresponding storage space needs to be allocated, so that the compressed file and the decompressed file of the compressed file can be conveniently stored.
In some embodiments, the in-vehicle system includes a remote communication module for establishing communication with the early-booted slave core, the method further comprising, prior to establishing a communication connection:
setting the telecommunications module to a built-in mode.
The mode of the remote communication module is changed, so that the kernel as a master core establishes communication with the plurality of slave cores in advance.
In some embodiments, the executing the second pre-processing flow further comprises:
determining a started slave core;
closing the initialized configuration of the started slave core;
closing the reset remote process of the started slave core;
and closing the timer vehicle-mounted function of the started slave core.
Thus, since a plurality of slave cores are started in advance, the later attachment of the slave cores is prevented from being influenced by the configuration.
In some embodiments, before initiating the boot to perform the boot of the master core and the early boot of the at least one slave core, the method further comprises:
judging whether the files of the slave core are compressed or not;
if not, decompressing the file, and loading the decompressed file into an internal memory;
and if so, loading the decompressed file into the memory.
By judging whether the files of the slave core are compressed before the initialization starting, the decompressed files are prevented from being decompressed again, and the starting time is reduced.
The embodiment of the application simultaneously provides a vehicle-mounted system starting device, which is applied to a vehicle, wherein the vehicle-mounted system comprises a main core and a plurality of slave cores, and the vehicle-mounted system starting device comprises;
the determining module is used for determining a slave core to be started;
the execution module is used for executing a first preprocessing flow according to the slave core to be started;
the updating module is used for acquiring a first address of the slave core and updating the first address into a first page table;
a boot module to initiate a boot to perform a boot of the master core and an early boot of at least one of the slave cores;
further, the update module is further configured to update the first address of the slave core into a second page table;
the execution module is also used for executing a second preprocessing flow;
an addressing module to perform addressing based on the second page table;
the communication module is used for establishing communication connection;
the execution module is further to perform a late attach of the slave core that is early booted to establish communication between the slave core and the master core.
Therefore, the plurality of slave cores to be started are started in the phase from U-Boot in advance, so that the corresponding vehicle-mounted functions of the plurality of slave cores take effect in advance, and the communication between the plurality of slave cores and the kernel is established after the plurality of slave cores are started. Through the device, the starting time of the plurality of slave cores can be integrally advanced, and the plurality of slave cores and the kernel are synchronously started, so that the starting time is reduced, and the realization of the vehicle-mounted function preset by a user is advanced.
The application also provides an on-board device, which comprises a memory, a processor and a computer program stored in the memory and capable of running on the processor, wherein the processor executes the computer program to realize the steps of the on-board system starting method according to the embodiment.
The vehicle-mounted device starts a plurality of to-be-started slave cores to the U-Boot stage in advance, so that the vehicle-mounted functions corresponding to the slave cores take effect in advance, and the communication between the slave cores and the kernel is established after the slave cores are started in the later period of the slave cores. The starting time of the plurality of slave cores is integrally advanced, and the plurality of slave cores and the kernel are synchronously started, so that the starting time is reduced, and the realization of the vehicle-mounted function preset by a user is advanced.
The application simultaneously provides a vehicle, includes above-mentioned embodiment the car-mounted device.
The vehicle-mounted device of the vehicle starts a plurality of slave cores to be started to a U-Boot stage in advance, so that the vehicle-mounted functions corresponding to the slave cores are started in advance, and the communication between the slave cores and the kernel is established after the slave cores are started. The starting time of the plurality of slave cores is integrally advanced, and the plurality of slave cores and the kernel are synchronously started, so that the starting time is reduced, and the realization of the vehicle-mounted function preset by a user is advanced.
The present application also provides a computer-readable storage medium, which stores a computer program, and the computer program, when executed by a processor, implements the steps of the vehicle-mounted system starting method according to the above embodiment.
Therefore, the vehicle-mounted system starting method can be realized by the computer program stored in the computer readable storage medium, so that the starting time is reduced, and the vehicle-mounted functions preset by a user are realized in advance.
Drawings
Fig. 1 is a schematic flowchart of a first method for starting an on-board system according to a first embodiment of the present application.
Fig. 2 is a schematic flowchart of a second method for starting an on-board system according to a first embodiment of the present application.
Fig. 3 is a schematic structural diagram of an on-vehicle system starting apparatus according to an embodiment of the present application.
Fig. 4 is a schematic structural diagram of an in-vehicle device according to an embodiment of the present application.
Description of the main elements
In-vehicle system starting apparatus 100
Determining module 101
Judging module 105
Addressing module 108
Vehicle-mounted device 10
Detailed Description
In order that the objects, features and advantages of the present application can be more clearly understood, the present application will be described in detail below with reference to the accompanying drawings and specific embodiments. It should be noted that the embodiments and features of the embodiments of the present application may be combined with each other without conflict. In the following description, numerous specific details are set forth to provide a thorough understanding of the present application, and the described embodiments are merely a subset of the embodiments of the present application and are not intended to be a complete embodiment.
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein in the description of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application.
Referring to fig. 1 and fig. 2, fig. 1 and fig. 2 are schematic flow charts of a vehicle-mounted system starting method according to an embodiment of the present application. The order of the steps in the flow chart may be changed and some steps may be omitted according to different needs. For convenience of explanation, only portions related to the embodiments of the present application are shown.
The vehicle-mounted system starting method is applied to the vehicle. The vehicle-mounted system of the vehicle is realized through multiple cores and comprises a main core and a plurality of slave cores, wherein the main core is a core for independently realizing functions, the slave cores are cores for realizing the functions based on communication connection, and the slave cores are mainly used for realizing auxiliary functions of the vehicle, such as screen display and annular display, and are used for helping a user to know vehicle conditions or vehicle surrounding side environment conditions when the vehicle is started so as to improve the experience of the user in using the vehicle. The starting method of the vehicle-mounted system comprises the following steps.
The vehicle-mounted system starting method comprises a U-Boot stage and a kernel stage, wherein the U-Boot is a Boot loader mainly used for an embedded system, and the U-Boot stage is mainly used for starting a master Boot program after the vehicle-mounted system is started. It is understood that kernel is the main core of the vehicle-mounted system.
Further, referring to fig. 1 again, the U-Boot stage mainly includes the following steps:
step S101: and determining the slave core to be started.
It can be understood that the plurality of slave cores can realize different vehicle-mounted functions according to actual requirements, such as a vehicle-mounted display function of a vehicle-mounted system and a vehicle-mounted all-around vehicle-mounted function, so that a user can acquire the starting entrance of the vehicle-mounted system and the surrounding environment condition after the vehicle is started in real time. In this way, the slave core to be started can be selected according to requirements.
In an embodiment, step S101 specifically includes:
and acquiring the vehicle-mounted functions selected by the user, wherein the vehicle-mounted functions comprise vehicle-mounted functions configured by system defaults and vehicle-mounted functions selected by the user actively, for example, the vehicle-mounted system is started to automatically check the health condition of the vehicle, and the vehicle endurance mileage and fuel consumption condition of the vehicle are displayed, or prompt music or voice is played when the vehicle-mounted system is started according to the selection of the user.
And matching the vehicle-mounted function with a plurality of slave cores to determine the slave core to be started.
And determining the corresponding slave core to be started according to the vehicle-mounted function used for pre-configuration.
Further, the vehicle-mounted function selected by the user can be determined by acquiring a control instruction input by the user through an operation control device when the vehicle-mounted system is started and matching the control instruction with the corresponding vehicle-mounted function; and matching the vehicle-mounted function with a plurality of slave cores to determine the slave core executing the vehicle-mounted function. That is, the slave core to be started can be started at the vehicle-mounted system and selected by user input.
Step S102: and executing a first preprocessing flow according to the slave core to be started.
Specifically, step S102 specifically includes:
acquiring a second address of the U-Boot and sending a control command to place a compressed file of the slave core at the second address;
and distributing corresponding storage space according to the compressed file, wherein the storage space is used for storing the compressed file and the decompressed file of the compressed file.
Specifically, the compressed file of the slave core is placed in a partition or a storage file consistent with the U-Boot, so that the U-Boot can read the file and allocate a storage space for the compressed file.
In this embodiment, the compressed file is a file in an lzop compression format.
Step S103: and acquiring a first address of the slave core and updating the first address into a first page table.
Thus, the U-Boot is convenient to load the firmware of the slave core to be started according to the address in the first page table.
Step S104: initiating a boot to perform a boot of the master core and an early boot of at least one slave core.
In this way, the early stage guide of the slave core is executed in advance in the U-Boot stage, so that the vehicle-mounted function selected by the user and corresponding to the slave core is realized in advance.
In an embodiment, step S104 further includes:
judging whether the files of the slave core are compressed or not;
if not, decompressing the file, and loading the decompressed file into an internal memory;
and if so, loading the decompressed file into the memory.
In order to reduce the occupation of the storage space, most of the Linux kernels and files are compressed, and the Linux kernels and files loaded into the internal memory cannot be compressed, so that the compressed Linux kernels and files need to be decompressed and then loaded into the internal memory.
Further, the kernel is a Linux operating system and is responsible for program scheduling and management of various hardware resources, the kernel stage is mainly used for starting the kernel and establishing communication between the kernel and the slave core, please refer to fig. 2 again, and the kernel stage mainly includes the following steps:
step S201: the EDMA vehicle-mounted function of the main core configuration is closed.
Wherein, EMMA (enhanced direct memory access) is enhanced direct memory access for fast data exchange. Because the slave core executes the EDMA vehicle-mounted function in advance in the U-Boot stage, the master core is closed to configure the EDMA vehicle-mounted function, and repeated execution is avoided.
It is understood that in another embodiment, the EDMA in-vehicle function may be adaptively turned off based on the start-up condition of the slave core, and step S201 may be omitted.
Step S202: updating the first address of the early-guided slave core into the kernel second page table.
Specifically, the address of the slave core is updated into the second page table of the kernel to facilitate addressing by the kernel.
Step S203: and executing a second preprocessing flow.
Specifically, the kernel is configured in advance so as to realize the kernel as communication between the master core and the plurality of slave cores.
In an embodiment, step S203 specifically includes:
determining a started slave core;
closing the initialized configuration of the started slave core;
closing the reset remote process of the started slave core;
and closing the timer vehicle-mounted function of the started slave core.
In particular, since multiple slave cores are already running, the above on-board function reset may result in a late attachment failure of the slave cores.
Step S204: performing addressing based on the second page table.
In particular, addressing of the slave core is performed based on the address of the slave core in the second page table.
Step S205: a communication connection is established.
Specifically, the necessary configuration of the communication connection of the master core is performed.
Further, the in-vehicle system has a remote communication module therein for establishing communication with the plurality of slave cores, and step S205 further includes:
the telecommunications module is set to a built-in mode. Therefore, remote communication is started in advance, communication is established with a plurality of slave cores earlier, and starting time is optimized.
Step S206: performing a late attach of an early booted slave core to establish communication between the slave core and the master core.
Specifically, the kernel acquires the address of the slave core through the second page table and performs addressing to establish communication between the slave core and the kernel, and the early starting of the plurality of slave cores is completed.
Therefore, the plurality of slave cores to be started are started in the phase from U-Boot in advance, so that the corresponding vehicle-mounted functions of the plurality of slave cores take effect in advance, and the communication between the plurality of slave cores and the kernel is established after the plurality of slave cores are started. By the method, the starting time of the plurality of slave cores can be integrally advanced, and the plurality of slave cores and the kernel are synchronously started, so that the starting time is reduced, and the advance realization of the vehicle-mounted function preset by a user is realized.
The sequence number of each step in the foregoing embodiments does not mean the execution sequence, and the execution sequence of each process should be determined by the vehicle-mounted function and the internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.
Fig. 1 and 2 describe in detail a vehicle-mounted system starting method of the present application, by which a vehicle-mounted function preset by a user can be implemented in advance. The functional modules and the hardware device architecture for implementing the vehicle-mounted system starting device are described below with reference to fig. 3 and 4. It is to be understood that the embodiments are illustrative only and that the scope of the claims is not limited to this configuration.
Fig. 3 is a functional block diagram of an in-vehicle system starting apparatus according to an embodiment of the present application.
In some embodiments, the in-vehicle system starting apparatus 100 may include a plurality of functional modules composed of program code segments. The program codes of the respective program segments in the in-vehicle system starting apparatus 100 may be stored in the memory of the in-vehicle apparatus 10 and executed by at least one processor in the in-vehicle apparatus 10 to implement the in-vehicle system starting function.
Referring to fig. 3, in the present embodiment, the vehicle-mounted system starting apparatus 100 may be divided into a plurality of functional modules according to the functions performed by the apparatus, and the functional modules are used for executing the steps in the corresponding embodiments of fig. 1 and 2 to realize the function of starting the vehicle-mounted system. In the present embodiment, the functional blocks of the in-vehicle system starting apparatus 100 include: the system comprises a determining module 101, an executing module 102, an updating module 103, a starting module 104, a judging module 105, a compressing module 106, a loading module 107, an addressing module 108 and a communication module 109.
A determining module 101, configured to determine a slave core to be started;
an execution module 102, configured to execute a first preprocessing flow according to the slave core to be started;
an update module 103, configured to obtain a first address of an early-booted slave core and update the first address into a first page table;
a boot module 104 configured to initiate a boot to perform a boot of the master core and an early boot of at least one of the plurality of slave cores;
further, the update module 103 is further configured to update the first address of the slave core into the second page table of the kernel;
the execution module 102 is further configured to execute a second preprocessing flow.
Specifically, the second preprocessing flow is a processing measure performed before the communication is established between the master core and the slave core, so as to avoid affecting the late attachment flow of the slave core.
An addressing module 108 for performing addressing based on the second page table.
In particular, addressing of the slave core is performed based on the address of the slave core in the second page table.
And a communication module 109 for establishing a communication connection.
Specifically, the necessary configuration of the communication connection of the master core is performed.
The execution module 102 is further configured to perform a late attach of the slave core to establish communication between the slave core and the master core.
Therefore, the plurality of slave cores to be started are started in the phase from U-Boot in advance, so that the corresponding vehicle-mounted functions of the plurality of slave cores take effect in advance, and the communication between the plurality of slave cores and the kernel is established after the plurality of slave cores are started. Through the device, the starting time of the plurality of slave cores can be integrally advanced, and the plurality of slave cores and the kernel are synchronously started, so that the starting time is reduced, and the realization of the vehicle-mounted function preset by a user is advanced.
Further, the determining module 101 includes:
and the first sub-acquisition module is used for acquiring the control instruction input by the user. The control command can be command information input by a user through a key or a touch screen.
The sub-matching module is used for matching the control instruction with the corresponding vehicle-mounted function so as to determine the vehicle-mounted function selected by the user;
the sub-matching module is further used for matching the vehicle-mounted function with a plurality of slave cores so as to determine the slave core executing the vehicle-mounted function.
Further, the executing module 102 includes:
and the second sub-obtaining module is used for obtaining a second address of the U-Boot.
The sub-control module is used for sending a control command to place the compressed file of the slave core at the second address;
and the sub-distribution module is used for distributing corresponding storage space according to the compressed file, and the storage space is used for storing the compressed file and the decompressed file of the compressed file.
Further, the kernel includes a remote communication module for establishing communication with the slave core, and the execution module 102 further includes:
and the sub-setting module is used for setting the remote communication module to be in a built-in mode.
Further, the executing the second preprocessing flow further includes:
the sub-determination module is used for determining the started slave core;
the sub-closing module is used for closing the initialized configuration of the started slave core and closing the reset remote process of the started slave core; and closing the timer vehicle-mounted function of the started slave core.
The functional modules of the vehicle-mounted system starting device 100 further include:
a judging module 105, configured to judge whether a file of the slave core is compressed;
if not, the compression module 106 is configured to decompress the file, and the loading module 107 sends a loading instruction to load the decompressed file into the memory;
if yes, the loading module 107 sends a loading instruction to load the decompressed file into the memory.
Fig. 4 is a schematic structural diagram of an in-vehicle device according to an embodiment of the present application. The vehicle-mounted device 10 comprises a memory 11, a processor 12 and a communication bus 13, wherein the memory 11 is connected with the processor 12 in a communication mode through the communication bus 13.
The in-vehicle device 10 further comprises a computer program 14, such as an in-vehicle system-initiated program, stored in the memory 11 and executable on the processor 12.
The steps of the method for starting the vehicle-mounted system in the embodiment of the method are realized when the computer program 14 is executed by the processor 12. Alternatively, the processor 12 executes the computer program 14 to realize the functions of the modules/units in the system embodiment.
Illustratively, the computer program 14 may be partitioned into one or more modules/units, which are stored in the memory 11 and executed by the processor 12 to accomplish the present application. The one or more modules/units may be a series of computer program instruction segments capable of performing specific functions, which are used to describe the execution process of the computer program 14 in the in-vehicle apparatus 10. For example, the computer program 14 may be partitioned into modules 101 and 109 in FIG. 3.
It will be understood by those skilled in the art that the schematic diagram 4 is merely an example of the in-vehicle apparatus 10, and does not constitute a limitation to the in-vehicle apparatus 10, and the in-vehicle apparatus 10 may include more or less components than those shown, or combine some components, or different components, for example, the in-vehicle apparatus 10 may further include an input device, etc.
The Processor 12 may be a Central Processing Unit (CPU), and may include other general purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field-Programmable Gate arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components, and the like. The general purpose processor may be a microprocessor or the processor may be any conventional processor or the like, and the processor 12 is a control center of the in-vehicle apparatus 10 and connects various parts of the entire in-vehicle apparatus 10 by various interfaces and lines.
The memory 11 may be used for storing the computer program 14 and/or the modules/units, and the processor 12 may implement various functions of the in-vehicle apparatus 10 by running or executing the computer program and/or the modules/units stored in the memory 11 and calling data stored in the memory 11. The storage 11 may include an external storage medium and may also include a memory. In addition, the memory 11 may include a high speed random access memory, and may also include a non-volatile memory, such as a hard disk, a memory, a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), at least one magnetic disk storage device, a Flash memory device, or other volatile solid state storage device.
The modules/units integrated with the in-vehicle apparatus 10 may be stored in a computer-readable storage medium if they are implemented in the form of software functional units and sold or used as separate products. Based on such understanding, all or part of the processes in the methods of the embodiments may be implemented by a computer program, which may be stored in a computer-readable storage medium and used by a processor to implement the steps of the embodiments of the methods. It should be noted that the computer readable medium may contain content that is subject to appropriate increase or decrease as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals as is required by legislation and patent practice.
An embodiment of the present application provides a vehicle (not shown). The vehicle includes the vehicle-mounted device 10 described in the above embodiment. The vehicle-mounted device 10 of the vehicle starts a plurality of slave cores to be started to the U-Boot stage in advance, so that the vehicle-mounted functions corresponding to the slave cores are started in advance, and the communication with the kernel is established after the slave cores are started. Through the device, the starting time of the plurality of slave cores can be integrally advanced, and the plurality of slave cores and the kernel are synchronously started, so that the starting time is reduced, and the realization of the vehicle-mounted function preset by a user is advanced.
Finally, it should be noted that the above embodiments are only used for illustrating the technical solutions of the present application and not for limiting, and although the present application is described in detail with reference to the preferred embodiments, it should be understood by those skilled in the art that modifications or equivalent substitutions can be made on the technical solutions of the present application without departing from the spirit and scope of the technical solutions of the present application.
Claims (10)
1. A linux-based vehicle-mounted system starting method is characterized in that the vehicle-mounted system comprises a master core and a plurality of slave cores, and the method comprises a U-Boot stage and a kernel stage;
the U-Boot stage comprises:
determining a slave core to be started;
executing a first preprocessing flow according to the slave core to be started;
acquiring a first address of the slave core and updating the first address into a first page table;
initiating a boot to perform a boot of the master core and an early boot of at least one of the slave cores;
the kernel phase includes:
updating the first address of the early-booted slave core into a second page table;
executing a second preprocessing flow;
performing addressing based on the second page table;
establishing a communication connection;
performing a late attach of the early-booted slave core to establish communication between the slave core and the master core.
2. The vehicle-mounted system starting method according to claim 1, wherein the determining of the slave core to be started specifically comprises:
acquiring a control instruction input by a user;
matching the control instruction with the corresponding vehicle-mounted function to determine the vehicle-mounted function selected by the user;
and matching the vehicle-mounted function with a plurality of slave cores to determine the slave core executing the vehicle-mounted function.
3. The vehicle-mounted system starting method according to claim 1 or 2, wherein executing a first preprocessing flow according to the slave core to be started specifically comprises:
acquiring a second address and sending a control command to place the compressed file of the slave core to be started at the second address;
and distributing corresponding storage space according to the compressed file, wherein the storage space is used for storing the compressed file and the decompressed file.
4. The in-vehicle system startup method according to claim 1 or 2, characterized in that the in-vehicle system comprises a remote communication module for establishing communication with the early-booted slave core, and before establishing a communication connection, the method further comprises:
setting the telecommunications module to a built-in mode.
5. The vehicle system starting method according to claim 4, wherein the executing the second preprocessing flow further comprises:
determining a started slave core;
closing the initialized configuration of the started slave core;
closing the reset remote process of the started slave core;
and closing the timer vehicle-mounted function of the started slave core.
6. The in-vehicle system starting method according to claim 1 or 2, wherein before initiating the start-up to perform the start-up of the master core and the early boot of the at least one slave core, further comprising:
judging whether the files of the slave core are compressed or not;
if not, decompressing the file, and loading the decompressed file into an internal memory;
and if so, loading the decompressed file into the memory.
7. An on-vehicle system starting device, the on-vehicle system includes the main core and a plurality of from the core, characterized by that, the on-vehicle system starting device includes;
the determining module is used for determining a slave core to be started;
the execution module is used for executing a first preprocessing flow according to the slave core to be started;
the updating module is used for acquiring a first address of the early-guided slave core and updating the first address into a first page table;
the starting module is used for initiating starting to execute the starting of the main core and early boot of at least one slave core, the updating module is further used for updating a first address of the slave core into a second page table, and the executing module is further used for executing a second preprocessing flow;
an addressing module to perform addressing based on the second page table;
the communication module is used for establishing communication connection;
the execution module is further to perform a late attach of the slave core that is early booted to establish communication between the slave core and the master core.
8. An in-vehicle apparatus comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the steps of the in-vehicle system startup method according to any one of claims 1 to 6 when executing the computer program.
9. A vehicle characterized by comprising the in-vehicle apparatus according to claim 8.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the steps of the in-vehicle system startup method according to any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011159317.1A CN112256350A (en) | 2020-10-26 | 2020-10-26 | Vehicle-mounted system starting method and device, vehicle-mounted device, vehicle and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011159317.1A CN112256350A (en) | 2020-10-26 | 2020-10-26 | Vehicle-mounted system starting method and device, vehicle-mounted device, vehicle and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112256350A true CN112256350A (en) | 2021-01-22 |
Family
ID=74262474
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011159317.1A Withdrawn CN112256350A (en) | 2020-10-26 | 2020-10-26 | Vehicle-mounted system starting method and device, vehicle-mounted device, vehicle and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112256350A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115951658A (en) * | 2023-01-03 | 2023-04-11 | 重庆长安汽车股份有限公司 | Vehicle remote diagnosis method, device, server and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101464807A (en) * | 2009-01-08 | 2009-06-24 | 杭州华三通信技术有限公司 | Application program loading method and device |
| CN103155524A (en) * | 2010-08-05 | 2013-06-12 | 思杰***有限公司 | Systems and methods for IIP address sharing across cores in a multi-core system |
| CN106126241A (en) * | 2016-06-29 | 2016-11-16 | 上海友衷科技有限公司 | A kind of linux system starts method and system |
| CN110147304A (en) * | 2019-04-03 | 2019-08-20 | 珠海全志科技股份有限公司 | A kind of method and apparatus of acquisition system bootload log |
| CN111745650A (en) * | 2020-06-15 | 2020-10-09 | 哈工大机器人（合肥）国际创新研究院 | Operation method of robot operation system and control method of robot |
-
2020
- 2020-10-26 CN CN202011159317.1A patent/CN112256350A/en not_active Withdrawn
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101464807A (en) * | 2009-01-08 | 2009-06-24 | 杭州华三通信技术有限公司 | Application program loading method and device |
| CN103155524A (en) * | 2010-08-05 | 2013-06-12 | 思杰***有限公司 | Systems and methods for IIP address sharing across cores in a multi-core system |
| CN106126241A (en) * | 2016-06-29 | 2016-11-16 | 上海友衷科技有限公司 | A kind of linux system starts method and system |
| CN110147304A (en) * | 2019-04-03 | 2019-08-20 | 珠海全志科技股份有限公司 | A kind of method and apparatus of acquisition system bootload log |
| CN111745650A (en) * | 2020-06-15 | 2020-10-09 | 哈工大机器人（合肥）国际创新研究院 | Operation method of robot operation system and control method of robot |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115951658A (en) * | 2023-01-03 | 2023-04-11 | 重庆长安汽车股份有限公司 | Vehicle remote diagnosis method, device, server and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109062617B (en) | Application method of platform supporting multiple types of equipment and mobile terminal | |
| KR101555210B1 (en) | Apparatus and method for downloadin contents using movinand in portable terminal | |
| CN102238265A (en) | Mobile phone and method for realizing double-system mobile phone | |
| CN109408122B (en) | Equipment starting method, electronic equipment and computer storage medium | |
| US11157264B2 (en) | Electronic device and method for controlling update of electronic device | |
| CN115658160A (en) | Multi-operating system upgrading method, device and system based on multi-core heterogeneous SOC | |
| CN109413497B (en) | Intelligent television and system starting method thereof | |
| CN110597533A (en) | FPGA board card program updating system and method | |
| US7607001B2 (en) | Memory management method for simultaneously loading and executing program codes | |
| CN116737244A (en) | Method and device for starting multiple hardware domains of chip | |
| CN115357310A (en) | System starting method and device, electronic equipment and storage medium | |
| CN111708548A (en) | Software installation method, device, equipment and storage medium | |
| CN112256350A (en) | Vehicle-mounted system starting method and device, vehicle-mounted device, vehicle and storage medium | |
| CN115145605A (en) | Vehicle-mounted application software upgrading method and system, electronic equipment and storage medium | |
| CN110515671A (en) | Initial method, apparatus for initializing, terminal device and readable storage medium storing program for executing | |
| CN112199272A (en) | Intelligent terminal testing method and device, terminal equipment and medium | |
| CN116954674A (en) | eMMC firmware upgrading method, firmware upgrading equipment and storage device | |
| US20060230190A1 (en) | Method and apparatus for executing application in system having NAND flash memory | |
| WO2023060893A1 (en) | Storage space management method and apparatus, and device and storage medium | |
| CN102799451B (en) | WINCE system mirror image construction method and system, WINCE system mirror image | |
| CN102915246A (en) | Terminal device and method of supporting multi-firmware loading | |
| CN115827074A (en) | Rapid mapping method and device for vehicle-mounted cabin system aiming at EMMC storage, storage and vehicle | |
| CN116048593A (en) | System intelligent upgrading method, device, computer equipment and storage medium | |
| CN113885949A (en) | Quick startup method and system | |
| CN113157301A (en) | Terminal version upgrading method, system, storage medium and terminal |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20210127 Address after: 215131 No. 233 Kangyang Road, Huangdi Town, Xiangcheng District, Suzhou City, Jiangsu Province Applicant after: SUZHOU OFILM TECH Co.,Ltd. Address before: 201800 4th floor, building 43, 1485 Jialuo Road, Jiading District, Shanghai Applicant before: SHANGHAI CETC-MOTOR Co.,Ltd. Applicant before: SHANGHAI OFILM INTELLIGENT VEHICLE Co.,Ltd. Applicant before: SUZHOU OFILM TECH Co.,Ltd. |
|
| WW01 | Invention patent application withdrawn after publication | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20210122 |