Embedded system cross-debugging method and device

Abstract

The invention relates to a cross-debugging method of embedded system. The cross-debugging method comprises the following steps that S1, electrified starting is performed, and an operating system is loaded and operates; S2, whether a program is required to be updated or not is judged, if yes, the step S3 is executed, and if not, the step S9 is executed; S3, the operating system loads and operates a program updating module; S4, a JTAG downloads a modified application program into a memory; S5, the JTAG writes program information into the predetermined memory; S6, the program updating module writes the application program of the memory into an external storage firmware zone according to program information; S7, a record pointing to the application program is added in a firmware zone file system directory entry; S8, updating completion is prompted, and restarting is performed; S9, a normal application loading state is enabled, and the newest directory entry corresponding to the application is retrieved from the tail to the head of the firmware zone file system directory entry; S10, the application program is loaded through the newest directory entry, operates and is debugged. The invention further provides a device for achieving the method.

Description

Technical field [0001] The invention relates to a debugging method and device, in particular to an efficient embedded system cross debugging method and device. Background technique [0002] Embedded system cross debugging methods are generally divided into two types, one is the on-chip debugging method based on JTAG, and the other is the remote debugging method based on debugging agent. [0003] See figure 1 , Which is the connection block diagram of the JTAG-based on-chip debugging method. JTAG is an international standard chip test protocol, and most CPU systems currently support JTAG. The most prominent representative of the JTAG-based on-chip debugging method is the JLink debugger, which defines a software debugging level RDI interface standard, and then the JLink debugger converts the RDI interface issued by the debugging environment software (IAR, KEIL, etc.) into JTAG commands. Debug the chip. This method is mostly suitable for the debugging of the bottom layer of the emb...

AI Technical Summary

Problems solved by technology

[0014] However, the biggest problem with this debugging method in the prior art is that the efficiency is very low

Because every time the program is modified, the entire firmware must be repackaged, which generally takes 10 minutes or even longer; at the same time, the entire firmware must be reprogrammed, and the external memory must be erased before programming, which also takes a lot of time

In addition, since programming firmware and JTAG debugging are two different tools, it takes a lot of time to switch back and forth

Images