A workshop FCT program generation injection method for thermal management domain controller

Abstract

The present invention provides a workshop FCT program generation and injection method for a thermal management domain controller, which relates to the field of FCT program generation and injection, and includes the following steps: S1, changing the software and hardware version number through a postbuild script; S2, generating information security related information through a configuration tool; S3, opening or closing the program flashing port through a protocol; S4, reading multiple burning programs in a test circuit board, merging them into one through a script, and then burning them to a hardware circuit board. This application can automatically generate software and hardware version number information without compiling the program; can automatically generate information security related information without changing the program; open or close security protection through a protocol to achieve multiple flashing; and merge multiple burning FCT programs into one, thereby improving efficiency.

Description

Technical Field

[0001] The present invention relates to the technical field of FCT program generation, and in particular to a workshop FCT program generation and injection method for a thermal management domain controller. Background Art

[0002] The thermal management domain controller TMCU is a new type of product, and it is necessary to perform FCT program (hardware test program) on it during product design.

[0003] During software system development, if the software system has system errors due to its own defects or other reasons, or if users put forward new requirements, the software needs to be improved. In the traditional controller, the corresponding code needs to be changed, compiled, generated and burned during the software improvement process. The whole procedure is cumbersome and has a long cycle, which makes it difficult to meet the efficiency of the production line.

[0004] Currently, most software programs choose full upgrade as the upgrade solution, which will lead to low generation efficiency and inconvenience for batch updates. Summary of the invention

[0005] The technical problem to be solved by the present invention is that the controller needs to comprehensively change the code, compile, generate and burn it to meet the emerging needs. In order to overcome the defects of the above-mentioned prior art, the present invention provides a workshop FCT program generation and injection method for a thermal management domain controller.

[0006] The present invention provides a workshop FCT program generation and injection method for a thermal management domain controller, comprising the following steps:

[0007] S1. Change the software and hardware version numbers through the postbuild script;

[0008] S2. Generate information security related information through configuration tools;

[0009] S3, open or close the program flash port through the protocol;

[0010] S4, read multiple burning programs in the test circuit board, merge them into one through the script, and then burn it to the hardware circuit board.

[0011] Compared with the prior art, the workshop FCT program generation and injection method for a thermal management domain controller in the present application has the following advantages: software and hardware version number information can be automatically generated without compiling the program; information security related information can be automatically generated without changing the program; security protection can be turned on or off through the protocol to achieve multiple flashing; multiple FCT programs can be burned and merged into one, thereby improving efficiency.

[0012] In a possible implementation manner, step S1 specifically includes the following steps:

[0013] S11. Install HxDSetup compiler;

[0014] S12. Open the postbuild.bin file through the HxDSetup compiler, modify the DID data of the software and hardware version, and save it;

[0015] S13, open the batch processing program and generate the corresponding postbuild.hex file;

[0016] S14. Use the merge script to merge the postbuild.hex file with the original pbl.hex file to generate a new pbl_postbuild.hex file.

[0017] Compared with the existing technology, there is no need to change the original program, which prevents human errors during modification and compilation. The postbuild method can quickly complete the hex file and can operate in batches efficiently.

[0018] In a possible implementation, step S2 specifically includes the following steps:

[0019] S21, program nvr into the hardware circuit board through Program;

[0020] S22, batch erase flash;

[0021] S23, generating an NVR.hex file containing information security related information through GenerateHex;

[0022] S24. Open the NVR.hex file through HexView, and open pbl_postbuild.hex to merge them to generate pbl_postbuild_NVR.hex.

[0023] Compared with the existing technology, there is no need to change the original program, which prevents human errors during modification and compilation, and the configuration tool is convenient and efficient.

[0024] In a possible implementation manner, step S3 specifically includes the following steps:

[0025] S31, setting a secret key through a protocol;

[0026] S32, determining whether it is necessary to flash information through the program flash port;

[0027] If so, send the secret key through the protocol to unlock the program flash port and go to step S4; otherwise, lock the program flash port.

[0028] Compared with the existing technology, setting the secret key through the protocol can be done multiple times, which is convenient and efficient, and can ensure information security.

[0029] In a possible implementation, step S4 includes the following steps:

[0030] S41, the host computer burns the pbl_postbuild_NVR.hex program to the test circuit board;

[0031] S42, the host computer burns SBL and FCT.APP programs to the test circuit board;

[0032] S43, jlink test program reads the burning program in the test circuit board and obtains A.hex, B.hex, and C.hex;

[0033] S44. Open HexView, merge A.hex, B.hex, and C.hex to generate FCT_SBL_PBL.hex, and burn FCT_SBL_PBL.hex to the hardware circuit board.

[0034] Compared with the existing technology, only one program file needs to be burned to realize complete program entry, which improves efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] Figure 1 A flow chart of a workshop FCT program generation injection method for a thermal management domain controller of the present invention. DETAILED DESCRIPTION

[0036] First, those skilled in the art should understand that these implementations are only used to explain the technical principles of the embodiments of the present application, and are not intended to limit the protection scope of the embodiments of the present application. Those skilled in the art can make adjustments to them as needed to adapt to specific application scenarios.

[0037] In the description of the embodiments of the present application, it should be noted that, unless otherwise clearly specified and limited, the terms "connected" and "connection" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be directly connected or indirectly connected through an intermediate medium. For ordinary technicians in this field, the specific meanings of the above terms in the embodiments of the present application can be understood according to specific circumstances.

[0038] The present application is further described in detail below with reference to the accompanying drawings and specific embodiments.

[0039] See also Figure 1 As shown, the embodiment of the present application discloses a workshop FCT program generation and injection method for a thermal management domain controller, comprising the following steps:

[0040] S1. Change the software and hardware version numbers through the postbuild script;

[0041] S2. Generate information security related information through configuration tools;

[0042] S3, open or close the program flash port through the protocol;

[0043] S4, read multiple burning programs in the test circuit board, merge them into one through the script, and then burn it to the hardware circuit board.

[0044] Software and hardware version number information can be automatically generated without compiling the program; information security related information can be automatically generated without changing the program; security protection can be turned on or off through the protocol to achieve multiple flashing; multiple FCT burning programs can be merged into one to improve efficiency.

[0045] Wherein, in step S1, the following steps are specifically included:

[0046] S11. Install HxDSetup compiler;

[0047] S12. Open the postbuild.bin file through the HxDSetup compiler, modify the DID data of the software and hardware version, and save it;

[0048] S13, open the batch processing program and generate the corresponding postbuild.hex file;

[0049] S14. Use the merge script to merge the postbuild.hex file with the original pbl.hex file to generate a new pbl_postbuild.hex file.

[0050] When the original program needs to be changed, you only need to use the postbuild script of HxDSetup compiler to open the postbuild.bin file, and then change the version number of related software and hardware to generate postbuild.hex; then use the merge script to merge it with the original pbl.hex file to generate a new pbl_postbuild.hex file.

[0051] There is no need to change the original program, which prevents human errors during changes and compilation, and the postbuild method can quickly complete the hex file. Compared with the original change of the original program for compilation, the version numbers of the software and hardware are directly modified through the compiler, and then merged through the script. The operation of changing the version numbers of the software and hardware in this embodiment is simple and efficient.

[0052] Wherein, in step S2, the following steps are specifically included:

[0053] S21, program nvr into the hardware circuit board through Program;

[0054] S22, batch erase flash;

[0055] S23, generating an NVR.hex file of information security related information (NVR) through GenerateHex;

[0056] S24. Open the NVR.hex file through HexView, and open pbl_postbuild.hex to merge them to generate pbl_postbuild_NVR.hex.

[0057] First, use the configuration tool to configure the corresponding values, and then generate NVR.hex; then use the merge script of HexView to merge it with pbl_postbuild.hex to generate pbl_postbuild_NVR.hex.

[0058] There is no need to change the original program, which can effectively prevent human errors during changes and compilation. Compared with the original need to configure relevant registers and then set them by comparing with the chip manual, the operation is cumbersome and requires changing the original program. The operation of generating information security related information in this embodiment is convenient and efficient.

[0059] Wherein, in step S3, the following steps are specifically included:

[0060] S31, setting a secret key through a protocol;

[0061] S32, determining whether it is necessary to flash information through the program flash port;

[0062] If so, send the secret key through the protocol to unlock the program flash port and go to step S4; otherwise, lock the program flash port.

[0063] The program sets a secret key through the protocol, and then sends the secret key through the protocol to unlock the flash port, allowing multiple flashings to be performed, facilitating subsequent maintenance and problem finding.

[0064] Compared with the original hardware's conformal coating writing port, the writing port of this embodiment can prevent information from being written at one time, and is easy to operate and can efficiently realize information reading and writing.

[0065] Wherein, in step S4, the following steps are included:

[0066] S41, the host computer burns the pbl_postbuild_NVR.hex program to the test circuit board;

[0067] S42, the host computer burns SBL and FCT.APP programs to the test circuit board;

[0068] S43, jlink test program reads the burning program in the test circuit board and obtains A.hex, B.hex, and C.hex;

[0069] S44. Open HexView, merge A.hex, B.hex, and C.hex to generate FCT_SBL_PBL.hex, and burn FCT_SBL_PBL.hex to the hardware circuit board.

[0070] Compared with the original burning of FCT program, it is necessary to burn the pbl_postbuild_NVR.hex file first, and then burn the SBL and FCT.APP programs through the host computer. In this way, the production line requires two processes and needs to be done twice. However, in this embodiment, after merging multiple programs through the above method, each hardware circuit board in the workshop only needs to be burned in sequence to complete the burning, which improves efficiency.

[0071] In the description of the embodiments of the present application, it should be noted that in the description of the present application, terms such as "inside" and "outside" indicating directions or positional relationships are based on the directions or positional relationships shown in the drawings. This is only for the convenience of description, and does not indicate or imply that the device or component must have a specific orientation, be constructed and operated in a specific orientation. Therefore, it cannot be understood as a limitation on the present application.

[0072] In the description of the present application, the description with reference to the terms "one embodiment", "some embodiments", "in the present embodiment", "specific example", or "some examples" etc. means that the specific features, mechanisms, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, mechanisms, materials or characteristics described may be combined in a suitable manner in any one or more embodiments or examples. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradiction.

[0073] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.

Claims

1. A workshop FCT program generation and injection method for a thermal management domain controller, characterized in that: The steps include: S1. Change the software and hardware version numbers through the postbuild script; S2. Generate information security related information through configuration tools; S3, open or close the program flash port through the protocol; S4, read multiple burning programs in the test circuit board, merge them into one through the script, and then burn it to the hardware circuit board.

2. The workshop FCT program generation and injection method for a thermal management domain controller according to claim 1 is characterized in that: In step S1, the following steps are specifically included: S11. Install HxDSetup compiler; S12. Open the postbuild.bin file through the HxDSetup compiler, modify the DID data of the software and hardware version, and save it; S13, open the batch processing program and generate the corresponding postbuild.hex file; S14. Use the merge script to merge the postbuild.hex file with the original pbl.hex file to generate a new pbl_postbuild.hex file.

3. The workshop FCT program generation and injection method for a thermal management domain controller according to claim 2 is characterized in that: In step S2, the following steps are specifically included: S21, program nvr into the hardware circuit board through Program; S22, batch erase flash; S23, generating an NVR.hex file containing information security related information through GenerateHex; S24. Open the NVR.hex file through HexView, and open pbl_postbuild.hex to merge them to generate pbl_postbuild_NVR.hex.

4. The workshop FCT program generation and injection method for a thermal management domain controller according to claim 1 is characterized in that: In step S3, the following steps are specifically included: S31, setting a secret key through a protocol; S32, determining whether it is necessary to flash information through the program flash port; If so, send the secret key through the protocol to unlock the program flash port and go to step S4; otherwise, lock the program flash port.

5. The workshop FCT program generation and injection method for a thermal management domain controller according to claim 3 is characterized in that: In step S4, the following steps are included: S41, the host computer burns the pbl_postbuild_NVR.hex program to the test circuit board; S42, the host computer burns SBL and FCT.APP programs to the test circuit board; S43, jlink test program reads the burning program in the test circuit board and obtains A.hex, B.hex, and C.hex; S44. Open HexView, merge A.hex, B.hex, and C.hex to generate FCT_SBL_PBL.hex, and burn FCT_SBL_PBL.hex to the hardware circuit board.

Images