From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31131 invoked by alias); 26 Oct 2007 20:54:17 -0000 Received: (qmail 31122 invoked by uid 22791); 26 Oct 2007 20:54:16 -0000 X-Spam-Check-By: sourceware.org Received: from cerberus.pixim.com (HELO ext-mail.pixim.com) (12.162.1.22) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 26 Oct 2007 20:54:15 +0000 Received: from exchange.pixim.com ([172.16.0.13]) by ext-mail.pixim.com with esmtp (Exim 3.22 #1) id 1IlWC5-000451-00 for gdb@sourceware.org; Fri, 26 Oct 2007 13:54:13 -0700 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: Simulator newbie question Date: Fri, 26 Oct 2007 20:54:00 -0000 Message-ID: <16020FEDDBAF5440A59EB485AC75B2BB023075D3@exchange.pixim.com> From: "Mike Motyka" To: X-IsSubscribed: yes 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: 2007-10/txt/msg00279.txt.bz2 I'm looking at ISS options for SW bringup of a fairly elaborate SOC. The CPU will be a 9x6E_S so it looks like the ARMulator supports the instruction set. Our toolchain is gnu.=20 =20 I want to have a decent understanding of the architecture of the simulator before I start adding our stuff. I've done some cursory browsing of the source. Is there any design documentation for the GDB simulators in general and the ARMulator in particular? =20 Assuming that there is little documentation to be discovered :) I'll ask a few questions for the hell of it: =20 The GDB remote protocol is RSP - it's well documented and I assume this is what the ARMul speaks over the socket it opens? =20 Why are there references to RDP and RDI buried in the ARMul?=20 =20 Why is the "Angel" debug thingy from ARM in there? Is it present by default? I need a clean CPU. =20 It looks like armvirt.c is my attachment point for I/O though I'll probably have to get a hook into the instruction cycle somewhere to drive even a crude approximation of a timer. =20 All in all it looks like a decent place to start. =20 =20 Time is a great teacher, but unfortunately it kills all its pupils.~ Hector Berlioz