Adding GDB BSPs to rtems-tester

[Joel Sherrill]

On Sat, Mar 21, 2020 at 10:38 AM Niteesh G. S. <niteesh.gs at gmail.com> wrote:

> Which architecture should I try then? Maybe powerpc or mips? If you have
> any
> of them already built can you please try them out? Building everything from
> source takes a lot of time in my dev machine.
>
> On Sat, Mar 21, 2020 at 6:41 PM Gedare Bloom <gedare at rtems.org> wrote:
>
>> On Sat, Mar 21, 2020 at 12:54 AM Niteesh G. S. <niteesh.gs at gmail.com>
>> wrote:
>> >
>> > On Thu, Mar 19, 2020 at 11:43 PM Gedare Bloom <gedare at rtems.org> wrote:
>> >>
>> >> On Thu, Mar 19, 2020 at 11:56 AM Niteesh G. S. <niteesh.gs at gmail.com>
>> wrote:
>> >> >
>> >> > Hello,
>> >> >
>> >> > While looking for small tasks to take up, Gedare mentioned about
>> adding GDB BSPs
>> >> > to rtems-tester. Can some please explain a bit more of what has to
>> be done? I guess
>> >> > we have to write configuration files for BSPs that support
>> simulation in GDB. If so, how
>> >> > could I find those BSPs, do I have to individually look at all the
>> BSPs?
>> >> >
>> >> As I said off-list, I don't know if there's a list of GDB BSPs, but I
>> >> know of at least:
>> >> powerpc/psim
>> >> mips/jmr3904
>> >> moxie/moxiesim
>> >> arm/gdbarmsim
>> >> sh/shsim
>> >>
>> >> I have no idea what any of their statuses are or if they are expected
>> >> to work. The first step would be building them and see if they run
>> >> anything. After that, you should look at the existing tester scripts
>> for
>> >> some targets:
>> >>   rtems-tools.git/tester/rtems/testing/bsps
>> >> I see scripts for most of what I listed above, so the next step would
>> >> be trying to run them via tester and see if it works.
>> >
>> >
>> > I built the simsh1 BSP but couldn't get it running. Before trying it
>> with rtems-run
>> > and rtems-test I tried manually loading it in the simulator. But gdb
>> doesn't respond
>> > as soon as I execute the run command. The only way to exit it was using
>> ctrl-c and GDB
>> > responds with
>> > sim_events_schedule_after_signal - buffer overflow
>> > Quit
>> > Aborted (core dumped)
>> > I tried setting breakpoints within GDB but it never seems to hit them.
>> I tried running the
>> > examples through rtems-test results in ta imeout.
>> >
>> > Due to the slow internet connection and slow development machine, I
>> could only build
>> > and test a few BSPs. In case if anyone has an already built tool suite
>> and BSP for the
>> > mentioned arch please try them out.
>> >
>> I don't know that anyone uses this architecture. Don't spend too much
>> effort trying to debug the simulator :)
>>
>
mips jmr3904 and powerpc psim should work well.

I agree with Gedare, spending a lot of time on the SH isn't high payoff.
I'm glad for the report but there could be bitrot in the simulator or BSP.


>
>> >> BTW: Did I mention adding these to tester, or did I mention creating
>> >> build sets for them? Anyway, I think the GDB simulator builds by
>> >> default with the toolchain, so there is no difference between a BSP
>> >> buildset (such as for jmr3904) and one that supports running on GDB.
>> >> At least, I think so. It is worth verifying.
>> >>
>> >> Gedare
>> >>
>> >> > Thank you,
>> >> > Niteesh.
>> >> > _______________________________________________
>> >> > devel mailing list
>> >> > devel at rtems.org
>> >> > http://lists.rtems.org/mailman/listinfo/devel
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20200321/efcc7180/attachment-0001.html>