From: Joel Sherrill <joel.sherrill@oarcorp.com>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: lm32 simulator configuration file question
Date: Sun, 05 Apr 2015 00:27:00 -0000 [thread overview]
Message-ID: <55208159.4090504@oarcorp.com> (raw)
In-Reply-To: <20150404210848.GQ22171@vapier>
On 04/04/2015 04:08 PM, Mike Frysinger wrote:
> On 04 Apr 2015 08:49, Joel Sherrill wrote:
>> On 04/03/2015 09:57 PM, Mike Frysinger wrote:
>>> On 03 Apr 2015 19:00, Joel Sherrill wrote:
>>>> 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.
>>> OK, that should be sufficient. i just don't have any lm32 programs ;).
>> How about I just privately email you our RTEMS hello world
>> along with the instructions to run it in gdb, with run, and
>> the conf file?
> that's fine
OK. I ran it with --hw-trace and learned that the UART is not
behaving the same when started via gdb vs the run command.
Unfortunately, I also learned that our BSP was configured to
dirty memory. That is REALLY slow on the simulator. So rebuilding
now and should be able to send tomorrow I think.
Once we get by this one, I noticed that the lm32timer only
lets you instance it once. The real board has two timers.
Is there an example of a device which can be instanced
multiple times?
> -mike
--
-- Joel Sherrill
Ask me about RTEMS: a free RTOS
Support and Training Available
next prev parent reply other threads:[~2015-04-05 0:27 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
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 [this message]
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=55208159.4090504@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).