This is the mail archive of the
mailing list for the GDB project.
Re: lm32 simulator configuration file question
- From: Joel Sherrill <joel dot sherrill at oarcorp dot com>
- To: Mike Frysinger <vapier at gentoo dot org>
- Cc: "gdb at sourceware dot org" <gdb at sourceware dot org>
- Date: Sat, 4 Apr 2015 20:32:26 -0500
- Subject: Re: lm32 simulator configuration file question
- Authentication-results: sourceware.org; auth=none
- References: <551DC087 dot 7040103 at oarcorp dot com> <20150403014149 dot GJ22171 at vapier> <551EF633 dot 9030309 at oarcorp dot com> <20150403232113 dot GO22171 at vapier> <551F2996 dot 10003 at oarcorp dot com> <20150404025706 dot GP22171 at vapier> <551FEBE8 dot 7080801 at oarcorp dot com> <20150404210848 dot GQ22171 at vapier> <55208159 dot 4090504 at oarcorp dot com> <20150405011520 dot GA16816 at vapier>
On April 4, 2015 8:20:24 PM CDT, Mike Frysinger <email@example.com> wrote:
>On 04 Apr 2015 19:27, Joel Sherrill wrote:
>> 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?
>i glanced at the lm32timer device code and it looks correct to me --
>there is no
>global state (it's all attached to the instance via HW_ZALLOC (me,
>...), and all
>accesses go through the passed in "me" hw).
>why do you think it only lets you instantiate it once ?
When I configure two timers, it looks like the second address registration attempt is ignored based on the trace and faulting code. I can have timer 0 or 1 but not both. Two interrupt attaches seem to be honored.
I will finish putting together a kit for you tomorrow. The RTEMS tester framework uses the gdb/mi so I can automate runs of the rtems test suite. It was looking pretty good using gdb but something is wrong with run.
Enjoy your Saturday night and Easter Sunday. I will get the kit to you before I fly out Monday.