Hi Chris,
> Which BSPs that support qemu are missing from the rtems-test tool?
I suppose I had been thinking in terms of coverage and all I have is
coverage.mc files for PC386, Leon 2 and Leon 3 but now that I'm
thinking about it maybe all I need to do is to run the tests for qemu
and couverture
I would.focus first on running coverture-qemu instead regular qemu. This
includes the rsb support but is just focused on parity with no coverage.
Then run coverture-qemu with coverage on by hand and see if it gets the
output either the old or new scripts expect. Do this with just one test.
Then f
> I would.focus first on running coverture-qemu instead regular qemu. This
> includes the rsb support but is just focused on parity with no coverage.
Ok, so right now I should forget about the coverage. Run the tests
normally (qemu) and then with couverture-qemu for all the bsps
couverture suppo
On Jun 4, 2017 7:03 AM, "Cillian O'Donnell" wrote:
> I would.focus first on running coverture-qemu instead regular qemu. This
includes the rsb support but is just focused on parity with no coverage.
Ok, so right now I should forget about the coverage. Run the tests
normally (qemu) and then with
Now I have a problem with console-io.c file.
The problem is with csr macros - there is no more such a register "tohost".
Here it is described a little:
https://github.com/riscv/riscv-pk/issues/25
Could you explain what should be done here and what for was mtohost
register?
2017-06-02 2:22 GMT+03:
modify c/src/lib/libbsp/arm/beagle/Makefile.am
modify c/src/lib/libbsp/arm/beagle/include/i2c.h
delete c/src/lib/libbsp/arm/beagle/misc/i2c.c
---
c/src/lib/libbsp/arm/beagle/Makefile.am | 1 -
c/src/lib/libbsp/arm/beagle/include/i2c.h | 181
c/src/lib/libbsp/arm/beagle/misc/i2c.c
Update ticket #2891 and my GSOC project
add c/src/lib/libbsp/arm/beagle/i2c/bbb-i2c.c
modify c/src/lib/libbsp/arm/beagle/include/i2c.h
modify c/src/lib/libbsp/arm/beagle/include/bbb-gpio.h
modify c/src/lib/libcpu/arm/shared/include/am335x.h
modify c/src/lib/libbsp/arm/beagle/Makefile.am
Now can rea
2017-06-04 16:17 GMT+03:00 Denis Obrezkov :
> Now I have a problem with console-io.c file.
> The problem is with csr macros - there is no more such a register "tohost".
> Here it is described a little:
> https://github.com/riscv/riscv-pk/issues/25
>
> Could you explain what should be done here and
Hi Denis,
Yes, the Host-Target-Interface (HTIF) has been refactored/removed in
RISC-V. Also, it was meant to work with riscv front-end server
(riscv-fesvr) which is not the case for your HiFive BSP I guess.
I believe now it's the good time for you to start creating your own
HiFive BSP. You'll hav
2017-06-05 0:14 GMT+03:00 Hesham Almatary :
> Hi Denis,
>
> Yes, the Host-Target-Interface (HTIF) has been refactored/removed in
> RISC-V. Also, it was meant to work with riscv front-end server
> (riscv-fesvr) which is not the case for your HiFive BSP I guess.
>
> I believe now it's the good time
Hi Denis,
Yes, I'm willing to fix these, just need time. Shouldn't be that difficult.
You can get more details on RISC-V assembly reading RISC-V specs
(especially user-level spec) [1]. For example/references, you may have
a look at the riscv-linux and/or seL4 ports [2, 3] (though, you've to
be aw
On Jun 4, 2017 4:37 PM, "Hesham Almatary" wrote:
Hi Denis,
Yes, I'm willing to fix these, just need time. Shouldn't be that difficult.
You can get more details on RISC-V assembly reading RISC-V specs
(especially user-level spec) [1]. For example/references, you may have
a look at the riscv-linu
On 02/06/2017 23:00, Sebastian Huber wrote:
> Use HTTPS instead of FTP.
> ---
> source-builder/config/gcc-6-1.cfg | 8
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/source-builder/config/gcc-6-1.cfg
> b/source-builder/config/gcc-6-1.cfg
> index 9f75d6e..c17abc3 1006
13 matches
Mail list logo