From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 120494 invoked by alias); 3 Apr 2015 20:21:12 -0000 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 Received: (qmail 120479 invoked by uid 89); 3 Apr 2015 20:21:12 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.2 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,T_RP_MATCHES_RCVD autolearn=no version=3.3.2 X-HELO: OARmail.OARCORP.com Received: from oarmail.oarcorp.com (HELO OARmail.OARCORP.com) (67.63.146.244) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 03 Apr 2015 20:21:11 +0000 Received: from [192.168.1.169] (192.168.1.169) by OARmail.OARCORP.com (192.168.2.2) with Microsoft SMTP Server (TLS) id 8.3.342.0; Fri, 3 Apr 2015 15:21:07 -0500 Message-ID: <551EF633.9030309@oarcorp.com> Date: Fri, 03 Apr 2015 20:21:00 -0000 From: Joel Sherrill User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: "gdb@sourceware.org" Subject: Re: lm32 simulator configuration file question References: <551DC087.7040103@oarcorp.com> <20150403014149.GJ22171@vapier> In-Reply-To: <20150403014149.GJ22171@vapier> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2015-04/txt/msg00009.txt.bz2 On 4/2/2015 8:41 PM, Mike Frysinger wrote: > On 02 Apr 2015 17:19, Joel Sherrill wrote: >> RTEMS has a BSP for the lm32 which runs on the simulator in gdb. >> Based on our wrapper scripts and READMEs, this is how the simulator >> is invoked in gdb: >> >> tar sim --hw-device lm32cpu \ >> --hw-device "lm32uart/reg 0x80006000 0x100" \ >> --hw-device "/lm32uart > int int0 /lm32cpu" \ >> --hw-device "lm32timer/reg 0x80002000 0x80" \ >> --hw-device "/lm32timer > int int1 /lm32cpu" \ >> --memory-region 0x08000000,0x4000000 > you can pass --hw-file to target sim too Thank you. I updated the file to this: ======================= /lm32cpu /lm32uart@0x80006000/reg 0x80006000 0x100 /lm32uart > int int0 /lm32cpu /lm32timer@0x80002000/reg 0x80002000 0x80 /lm32timer > int int1 /lm32cpu ======================= And that works with gdb using the tar sim command below. tar sim --hw-file lm32_evr.conf --memory-region 0x08000000,0x4000000 But nothing comes out from the same executable using run lm32-rtems4.11-run --hw-file lm32_evr.conf --memory-region 0x08000000,0x4000000 .hello.exe Does that make any sense to you? >> That works great. When we use lm32-rtems4.11-run, you are supposed >> to provide a hw description file matching those arguments. This is >> the file we are using: >> >> ====================== >> lm32cpu >> lm32uart/reg 0x80006000 0x100 >> /lm32uart > int int0 /lm32cpu >> lm32timer/reg 0x80002000 0x80 >> /lm32timer > int int1 /lm32cpu > put a leading / for each one missing it > -mike -- Joel Sherrill, Ph.D. Director of Research & Development joel.sherrill@OARcorp.com On-Line Applications Research Ask me about RTEMS: a free RTOS Huntsville AL 35805 Support Available (256) 722-9985