CN101908016A - Method for managing debugging information and break point of multi-core embedded device - Google Patents
Method for managing debugging information and break point of multi-core embedded device Download PDFInfo
- Publication number
- CN101908016A CN101908016A CN2009101426693A CN200910142669A CN101908016A CN 101908016 A CN101908016 A CN 101908016A CN 2009101426693 A CN2009101426693 A CN 2009101426693A CN 200910142669 A CN200910142669 A CN 200910142669A CN 101908016 A CN101908016 A CN 101908016A
- Authority
- CN
- China
- Prior art keywords
- program
- identification code
- development environment
- storage
- debugging information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The invention relates to a method for managing debugging information and a break point of a multi-core embedded device. The method for managing the debugging information is used for debugging a multi-core embedded processor by an integrated development environment. The multi-core embedded processor comprises cores and an external memory, wherein the cores comprise a program memory and a reference memory, a program to be loaded is stored in the external memory, and the integrated development environment has the debugging information corresponding to the program in the program memory. The method comprises the following steps of: embedding a program identification code in a program reference; writing the program identification code into the reference memory; dynamically loading the program to the program memory from the external memory; and sending an event to the integrated development environment by a simulator according to the program identification code so as to update the debugging information.
Description
Technical field
The present invention system is about flush bonding processor, particularly for the debug and the breakpoint setting of multi-core embedded processor; More particularly, for the multi-core embedded processor that dynamic routine loads, the present invention proposes a kind of method of managing debug and breakpoint configuration information.
[prior art]
The embedded system in past is generally core, and application program is stored in the ROM (read-only memory) (ROM) in the chip.Yet embedded system is under the demand of stressing efficient and power saving at present, also begin to have had the design of on one chip, having taked the multinuclear heart, and consider following easily at cost and application, outside shared storage is set outside each core deposits shared program, the just execution of the program storage to core inside when needing from the external program memory dynamic load.
In view of this, United States Patent (USP) the 7th, 131 is addressed a kind of digital signal processor No. 114, and this digital signal processor contains the core processor that an external program memory and a plurality of external program memory therewith link.What deserves to be mentioned is that United States Patent (USP) the 7th, 131, the technical characterstic that is proposed for No. 114 are, place one or more breakpoint in this outside program storage, therefore the program in the program storage is externally carried out debug.
Yet in multi-core embedded processor, each core is identical haply, but external device (ED) that each core linked and hardware may differ widely, therefore when program stored in the external program memory is loaded on program in a certain core and remembers body, still need this core is carried out debug, and may change from the program that external program memory loaded at every turn, therefore need a kind of method to provide development environment to upgrade corresponding debugging information, so that this core is carried out suitable debug, and comprise United States Patent (USP) the 7th, there is no at interior prior art for 131, No. 114 and disclose any solution.
Summary of the invention
Because the shortcoming of prior art, for the multinuclear heart, have the embedded system of dynamic load programing power, when loading procedure from external program memory during, the invention provides mechanism and method that a kind of user of allowing correctly carries out the program trace debug and breakpoint (breakpoint) is set to core core internal program storer.
On the other hand, the present invention is embedded in program identification code (ID) in the program data or source code (binary code) of each program, supply firmware recognition and real-time update to need the information of loading procedure, and when simulator is carried out the instruction of program loading, by reading the program identification code in the data memory, know the program that is about to be loaded on core internal program storer, and send the debugger (debugger) of incident (Event) notice development environment, to carry out debug.
In addition, the present invention provides the loading procedure manager in development environment, is in charge of and provides loading procedure information to simulator interface, debugger and breakpoint management device.
The present invention increases the function of debugger, makes it to obtain the incident that simulator sends, and obtains loading procedure information according to the program identification code to the loading procedure manager, and upgrades the debugging information (runtime debug information) when carrying out according to this.
The present invention increases breakpoint management device function, preserve and manage the user to the set breakpoint of loading procedure, and after receiving the incident that simulator sends, preserve the module breakpoint of coated region, and the breakpoint that the program that is loaded was preserved last time is updated to debugger.
Particularly, the present invention provides a kind of debugging information management method, is used for integration development environment to debug that multi-core embedded processor carried out.Multi-core embedded processor comprises an external memory storage outside at least one core and the core, each core comprises program storage and data memory, and external memory storage has a program, and this integration development environment has debugging information and breakpoint configuration information to program in should program storage, to carry out debug.
In an embodiment of the present invention, the debugging information management method comprises following steps at least: embed the program identification code in the program data of program; The program identification code is write data memory; From the external memory storage loading procedure to program storage; The program identification code that simulator in the core is deposited according to data memory, the program of sending are loaded on the incident of program storage to integration development environment; Integration development environment upgrades debugging information in response to this incident.
In another embodiment of the present invention, the breakpoint management method comprises following steps at least: embed the program identification code in the program data of program; The program identification code is write data memory; From the external memory storage loading procedure to program storage; The program identification code that simulator in the core is deposited according to data memory, the program of sending are loaded on the incident of program storage to integration development environment; Integration development environment upgrades the breakpoint configuration information in response to this incident.
Description of drawings
By the narration and the conjunction with figs. explanation of following preferred embodiment, purpose of the present invention, feature and advantage will be more clear, wherein:
Fig. 1 is for digital signal processor among the present invention and be used for digital signal processor is carried out the computing machine of debug;
Fig. 2 shows the program storage of outside shared storage dynamic load program to the core;
Fig. 3 is the process flow diagram of debugging information management method in the embodiment of the invention;
Fig. 4 tables look-up for seeking of the embodiment of the invention; And
Fig. 5 is the process flow diagram of embodiment of the invention breakpoint management method.
Embodiment
The present invention is applied in flush bonding processor, particularly multi-core embedded processor.In example shown in Figure 1, digital signal processor (DSP) 10 is that (system on chip, SOC), (Integrated Development Environment, computing machine 15 IDE) links system single chip with carrying out integration development environment.Computing machine 15 can be desktop PC, have central processing unit 152 and storer 154, storer 154 for store debug programs 156, seek table look-up 158 and corresponding digital signals processor 10 in the debugging information and the breakpoint configuration information (not icon) of all programs, central processing unit 152 is carried out debug program (debugger) 156, and table look-up 158 to obtain suitable debugging information and breakpoint configuration information with reference to seeking, details is used for a certain particular core in the digital signal processor (DSP) 10 is carried out debug, after further will be specified in.
In addition, digital signal processor 10 is outside core 110 and 120, other contains outside shared storage 130, be used for store waiting for and dynamically loaded (load in) application program B or program C of program storage 114 to the core 110, and program B or program C contain more than one instruction (instruction) separately, wait for performed by core 110.In this example, outside shared storage 130 is embodied as the NAND flash ROM.It should be noted that as shown in Figure 2 at different time, program B or program C can be loaded on the identical address of program storage 114.
Fig. 3 is the process flow diagram of debugging information management method in the embodiment of the invention, cooperates Fig. 1 and Fig. 2 to further specify the present invention.In step 301, a certain ad-hoc location embeds program identification code (ID) in the program data (or source code) of program B or program C, and the program identification code is numeral normally, and its form can be word (word) or byte (byte).
In step 303, the firmware of core 110 reads the program identification code with said procedure B, and it is write to a certain particular address in the data memory 112.Simultaneously, in step 305, from outside shared storage 130, program B is loaded in the program storage 114 of core 110, and is arranged on after original program A.
Then, in step 307, (the in-circuit emulator of simulator in the core 110, ICE) the program identification code of the program B that deposits according to particular address in the aforesaid data storer 112, the debugger 156 of the incident that the program B of sending is loaded on program storage 114 to the integration development environment (computing machine) 15, preferably, the program identification code of program B also is transmitted in the lump.
In step 309, integration development environment 15 has loading procedure manager (not icon) and links up with debug program 156, and table look-up 158 with reference to seeking according to the program identification code of program B, the debugging information of extraction procedure B is further set up the debugging information of all programs in the program storage 114 instantly.
In step 311, the debugging information that debug program 156 is utilized in the step 309 again and set up carries out debug to core 110.And less importantly instantly (for example program C is replaced program B when the program C in the outside shared storage 130 is loaded on the program storage 114 of core 110, and the program B of occupying is originally in the address of program storage 114), can contrast abovementioned steps 303 to 311, upgrade debug program 156 needed debugging informations, make debug program 156 correctly to carry out debug core 110.
The further demonstration of Fig. 4 is sought and is tabled look-up 158, wherein seeking tables look-up 158 comprises at least three fields, is respectively program identification code 1581, program (file route that comprises the title of program B and the debugging information of program B in computing machine 10) 1583 and address (address of program in program storage 114) 1585.
Fig. 5 is the process flow diagram of embodiment of the invention breakpoint management method, cooperates Fig. 1 and Fig. 2 to further specify the present invention.Step 501 is to step 507, as abovementioned steps 301 to 307, do not add at this and to give unnecessary details.
In step 509, integration development environment 15 has breakpoint management device (not icon), according to the program identification code of program B, and the breakpoint configuration information of extraction procedure B.In this embodiment, the breakpoint configuration information of program B is comprised in the debugging information of program B in the abovementioned steps 309, therefore can utilize aforesaid seek tabling look-up 158 obtain the breakpoint configuration information of program B, do not seek and tabling look-up and do not need to keep in addition one.
In step 511, debug program 156 is utilized the breakpoint configuration information of program B again, and the program B that is loaded on program storage 114 is carried out debug.And less importantly instantly (for example program C is replaced program B when the program C in the outside shared storage 130 is loaded on the program storage 114 of core 110, and the program B of occupying is originally in the address of program storage 114), can contrast abovementioned steps 503 to 511, upgrade debug program 156 needed breakpoint configuration informations, make debug program 156 correctly to carry out debug the program C that is loaded on program storage 114.
Though the present invention discloses as above with embodiment; right its is not in order to limit the present invention; any have a technical field of the invention know the knowledgeable usually; without departing from the spirit and scope of the present invention; when doing various changes and retouching; and can think to carry other different embodiment, so protection scope of the present invention is when looking being as the criterion that claim scope of the present invention defined.
Claims (16)
1. debugging information management method, be used for the debug that an integration development environment is carried out a flush bonding processor, this flush bonding processor comprises an external memory storage outside at least one core and this core, this core comprises a program storage and a data memory, this external memory storage has one first program, and this integration development environment has debugging information to program in should program storage to carry out debug, and this method comprises:
(a1) in the program data of this first program, embed one first program identification code;
(b1) this first program identification code is write this data memory;
(c1) load this first program to this program storage from this external memory storage;
(d1) this first program identification code that a simulator is deposited according to this data memory in this core is sent this first program and is loaded on one first incident of this program storage to this integration development environment;
(e1) this integration development environment upgrades this debugging information in response to this first incident.
2. debugging information management method as claimed in claim 1, wherein step (d1) comprises and transmits this first program identification code to this integration development environment, and this step (e1) also comprises according to this first program identification code and upgrades this debugging information.
3. debugging information management method as claimed in claim 2, wherein step (e1) also comprises this integration development environment is obtained this first program according to this first program identification code debugging information.
4. debugging information management method as claimed in claim 3, wherein this integration development environment comprises to seek and tables look-up, and seeks tabling look-up according to this with this first program identification code and obtains the debugging information of this first program and step (e1) also comprises this integration development environment.
5. debugging information management method as claimed in claim 4, wherein this step (e1) also be included in this seek table look-up in the file route of debugging information of this first program of a field record.
6. debugging information management method as claimed in claim 4, wherein this step (e1) also be included in this seek table look-up in the program data of this first program of a field record in the address of this program storage.
7. the described debugging information management method of claim 1, wherein this first program identification code is a numeral in step (a1).
8. debugging information management method as claimed in claim 1, this external memory storage have one second program, and this method also comprises:
(a2) in the program data of this second program, embed one second program identification code;
(b2) replace this first program identification code in this data memory with this second program identification code;
(c2) load this second program to this program storage from this external memory storage;
(d2) this simulator this second program identification code of depositing according to this data memory is sent this second program and is loaded on one second incident of this program storage to this integration development environment; And
(e2) this integration development environment upgrades this debugging information in response to this second incident.
9. debugging information management method as claimed in claim 8, wherein step (c2) comprises from this external memory storage and loads the address that this second program should the first program place to this program storage Central Plains.
10. breakpoint management method, be used for the debug that an integration development environment is carried out a flush bonding processor, this flush bonding processor comprises an external memory storage outside at least one core and this core, this core comprises a program storage and a data memory, this external memory storage has one first program, and this integration development environment has breakpoint configuration information to program in should program storage to carry out debug, and this method comprises:
(a1) in the program data of this first program, embed one first program identification code;
(b1) this first program identification code is write this data memory;
(c 1) loads this first program to this program storage from this external memory storage;
(d1) this first program identification code that a simulator is deposited according to this data memory in this core is sent this first program and is loaded on one first incident of this program storage to this integration development environment;
(e1) this integration development environment upgrades this breakpoint configuration information in response to this first incident.
11. breakpoint management method as claimed in claim 10, wherein step (d1) comprises and transmits this first program identification code to this integration development environment, and this step (e1) also comprises this integration development environment and upgrades this breakpoint configuration information according to this first program identification code.
12. breakpoint management method as claimed in claim 11, wherein step (e1) also comprises this integration development environment and obtains breakpoint configuration information that should first program according to this first program identification code.
13. breakpoint management method as claimed in claim 10, wherein this first program identification code is a numeral in step (a1).
14. breakpoint management method as claimed in claim 10, this external memory storage have one second program, this method also comprises:
(a2) in the program data of this second program, embed one second program identification code;
(b2) replace this first program identification code in this data memory with this second program identification code;
(c2) load this second program to this program storage from this external memory storage;
(d2) this simulator this second program identification code of depositing according to this data memory is sent this second program and is loaded on one second incident of this program storage to this integration development environment; And
(e2) this integration development environment upgrades this breakpoint configuration information in response to this second incident.
15. breakpoint management method as claimed in claim 14, wherein step (c2) comprises from this external memory storage and loads the address that this second program should the first program place to this program storage Central Plains.
16. breakpoint management method as claimed in claim 15, wherein step (e2) also comprises this breakpoint configuration information of record renewal.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2009101426693A CN101908016A (en) | 2009-06-05 | 2009-06-05 | Method for managing debugging information and break point of multi-core embedded device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2009101426693A CN101908016A (en) | 2009-06-05 | 2009-06-05 | Method for managing debugging information and break point of multi-core embedded device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101908016A true CN101908016A (en) | 2010-12-08 |
Family
ID=43263480
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2009101426693A Pending CN101908016A (en) | 2009-06-05 | 2009-06-05 | Method for managing debugging information and break point of multi-core embedded device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101908016A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102096607A (en) * | 2010-03-16 | 2011-06-15 | 威盛电子股份有限公司 | Microprocessor and debugging method thereof |
| CN102662847A (en) * | 2012-04-23 | 2012-09-12 | 中颖电子股份有限公司 | System and method for program debugging of embedded system based on flash memory application |
| CN102841836A (en) * | 2012-08-28 | 2012-12-26 | 华为技术有限公司 | Testing method and programmable processor |
-
2009
- 2009-06-05 CN CN2009101426693A patent/CN101908016A/en active Pending
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102096607A (en) * | 2010-03-16 | 2011-06-15 | 威盛电子股份有限公司 | Microprocessor and debugging method thereof |
| CN102096607B (en) * | 2010-03-16 | 2014-10-29 | 威盛电子股份有限公司 | Microprocessor and debugging method thereof |
| CN102662847A (en) * | 2012-04-23 | 2012-09-12 | 中颖电子股份有限公司 | System and method for program debugging of embedded system based on flash memory application |
| CN102841836A (en) * | 2012-08-28 | 2012-12-26 | 华为技术有限公司 | Testing method and programmable processor |
| CN102841836B (en) * | 2012-08-28 | 2016-06-08 | 华为技术有限公司 | Testing method and programmable processor |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20210081258A1 (en) | Synthesis Path For Transforming Concurrent Programs Into Hardware Deployable on FPGA-Based Cloud Infrastructures | |
| US7131114B2 (en) | Debugger breakpoint management in a multicore DSP device having shared program memory | |
| CN100565472C (en) | A kind of adjustment method that is applicable to multiprocessor karyonide system chip | |
| US9846660B2 (en) | Heterogeneous multiprocessor platform targeting programmable integrated circuits | |
| CN109669729B (en) | Starting guide method of processor | |
| CN113835945B (en) | Chip testing method, device, equipment and system | |
| CN107704285B (en) | Multi-version configuration chip, system and method for field programmable gate array | |
| CN103049375B (en) | A kind of camera on-line debugging method | |
| CN105930186B (en) | The method for loading software of multi -CPU and software loading apparatus based on multi -CPU | |
| CN110515641A (en) | The update method of server firmware, apparatus and system | |
| CN106445544A (en) | Device and method for configuring or updating programmable logic device | |
| CN113672342B (en) | Embedded virtualization system, construction and test methods, terminal and medium | |
| CN106843918A (en) | The method for entering line program renewal to the embedded system including ARM chips, dsp chip and fpga chip | |
| CN114580344A (en) | Test excitation generation method, verification system and related equipment | |
| CN111913822B (en) | Inter-core communication mode based on AMP architecture | |
| CN101620542B (en) | Compatible updating method of ultrasonic imaging equipment software data | |
| CN108108191A (en) | A kind of collocation method of SOC chip and SOC chip cpu instruction collection | |
| CN106648758A (en) | Multi-core processor BOOT starting system and method | |
| CN111190855A (en) | FPGA multiple remote configuration system and method | |
| CN112579508A (en) | Data processing method, data processing device, equipment and storage medium | |
| CN102253844B (en) | Method and device for starting processor | |
| CN105224309A (en) | A kind of method and apparatus transferring function | |
| CN101667133B (en) | Method for updating firmware and chip updating firmware by using same | |
| CN101908016A (en) | Method for managing debugging information and break point of multi-core embedded device | |
| EP3540598A1 (en) | Method, device and server for checking a defective function |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Open date: 20101208 |