On 11/06/2015 3:01 am, Gedare Bloom wrote:
> On Mon, Jun 8, 2015 at 5:44 AM, André Marques
> wrote:
>> Hello,
>>
>> I have just updated my GSOC blog [1] with a detailed post about how a
>> rtems-wide GPIO API could look like, and at the same time exposing the
>> current features of the Raspberry P
Hi
I changed the subject. Now to go through the output.
First, you ran only the samples so we could expect the coverage
to be very sparse at best.
Next, you may have to improve the error output for this message.
It could indicate a build problem on your side or something broken
recently in cov
Dear all!
When I execute the sample tests on a Leon2 in couverture-qemu with coverage
reports enabled by applying the patches from
https://devel.rtems.org/ticket/2314 I obtained the attached log file.
So, I obtain coverage results, but at the moment I do not really understand
what the error messag
On Mon, Jun 8, 2015 at 5:44 AM, André Marques
wrote:
> Hello,
>
> I have just updated my GSOC blog [1] with a detailed post about how a
> rtems-wide GPIO API could look like, and at the same time exposing the
> current features of the Raspberry Pi GPIO API and how it can evolve to that
> level.
>
Yes, this is due to an update in the memory management. There is
another issue in this test that is a bit harder to chase down.
On 10/06/15 02:16, Sujay Raj wrote:
I am working on the xilinx_zynq_a9_qemu bsp.
The output just prior to the error is :
test kqueue timer
test kqueue timer
test k
