Chip debugging enabling control method

Abstract

The invention provides a chip debugging control method, which is used for controlling a debugging terminal to debug a chip to be debugged, and comprises the following steps: authenticating the identity legality of the debugging terminal through a security debugging authentication system of the chip to be debugged; only when it is determined that the debugging terminal passes the identity legality authentication, allowing the debugging terminal to debug the to-be-debugged chip through a debugging interface, otherwise, not allowing the debugging terminal to debug the to-be-debugged chip through the debugging interface. The debugging requirement of the chip in each stage is met, the safety requirement is met, and the safety of assets or information in the chip is effectively protected.

Description

technical field [0001] The invention belongs to the field of chip design, in particular to a chip debugging enable control method. Background technique [0002] Chip debugging is an essential process in the chip design process. Controlling the debugging and enabling of the chip plays a vital role in protecting the assets and information security in the chip. A traditional solution for controlling chip debug enablement uses a hierarchical control method combining software and hardware, and hardware debug enable control has a higher priority than software debug enable control. If the hardware disables debugging, the debugging will be disabled; if the hardware does not disable debugging and the software debug enable control is disabled by hardware, then allow debugging; if the hardware does not disable debugging and the software debug enable control is enabled by hardware, then according to the software Debug enable control to decide whether to allow debugging, if the softwar...

AI Technical Summary

Problems solved by technology

[0011] 1) For Scenario 1 in Table 1, the chip cannot be debugged through the debugging interface. Once a functional problem occurs in the normal operation of the chip after productization, it will not be possible to debug and analyze the chip to accurately locate the cause of the problem.

[0012] 2) For Scenario 2 in Table 1, the chip is always in a debuggable state during the development and testing process, and there is no security certification control for the enabling of the debugging interface, resulting in assets and confidential information that need to be protected in the chip May be leaked, resulting in loss of interests for chip manufacturers or equipment manufacturers or end customers

[0013] 3) For scene 4 in Table 1, it is often used when the chip (in the setting of scene 3) needs to be debugged after a problem occurs during operation, and the software debugging enable control occurs in the startup code of the chip (Boot- Code), in general, in order to achieve a safe boot, the startup code of the chip is solidified, once the problem occurs in the startup phase of the chip, it will not be possible to debug and analyze the chip to accurately locate the cause of the problem

[0017] 1) The knock code is preset and fixed, and it is easy to leak; 2) The knock code is easy to crack, for example, it can be cracked by detecting the debug connection and the debug interface between the chip, or it can be cracked by multiple attempts. so there is no real security

Images