Re: Coverage tools project direction [GSOC]

2017-06-04 Thread Cillian O'Donnell
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

Re: Coverage tools project direction [GSOC]

2017-06-04 Thread Joel Sherrill
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

Re: Coverage tools project direction [GSOC]

2017-06-04 Thread Cillian O'Donnell
> 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

Re: Coverage tools project direction [GSOC]

2017-06-04 Thread Joel Sherrill
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

Re: Building RISC-V BSP

2017-06-04 Thread 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 what for was mtohost register? 2017-06-02 2:22 GMT+03:

[PATCH v3 1/2] Remove beagle old i2c code

2017-06-04 Thread Sichen Zhao
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

[PATCH v3 2/2] Add the i2c driver for Beaglebone Black

2017-06-04 Thread Sichen Zhao
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

Re: Building RISC-V BSP

2017-06-04 Thread Denis Obrezkov
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

Re: Building RISC-V BSP

2017-06-04 Thread 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 for you to start creating your own HiFive BSP. You'll hav

Re: Building RISC-V BSP

2017-06-04 Thread Denis Obrezkov
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

Re: Building RISC-V BSP

2017-06-04 Thread Hesham Almatary
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

Re: Building RISC-V BSP

2017-06-04 Thread Joel Sherrill
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

Re: [PATCH 5/6] Download GCC prerequisites from GNU server

2017-06-04 Thread Chris Johns
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