Okay. Thanks
On Mon, Aug 12, 2019 at 3:00 PM Hesham Almatary <
hesham.almat...@cl.cam.ac.uk> wrote:
> On Mon, 12 Aug 2019 at 03:55, Vaibhav Gupta
> wrote:
> >
> >
> >
> > On Mon, Aug 12, 2019, 12:01 AM Hesham Almatary <
> hesham.almat...@cl.cam.ac.uk> wrote:
> >>
> >>
> >>
> >> On Sun, 11 Aug 20
On Mon, 12 Aug 2019 at 03:55, Vaibhav Gupta wrote:
>
>
>
> On Mon, Aug 12, 2019, 12:01 AM Hesham Almatary
> wrote:
>>
>>
>>
>> On Sun, 11 Aug 2019 at 16:11, Vaibhav Gupta wrote:
>>>
>>> But I am not able to run:
>>>
>>> qemu-system-riscv64 -no-reboot -nographic -machine virt -m 256M -kernel
>>
On Mon, Aug 12, 2019, 12:01 AM Hesham Almatary
wrote:
>
>
> On Sun, 11 Aug 2019 at 16:11, Vaibhav Gupta
> wrote:
>
>> But I am not able to run:
>>
>> qemu-system-riscv64 -no-reboot -nographic -machine virt -m 256M -kernel
>> hello.exe
>>
>>
>> On Fri, Aug 9, 2019 at 2:53 PM Vaibhav Gupta
>> wr
On Sun, 11 Aug 2019 at 16:11, Vaibhav Gupta
wrote:
> But I am not able to run:
>
> qemu-system-riscv64 -no-reboot -nographic -machine virt -m 256M -kernel
> hello.exe
>
>
> On Fri, Aug 9, 2019 at 2:53 PM Vaibhav Gupta
> wrote:
>
>> I was able to run rv32imac using
>>
>> qemu-system-riscv32 -no-
But I am not able to run:
qemu-system-riscv64 -no-reboot -nographic -machine virt -m 256M
-kernel hello.exe
On Fri, Aug 9, 2019 at 2:53 PM Vaibhav Gupta
wrote:
> I was able to run rv32imac using
>
> qemu-system-riscv32 -no-reboot -nographic -machine virt -m 256M -kernel
> hello.exe
>
> When I
I was able to run rv32imac using
qemu-system-riscv32 -no-reboot -nographic -machine virt -m 256M
-kernel hello.exe
On Tue, Aug 6, 2019 at 9:04 PM Vaibhav Gupta
wrote:
> Awesome, thanks!
>
> On Tue, Aug 6, 2019 at 8:50 PM Hesham Almatary <
> hesham.almat...@cl.cam.ac.uk> wrote:
>
>> Hi Vaibhav,
Awesome, thanks!
On Tue, Aug 6, 2019 at 8:50 PM Hesham Almatary
wrote:
> Hi Vaibhav,
>
> * I recommend you use rv64* because of a potential 32-bit HTIF issue on
> Spike.
> * Make sure you install Spike correctly [1] and it's in your path or
> also qemu-system-riscv* instead.
> * If you're buildi
Hi Vaibhav,
* I recommend you use rv64* because of a potential 32-bit HTIF issue on Spike.
* Make sure you install Spike correctly [1] and it's in your path or
also qemu-system-riscv* instead.
* If you're building RTEMS for Spike (i.e., rv*_spike), make sure to
add RISCV_ENABLE_HTIF_SUPPORT to you
I am getting following error:
.
.
$ rtems-test --rtems-bsp=rv32imac_spike
--rtems-tools=$HOME/development/rtems/5
~/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples
RTEMS Testing - Tester, 5.0.not_released
Command Line: /home/varodek/development/rtems/5/bin/rtems-test
On Tue, Aug 6, 2019 at 2:36 PM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
>
>
> On 06/08/2019 10:54, Vaibhav Gupta wrote:
> > Getting this error:
> > $ rtems-test --rtems-bsp=rv32imac
> > --rtems-tools=$HOME/development/rtems/5
> >
> ~/development/rtems/kernel/rv32imac/riscv-rtem
On 06/08/2019 10:54, Vaibhav Gupta wrote:
Getting this error:
$ rtems-test --rtems-bsp=rv32imac
--rtems-tools=$HOME/development/rtems/5
~/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples
RTEMS Testing - Tester, 5.0.not_released
Command Line: /home/varodek/devel
Getting this error:
$ rtems-test --rtems-bsp=rv32imac --rtems-tools=$HOME/development/rtems/5
~/development/rtems/kernel/rv32imac/riscv-rtems5/c/rv32imac/testsuites/samples
RTEMS Testing - Tester, 5.0.not_released
Command Line: /home/varodek/development/rtems/5/bin/rtems-test
--rtems-bsp=rv32imac
On 06/08/2019 10:33, Vaibhav Gupta wrote:
But when I am trying to run hello world testsuite:
$ riscv-rtems5-run ./hello.exe
You have to use the RTEMS Tester, e.g.
rtems-test --rtems-bsp=rv32imac
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone
13 matches
Mail list logo
