CN117873015A

CN117873015A - Implementation method, system and storage medium for loading EOL software on production line

Info

Publication number: CN117873015A
Application number: CN202311690888.1A
Authority: CN
Inventors: 韩小彬
Original assignee: Huizhou Desay SV Automotive Co Ltd
Current assignee: Huizhou Desay SV Automotive Co Ltd
Priority date: 2023-12-08
Filing date: 2023-12-08
Publication date: 2024-04-12

Abstract

The application provides a method, a system and a storage medium for realizing EOL software loading of a production line, wherein the method comprises the following steps: responding to an EOL software downloading request sent by an upper computer of a production line, and receiving and storing an EOL software data packet by a target host; only after the EOL software data package is successfully downloaded, the target host receives an EOL software starting request sent by an upper computer of a production line so as to activate the EOL software; and after the EOL software completes the self-checking test on the target host, synchronously feeding back a test result to the production line upper computer, and ending production. The method and the device utilize a complete decoupling mode to test and verify the ECU on a production line by installing the ECU into an EOL test station, and verify the performance and quality of the ECU through self-checking, so that the influence of ECU production software on production equipment and human input can be effectively reduced, and the human input of both an ECU provider and a host factory in EOL requirements, approval and the like is reduced.

Description

Implementation method, system and storage medium for loading EOL software on production line

Technical Field

The application belongs to the technical field of domain controller production lines, and particularly relates to a method, a system and a storage medium for realizing EOL software loading of a production line.

Background

The software of the ADAS (Advanced Driver Assistance System) domain controller includes functional software and nonfunctional software, wherein EOL (End of Line) software is a nonfunctional software related to production line production. The functions of the EOL software mainly comprise key burning, offline configuration, hardware consistency detection and the like. The currently adopted software integration scheme is that functional software and nonfunctional software are integrated and packaged together and accepted and released together. Once a mass-produced version of an ECU (target host) is approved by a host factory, the production process must be strictly in accordance with the mass-produced version for production. However, if the current production station of the production line and the test equipment are not matched with the EOL software of the mass-produced version of the ECU, the problem can be solved only by modifying or adding the production station or equipment of the production line, which not only increases the production cost but also seriously affects the production efficiency of the production line. This can be a serious delivery problem if an urgent production need arises. And EOL belongs to a non-functional requirement, wherein the hardware uniformity detection function belongs to an ECU vendor internal production requirement. Since EOL software is released integrally with functional software, each time EOL software update and release requires acceptance and approval by the host factory, both the host factory and the ECU vendor, which is a significant effort investment, which greatly increases the time and cost of development, production and maintenance.

Disclosure of Invention

In view of the defects in the prior art, the application provides a method, a system and a storage medium for realizing EOL software loading of a production line, wherein the method tests and verifies the ECU on the production line by loading the ECU into an EOL test station, and verifies the performance and quality of the ECU through self-checking, so that the influence of the ECU production software on production equipment and manpower input can be effectively reduced, the standardization and the planarization of EOL software design are effectively enhanced, and the cost of EOL software requirement, development and maintenance is reduced.

In order to achieve the above objective, the present application provides a method for implementing EOL software loading on a production line, where the method mainly includes:

s1: and responding to an EOL software downloading request sent by the production line upper computer, and receiving and storing an EOL software data packet by the target host.

S2: and only after the EOL software data package is successfully downloaded, the target host receives an EOL software starting request sent by the production line upper computer so as to activate the EOL software.

S3: and after the EOL software completes the self-checking test on the target host, synchronously feeding back a test result to the production line upper computer, and ending production.

In the present application, before the step S1, the method further includes:

and finishing the preparation work of the generating environment, and installing the target host into an EOL test station.

And the production line upper computer establishes handshake connection with the target host computer, and performs identity verification test on the production line upper computer through the target host computer.

In the present application, before the step S1, the method further includes:

after the handshake connection is successful and the authentication test authentication is successful, the production line upper computer sends an EOL software downloading request to the target host; otherwise, the EOL software function of the upper computer of the production line fails to be activated.

In this application, the self-test includes at least: link testing, memory testing, and high and low temperature burn-in testing.

In this application, the step S3 further includes:

and when the link test and the memory test are carried out, the test result is normal only when the link test result is in the first test threshold range, the memory test result is in the second test threshold range and the high-low temperature aging test result is in the third test threshold range, and the self-checking test of the target host is output to the upper computer of the production line to be successfully passed.

In order to achieve the above object, the present application further provides a system for implementing EOL software loaded on a production line, where the system includes:

the device comprises a receiving processing module, an activating processing module and a self-checking feedback module.

And the receiving and processing module is used for responding to an EOL software downloading request sent by the upper computer of the production line, and the target host receives and stores the EOL software data packet.

And the activation processing module is used for receiving an EOL software starting request sent by the production line upper computer only after the EOL software data packet is downloaded successfully so as to activate the EOL software.

And the self-checking feedback module is used for synchronously feeding back a test result to the production line upper computer after the EOL software completes self-checking test on the target host computer, and ending production.

Further, the self-checking processing module at least comprises: the device comprises a link test module, a memory test module and a high-low temperature aging test module.

In this application, the system further comprises:

the communication connection module is used for installing the target host into an EOL test station after completing the preparation work of the generating environment; and the production line upper computer establishes handshake connection with the target host computer, and performs identity verification test on the production line upper computer through the target host computer.

In this application, the system further comprises:

the self-checking judging module is used for outputting the self-checking test of the target host to the upper computer of the production line as successful passing only when the link test result is in the first test threshold range, the memory test result is in the second test threshold range and the high-low temperature aging test result is in the third test threshold range.

To achieve the above object, the present application further provides a storage medium, which is one of computer readable storage media, on which a computer program is stored, where the computer program is executed by a processor, and the method for implementing the EOL software loading on a production line according to any one of the above.

Compared with the prior art, the application has the beneficial effects that:

according to the method, the ECU is installed in the EOL test station to test and verify the ECU on the production line, and the performance and the quality of the ECU are verified through self-checking, so that the influence of the ECU production software on production equipment and personnel investment can be effectively reduced, and temporary and unexpected production cost is reduced; the development and release efficiency of EOL software can be effectively improved, and the investment of non-functional software by both an ECU provider and a host factory is reduced; and effectively strengthen the standardization and the platform of EOL software design, reduce EOL software requirement, development and maintenance cost.

Drawings

FIG. 1 is a flowchart of a method for implementing EOL software loading on a production line according to an embodiment of the present application.

FIG. 2 is a schematic diagram of steps of a method for implementing EOL software loading on a production line according to an embodiment of the present application.

Fig. 3 is a schematic structural diagram of an implementation system for loading EOL software on a production line according to an embodiment of the present application.

Detailed Description

For the purposes, technical solutions and advantages of the embodiments of the present application to be more apparent, the technical solutions will be clearly and completely described below in connection with the embodiments of the present application. It will be apparent that the embodiments described are some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.

Embodiment one:

as shown in fig. 1, in order to solve the above technical problems, the present application provides a method for implementing EOL software loading on a production line. It should be noted that in the prior art, there is a problem that the production line production station and the testing equipment are not matched with the EOL software of the ECU mass production version: if the station and the test equipment of the current production line are not matched with the EOL software version of the ECU, the problem is solved by modifying or adding the station or the equipment of the production line; the EOL software update and release is accepted and approved with a large amount of work: because the functional software is integrally released together with the nonfunctional software, each time the EOL software is updated and released, the acceptance and approval of the host factory is required; hardware consistency detection belongs to the internal requirements of the ECU suppliers: the hardware compliance detection function is a production requirement internal to the ECU vendor, but since it is released with EOL software, its updating and release also requires acceptance and approval by the host factory.

Obviously, the current software integration schemes mostly have management bottlenecks and cost increases, especially in the process of coping with emergency production demands and updating release, and solving the problems needs to consider a more flexible software management mode so as to reduce production cost, improve efficiency and reduce dependence on acceptance of a host factory, which results in complicated flow.

The ECU is tested and verified on the production line by being installed in the EOL test station, and the performance and quality of the ECU are verified through self-checking, so that the dependence on acceptance of a host factory is greatly reduced.

In this embodiment, the method mainly includes:

It should be noted that, when the on-line host computer needs to load new EOL software into the target host computer, it sends an EOL software download request to the target host computer. And after detecting the downloading request of the upper computer of the production line, the target host responds immediately and prepares to receive the EOL software data packet.

Preferably, for example, the production line host computer sends the following request: "download EOL software version x.y.z. The target host is ready to receive the relevant version of EOL software after receiving the request.

Then, the production line host computer starts to transmit the EOL software data packets, and the target host computer receives and stores the data packets.

Preferably, the production line host computer transmits binary data of EOL software to the target host computer via a secure channel, for example. The target host receives the data packet and stores it in the designated location.

In this embodiment, by responding to a download request from an upper computer on the production line, the target host can update EOL software in time, so as to ensure that the latest version of nonfunctional software is used in the production process. Because the target host can quickly respond to the download request and receive the data, the downtime of the production line is minimized, and the production efficiency is improved. And the whole EOL software data package is stored on the target host, so that the integrity of the software is ensured, and the loss or damage in data transmission is avoided.

In summary, this step is a key link for ensuring EOL software update and loading in practical applications, which helps to improve flexibility and efficiency of the production line.

In the present application, before the step S1, the method further includes:

It should be noted that, in this embodiment, the target host needs to be installed in a special EOL test station first, so as to prepare for subsequent software loading and testing.

It should be noted that, in this embodiment, a communication connection needs to be established between the upper computer and the target host in the production line, and identity verification is performed to ensure validity and security of the connection.

In this embodiment, on the production line, the staff installs the target host into a dedicated EOL test station, ensuring that the target host is properly connected to the test equipment and other related equipment.

Preferably, the staff physically installs the target host onto the EOL test station and connects the necessary power, data lines, etc. And the production line upper computer and the target host establish communication connection so as to ensure that the production line upper computer and the target host can perform data transmission and interaction. The production line host computer then establishes a connection with the target host computer via a network or a dedicated interface, ensuring that they can communicate with each other. The target host initiates an identity verification test to the upper computer of the production line so as to ensure the legitimacy and the safety of the upper computer of the production line. For example: the target host sends an identity verification request to the production line upper computer, and the production line upper computer must provide a valid identity credential or password for verification.

In this embodiment, the completion of the production environment preparation work includes installing the target host to the EOL test station, ensuring that the equipment and environment on the production line meet the requirements, ready for subsequent software loading and testing. Through handshake connection and identity verification test, the communication connection between the upper computer and the target host computer in the production line is ensured to be safe and reliable, and unauthorized access and data leakage are prevented. And through the identity verification test, the communication and the operation of the authorized production line upper computer and the target host computer can be ensured, and the malicious operation and illegal access are prevented.

In conclusion, the steps are helpful to ensure the safety and stability of the production environment in practical application, and a reliable basis is provided for subsequent software loading and testing.

As shown in fig. 2, in the present application, before the step S1, the method further includes:

It should be noted that, the handshake connection established between the upper computer of the production line and the target host is successful, and the target host successfully verifies the identity of the upper computer of the production line. For example, the target host sends a handshake signal to the on-line host, which responds correctly and passes the authentication test. After the handshake connection and the identity verification are successful, the production line upper computer sends an EOL software downloading request to the target host. For example, the production line upper computer sends the following request: "download EOL software version x.y.z. "

And after receiving the EOL software downloading request of the production line upper computer, the target host responds immediately and prepares to receive the EOL software data packet. For example, the target host sends an acknowledgement signal to the production line host indicating that the EOL software data packet is ready to be received.

In this embodiment, through the success of handshake connection and authentication, it is ensured that only the authenticated production line upper computer can send an EOL software download request to the target host computer, thereby preventing unauthorized download operation. Only if the handshake connection and the authentication are successful, the production line upper computer can successfully send an EOL software download request. Otherwise, the EOL software function cannot be activated, so that the safety and the legality of the software are ensured. Through the authentication test, the communication and the operation of the authorized production line upper computer and the target host computer can be ensured, and the malicious operation and the illegal access are prevented.

In summary, the embodiment is helpful to ensure the security and legitimacy of software download, protect the security of the production environment, and prevent unauthorized access and operation in practical application.

It should be noted that, the on-line host computer successfully transmits the EOL software data packets to the target host computer, and the target host computer successfully receives and stores the data packets. For example, the production line host transmits EOL software data packets to the target host via the secure channel, and the target host receives and stores the data packets.

The production line upper computer sends an EOL software starting request to the target host computer to activate the EOL software which is successfully downloaded. For example, the production line upper computer sends the following request: "start EOL software".

After receiving the EOL software starting request of the upper computer of the production line, the target host verifies the validity of the request and carries out corresponding processing to activate the EOL software. For example, the target host verifies the validity of the request of the upper computer of the production line, and after confirming that the request is valid, the corresponding operation is executed to activate the EOL software.

In the embodiment, the start request is received after the EOL software data package is required to be downloaded successfully, so that the completeness and the correctness of the EOL software are ensured. Only in case of a successful download will the target host activate EOL software. By verifying the legitimacy of the initiation request, the target host may prevent illegal or incomplete software initiation, ensuring that only authorized and complete software can be activated. By receiving the start request after the successful download, the safety and reliability of the software loading are ensured. Only if the download is successful, the start-up operation is performed, reducing potential errors and risks.

In summary, the embodiment is helpful to ensure the integrity and correctness of EOL software in practical application, prevent illegal or incomplete software start, and improve the security and reliability of software loading.

It should be noted that, the target host runs EOL software to perform self-checking test, including testing and verifying various functions and performances of the ECU. For example, EOL software performs self-test on the ECU's CAN link, flex link, ethernet link, DDR, UFS, and high low temperature aging, etc.

The EOL software feeds back the results of the self-test to the production line host computer for further processing and recording. For example, EOL software sends the self-test result to the production line upper computer in the form of data packets, and the production line upper computer receives and analyzes the data packets to obtain the self-test result.

And according to the result of the self-checking test, the upper computer of the production line decides whether to finish production according to preset rules or judging conditions. For example, if the self-test results show that the ECU passes all of the functional and performance tests, the production line upper computer may decide to continue production. If the self-checking test result shows that the ECU has a problem or fails the test, the upper computer of the production line can decide to end production and take corresponding measures.

According to the embodiment, through self-checking test, EOL software tests and verifies various functions and performances of the ECU, and normal operation and quality of the ECU in a production environment are ensured to meet requirements. The EOL software synchronously feeds back the self-checking test result to the production line upper computer, and the production line upper computer can monitor the state and performance of the ECU in real time so as to carry out further processing and recording. According to the result of the self-checking test, the upper computer of the production line can determine whether to finish production according to a preset rule or a judgment condition so as to ensure that the produced product meets the quality requirement.

In summary, the embodiment is helpful to verify the functions and performances of the ECU in practical application, monitor the state of the ECU in real time, and determine whether to end production according to the test result, so as to ensure that the quality of the produced product meets the requirements.

The link test includes at least self-checking of a CAN link, a FLEXRAY link, an ethernet link, and the like. The memory test includes at least self-checking of DDR and UFS. The high and low temperature aging test is used for simulating the working condition of the ECU under the extreme temperature condition so as to verify the stability and reliability of the ECU. Specific implementations may include placing the ECU in a high and low temperature environment and running and testing for extended periods of time to detect the presence of temperature related problems or malfunctions.

Preferably, DDR self-test generally refers to self-testing and verification of double data rate memory (DDR memory). In the ECU production environment, DDR self-test is mainly:

and (3) testing a read-write function: the DDR memory can be ensured to correctly read and write data.

And (3) time sequence testing: and verifying the timing parameters of the DDR memory, including a read-write timing and a refresh timing.

And (3) electrical parameter testing: the electrical characteristics of the DDR memory are checked to ensure operation within a specified voltage and temperature range.

Data integrity test: ensuring that no errors occur during data transmission to maintain the integrity of the stored data.

In another embodiment, UFS self-test consists essentially of:

and (3) testing a read-write function: ensuring that the UFS memory can correctly read and write data.

Block erase test: the block erase function of the UFS memory is verified, ensuring that the block erase operation can be performed correctly when needed.

And (3) electrical parameter testing: the electrical characteristics of the UFS memory are checked to ensure compliance with prescribed voltage and temperature requirements.

Data transmission rate test: the data transfer rate of the UFS memory is tested to ensure that a specified performance level can be achieved in high speed read and write operations.

The above self-checking steps aim to ensure proper operation of DDR and UFS in the ECU, and their performance and quality meet expected requirements.

In this application, the step S3 further includes:

It should be noted that, the EOL software performs a link test, a memory test, and a high-low temperature aging test on the ECU, and obtains a corresponding test result. For example, EOL software sends test data packets for link testing, reads and writes the test data for memory testing, and places the ECU in a high and low temperature environment for burn-in testing.

And then judging the results of the link test, the memory test and the high-low temperature aging test, and checking whether the results are within a preset test threshold range. For example, comparing the link test results to check whether the link test results are within a first test threshold; verifying the memory test result, and checking whether the memory test result is within a second test threshold range; and evaluating the high and low temperature aging test result, and checking whether the high and low temperature aging test result is within a third test threshold range.

If the results of the link test, the memory test and the high-low temperature aging test are all within the test threshold range, the self-checking test result is considered to be normal, and the information that the self-checking test of the target host is successfully passed is output to the upper computer of the production line. For example, if the results of the link test, the memory test, and the high and low temperature burn-in test are all within the preset test threshold range, the EOL software sends a message to the production line upper computer that the self-test is successful.

According to the embodiment, the link test, the memory test and the high-low temperature aging test result are judged, so that the test result is ensured to be within the preset test threshold range, and the accuracy and the reliability of the test result are improved. Screening out normal self-checking test results: and outputting the information that the self-checking test of the target host machine passes successfully to the upper computer of the production line only when the results of the link test, the memory test and the high-low temperature aging test are all within the test threshold range. By setting the test threshold range, a reliable basis is provided for judging the self-checking test result, and the function and performance of the ECU are ensured to meet the expected requirements.

Preferably, the set range of the first test threshold range (link test) may be 500Mbps to 1000Mbps.

The link test is used to verify the communication link performance of the ECU, and the preset test threshold range indicates that the link transmission rate is normal between 500Mbps and 1000Mbps. If the test results are less than or exceed this range, it may be indicative of a problem with the communication link.

The second test threshold range (memory test) may be set to 95% to 100%.

The memory test is used for verifying the reliability of the memory of the ECU, and the preset test threshold range indicates that the success rate of the memory read-write operation is normal between 95% and 100%. If the test results are below 95% or above 100%, it may be indicative of a memory failure or performance problem.

The third test threshold range (high low temperature burn-in test) may be set to a range of-40 ℃ to 85 ℃.

The high and low temperature aging test is used for verifying the stability of the ECU under the extreme temperature condition, and the preset test threshold range indicates that the ECU works normally in the temperature range of-40 ℃ to 85 ℃. If the test results are outside this range, it may be indicative of an unstable performance of the ECU under extreme temperature conditions.

In other embodiments, the test threshold is set taking into account the specific hardware and software specifications, as well as the actual operating environment of the system. In practical applications, the setting of the threshold is usually adjusted in detail by a person skilled in the relevant art according to the product requirements and performance criteria, and is not limited thereto.

In summary, the embodiment provides a detailed analysis and illustration for an implementation method for loading EOL software on a production line, and the application reduces the dependence on acceptance of a host factory and improves the flexibility and efficiency of the production line by loading an ECU into an EOL test station and testing and verifying on the production line. Through handshake connection, identity verification and EOL software download request verification, the security and reliability of software loading are ensured, illegal access and operation are prevented, and through EOL software self-checking test, the functions and performances of the ECU are comprehensively verified and tested, the normal operation of the ECU in a production environment is ensured, and the ECU meets the preset test threshold range. By performing self-checking tests and verification on the production line, the dependence on acceptance of a host factory is reduced, the production cost is reduced, and the occurrence of delivery problems is reduced. Meanwhile, potential problems can be quickly found and solved through timely self-checking test and feedback, and the production efficiency and the product quality are improved.

Embodiment two:

as shown in fig. 3, in order to solve the above technical problem, the present application further provides a system for implementing EOL software loading on a production line, where the system includes:

It should be noted that, the module receives and stores the EOL software data packet from the production line upper computer by receiving the EOL software download request sent by the production line upper computer.

Through the receiving processing module, the target computer can receive and store the EOL software data package from the upper computer of the production line, and prepare for subsequent software loading.

It should be noted that, after the EOL software data packet is downloaded successfully, the module receives and processes an EOL software start request sent by the upper computer of the production line to activate the EOL software.

By activating the processing module, the EOL software is activated only under the condition that the EOL software data package is successfully downloaded, and the safety and reliability of software loading are ensured.

It should be noted that, the module receives the result of the self-checking test and synchronously feeds back the result to the upper computer of the production line for further processing and recording.

Through the self-checking feedback module, the upper computer of the production line can acquire the self-checking test result of the ECU in real time so as to further process and record, and decide whether to end production according to the result.

It should be noted that the link test module is used to verify the proper operation of the communication link between the ECU and other devices. Particular implementations may include sending and receiving test data packets, checking the accuracy and stability of data transmissions, and detecting if a link is faulty or interfering. For example: CAN links, FLEXRAY links, ethernet links, etc., are not limited thereto.

The memory test module is used to verify the ECU internal memory, for example: DDR and UFS function properly. Particular implementations may include reading and writing test data, checking the consistency and integrity of the data, and detecting if there is a failure or corruption of memory.

The high-low temperature aging test module is used for simulating the working condition of the ECU under the extreme temperature condition so as to verify the stability and reliability of the ECU. Particular implementations may include placing the ECU in a high and low temperature environment and running and testing for extended periods of time to detect the presence of temperature related problems or malfunctions.

In this application, the system further comprises:

It should be noted that, the module ensures that handshake connection is established between the upper computer of the production line and the target host computer, and performs an authentication test to ensure validity and security of the connection.

And the communication connection module ensures that the communication connection between the upper computer of the production line and the target host is safe and reliable, and prevents unauthorized access and operation.

In this application, the system further comprises:

It should be noted that, the module judges the results of the link test and the memory test, and checks whether the results are within the preset test threshold range.

And through the self-checking judging module, whether the self-checking test result is normal or not can be judged according to a preset test threshold range, and information that the self-checking test of the target host machine is successfully passed is output to the upper computer of the production line.

In summary, embodiment two makes detailed analysis and illustration to the implementation system of production line loading EOL software that this application provided, and this application is through carrying out self-checking test and verification on the production line, reduces the dependence to the host computer factory acceptance, has improved the flexibility and the efficiency of production line, has ensured the security and the reliability of software loading simultaneously, has improved the quality and the performance of ECU, has reduced the emergence of manufacturing cost and delivery problem. These beneficial effects are significant in improving the efficiency and product quality of the production line. The specific implementation process and principle are described in detail in the first embodiment, and are not described in detail in this embodiment.

Embodiment III:

the application also provides an SDSA domain controller, which at least comprises the implementation system for loading EOL software on a production line.

The SDSA domain controller refers to a domain controller based on a software defined security architecture (Software Defined Secure Architecture). Its purpose is to provide secure, flexible and scalable network control and management.

In a specific implementation process, the SDSA domain controller can analyze the implementation process of loading EOL software on the production line and analyze the domain controller aiming at the software. In this process, the SDSA domain controller can be implemented by:

identifying line loading EOL software: the SDSA domain controller can identify the existence of the EOL software loaded on the production line by monitoring network traffic, detecting file transmission, analyzing software behaviors and the like.

Analyzing the software behavior: once the line is identified to be loaded with EOL software, the SDSA domain controller can perform in-depth analysis on the software. It can detect the behavior of the software, identify potential threats or vulnerabilities, and generate corresponding reports.

Safety control is implemented: based on the analysis result of the EOL software loaded on the production line, the SDSA domain controller can take corresponding security measures. For example, it may implement access control policies, prevent malware from spreading, quarantine infected devices, etc., to secure the entire network environment.

Through the implementation process, the SDSA domain controller can provide the following effects:

real-time monitoring and detection: the SDSA domain controller can monitor activity in the network in real time and detect potential security threats. It can help enterprises discover and deal with various security events and attacks in time.

Fast response and response: once a security threat is found, the SDSA domain controller can respond quickly and take appropriate action to deal with. It can automatically prevent the spread of malware and isolate infected devices to reduce potential losses.

Network security management and control: the SDSA domain controller provides a centralized network management and control platform. The method can help enterprises to implement unified security policies, manage network equipment and user access, and improve overall network security.

In summary, the SDSA domain controller in this embodiment can provide a network security solution for real-time monitoring, fast response, and centralized management. This helps to increase the security and reliability of the enterprise network.

Embodiment four:

the application also provides a storage medium, which is one of computer readable storage media, and a computer program is stored on the storage medium, and when the computer program is executed by a processor, the implementation method for loading the EOL software on the production line is realized.

The computer readable storage medium may be configured on any computer device, may be a computing device such as a tablet computer, a desktop computer, a cloud server, or may be a vehicle terminal or a control system, for example, may further include an input/output device, a network access device, and the like.

Preferably, the computer program in the storage medium analyzes:

first, a computer program in a storage medium is read into a memory and executed by a processor. By analyzing the codes and logic of these computer programs, the implementation method of the EOL software loaded on the production line can be known. By analyzing and debugging the computer program in the storage medium row by row, the specific implementation process of loading the EOL software on the production line can be known. This includes the steps of initializing, configuring, connecting to the network, downloading and installing updates of the software.

By executing the computer program in the storage medium, the production line loading EOL software can achieve the following effects:

the latest EOL software version is loaded to the production line equipment to ensure that the equipment has the latest functions and performance.

Suitable software updates are automatically identified and installed to repair potential vulnerabilities and improve security.

The status of production line equipment is managed and monitored, including operating conditions, fault diagnostics, and performance optimization.

In summary, by the computer program stored in the storage medium in this embodiment, the implementation method of loading EOL software on the production line can be implemented, and effects such as equipment upgrade, security improvement, and performance optimization are brought. This helps to improve the efficiency and reliability of the production line.

The processor may be a Central Processing Unit (CPU), but may also be other general purpose processors, digital Signal Processors (DSPs), application Specific Integrated Circuits (ASICs), off-the-shelf programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The memory is used to store an operating system, application programs, boot loader (BootLoader), data, and other programs, etc., such as program code for the computer program, etc. The memory may also be used to temporarily store data that has been output or is to be output.

In several embodiments provided herein, it will be understood that each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.

The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device to perform all or part of the steps of the method described in the various embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing embodiments have been provided for the purpose of illustrating the objects, technical solutions and advantages of the present application in further detail, and it should be understood that the foregoing embodiments are merely examples of the present application and are not intended to limit the scope of the present application. It should be noted that any modifications, equivalent substitutions, improvements, etc. made by those skilled in the art, which are within the spirit and principles of the present application, are intended to be included within the scope of the present application.

Claims

1. The implementation method for loading EOL software on a production line is characterized by comprising the following steps:

s1: responding to an EOL software downloading request sent by an upper computer of a production line, and receiving and storing an EOL software data packet by a target host;

s2: only after the EOL software data package is successfully downloaded, the target host receives an EOL software starting request sent by an upper computer of a production line so as to activate the EOL software;

2. The method for implementing EOL software loading in a production line of claim 1, further comprising, prior to step S1:

completing the preparation work of the generating environment, and installing the target host into an EOL test station;

3. The method for implementing EOL software loading in a production line according to claim 2, further comprising, before step S1:

4. The method for implementing EOL software loading on a production line according to claim 3,

the self-test comprises at least: link testing, memory testing, and high and low temperature burn-in testing.

5. The method for implementing EOL software loading in a production line of claim 4, wherein the step S3 further comprises:

6. A system for implementing line loading EOL software, comprising:

the device comprises a receiving processing module, an activating processing module and a self-checking feedback module;

the receiving and processing module is used for responding to an EOL software downloading request sent by the upper computer of the production line, and the target host receives and stores an EOL software data packet;

the activation processing module is used for receiving an EOL software starting request sent by the production line upper computer only after the EOL software data packet is downloaded successfully, so as to activate the EOL software;

7. The production line EOL software loading implementation system of claim 6, further comprising:

8. The system for implementing the line loading EOL software of claim 7,

the self-checking processing module at least comprises: the device comprises a link test module, a memory test module and a high-low temperature aging test module.

9. The production line EOL software loading implementation system of claim 8, further comprising:

10. A storage medium, one of computer readable storage media, having stored thereon a computer program, which when executed by a processor, implements a method of loading EOL software for a production line according to any of claims 1-5.