CN-122018933-A - Cross-system file updating method, system level chip and device

Abstract

The embodiment of the application provides a cross-system file updating method, a system-level chip and equipment, wherein the method comprises the steps that a client system enters an engineering mode, and the client system writes a system file to be updated under a USB interface directory into a shared file space of the client system and a host system; the host system periodically polls whether the system file to be updated exists in the shared file space, when the system file to be updated exists, the host system writes the system file into the system partition and modifies the state of the system file, and the client system determines the operation result based on the state of the system file. According to the scheme, the existing shared file space is multiplexed, the transmission of the cross-system instruction can be completed without a real-time communication channel through a polling mechanism and the state change of the system file, the development requirement of a cross-system communication protocol is avoided, and the development cost is reduced.

Inventors

• SUN TAIYU

Assignees

• 亿咖通(湖北)技术有限公司

Dates

Publication Date

20260512

Application Date

20251231

Claims (10)

1. 1. A system file updating method across systems, applied to a system on chip SOC, wherein a host system and a client system are running on the system on chip, the method comprising: The client system enters an engineering mode; The client system writes a system file to be updated under a USB interface directory into a shared file space of the client system and a host system, wherein the system file is an image file for controlling an SOC safety function; The host system periodically polls whether the system file to be updated exists in the shared file space; when the system file to be updated exists, the host system writes the system file into a system partition, and modifies the state of the system file; the client system determines the result of the operation based on the state of the system file.
2. 2. The method of claim 1, further comprising, after the client system enters an engineering mode: The client system determines the type of the system file to be updated under the USB interface directory; the client system determining a fuse state of the SOC; The client system provides corresponding safety function operation buttons according to the type of the system file and the fuse state of the SOC; the client system controlling the security function operation button to be in an operable state; and when the client system receives a clicking operation event of the safety function operation button, executing the step that the client system writes the system file to be updated under the USB interface directory into a shared file space of the client system and a host system.
3. 3. The method of claim 2, wherein the client system provides corresponding security function operation buttons according to the type of the system file and the fuse state of the SOC, comprising: If the client system determines that the system file is an image file for controlling to start the secure boot function of the SOC and determines that the fuse state of the SOC is an unfused state, the client system provides an operation button for starting the secure boot function.
4. 4. The method of claim 2, wherein the client system provides corresponding security function operation buttons according to the type of the system file and the fuse state of the SOC, comprising: if the system file is an image file for controlling the secure boot function of the SOC to be temporarily turned off and the fuse state of the SOC is determined to be the fused state, the client system provides an operation button for turning off the secure boot function.
5. 5. The method of claim 2, wherein the client system provides corresponding security function operation buttons according to the type of the system file and the fuse state of the SOC, comprising: If the system file is an image file for starting the secure debug function and the fuse state of the SOC is determined to be the fused state, the client system provides an operation button for starting the secure debug function.
6. 6. The method of claim 1, wherein the host system performing the operation of writing the system file to a system partition and modifying the state of the system file comprises: the host system writes the system file into a system partition, if the system file is written successfully, deleting the system file or adding identification information which is written successfully into the name of the system file; if the writing fails, adding the identification information of the writing failure in the name of the system file.
7. 7. The method of claim 6, wherein the client system determining the result of the operation based on the state of the system file comprises: when the client system detects that the system file is deleted or the name of the system file comprises identification information of successful writing, determining that the writing operation is successful; And when the client system detects that the name of the system file comprises the identification information of the writing failure, determining that the writing operation fails.
8. 8. The method of claim 1, further comprising, prior to the host system writing the system file to a system partition: The host system judges whether the condition of the writing operation is met or not, wherein the condition of the writing operation is met comprises that the host system does not enter a low power consumption mode, or the host system detects that the system file is not written in through a system identifier; And if so, writing the system file into the operation of the system partition.
9. 9. A system-on-chip having a host system and a client system running thereon, wherein, When the client system enters an engineering mode, the client system writes a system file to be updated under a USB interface directory into a shared file space of the client system and the host system, wherein the system file is an image file for controlling an SOC safety function; The host system periodically polls whether the system file to be updated exists in the shared file space; when the system file to be updated exists, the host system writes the system file into a system partition, and modifies the state of the system file; the client system determines the result of the operation based on the state of the system file.
10. 10. An electronic device is characterized by comprising a memory and a processor; The memory stores computer-executable instructions; The processor executing computer-executable instructions stored in the memory, causing the processor to perform the method of any one of claims 1-8.

Description

Cross-system file updating method, system level chip and device Technical Field The present application relates to the field of computer technologies, and in particular, to a method for updating a system file across systems, a system-level chip, and a device. Background With the sophistication of automotive intelligence and electronic electrical architecture, modern automotive systems typically employ multi-System architecture, such as running on a System on Chip or SOC (SOC for short), a HOST System, such as a QNX (QNX may also be referred to as Neutrino Real-Time Operating System) System, and a client System, such as an Android System. In the development, debugging and production phases, the on-board system needs to update the system configuration, wherein the updating of the system configuration generally needs to be coordinated across systems (such as a host system and a client system), and involves operations such as reading and programming of an image file of the system. In the related art, the writing operation on the image file generally needs to rely on a complex communication link, which results in low operation efficiency and high development complexity, thereby increasing development cost. Disclosure of Invention The embodiment of the application provides a cross-system file updating method, a system-level chip and equipment, which are used for reducing development cost. In a first aspect, an embodiment of the present application provides a method for updating a system file across systems, applied to a system-on-a-chip SOC, where a host system and a client system are running on the system-on-a-chip, where the method includes the client system entering an engineering mode, the client system writing a system file to be updated under a USB interface directory into a shared file space of the client system and the host system, the system file being an image file for controlling an SOC security function, the host system periodically polling whether the system file to be updated exists in the shared file space, when the system file to be updated exists, the host system writing the system file into a system partition and modifying a state of the system file, and the client system determining a result of an operation based on the state of the system file. In one possible implementation, after the client system enters the engineering mode, the method further comprises the steps that the client system determines the type of the system file to be updated under the USB interface directory, the client system determines the fuse state of the SOC, the client system provides corresponding safety function operation buttons according to the type of the system file and the fuse state of the SOC, the client system controls the safety function operation buttons to be in an operable state, and when the client system receives a clicking operation event of the safety function operation buttons, the client system writes the system file to be updated under the USB interface directory into a shared file space of the client system and the host system. In one possible implementation, the client system providing corresponding security function operation buttons according to the type of the system file and the fuse state of the SOC includes providing an operation button for turning on the security start-up function if the client system determines that the system file is an image file for controlling the security start-up function of the SOC to be turned on and determines that the fuse state of the SOC is an un-fuse state. In one possible implementation, the client system provides corresponding security function operation buttons according to the type of the system file and the fuse state of the SOC, and the client system provides the operation buttons for starting the security debugging function if the system file is an image file for starting the security debugging function and the fuse state of the SOC is determined to be the fused state. In one possible implementation, the host system performs the operation of writing the system file into the system partition and modifies the state of the system file, including writing the system file into the system partition by the host system, deleting the system file or adding identification information of successful writing to the name of the system file if the writing is successful, and adding identification information of failed writing to the name of the system file if the writing is failed. In one possible implementation, the client system determines the result of the operation based on the state of the system file, including determining that the write operation was successful when the client system detects that the system file has been deleted or that the name of the system file includes identification information that the write was successful, and determining that the write operation was failed when the client system detects that the name of the system file includes identificatio