Re: Adding new arch/bsp to rtems tools

2017-06-16 Thread Gedare Bloom 
On Fri, Jun 16, 2017 at 6:14 PM, Denis Obrezkov  wrote:
> Hello,
> I want to compile examples-v2 for HiFive1 board.
> I follow these steps in my blog but for new pair arch/bsp:
> http://embeddedden.blogspot.de/2017/02/building-rtems-and-first-example.html
>
> I've added new ini file rtems-bsps-riscv32.ini to rtems-tools/tester/rtems
> and
> hifive1.mc to rtems-tools/tester/rtems/testing/bsps and after rebuilding the
> tools
> (having the line
> + install
> /home/reprofy/Projects/riscv/rtems/development/rtems/4.12/share/rtems/tester/rtems/testing/bsps/hifive1.mc
> (from tester/rtems/testing/bsps/hifive1.mc)
> during the process) I am trying to run configure for examples-v2:
>
> ./waf configure --rtems=$RTEMS_DEV/rtems/4.12
> --rtems-tools=$RTEMS_DEV/rtems/4.12 --rtems-bsps=riscv32/hifive1
> --rtems-version=4.12Setting top to   :
> /home/reprofy/Projects/riscv/rtems/development/examples-v2
> Setting out to   :
> /home/reprofy/Projects/riscv/rtems/development/examples-v2/build
> No valid arch/bsps found
> (complete log in
> /home/reprofy/Projects/riscv/rtems/development/examples-v2/build/config.log)
>
> What should I do to make it work?

I don't think that the tester subdirectory has anything to do with this

Confirm that you can successfully 'waf configure' for the sparc/erc32.
If not, the problem is somewhere in your command line or install
point. Note that rtems-tools should point to the installed toolchain,
and --rtems should point to the installed build of your BSP/rtems.
Check that your 'make install' succeeded.

> --
> Regards, Denis Obrezkov
>
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Adding new arch/bsp to rtems tools

2017-06-16 Thread Denis Obrezkov 
Hello,
I want to compile examples-v2 for HiFive1 board.
I follow these steps in my blog but for new pair arch/bsp:
http://embeddedden.blogspot.de/2017/02/building-rtems-and-first-example.html

I've added new ini file rtems-bsps-riscv32.ini to rtems-tools/tester/rtems
and
hifive1.mc to rtems-tools/tester/rtems/testing/bsps and after rebuilding
the tools
(having the line
+ install
/home/reprofy/Projects/riscv/rtems/development/rtems/4.12/share/rtems/tester/rtems/testing/bsps/
hifive1.mc (from tester/rtems/testing/bsps/hifive1.mc)
during the process) I am trying to run configure for examples-v2:

./waf configure --rtems=$RTEMS_DEV/rtems/4.12
--rtems-tools=$RTEMS_DEV/rtems/4.12 --rtems-bsps=riscv32/hifive1
--rtems-version=4.12Setting top to   :
/home/reprofy/Projects/riscv/rtems/development/examples-v2
Setting out to   :
/home/reprofy/Projects/riscv/rtems/development/examples-v2/build
No valid arch/bsps found
(complete log in
/home/reprofy/Projects/riscv/rtems/development/examples-v2/build/config.log)

What should I do to make it work?
-- 
Regards, Denis Obrezkov
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: RSB Couverture-Qemu build queries

2017-06-16 Thread Jiri Gaisler 
Hi Cillian,

the gaisler.org server is currently down due to a power problem last
week. I am in the Caribbean at the moment so I can't fix it until
Tuesday next week. I suggest you skip the LEON3 patches until I fix the
server next week. Let me know if you get problems merging the patches,
and I will try to sort it out.

Jiri.


On 06/16/2017 03:13 PM, Cillian O'Donnell wrote:
> Hi,
>
> I am getting the RSB to build Couverture-Qemu and I just want to check
> a few things I have done so far.
>
> 1. There are about 5 patches applied to the current qemu build. Only
> one of which applies cleanly to the Couverture build. Do you want me
> to try and fix these up, comment them out and leave a note for
> whoever wants to fix them or remove them completely? The patches that
> don't work are:
>
> %patch add qemu
> pw://patchwork.ozlabs.org/patch/406903/raw/Provide-the-missing-LIBUSB_LOG_LEVEL_-for-older-libusb-or-FreeBSD.-Providing-just-the-needed-value-as-a-defined..patch
>
> %patch add qemu
> https://gaisler.org/qemu/0001-LEON3-Add-emulation-of-AMBA-plug-
> play.patch
>
> %patch add qemu
> https://gaisler.org/qemu/0002-LEON3-Build-AMBA-plug-and-play-records-from-high-lev.patch
>
> %patch add qemu
> https://gaisler.org/qemu/0003-LEON3-Init-UART-timers-and-CPU-if-we-run-a-RAM-image.patch
>
>
> 2. For this source setting section, is the first part just dealing
> with the case were this a packaged release so a tar of the download is
> already included with it?
>
> %if %{rsb_released} && %{!defined without_release_url}
> %source set qemu
> %{rtems_release_url}/%{rtems_version}/sources/qemu-git-42d58e7.tar.xz
> %else
> %source set qemu
> https://github.com/AdaCore/qemu/archive/%{qemu_version}.tar.gz
> %endif
>
> 3. What does the -q option do in the %prep section of the build, this
> option shows up in examples in the docs but there is no description of
> what it does?
>
> %source setup qemu -q -n qemu-%{qemu_version}
>
> 4. The current qemu build is configured with the default setting to
> build for all architectures but most of the arch's aren't used by
> RTEMS and/or don't have machine support for same bsps, so I've added a
> --target-list to only build the targets that have a corresponding bsp
> (sparc64-softmmu is missing as it runs into build issues, I forgot to
> mention in the initial results). However the list spills over 80 lines
> so should I make a %{qemu_targets} macro and if so where should I put
> it?
>
>  --make=%{__make} \
>  72 
> --target-list=arm-softmmu,i386-softmmu,lm32-softmmu,mips-softmmu,ppc-softmmu,sparc-softmmu
> \
>  73 ${VDE_CONFIG} \
>  74 --disable-smartcard-nss \
>
> Thanks,
>
> Cillian.
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: RSB Couverture-Qemu build queries

2017-06-16 Thread Gedare Bloom 
On Fri, Jun 16, 2017 at 4:38 PM, Joel Sherrill  wrote:
>
>
> On Fri, Jun 16, 2017 at 2:13 PM, Cillian O'Donnell 
> wrote:
>>
>> Hi,
>>
>> I am getting the RSB to build Couverture-Qemu and I just want to check
>> a few things I have done so far.
>>
>> 1. There are about 5 patches applied to the current qemu build. Only
>> one of which applies cleanly to the Couverture build. Do you want me
>> to try and fix these up, comment them out and leave a note for
>> whoever wants to fix them or remove them completely? The patches that
>> don't work are:
>>
>> %patch add qemu
>>
>> pw://patchwork.ozlabs.org/patch/406903/raw/Provide-the-missing-LIBUSB_LOG_LEVEL_-for-older-libusb-or-FreeBSD.-Providing-just-the-needed-value-as-a-defined..patch
>>
>> %patch add qemu
>> https://gaisler.org/qemu/0001-LEON3-Add-emulation-of-AMBA-plug-
>> play.patch
>>
>> %patch add qemu
>>
>> https://gaisler.org/qemu/0002-LEON3-Build-AMBA-plug-and-play-records-from-high-lev.patch
>>
>> %patch add qemu
>>
>> https://gaisler.org/qemu/0003-LEON3-Init-UART-timers-and-CPU-if-we-run-a-RAM-image.patch
>>
>>
>
> I think they need to be proposed to the Couverture project to be evaluated.
> They should
> be OK with the Gaisler ones without too much trouble. We can bring in
> Gaisler folks.
> The other is a portability one.
>
> So at least make the project aware of them.
>
> https://forge.open-do.org/projects/couverture-qemu/
>
> Make sure myself and chrisj@ are on any issue/email you file.
>
>>
>> 2. For this source setting section, is the first part just dealing
>> with the case were this a packaged release so a tar of the download is
>> already included with it?
>>
>> %if %{rsb_released} && %{!defined without_release_url}
>> %source set qemu
>> %{rtems_release_url}/%{rtems_version}/sources/qemu-git-42d58e7.tar.xz
>> %else
>> %source set qemu
>> https://github.com/AdaCore/qemu/archive/%{qemu_version}.tar.gz
>> %endif
>
>
> I think so but Chris should confirm that.
>>
>>
>> 3. What does the -q option do in the %prep section of the build, this
>> option shows up in examples in the docs but there is no description of
>> what it does?
>>
>> %source setup qemu -q -n qemu-%{qemu_version}
>
>
> Chris will have to answer this.
>
>>
>>
>> 4. The current qemu build is configured with the default setting to
>> build for all architectures but most of the arch's aren't used by
>> RTEMS and/or don't have machine support for same bsps, so I've added a
>> --target-list to only build the targets that have a corresponding bsp
>> (sparc64-softmmu is missing as it runs into build issues, I forgot to
>> mention in the initial results). However the list spills over 80 lines
>> so should I make a %{qemu_targets} macro and if so where should I put
>> it?
>
>
> I like the idea of limiting the targets built. You are right that we don't
> care about the others.
>

sparc64-softmmu did not work for rtems the last time that I checked,
but that was a few years ago.

> The style and variable name are Chris questions.
>
>>
>>
>>  --make=%{__make} \
>>  72
>> --target-list=arm-softmmu,i386-softmmu,lm32-softmmu,mips-softmmu,ppc-softmmu,sparc-softmmu
>> \
>>  73 ${VDE_CONFIG} \
>>  74 --disable-smartcard-nss \
>>
>> Thanks,
>>
>> Cillian.
>
>
>
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: RSB Couverture-Qemu build queries

2017-06-16 Thread Joel Sherrill 
On Fri, Jun 16, 2017 at 2:13 PM, Cillian O'Donnell 
wrote:

> Hi,
>
> I am getting the RSB to build Couverture-Qemu and I just want to check
> a few things I have done so far.
>
> 1. There are about 5 patches applied to the current qemu build. Only
> one of which applies cleanly to the Couverture build. Do you want me
> to try and fix these up, comment them out and leave a note for
> whoever wants to fix them or remove them completely? The patches that
> don't work are:
>
> %patch add qemu
> pw://patchwork.ozlabs.org/patch/406903/raw/Provide-the-
> missing-LIBUSB_LOG_LEVEL_-for-older-libusb-or-FreeBSD.-
> Providing-just-the-needed-value-as-a-defined..patch
>
> %patch add qemu
> https://gaisler.org/qemu/0001-LEON3-Add-emulation-of-AMBA-plug-
> play.patch
>
> %patch add qemu
> https://gaisler.org/qemu/0002-LEON3-Build-AMBA-plug-and-
> play-records-from-high-lev.patch
>
> %patch add qemu
> https://gaisler.org/qemu/0003-LEON3-Init-UART-timers-and-
> CPU-if-we-run-a-RAM-image.patch
>
>
>
I think they need to be proposed to the Couverture project to be evaluated.
They should
be OK with the Gaisler ones without too much trouble. We can bring in
Gaisler folks.
The other is a portability one.

So at least make the project aware of them.

https://forge.open-do.org/projects/couverture-qemu/

Make sure myself and chrisj@ are on any issue/email you file.


> 2. For this source setting section, is the first part just dealing
> with the case were this a packaged release so a tar of the download is
> already included with it?
>
> %if %{rsb_released} && %{!defined without_release_url}
> %source set qemu
> %{rtems_release_url}/%{rtems_version}/sources/qemu-git-42d58e7.tar.xz
> %else
> %source set qemu
> https://github.com/AdaCore/qemu/archive/%{qemu_version}.tar.gz
> %endif
>

I think so but Chris should confirm that.

>
> 3. What does the -q option do in the %prep section of the build, this
> option shows up in examples in the docs but there is no description of
> what it does?
>
> %source setup qemu -q -n qemu-%{qemu_version}
>

Chris will have to answer this.


>
> 4. The current qemu build is configured with the default setting to
> build for all architectures but most of the arch's aren't used by
> RTEMS and/or don't have machine support for same bsps, so I've added a
> --target-list to only build the targets that have a corresponding bsp
> (sparc64-softmmu is missing as it runs into build issues, I forgot to
> mention in the initial results). However the list spills over 80 lines
> so should I make a %{qemu_targets} macro and if so where should I put
> it?
>

I like the idea of limiting the targets built. You are right that we don't
care about the others.

The style and variable name are Chris questions.


>
>  --make=%{__make} \
>  72 --target-list=arm-softmmu,i386-softmmu,lm32-softmmu,
> mips-softmmu,ppc-softmmu,sparc-softmmu
> \
>  73 ${VDE_CONFIG} \
>  74 --disable-smartcard-nss \
>
> Thanks,
>
> Cillian.
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

RSB Couverture-Qemu build queries

2017-06-16 Thread Cillian O'Donnell 
Hi,

I am getting the RSB to build Couverture-Qemu and I just want to check
a few things I have done so far.

1. There are about 5 patches applied to the current qemu build. Only
one of which applies cleanly to the Couverture build. Do you want me
to try and fix these up, comment them out and leave a note for
whoever wants to fix them or remove them completely? The patches that
don't work are:

%patch add qemu
pw://patchwork.ozlabs.org/patch/406903/raw/Provide-the-missing-LIBUSB_LOG_LEVEL_-for-older-libusb-or-FreeBSD.-Providing-just-the-needed-value-as-a-defined..patch

%patch add qemu
https://gaisler.org/qemu/0001-LEON3-Add-emulation-of-AMBA-plug-
play.patch

%patch add qemu
https://gaisler.org/qemu/0002-LEON3-Build-AMBA-plug-and-play-records-from-high-lev.patch

%patch add qemu
https://gaisler.org/qemu/0003-LEON3-Init-UART-timers-and-CPU-if-we-run-a-RAM-image.patch


2. For this source setting section, is the first part just dealing
with the case were this a packaged release so a tar of the download is
already included with it?

%if %{rsb_released} && %{!defined without_release_url}
%source set qemu
%{rtems_release_url}/%{rtems_version}/sources/qemu-git-42d58e7.tar.xz
%else
%source set qemu
https://github.com/AdaCore/qemu/archive/%{qemu_version}.tar.gz
%endif

3. What does the -q option do in the %prep section of the build, this
option shows up in examples in the docs but there is no description of
what it does?

%source setup qemu -q -n qemu-%{qemu_version}

4. The current qemu build is configured with the default setting to
build for all architectures but most of the arch's aren't used by
RTEMS and/or don't have machine support for same bsps, so I've added a
--target-list to only build the targets that have a corresponding bsp
(sparc64-softmmu is missing as it runs into build issues, I forgot to
mention in the initial results). However the list spills over 80 lines
so should I make a %{qemu_targets} macro and if so where should I put
it?

 --make=%{__make} \
 72 
--target-list=arm-softmmu,i386-softmmu,lm32-softmmu,mips-softmmu,ppc-softmmu,sparc-softmmu
\
 73 ${VDE_CONFIG} \
 74 --disable-smartcard-nss \

Thanks,

Cillian.
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel