debugging method for a multi-core central processing unit (CPU) board card

Abstract

The invention discloses a debugging method for a multi-core central processing unit (CPU) board card, which is characterized by comprising the following steps of: connecting the multi-core CPU board card to be tested with a memory in which a test program and a production program are stored; reading the test program from the memory and running the test program to obtain an execution result of at least one test item by the CPU core in the multi-core CPU board card; Determining a test result of the multi-core CPU board card according to the execution result; And if the test result is qualified, reading the production program from the memory and storing the production program by the multi-core CPU board card. The invention further discloses a multi-core central processing unit CPU board card debugging device and a mobile storage medium.

Description

technical field [0001] The invention relates to a multi-core processor, in particular to a method and device for debugging a multi-core central processing unit CPU board card, and a mobile storage medium. Background technique [0002] There are two main types of multi-core CPU board debugging currently used: [0003] (1) Download the test program to the multi-core CPU board through the programmer. After the test is completed, download the official production program through the programmer to the multi-core CPU board. [0004] (2) Insert the bootable rewritable memory written with the boot program into the chip socket of the multi-core CPU board, connect the PC through Ethernet after power-on, and use the PC to download the test program to the multi-core CPU board. Download the production program to the multi-core CPU board through the PC. [0005] Both of the above test methods have obvious disadvantages: [0006] Method (1) It is necessary to frequently use the programme...

AI Technical Summary

Problems solved by technology

[0006] Method (1) needs to frequently use the programmer to erase the program, and the production debugger needs to use the programmer to "connect the programmer-download the test program-observe the test results-download the production program-disconnect the programmer connection" on different boards, It is so difficult to ensure the correctness of the operation, which affects the quality of the product and greatly limits the production efficiency

Method (2) eliminates the cumbersome process of constantly plugging and unplugging the programmer, but it needs to operate a PC to complete the same repetitive work, and at the same time increases the complexity of the networking; and when multiple boards of the same type are connected to the same network at the same time , there will be network address conflicts and the test will fail; if the boards are set with different IPs, it will result in the need to prepare multiple boot memories for the same type of boards, and it is also prone to errors in testing and production programs.

Images