From: Joel Sherrill <joel.sherrill@oarcorp.com>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: lm32 simulator configuration file question
Date: Sat, 04 Apr 2015 00:00:00 -0000 [thread overview]
Message-ID: <551F2996.10003@oarcorp.com> (raw)
In-Reply-To: <20150403232113.GO22171@vapier>
On 04/03/2015 06:21 PM, Mike Frysinger wrote:
> On 03 Apr 2015 15:21, Joel Sherrill wrote:
>> 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?
> honestly, i know nothing about the lm32 arch. it has no testsuite, and i have
> no idea how to make example programs. so i can't really explain why it might
> not be working. with Blackfin, i use a leading slash on everything and it
> works for me.
>
sigh.. no testsuite. :(
Just to be clear, the simulator works when I invoke it inside
gdb. Just not via run. I am guessing some glue isn't right.
> could i convince you to write a simple hello world program ? first one that'd
> run in the virtual environment, and the one that'd setup& write to the serial
> port ? that way we could check the .s files into the testsuite dir, and i could
> try poking around the models.
>
I will build an lm32-elf toolset and throw that together. I am travelling
next week so it may be slow to happen since I am no expert at lm32
assembly language. But a hello world shouldn't be a problem.
> if the latest version isn't working, you could try grabbing previous releases of
> gdb and building the sim for that.
I tried a couple of older gdb's I had laying around. They behaved the
same. Not sure how far I would have to go back.
> -mike
--
-- Joel Sherrill
Ask me about RTEMS: a free RTOS
Support and Training Available
next prev parent reply other threads:[~2015-04-04 0:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-02 22:19 Joel Sherrill
2015-04-03 1:41 ` Mike Frysinger
2015-04-03 20:21 ` Joel Sherrill
2015-04-03 23:21 ` Mike Frysinger
2015-04-04 0:00 ` Joel Sherrill [this message]
2015-04-04 2:57 ` Mike Frysinger
2015-04-04 13:49 ` Joel Sherrill
2015-04-04 21:08 ` Mike Frysinger
2015-04-05 0:27 ` Joel Sherrill
2015-04-05 1:20 ` Mike Frysinger
2015-04-05 1:32 ` Joel Sherrill
2015-04-05 2:05 ` Mike Frysinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=551F2996.10003@oarcorp.com \
--to=joel.sherrill@oarcorp.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).