A method and system for removing power online batch firmware upgrade of eMMC mass production tool

Abstract

The application discloses an eMMC mass production tool power-off online batch firmware upgrading method and system, relates to the technical field of storage device production, and comprises the following steps: receiving a firmware path and a device list, and acquiring device information of an eMMC open card board card and a subcard to be upgraded. The completeness of the device information is checked, a restart instruction is issued if the information is complete, and the device enters a bootrom mode. The device is rescanned, and if a bootrom state device is identified, the next step is entered. The tool is called to download firmware, and the downloading progress and state are synchronously downloaded in real time. After the downloading is completed, the device is restarted to recover to a normal operation mode, the firmware version is read and compared with a target version for verification. If the versions are consistent, the upgrading is successful, and the number of successes is counted. After all the devices are processed, signals are sent according to the number of successes and failures, and the results are displayed, and all the state information is updated. The application does not need manual physical power-off of the device, reduces operation steps, avoids the risk of damage of the board card / subcard caused by manual operation, and is more convenient to operate.

Description

Technical Field

[0001] This invention relates to the field of storage device manufacturing technology, and specifically to a method and system for power-off online batch firmware upgrade of eMMC mass production tools. Background Technology

[0002] Firmware upgrades are a crucial step in the production process of eMMC-enabled boards / daughter cards. Existing firmware upgrade methods involve manually powering down each eMMC-enabled board / daughter card, then powering it back on and shorting it to enter bootrom mode. Firmware is then downloaded to each board / daughter card individually, and finally, the upgrade results are verified.

[0003] However, the existing method has problems in the following aspects:

[0004] 1) The operation is cumbersome, requiring manual physical power-off of the board / daughter card device, and it is impossible to directly put the device into bootrom state through commands;

[0005] 2) Inefficient, unable to process multiple eMMC cards / daughter cards in batches, and lacking standardized SVN version comparison and verification procedures, making it impossible to accurately control the upgrade success rate.

[0006] 3) Prone to errors; manual operation of boards / daughters may damage the equipment, and manual verification of upgrade results is prone to misjudgment.

[0007] 4) Long production cycle affects the overall production efficiency of eMMC card opening board / daughter card, and non-standard upgrade verification process will also increase subsequent rework costs;

[0008] Therefore, a more efficient, reliable method for firmware upgrades of eMMC open-card boards / daughter cards with standardized verification procedures is needed. Summary of the Invention

[0009] The purpose of this invention is to overcome the shortcomings of the prior art and provide a method and system for power-off online batch firmware upgrade of eMMC mass production tools.

[0010] The objective of this invention is achieved through the following technical solution:

[0011] In a first aspect, this application discloses a method for power-off online batch firmware upgrade of an eMMC mass production tool, comprising the following steps:

[0012] S1. Initialize the thread, receive the firmware path and active device list, and obtain the device information of the eMMC card / daughter card to be upgraded, including device ID, device path information, device SN and current device running status;

[0013] S2. Iterate through each eMMC card to be upgraded, check if its device information is complete. If the device information is incomplete, record the error and accumulate the failure count. If the device information is complete, send a preset restart command to the corresponding eMMC card to be upgraded, so that it restarts online and enters the bootrom state. After sending the preset restart command, wait for a preset time to ensure that it fully enters the bootrom state.

[0014] S3. After sending a preset reboot command to all eMMC card opening boards / daughters with complete device information, rescan them and identify eMMC card opening boards / daughters in the bootrom state; if no eMMC card opening board / daughter in the bootrom state is identified, record the error and accumulate the failure count; if an eMMC card opening board / daughter in the bootrom state is identified, proceed to step S4.

[0015] S4. For the eMMC open card / daughter card with the identified bootrom status, use a firmware download tool to perform firmware download operation, and at the same time provide real-time feedback on the download progress and status during the download process;

[0016] S5. After the firmware download is complete, perform a reboot operation on each eMMC card / daughter card in bootrom state to exit bootrom state and enter production firmware mode. After the eMMC card / daughter card in production firmware mode is running stably, read its version information and then compare the version information with the preset target version to verify whether the upgrade is successful. If the version information is consistent with the preset target version, the upgrade is successful, the success count is accumulated, and a progress signal is sent. If the version information is inconsistent with the preset target version, the upgrade fails, the failure count is accumulated, and error details are recorded. The error details include the device ID, version information, and the difference between the version information and the preset target version.

[0017] S6. After traversing all eMMC activation cards / daughters to be upgraded, determine if any eMMC activation cards / daughters have been successfully upgraded. If no successful upgrades are found, send a failure signal and display all error messages. If successful upgrades are found, further determine if any upgrades have failed. If no upgrades have failed, send a first success signal to indicate that all eMMC activation cards / daughters to be upgraded have downloaded and verified successfully. If upgrades have failed, send a second success signal to display the number of successful and failed eMMC activation cards / daughters to be upgraded and the reasons for the failures. Finally, send a rescan signal to scan all eMMC activation cards / daughters to be upgraded and update the status of all eMMC activation cards / daughters to be upgraded.

[0018] Based on the first aspect, the preset reboot command mentioned in step S2 includes a reboot command that can put the eMMC card / daughter card into the bootrom state without physical power failure.

[0019] Based on the first aspect, the preset time mentioned in step S2 is dynamically adjusted according to the device model and mass production scenario of the eMMC card opening board / daughter card, and it is necessary to ensure that the eMMC card opening board / daughter card is fully entered into the bootrom state.

[0020] Based on the first aspect, the firmware download tool mentioned in step S4 includes a tool that supports downloading firmware for eMMC card / daughter card in bootrom mode and can provide feedback on the download progress.

[0021] Based on the first aspect, the preset target version mentioned in step S5 includes the SVN version.

[0022] Based on the first aspect, the processing of multiple eMMC card opening boards / daughter cards adopts a multi-threaded parallel or multi-process parallel approach to achieve batch upgrades.

[0023] Secondly, this application discloses a power-off online batch firmware upgrade system for eMMC mass production tools, which utilizes the aforementioned power-off online batch firmware upgrade method for eMMC mass production tools, including:

[0024] Device Management Module: Used to obtain and manage the list of eMMC cards / daughters to be upgraded, initialize threads, receive firmware paths and active device information, and obtain device information of eMMC cards / daughters to be upgraded;

[0025] The bootrom control module is used to send a preset restart command to each eMMC card / daughter card device to be upgraded, so that the eMMC card / daughter card device to be upgraded restarts online and enters the bootrom state, and waits for a preset time to ensure that it is fully in the bootrom state.

[0026] Device identification module: After sending a preset reboot command to all eMMC card opening boards / daughters with complete device information, it rescans them and identifies eMMC card opening boards / daughters with a bootrom status.

[0027] Firmware download module: Used to perform firmware download operations on the identified bootrom-state eMMC open card / daughter card using a firmware download tool, and provide real-time feedback on download progress and status during the download process;

[0028] Upgrade verification module: Performs a reboot operation on each eMMC card / daughter card in bootrom state to exit bootrom state and enter production firmware mode; after the eMMC card / daughter card in production firmware mode is running stably, reads its version information, and then compares the version information with the preset target version to verify whether the upgrade is successful; records the version comparison results and error details to provide a basis for result processing;

[0029] Results Processing Module: This module summarizes the comparison results from the upgrade verification module, counts the number of successful and failed devices, records error details, sends corresponding success, failure, or partial success signals based on the statistical results, generates a detailed upgrade report, sends a device rescan signal, and updates the current status of all eMMC card opening boards / daughters.

[0030] The beneficial effects of this invention are:

[0031] 1) This application enables the eMMC card opening board / daughter card to enter the bootrom state online by sending the vendor_reboot command, without the need for manual physical power-off of the equipment, reducing operation steps, avoiding the risk of damage to the board / daughter card caused by manual operation, and making operation more convenient; at the same time, it supports firmware upgrades for multiple eMMC card opening boards / daughter cards at the same time. Through thread initialization and device traversal, it realizes parallel processing of multiple devices, which greatly improves the production efficiency of the board / daughter card and shortens the production cycle.

[0032] 2) The entire board / daughter card upgrade process of this application is fully automated, from device acquisition, sending the vendor_reboot command, identifying the bootrom device, downloading firmware, to restart verification and result processing. This reduces manual intervention, lowers the probability of errors, and improves the consistency of board / daughter card upgrades.

[0033] 3) This application uses an SVN version comparison verification step. After the upgrade, the production firmware is compared with the SVN version to accurately determine whether the upgrade was successful, avoiding missed detections and misjudgments, ensuring upgrade quality, and reducing subsequent rework costs. At the same time, it provides real-time board / daughter card upgrade progress, device status, version comparison results, and error information feedback, which facilitates operators to monitor and handle abnormal situations in a timely manner and improves operational convenience.

[0034] 4) This application is applicable to mass production scenarios of various eMMC card opening boards / daughter cards, adapts to the needs of multi-channel parallel mass production, and can flexibly adjust the vendor_reboot instruction waiting time and svn version comparison standard according to the actual production scenario, with strong adaptability. Attached Figure Description

[0035] Figure 1This is a flowchart illustrating a method for power-off online batch firmware upgrade of an eMMC mass production tool according to an embodiment of the present invention. Detailed Implementation

[0036] The technical solution of the present invention will be clearly and completely described below with reference to the embodiments. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0037] This application provides a power-off online batch firmware upgrade method for eMMC mass production tools. It is used for firmware upgrades of eMMC-enabled boards / daughter cards, and for non-eMMC chip firmware upgrades. The aim is to solve the problems of existing eMMC board / daughter card firmware upgrade processes requiring physical power-off, being cumbersome, inefficient, and lacking standardized upgrade verification steps. The method first obtains a list of devices to be upgraded, sends a vendor_reboot command to each device to put it into bootrom state, then retrieves the devices in bootrom state again and performs batch firmware upgrades. After the upgrade is complete, the devices are restarted, and the upgrade success is checked by comparing the SVN version. The entire process is automated, reducing manual intervention and improving the mass production efficiency and upgrade success rate of eMMC-enabled boards / daughter cards. A flowchart of the method is shown below. Figure 1 As shown, the specific steps include:

[0038] S1. Initialize the thread, receive the firmware path and active device list, and obtain the device information of the eMMC card / sub-card to be upgraded, including device ID, device path information, device SN and current device running status, etc.; ensure the integrity of the basic data for subsequent upgrade operations, and prepare for batch upgrades and subsequent verification.

[0039] S2. Iterate through each eMMC card / daughter card to be upgraded and check if its device information is complete. If the device information is incomplete, record the error and accumulate the failure count. If the device information is complete, send a preset restart command to the corresponding eMMC card / daughter card to be upgraded to restart it online and enter the bootrom state. After sending the preset restart command, wait for a preset time to ensure that it is fully in the bootrom state to avoid subsequent identification failures due to the device not being ready.

[0040] S3. After sending a preset reboot command to all eMMC unlocking cards / daughters with complete device information, rescan them and identify eMMC unlocking cards / daughters in bootrom status. If no eMMC unlocking card / daughter in bootrom status is identified, record the error and accumulate the failure count. If an eMMC unlocking card / daughter in bootrom status is identified, proceed to step S4. Ensure that the upgrade operation is performed only on devices in the target status.

[0041] S4. For the eMMC open card / daughter card with the identified bootrom status, use a firmware download tool to perform firmware download operation, and at the same time provide real-time feedback on download progress and status during the download process; to ensure that operators can monitor the upgrade status in real time and promptly detect and handle download anomalies;

[0042] S5. After the firmware download is complete, perform a reboot operation on each eMMC card / daughter card in bootrom state to exit bootrom state and enter production firmware mode. After the eMMC card / daughter card in production firmware mode is running stably, read its version information and then compare the version information with the preset target version to verify whether the upgrade is successful. If the version information is consistent with the preset target version, the upgrade is successful, the success count is accumulated, and a progress signal is sent. If the version information is inconsistent with the preset target version, the upgrade fails, the failure count is accumulated, and error details are recorded. The error details include the device ID, version information, and the difference between the version information and the preset target version.

[0043] S6. After traversing all eMMC activation cards / daughters to be upgraded, determine if any eMMC activation cards / daughters have been successfully upgraded. If no successful upgrades are found, send a failure signal and display all error messages. If successful upgrades are found, further determine if any upgrades have failed. If no upgrades have failed, send a first success signal to indicate that all eMMC activation cards / daughters to be upgraded have downloaded and verified successfully. If upgrades have failed, send a second success signal to display the number of successful and failed eMMC activation cards / daughters to be upgraded and the reasons for the failures. Finally, send a rescan signal to scan all eMMC activation cards / daughters to be upgraded, update the status of all eMMC activation cards / daughters to be upgraded, and complete the entire upgrade process.

[0044] For example, the preset reboot command mentioned in step S2 includes a reboot command that can put the eMMC card / daughter card into the bootrom state without physical power failure. In this embodiment, the vendor_reboot command is used.

[0045] For example, the preset time mentioned in step S2 is dynamically adjusted according to the device model and mass production scenario of the eMMC card / daughter card. It is necessary to ensure that the eMMC card / daughter card is fully entered into the bootrom state. In this embodiment, the preset time is set to 3 seconds.

[0046] For example, the firmware download tool mentioned in step S4 includes a tool that supports firmware download of eMMC card / daughter card in bootrom mode and can provide feedback on the download progress. In this embodiment, the firmware download tool used is T6x0Service.

[0047] For example, the preset target version mentioned in step S5 includes the SVN version. The SVN version comparison method can be replaced by other version verification methods, as long as it can accurately determine whether the production firmware and the target version are consistent, ensuring a successful upgrade.

[0048] For example, multiple eMMC card opening / daughter card processing can be carried out in a multi-threaded parallel or multi-process parallel manner to achieve batch upgrades.

[0049] For example, this application also discloses a power-off online batch firmware upgrade system for eMMC mass production tools, which utilizes the power-off online batch firmware upgrade method for eMMC mass production tools described above, including:

[0050] Device Management Module: Used to obtain and manage the list of eMMC cards / daughters to be upgraded, initialize threads, receive firmware paths and active device information, and obtain device information of the eMMC cards / daughters to be upgraded; it also supports reading the device status before and after the upgrade, providing data support for subsequent operations;

[0051] The bootrom control module is used to send a preset reboot command to each eMMC card / daughter card to be upgraded, so that the eMMC card / daughter card to be upgraded reboots online and enters the bootrom state, and waits for a preset time to ensure that it is fully in the bootrom state; ensuring that the card / daughter card is fully in the target state, replacing the original online reboot module and meeting the command requirements;

[0052] Device identification module: After sending a preset reboot command to all eMMC cards / daughters with complete device information to be upgraded, it rescans them and identifies eMMC cards / daughters with a bootrom status; it extracts device path and ID information, and at the same time, it parses the firmware file path to extract firmware version information in preparation for firmware download;

[0053] Firmware download module: Used to perform firmware download operations on the identified bootrom-state eMMC open card / daughter card using a firmware download tool, while providing real-time feedback on download progress and status during the download process; ensuring that the download process is monitorable and traceable;

[0054] Upgrade verification module: Performs a reboot operation on each eMMC card / daughter card in bootrom state to exit bootrom state and enter production firmware mode; after the eMMC card / daughter card in production firmware mode is running stably, reads its version information, and then compares the version information with the preset target version to verify whether the upgrade is successful; records the version comparison results and error details to provide a basis for result processing;

[0055] Results Processing Module: This module summarizes the comparison results from the upgrade verification module, counts the number of successful and failed devices, records error details, sends corresponding success, failure, or partial success signals based on the statistical results, generates a detailed upgrade report, sends a device rescan signal, and updates the current status of all eMMC card opening boards / daughters.

[0056] In summary, this application utilizes a technology that eliminates the need for physical power-off by sending a `vendor_reboot` command to bring eMMC unlocking boards / daughters into bootrom mode online. This replaces the cumbersome traditional method of physical power-off and short-circuiting. This technology is applicable to boards / daughters, not non-eMMC chips. The complete automated process of this application includes obtaining a device list, sending the `vendor_reboot` command, identifying the bootrom device, firmware upgrade, and SVN version comparison and verification after reboot, achieving closed-loop control for batch upgrades and accurate verification of boards / daughters. The batch processing flow for multiple eMMC unlocking boards / daughters, through thread initialization and device traversal, enables parallel upgrades of multiple boards / daughters, improving mass production efficiency. The verification mechanism comparing the upgraded production firmware with the SVN version ensures accurate determination of upgrade results, improving upgrade quality and reliability. The automatic device status update mechanism after board / daughter upgrades synchronizes the latest status of the eMMC unlocking boards / daughters in real time by sending a rescan signal, facilitating seamless integration with subsequent production processes.

[0057] The above description is merely a preferred embodiment of the present invention. It should be understood that the present invention is not limited to the forms disclosed herein and should not be construed as excluding other embodiments. It can be used in various other combinations, modifications, and environments, and can be altered within the scope of the concept described herein through the above teachings or related technologies or knowledge. Modifications and variations made by those skilled in the art that do not depart from the spirit and scope of the present invention should be within the protection scope of the appended claims.

Claims

1. A method for power-off online batch firmware upgrade of an eMMC mass production tool, characterized in that, Includes the following steps: S1. Initialize the thread, receive the firmware path and active device list, and obtain the device information of the eMMC card / daughter card to be upgraded, including device ID, device path information, device SN and current device running status; S2. Iterate through each eMMC card to be upgraded, check if its device information is complete. If the device information is incomplete, record the error and accumulate the failure count. If the device information is complete, send a preset restart command to the corresponding eMMC card to be upgraded, so that it restarts online and enters the bootrom state. After sending the preset restart command, wait for a preset time to ensure that it fully enters the bootrom state. S3. After sending a preset reboot command to all eMMC card opening boards / daughters with complete device information, rescan them and identify eMMC card opening boards / daughters in the bootrom state; if no eMMC card opening board / daughter in the bootrom state is identified, record the error and accumulate the failure count; if an eMMC card opening board / daughter in the bootrom state is identified, proceed to step S4. S4. For the eMMC open card / daughter card with the identified bootrom status, use a firmware download tool to perform firmware download operation, and at the same time provide real-time feedback on the download progress and status during the download process; S5. After the firmware download is complete, perform a reboot operation on each eMMC card / daughter card in the bootrom state to exit the bootrom state and enter the production firmware mode. After the eMMC card / daughter card in the production firmware mode is running stably, read its version information, and then compare the version information with the preset target version to verify whether the upgrade is successful. If the version information is consistent with the preset target version, the upgrade is successful, the success count is accumulated, and a progress signal is sent. If the version information is inconsistent with the preset target version, the upgrade fails, the failure count is accumulated and the error details are recorded. The error details include the device ID, the version information and the difference between the preset target version. S6. After traversing all eMMC activation cards / daughters to be upgraded, determine if there are any successfully upgraded eMMC activation cards / daughters; if there are no successfully upgraded ones, send a failure signal and display all error messages. If there are successful upgrades, then further determine if there are any failed upgrades. If there are no failed upgrades, then send the first success signal to prompt all eMMC cards / sub-cards to be upgraded to download and verify successfully. If any upgrades fail, a second success signal is sent, displaying the number of successful and failed eMMC activation cards / daughters to be upgraded and the reasons for the failures. Finally, a rescan signal is sent to scan all eMMC activation cards / daughters to be upgraded and update the status of all eMMC activation cards / daughters to be upgraded.

2. The method for power-off online batch firmware upgrade of an eMMC mass production tool according to claim 1, characterized in that: The preset reboot command mentioned in step S2 includes a reboot command that can put the eMMC card / daughter card into bootrom state without physical power failure.

3. The method for power-off online batch firmware upgrade of an eMMC mass production tool according to claim 1, characterized in that: The preset time mentioned in step S2 is dynamically adjusted according to the device model and mass production scenario of the eMMC card / daughter card, and it is necessary to ensure that the eMMC card / daughter card is fully entered into the bootrom state.

4. The method for power-off online batch firmware upgrade of an eMMC mass production tool according to claim 1, characterized in that: The firmware download tool mentioned in step S4 includes a tool that supports downloading firmware for eMMC unlocking boards / daughter cards in bootrom mode and can provide feedback on the download progress.

5. The method for power-off online batch firmware upgrade of an eMMC mass production tool according to claim 1, characterized in that: The preset target version mentioned in step S5 includes the SVN version.

6. The method for power-off online batch firmware upgrade of an eMMC mass production tool according to claim 1, characterized in that: The processing of multiple eMMC card opening boards / daughter cards adopts a multi-threaded parallel or multi-process parallel approach to achieve batch upgrades.

7. A power-off online batch firmware upgrade system for eMMC mass production tools, employing the power-off online batch firmware upgrade method for eMMC mass production tools as described in any one of claims 1-6, characterized in that... include: Device Management Module: Used to obtain and manage the list of eMMC cards / daughters to be upgraded, initialize threads, receive firmware paths and active device information, and obtain device information of eMMC cards / daughters to be upgraded; The bootrom control module is used to send a preset restart command to each eMMC card / daughter card device to be upgraded, so that the eMMC card / daughter card device to be upgraded restarts online and enters the bootrom state, and waits for a preset time to ensure that it is fully in the bootrom state. Device identification module: After sending a preset reboot command to all eMMC card opening boards / daughters with complete device information, it rescans them and identifies eMMC card opening boards / daughters with a bootrom status. Firmware download module: Used to perform firmware download operations on the identified bootrom-state eMMC open card / daughter card using a firmware download tool, and provide real-time feedback on download progress and status during the download process; Upgrade verification module: Perform a reboot operation on each eMMC card / daughter card in bootrom state to exit bootrom state and enter production firmware mode; after the eMMC card / daughter card in production firmware mode is running stably, read its version information, and then compare the version information with the preset target version to verify whether the upgrade is successful. Record version comparison results and error details to provide a basis for result processing; Results Processing Module: This module summarizes the comparison results from the upgrade verification module, counts the number of successful and failed devices, records error details, sends corresponding success, failure, or partial success signals based on the statistical results, generates a detailed upgrade report, sends a device rescan signal, and updates the current status of all eMMC card opening boards / daughters.

Images