Re: Status of RISCV port on sis

2019-01-15 Thread Hesham Almatary
Sounds great. It might be worth it to add an entry for sis here [1] [1] https://github.com/riscv/riscv-wiki/wiki/RISC-V-Software-Status On Sun, 13 Jan 2019 at 15:30, Jiri Gaisler wrote: > > > On 1/13/19 2:48 PM, Sebastian Huber wrote: > > - Am 13. Jan 2019 um 0:09 schrieb Jiri Gaisler j...@g

Re: Status of RISCV port on sis

2019-01-13 Thread Jiri Gaisler
On 1/13/19 2:48 PM, Sebastian Huber wrote: > - Am 13. Jan 2019 um 0:09 schrieb Jiri Gaisler j...@gaisler.se: > >> On 1/11/19 1:36 PM, Jiri Gaisler wrote: >>> On 1/9/19 10:46 AM, Sebastian Huber wrote: Hello Jiri, could you please rebase your work to this RTEMS commit:

Re: Status of RISCV port on sis

2019-01-13 Thread Sebastian Huber
- Am 13. Jan 2019 um 0:09 schrieb Jiri Gaisler j...@gaisler.se: > On 1/11/19 1:36 PM, Jiri Gaisler wrote: >> On 1/9/19 10:46 AM, Sebastian Huber wrote: >>> Hello Jiri, >>> >>> could you please rebase your work to this RTEMS commit: >>> >>> https://git.rtems.org/rtems/commit/?id=b9ffc41c9678fb3

Re: Status of RISCV port on sis

2019-01-12 Thread Jiri Gaisler
On 1/11/19 1:36 PM, Jiri Gaisler wrote: > On 1/9/19 10:46 AM, Sebastian Huber wrote: >> Hello Jiri, >> >> could you please rebase your work to this RTEMS commit: >> >> https://git.rtems.org/rtems/commit/?id=b9ffc41c9678fb3c5386c1a6ab394656ec85dbc6 >> > This works fine for me - I can now pass all u

Re: Status of RISCV port on sis

2019-01-11 Thread Jiri Gaisler
On 1/11/19 1:45 PM, Sebastian Huber wrote: > - Am 11. Jan 2019 um 13:36 schrieb Jiri Gaisler j...@gaisler.se: > >> On 1/9/19 10:46 AM, Sebastian Huber wrote: >>> Hello Jiri, >>> >>> could you please rebase your work to this RTEMS commit: >>> >>> https://git.rtems.org/rtems/commit/?id=b9ffc41c9

Re: Status of RISCV port on sis

2019-01-11 Thread Sebastian Huber
- Am 11. Jan 2019 um 13:36 schrieb Jiri Gaisler j...@gaisler.se: > On 1/9/19 10:46 AM, Sebastian Huber wrote: >> Hello Jiri, >> >> could you please rebase your work to this RTEMS commit: >> >> https://git.rtems.org/rtems/commit/?id=b9ffc41c9678fb3c5386c1a6ab394656ec85dbc6 >> > This works fine

Re: Status of RISCV port on sis

2019-01-11 Thread Jiri Gaisler
On 1/9/19 10:46 AM, Sebastian Huber wrote: > Hello Jiri, > > could you please rebase your work to this RTEMS commit: > > https://git.rtems.org/rtems/commit/?id=b9ffc41c9678fb3c5386c1a6ab394656ec85dbc6 > This works fine for me - I can now pass all uni-processor tests. On SMP, I still have a few fa

Re: Status of RISCV port on sis

2019-01-09 Thread Sebastian Huber
Hello Jiri, could you please rebase your work to this RTEMS commit: https://git.rtems.org/rtems/commit/?id=b9ffc41c9678fb3c5386c1a6ab394656ec85dbc6 -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89 189 47 41-16 Fax : +49 89 189 47

Re: Status of RISCV port on sis

2019-01-09 Thread Sebastian Huber
On 08/01/2019 08:57, Sebastian Huber wrote: It is not clear why the failures didn't show up on the Qemu test runs. I did some tests with Qemu and the sp37 fails also here. Somehow I didn't notice this failure before. -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178

Re: Status of RISCV port on sis

2019-01-07 Thread Sebastian Huber
On 07/01/2019 16:38, Jiri Gaisler wrote: On 1/7/19 3:55 PM, Sebastian Huber wrote: On 07/01/2019 15:47, Jiri Gaisler wrote: On 1/7/19 3:31 PM, Sebastian Huber wrote: On 07/01/2019 15:21, Jiri Gaisler wrote: The sp37 test fails with an interesting error:    *** BEGIN OF TEST SP 37 *** ] ***

Re: Status of RISCV port on sis

2019-01-07 Thread Jiri Gaisler
On 1/7/19 3:55 PM, Sebastian Huber wrote: > On 07/01/2019 15:47, Jiri Gaisler wrote: >> On 1/7/19 3:31 PM, Sebastian Huber wrote: >>> On 07/01/2019 15:21, Jiri Gaisler wrote: The sp37 test fails with an interesting error:    *** BEGIN OF TEST SP 37 *** ] *** TEST VERSION:

Re: Status of RISCV port on sis

2019-01-07 Thread Sebastian Huber
On 07/01/2019 15:47, Jiri Gaisler wrote: On 1/7/19 3:31 PM, Sebastian Huber wrote: On 07/01/2019 15:21, Jiri Gaisler wrote: The sp37 test fails with an interesting error:   *** BEGIN OF TEST SP 37 *** ] *** TEST VERSION: 5.0.0.eba55a6ad63a1433f50ba0d627394f447bacd04f-modified ] *** TEST STATE

Re: Status of RISCV port on sis

2019-01-07 Thread Jiri Gaisler
On 1/7/19 3:31 PM, Sebastian Huber wrote: > On 07/01/2019 15:21, Jiri Gaisler wrote: >> The sp37 test fails with an interesting error: >> >>   *** BEGIN OF TEST SP 37 *** >> ] *** TEST VERSION: >> 5.0.0.eba55a6ad63a1433f50ba0d627394f447bacd04f-modified >> ] *** TEST STATE: EXPECTED-PASS >> ] *** T

Re: Status of RISCV port on sis

2019-01-07 Thread Sebastian Huber
On 07/01/2019 15:21, Jiri Gaisler wrote: The sp37 test fails with an interesting error:  *** BEGIN OF TEST SP 37 *** ] *** TEST VERSION: 5.0.0.eba55a6ad63a1433f50ba0d627394f447bacd04f-modified ] *** TEST STATE: EXPECTED-PASS ] *** TEST BUILD: RTEMS_NETWORKING RTEMS_POSIX_API ] *** TEST TOOLS: 9

Status of RISCV port on sis

2019-01-07 Thread Jiri Gaisler
I have now made a bsp for a RISCV/GRLIB system, and have been running the testsuite on sis/RISCV. I have a few remaining failures: $ rtems-test --rtems-bsp=riscv-sis riscv-rtems5/c/grlib/testsuites --log=all.txt Passed:    569 Failed:  5 User Input:  5 Expected Fail:   0 Indetermi