I have updated the doc to use erc32-sis, and attached the patch file in
this mail. Can someone review it.

On Mon, Nov 18, 2019 at 12:07 PM Niteesh <gsnb...@gmail.com> wrote:

> I know this, but the docs are not updated so should I send a pull request?
>
>
> On Mon, Nov 18, 2019 at 12:06 PM Vaibhav Gupta <vaibhavgupt...@gmail.com>
> wrote:
>
>>
>>
>> On Mon, Nov 18, 2019, 11:12 AM Niteesh <gsnb...@gmail.com> wrote:
>>
>>> On Mon, Nov 18, 2019 at 3:17 AM Joel Sherrill <j...@rtems.org> wrote:
>>>
>>>> The instructions are out of date by a couple of months. The SPARC
>>>> Instruction Simulator (sis) has seen significant enhancements and it's now
>>>> a standalone program. It is not enabled as a built-in with gdb because
>>>> that's some very old version of sis. The new version has symmetric
>>>> multiprocessing and support for the RISC-V.
>>>>
>>>> Those instructions worked for a LONG time but need to be updated to
>>>> reflect the recent changes with SIS.
>>>>
>>>> If you used rtems-tester, it should work. And looking at the .ini file
>>>> for this bsp will sure you have to just run programs with the simulator. My
>>>> recollection is that by adding -gdb argument, you can attached to it as a
>>>> remote debugger.
>>>>
>>> Yes. And I also faced this problem (in my case it was riscv)and i guess
>> this question was asked by others also on devel.
>> I simply used these steps:
>>
>> Open Terminal 1:
>>
>> $ sparc-rtems5-sis -gdb
>>
>>         # It will print 'gdb: listening on port 1234'.
>>
>>         # Note you can define port number with '-port' option.
>>
>> Open Terminal 2:
>>
>> $ sparc-rtems5-gdb hello.exe
>>
>>         # gdb asks for several inputs
>>
>>                 $ target extended-remote localhost:1234
>>
>>                 $ load
>>
>>                 $ r
>>
>> You will see output in Terminal 1.
>>
>>> I would like to update the docs for this, Can I proceed? I am planning
>>> to change the cmd to use erc-sis instead of erc. And also the build your
>>> application section is incomplete, can I add the instruction to modify a
>>> test program and build it in this section?
>>>
>>>> BTW I know it's a way too early for GSOC but I have anyway attached the
>>>>> patch for hello world.
>>>>>
>>>>
>>>> What type projects are you interested in?
>>>>
>>> I am interested in driver development and BSP support.
>>>
>>>> _______________________________________________
>>>>> devel mailing list
>>>>> devel@rtems.org
>>>>> http://lists.rtems.org/mailman/listinfo/devel
>>>>
>>>> _______________________________________________
>>> devel mailing list
>>> devel@rtems.org
>>> http://lists.rtems.org/mailman/listinfo/devel
>>
>>
From c7768d10a55a557abf65867d9039d7dc0642b270 Mon Sep 17 00:00:00 2001
From: gs-niteesh <gsnb...@gmail.com>
Date: Mon, 18 Nov 2019 12:46:43 +0530
Subject: [PATCH] user/start/bsp-test.rst: Changed bsp to erc32-sis.

This commit removd the target sim from gdb id=abc540105d10ddc9cad7de3c7ac0a9aa209ac828
but the doc was not updated, so on running rtems test caused failures,
this commit changes it use the erc32-sis which used standalone sis
simulator.
---
 user/start/bsp-test.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/user/start/bsp-test.rst b/user/start/bsp-test.rst
index 5278375..8a14862 100644
--- a/user/start/bsp-test.rst
+++ b/user/start/bsp-test.rst
@@ -21,7 +21,7 @@ Just run this command:
 .. code-block:: none
 
     cd $HOME/quick-start/build/b-erc32
-    rtems-test --rtems-bsp=erc32 --rtems-tools=$HOME/quick-start/rtems/5 .
+    rtems-test --rtems-bsp=erc32-sis --rtems-tools=$HOME/quick-start/rtems/5 .
 
 This command should output something like this (omitted lines are denoted by
 ...).  In this output the base directory :file:`$HOME/quick-start` was replaced
-- 
2.17.1

_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Reply via email to