From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8131 invoked by alias); 6 Jul 2010 14:48:14 -0000 Received: (qmail 8114 invoked by uid 22791); 6 Jul 2010 14:48:13 -0000 X-SWARE-Spam-Status: No, hits=-0.5 required=5.0 tests=AWL,BAYES_40,MSGID_MULTIPLE_AT,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from cam-admin0.cambridge.arm.com (HELO cam-admin0.cambridge.arm.com) (217.140.96.50) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 06 Jul 2010 14:48:03 +0000 Received: from cam-owa2.Emea.Arm.com (cam-owa2.emea.arm.com [10.1.105.18]) by cam-admin0.cambridge.arm.com (8.12.6/8.12.6) with ESMTP id o66ElteI005878; Tue, 6 Jul 2010 15:47:55 +0100 (BST) Received: from e102139 ([10.1.255.212]) by cam-owa2.Emea.Arm.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 6 Jul 2010 15:47:55 +0100 From: "Will Deacon" To: "'xingxing pan'" , "gdb" , "Matthew Gretton-Dann" , References: In-Reply-To: Subject: RE: [Help] About the two debug modes of ARM Date: Tue, 06 Jul 2010 14:48:00 -0000 Message-ID: <005b01cb1d1a$366ab870$a3402950$@deacon@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2010-07/txt/msg00017.txt.bz2 Hi, > From the ARM11 reference manual, I know ARM11 has two debug modes, the > Halting mode and the Monitor Mode. > When we use debuggers to debug a program, often there are also two > modes. The remote debugging, the debugger runs on the host, the > debuggee runs on the target, and the debugger communicates with the > core through something like JTAG. The native debugging, the debugger > and debuggee run on the same computer. Right, those are the usual two debugging scenarios. > Here are my questions. > (1)Dose the Halting mode and the Monitor mode correspond to Remote > debugging and Native debugging respectively? Halting Mode means that the core is being debugged by an external JTAG debugger. Monitor mode means that the debugging is performed natively via co-processor or memory-mapped debug registers and debug events are handled via exceptions. > (2)Some cores like ARM920 don't have the Monitor mode. Dose it means > that when we are in native debugging on that cores, we can not use the > hardware breakpoints and watchpoints? You will need an external debugger in order to use hardware watchpoints or breakpoints on the ARM920. The 926 has monitor mode implemented using the EmbeddedICE-RT logic, so you can use the hardware resources there [with the relevant Kernel support]. Hope that helps, Will