Re: Beatnik RTEMS4.10.2 vmeTsi148 ISR: ERROR: no handler registered

2021-03-11 Thread Matt Rippa
It looks like the IRQEntry vector triggering this interrupt was null. I'm
not sure what condition would arise leading to this.
Maybe memory corruption or a bus error.

https://git.rtems.org/rtems/tree/c/src/lib/libbsp/shared/vmeUniverse/vmeTsi148.c?h=4.10.2#n1562

On Thu, Mar 11, 2021 at 2:42 PM Matt Rippa  wrote:

> Hello,
>
> Our Primary Mirror control system has a beatnik bsp running on a mvme6100
> with *RTEMS4.10.2 *and* EPICS 3.14.12.8* (which understandably is not
> actively supported). We've experienced a single event that we've never seen
> before. vmeTsi148 ISR: ERROR: no handler
>
> After this it appears all interrupts were disabled and the VME bus
> communications are down. This system is normally well behaved with
> uptimes measured in months. In 2020 we had an uptime of 301 days!
>
> Has anyone seen an error like this on the beatnik bsp?
>
> Subsequent to the error which corresponds closely with a casr command, we
> see dbScan warnings in our logs. These persisted several times per minute
> until the system was reboot.
>
> Thanks for any insight.
>
> -Matt Rippa
>
>
> <8/3/2021 8:00:32 hst>pcs-mk-ioc> casr
> <8/3/2021 8:00:33 hst>Channel Access Server V4.13
> <8/3/2021 8:00:33 hst>Connected circuits:
> <8/3/2021 8:00:33 hst>TCP , V4.13, 6 Channels,
> Priority=0
> <8/3/2021 8:00:33 hst>TCP , V4.13, 134 Channels,
> Priority=80
> <8/3/2021 8:00:33 hst>TCP , V4.13, 1 Channels, Priority=0
> <8/3/2021 8:00:33 hst>TCP , V4.13, 5 Channels, Priority=0
> <8/3/2021 8:00:33 hst>TCP , V4.13, 8 Channels, Priority=0
> <8/3/2021 8:00:33 hst>TCP , V4.13, 60 Channels, Priority=0
> <8/3/2021 8:00:33 hst>TCP , V4.13, 9 Channels, Priority=0
> <8/3/2021 8:00:34 hst>TCP , V4.13, 9 Channels, Priority=0
> <8/3/2021 8:00:34 hst>TCP , V4.13, 71 Channels, Priority=0
> <8/3/2021 8:00:34 hst>TCP , V4.13, 5 Channels, Priority=0
> <8/3/2021 8:00:34 hst>TCP , V4.13, 359 Channels, Priority=20
> <8/3/2021 8:00:34 hst>TCP , 741 Channels, Priority=20
> <8/3/2021 8:00:34 hst>TCP , V4.13, 5 Channels, Priority=20
> <8/3/2021 8:00:34 hst>pcs-mk-ioc> vmeTsi148 ISR: ERROR: no handler
> registered (level 2) IACK 0x0045 -- DISABLING level 2
> *<8/3/2021 8:05:14 hst>vmeTsi148 ISR: ERROR: no handler registered (level
> 4) IACK 0x0040 -- DISABLING level 4*
> <8/3/2021 8:34:54 hst>dbScan warning from '.2 second' scan thread:
> <8/3/2021 8:34:54 hst>Scan processing averages 0.300 seconds
> (0.300 .. 0.300).
> <8/3/2021 8:34:54 hst>Over-runs have now happened 10 times in a
> row.
> <8/3/2021 8:34:54 hst>To fix this, move some records to a slower
> scan rate.
> <8/3/2021 8:34:54 hst>
> <8/3/2021 8:35:09 hst>dbScan warning from '.2 second' scan thread:
> <8/3/2021 8:35:09 hst>Scan processing averages 0.300 seconds
> (0.300 .. 0.300).
> <8/3/2021 8:35:09 hst>Over-runs have now happened 10 times in a
> row.
> <8/3/2021 8:35:09 hst>To fix this, move some records to a slower
> scan rate.
> <8/3/2021 8:35:09 hst>
> ...
>
>
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: Issues with configuring BSP with waf

2021-03-11 Thread Ida Delphine
Hello,
Please I need some help. Following the GSoC getting started guide(
https://docs.rtems.org/branches/master/user/start/gsoc.html),everything
went well to the point I had to do an offline download. I used this command
../source-builder/sb-set-builder --source-only-download 5/rtems-sparc
Seems like there was a mismatch. I got this error:
b-set-builder --source-only-download 5/rtems-sparc
RTEMS Source Builder - Set Builder, 6 (5e449fb5c2cb)
Build Set: 5/rtems-sparc
error: no build set file found: 5/rtems-sparc.bset
Build Set: Time 0:00:00.000205
Build FAILED
I then replaced 5/rtems in the command with 6/rtems and everything worked.
I was able to install the suite, build the board support package, and test
my BSP though along the way I had to replace "5" with "6" in certain
commands. Everything went well until I wanted to prove I can work on RTEMS.
I followed the instructions to create my hello application and added the
necessary .c files. The problem was when I tried configuring this
application using waf with the command:

./waf configure --rtems=$HOME/quick-start/rtems/5 --rtems-bsp=sparc/erc32

I got this error:
Setting top to   :
/home/idadel/quick-start/app/hello
Setting out to   :
/home/idadel/quick-start/app/hello/build
RTEMS path is not valid, "/home/idadel/quick-start/rtems/5/share/rtems5"
not found.
(complete log in /home/idadel/quick-start/app/hello/build/config.log)
I thought I showld startover but and work with rtems.git/5 instead of
rtems.git/master. Same with rsb. So I got the sources and did a "git
checkout"  from the master to the "5" branch. Everything went well with me
not not having to change any "5" to "6" in some commands. I didn't make it
as far as testing my BSP. I had issues with configuring my BSP with the
command:

./waf configure --rtems=$HOME/quick-start/rtems/5 --rtems-bsp=sparc/erc32

I got this:
bash: ./waf: No such file or directory
I'm confused and don't know what I missed or where I went wrong.

Ida.




On Thu, Mar 11, 2021 at 6:03 PM Ida Delphine  wrote:

> Okay. Thank you :)
>
> On Thu, 11 Mar 2021, 5:57 pm Gedare Bloom,  wrote:
>
>> On Thu, Mar 11, 2021 at 9:48 AM Ida Delphine  wrote:
>> >
>> > Thank you for your response. I am not working on the rtems.git/master
>> branch. I'm not using it because earlier I tried downloading sources with
>> it but I got this error
>> > error: shell macro failed:
>> /home/idadel/quick-start/src/rsb/source-builder/sb/rtems-build-dep -c gcc
>> -l : 2: error: no library (-l) provided
>> > So I decided to use the other alternative(get the sources from releases)
>> >
>> > Since I'm a GSoC applicant should I wait till the issue at the master
>> branch is resolved?
>> >
>> Yes, that issue has been resolved so please try again. Hopefully,
>> things work a bit better. We try not to break things, but unexpected
>> problems come up from time to time, especially based on host OS
>> dependencies.
>>
>> > Cheers,
>> > Ida.
>> >
>> > On Thu, Mar 11, 2021 at 4:18 PM Gedare Bloom  wrote:
>> >>
>> >> On Thu, Mar 11, 2021 at 7:33 AM Ida Delphine 
>> wrote:
>> >> >
>> >> > Hello everyone,
>> >> > Was following the quick build documentation and had issues around
>> where I have to do a manual BSP build.  In the last step of configuring the
>> BSP, I ran this command:
>> >> >
>> >> > ./waf configure --prefix=$HOME/quick-start/rtems/5
>> >> >
>> >> Are you working on rtems.git/master branch or /5 branch? Note that you
>> >> need to be sure to use a consistent compiler toolchain based on the
>> >> version of RTEMS that you use.
>> >>
>> >> In rtems/5 branch we don't have waf support integrated yet. The
>> >> upgrade to waf is happening currently on the master branch, which will
>> >> eventually become the RTEMS version 6 release.
>> >>
>> >> For GSoC students we expect development to happen on the development
>> >> head and not a release, so please make sure that you have the
>> >> toolchain built from rtems-source-builder.git/master and the rtems
>> >> source tree from rtems.git/master.
>> >>
>> >> > It didn't produce the expected output. I instead got:
>> >> > bash: ./waf: No such file or directory
>> >> > As a result I downloaded it with the command:
>> >> > curl https://waf.io/waf-2.0.19 > waf
>> >>
>> >> https://git.rtems.org/rtems/tree/waf
>> >>
>> >> Currently, the waf-based build of rtems only supports "in tree"
>> >> builds, which means you need to run waf from within the rtems.git/
>> >> root of your source. This is a limitation of the waf build.
>> >>
>> >> FWIW, waf build improvements could also fall under GSoC effort,
>> >> although no one has written it up as a task yet. It would be mostly
>> >> Python.
>> >>
>> >> > I ran  the last command to configure the BSP again but still did not
>> get the expected  output. I got this rather:
>> >> > Waf: Run from a folder containing a 'wscript' file (or try -h for
>> the generic options)
>> >> > Please how do I fix this? What am I missing?
>> >> > I have 

Beatnik RTEMS4.10.2 vmeTsi148 ISR: ERROR: no handler registered

2021-03-11 Thread Matt Rippa
Hello,

Our Primary Mirror control system has a beatnik bsp running on a mvme6100
with *RTEMS4.10.2 *and* EPICS 3.14.12.8* (which understandably is not
actively supported). We've experienced a single event that we've never seen
before. vmeTsi148 ISR: ERROR: no handler

After this it appears all interrupts were disabled and the VME bus
communications are down. This system is normally well behaved with uptimes
measured in months. In 2020 we had an uptime of 301 days!

Has anyone seen an error like this on the beatnik bsp?

Subsequent to the error which corresponds closely with a casr command, we
see dbScan warnings in our logs. These persisted several times per minute
until the system was reboot.

Thanks for any insight.

-Matt Rippa


<8/3/2021 8:00:32 hst>pcs-mk-ioc> casr
<8/3/2021 8:00:33 hst>Channel Access Server V4.13
<8/3/2021 8:00:33 hst>Connected circuits:
<8/3/2021 8:00:33 hst>TCP , V4.13, 6 Channels,
Priority=0
<8/3/2021 8:00:33 hst>TCP , V4.13, 134 Channels,
Priority=80
<8/3/2021 8:00:33 hst>TCP , V4.13, 1 Channels, Priority=0
<8/3/2021 8:00:33 hst>TCP , V4.13, 5 Channels, Priority=0
<8/3/2021 8:00:33 hst>TCP , V4.13, 8 Channels, Priority=0
<8/3/2021 8:00:33 hst>TCP , V4.13, 60 Channels, Priority=0
<8/3/2021 8:00:33 hst>TCP , V4.13, 9 Channels, Priority=0
<8/3/2021 8:00:34 hst>TCP , V4.13, 9 Channels, Priority=0
<8/3/2021 8:00:34 hst>TCP , V4.13, 71 Channels, Priority=0
<8/3/2021 8:00:34 hst>TCP , V4.13, 5 Channels, Priority=0
<8/3/2021 8:00:34 hst>TCP , V4.13, 359 Channels, Priority=20
<8/3/2021 8:00:34 hst>TCP , 741 Channels, Priority=20
<8/3/2021 8:00:34 hst>TCP , V4.13, 5 Channels, Priority=20
<8/3/2021 8:00:34 hst>pcs-mk-ioc> vmeTsi148 ISR: ERROR: no handler
registered (level 2) IACK 0x0045 -- DISABLING level 2
*<8/3/2021 8:05:14 hst>vmeTsi148 ISR: ERROR: no handler registered (level
4) IACK 0x0040 -- DISABLING level 4*
<8/3/2021 8:34:54 hst>dbScan warning from '.2 second' scan thread:
<8/3/2021 8:34:54 hst>Scan processing averages 0.300 seconds (0.300
.. 0.300).
<8/3/2021 8:34:54 hst>Over-runs have now happened 10 times in a
row.
<8/3/2021 8:34:54 hst>To fix this, move some records to a slower
scan rate.
<8/3/2021 8:34:54 hst>
<8/3/2021 8:35:09 hst>dbScan warning from '.2 second' scan thread:
<8/3/2021 8:35:09 hst>Scan processing averages 0.300 seconds (0.300
.. 0.300).
<8/3/2021 8:35:09 hst>Over-runs have now happened 10 times in a
row.
<8/3/2021 8:35:09 hst>To fix this, move some records to a slower
scan rate.
<8/3/2021 8:35:09 hst>
...
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: Error by building a BSP on Ubuntu 18.04

2021-03-11 Thread Joel Sherrill
On Thu, Mar 11, 2021 at 2:41 PM Olga Syrbachova 
wrote:

> It is RTEMS 5.1. I've checked the configure step. It seems to be fine. I
> get this:
>
> config.status: creating Makefile
>
> target architecture: sparc.
> available BSPs: erc32.
> 'make all' will build the following BSPs: erc32.
> other BSPs can be built with 'make RTEMS_BSP="bsp1 bsp2 ..."'
>
> config.status: creating Makefile
>
> And I still have the same error running make -j 2.
>

I wonder if you bootstrapped with the RTEMS autoconf/automake or the system
one.

type autoconf

and see which is picked up. Normally the RTEMS tools bin directory goes at
the
head of your PATH.

--joel

>
> On Thu, 11 Mar 2021 at 00:18, Gedare Bloom  wrote:
>
>> Hi Olga,
>>
>> On Wed, Mar 10, 2021 at 1:35 PM Olga Syrbachova 
>> wrote:
>> >
>> > Hi! I'm following this tutorial
>> https://docs.rtems.org/branches/master/user/installation/kernel.html.
>> > After successfully building a tool chain for the SPARC architecture in
>> step 5.1.1. I moved to the step 5.3.1. And then in step 5.3.4. I get an
>> error:
>> >
>> > olga@olga-H270M-DS3H:~/development/rtems/kernel/erc32$ make -j 2
>> > Making all in sparc-rtems5/c
>> > make[1]: Entering directory
>> '/home/olga/development/rtems/kernel/erc32/sparc-rtems5/c'
>> > Making all in .
>> > make[2]: Entering directory
>> '/home/olga/development/rtems/kernel/erc32/sparc-rtems5/c'
>> > make[2]: Nothing to be done for 'all-am'.
>> > make[2]: Leaving directory
>> '/home/olga/development/rtems/kernel/erc32/sparc-rtems5/c'
>> > Making all in erc32
>> > make[2]: Entering directory
>> '/home/olga/development/rtems/kernel/erc32/sparc-rtems5/c/erc32'
>> > make[2]: *** No rule to make target 'all'.  Stop.
>> > make[2]: Leaving directory
>> '/home/olga/development/rtems/kernel/erc32/sparc-rtems5/c/erc32'
>> > Makefile:362: recipe for target 'all-recursive' failed
>> > make[1]: *** [all-recursive] Error 1
>> > make[1]: Leaving directory
>> '/home/olga/development/rtems/kernel/erc32/sparc-rtems5/c'
>> > Makefile:482: recipe for target 'all-recursive' failed
>> > make: *** [all-recursive] Error 1
>> >
>> We would need a bit more. Is this on rtems5? Often, this kind of
>> failure indicates that configure failed, check your configure step.
>>
>> In RTEMS6 we will be getting rid of configure, but for now there is
>> support for both in the RTEMS6 'master' branch.
>>
>> > Did I miss something or am I doing something wrong? Many thanks in
>> advance for your help!
>> > ___
>> > users mailing list
>> > users@rtems.org
>> > http://lists.rtems.org/mailman/listinfo/users
>>
> ___
> users mailing list
> users@rtems.org
> http://lists.rtems.org/mailman/listinfo/users
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: Error by building a BSP on Ubuntu 18.04

2021-03-11 Thread Olga Syrbachova
It is RTEMS 5.1. I've checked the configure step. It seems to be fine. I
get this:

config.status: creating Makefile

target architecture: sparc.
available BSPs: erc32.
'make all' will build the following BSPs: erc32.
other BSPs can be built with 'make RTEMS_BSP="bsp1 bsp2 ..."'

config.status: creating Makefile

And I still have the same error running make -j 2.

On Thu, 11 Mar 2021 at 00:18, Gedare Bloom  wrote:

> Hi Olga,
>
> On Wed, Mar 10, 2021 at 1:35 PM Olga Syrbachova 
> wrote:
> >
> > Hi! I'm following this tutorial
> https://docs.rtems.org/branches/master/user/installation/kernel.html.
> > After successfully building a tool chain for the SPARC architecture in
> step 5.1.1. I moved to the step 5.3.1. And then in step 5.3.4. I get an
> error:
> >
> > olga@olga-H270M-DS3H:~/development/rtems/kernel/erc32$ make -j 2
> > Making all in sparc-rtems5/c
> > make[1]: Entering directory
> '/home/olga/development/rtems/kernel/erc32/sparc-rtems5/c'
> > Making all in .
> > make[2]: Entering directory
> '/home/olga/development/rtems/kernel/erc32/sparc-rtems5/c'
> > make[2]: Nothing to be done for 'all-am'.
> > make[2]: Leaving directory
> '/home/olga/development/rtems/kernel/erc32/sparc-rtems5/c'
> > Making all in erc32
> > make[2]: Entering directory
> '/home/olga/development/rtems/kernel/erc32/sparc-rtems5/c/erc32'
> > make[2]: *** No rule to make target 'all'.  Stop.
> > make[2]: Leaving directory
> '/home/olga/development/rtems/kernel/erc32/sparc-rtems5/c/erc32'
> > Makefile:362: recipe for target 'all-recursive' failed
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory
> '/home/olga/development/rtems/kernel/erc32/sparc-rtems5/c'
> > Makefile:482: recipe for target 'all-recursive' failed
> > make: *** [all-recursive] Error 1
> >
> We would need a bit more. Is this on rtems5? Often, this kind of
> failure indicates that configure failed, check your configure step.
>
> In RTEMS6 we will be getting rid of configure, but for now there is
> support for both in the RTEMS6 'master' branch.
>
> > Did I miss something or am I doing something wrong? Many thanks in
> advance for your help!
> > ___
> > users mailing list
> > users@rtems.org
> > http://lists.rtems.org/mailman/listinfo/users
>
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: Problem by installing RTEMS 5.1 on Windows 10

2021-03-11 Thread Alireza Banejad
Try running msys2 64 as administrator

On Fri, Mar 5, 2021 at 12:06 PM Olga Syrbachova 
wrote:

> Thank you very much for your reply. I'm using MSYS2 MinGW 64-bit.
> Actually I also tried to install RTEMS 4.11.0 and 4.11.2 and I didn't
> succeed.
> After running:
> $ ../source-builder/sb-set-builder --prefix=/opt/rtems/4.11
> 4.11/rtems-sparc --jobs=none
>
> in ...@LAPTOP-NOT8H6PV MINGW64 /c/opt/rtems/4.11.0/rtems
>
> I got this error:
> ...
> package: expat-2.1.0-x86_64-w64-mingw32-1
> Build Set: Time 0:04:39.603651
> Traceback (most recent call last):
>   File "../source-builder/sb-set-builder", line 29, in 
> setbuilder.run()
>   File "../source-builder/sb/setbuilder.py", line 502, in run
> b.build(deps)
>   File "../source-builder/sb/setbuilder.py", line 354, in build
> self.build_package(configs[s], b)
>   File "../source-builder/sb/setbuilder.py", line 191, in build_package
> _build.make()
>   File "../source-builder/sb/build.py", line 471, in make
> self.builddir()
>   File "../source-builder/sb/build.py", line 340, in builddir
> self.rmdir(builddir)
>   File "../source-builder/sb/build.py", line 161, in rmdir
> path.removeall(rmpath)
>   File "../source-builder/sb/path.py", line 150, in removeall
> os.unlink(file)
> PermissionError: [WinError 5] Zugriff verweigert: 'C:\\opt\\rtems\\4.11.0\\
> rtems\\build\\e2xwm1\\expat-2.1.0\\xmlwf\\xmlwf.exe'
>
> On Fri, 5 Mar 2021 at 01:51, Chris Johns  wrote:
>
>> On 5/3/21 7:11 am, Olga Syrbachova wrote:
>> > Hi! I have a problem installing RTEMS. I follow the tutorial step by
>> step, but
>> > something goes wrong. I work on Windows 10.
>> >
>> > My steps after creating /c/opt/rtems
>> >
>> > $ wget
>> >
>> https://ftp.rtems.org/pub/rtems/releases/5/5.1/sources/rtems-source-builder-5.1.tar.xz
>> > <
>> https://ftp.rtems.org/pub/rtems/releases/5/5.1/sources/rtems-source-builder-5.1.tar.xz
>> >
>> > $ tar Jxf rtems-source-builder-5.1.tar.xz
>> > $ mv rtems-source-builder-5.1 5.1
>> > ...
>> > $ source-builder/sb-check
>> > RTEMS Source Builder - Check, 5.not_released
>> > Environment is ok
>> >
>> > What does 5.not_released mean?
>> >
>>
>> At a guess there is no VERSION file in the stop of the RSB source package
>> which
>> would seem strange give this exists in releases. If there is it is a bug
>> in the
>> RSB on Windows.
>>
>> > By running
>> > $ ../source-builder/sb-set-builder --list-bsets
>> > I get
>> > $ ../source-builder/sb-set-builder --list-bsets
>> > RTEMS Source Builder - Set Builder, 5.1
>> > Traceback (most recent call last):
>> >   File "../source-builder/sb/cmd-set-builder.py", line 26, in 
>> > setbuilder.run()
>> >   File "../source-builder/sb/setbuilder.py", line 722, in run
>> > if not list_bset_cfg_files(opts, configs):
>> >   File "../source-builder/sb/setbuilder.py", line 670, in
>> list_bset_cfg_files
>> > print('Examining: %s' % (os.path.relpath(p)))
>> > LookupError: unknown encoding: cp65001
>>
>> What shell environment are you using?
>>
>> Chris
>>
> ___
> users mailing list
> users@rtems.org
> http://lists.rtems.org/mailman/listinfo/users
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: Installing rtems on 32 bit windows host machine

2021-03-11 Thread Joel Sherrill
On Thu, Mar 11, 2021 at 1:05 PM Alireza Banejad 
wrote:

> Hello everyone,
> I was wondering whether I could install RTEMS on a 32-bit Windows 7 host
> machine using either msys2 or Cygwin.
> I already tried installing it on msys2 i686 but when running sb-check it
> returns:
>
> error: exe: not found: (__cc)  i686-w32-mingw32-gccerror: exe: not found: 
> (__cxx) i686-w32-mingw32-g++
>
> Environment is not correctly set up.
>
> It seems there is no such compiler as i686-w32-mingw32-gcc to add in the 
> first place.
>
>
Assuming you have installed the gcc package, what is the compiler called?

I don't think any of the core developers have seen Windows 7 especially
32-bit in a while.

The file that sets the expectations based on host is
source-builder/sb/windows.py. It may require some tinkering to match a
32-bit environment.

We'd love to have a patch to that file (don't break 64-bit) and, if needed,
documentation.

--joel

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

Installing rtems on 32 bit windows host machine

2021-03-11 Thread Alireza Banejad
Hello everyone,
I was wondering whether I could install RTEMS on a 32-bit Windows 7 host
machine using either msys2 or Cygwin.
I already tried installing it on msys2 i686 but when running sb-check it
returns:

error: exe: not found: (__cc)  i686-w32-mingw32-gccerror: exe: not
found: (__cxx) i686-w32-mingw32-g++

Environment is not correctly set up.

It seems there is no such compiler as i686-w32-mingw32-gcc to add in
the first place.
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

ftw() Test Additions May Require rtems6 Tool Update

2021-03-11 Thread Joel Sherrill
  Hi

First, this does NOT impact rtems5.

On February 3, Eshan Dhawan posted additions to the RTEMS test suite for
ftw() and nftw() which he had previously worked to add to newlib. There
have been multiple updates to the rtems6 tool recipes in the RSB since then
so if you may already have ftw() and nftw() in your tools. But if you
attempt to build RTEMS with tests enabled and get an test link failure
because ftw() is undefined, you will need to update your tools.

I posted a few days ago on devel@ and there was no negative feedback. This
is just being courteous and pointing out some may hit a bump as we improve
POSIX Compliance moving forward with RTEMS.

I'd like to thank Eshan and point out that porting these methods was part
of his GSoC 2020 project. It has just taken this long to make this
particular piece of the project acceptable to Newlib, Cygwin, and RTEMS.
The ftw.h in newlib is used by both Cygwin and Newlib.

Thanks.

--joel
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: RTEMS only executes no task and only finds one core imx7

2021-03-11 Thread Stefan Akatyschew
Hello together,

I think it is stuck in the _Per_CPU_Wait_for_job function in
kernel/rtems/cpukit/score/src/smpmulticastaction.c and I found the
comment in the case statement:
/*
 * Calling this function with the current processor is intentional.
 * We have to perform our own jobs here in case inter-processor
 * interrupts are not working.
 */
I assume there still must be something wrong with the device tree file,
for those interrupts to fail? Is there any way to verify if that is the case?

Kind Regards,
Stefan

On Mar 9 2021, at 8:11 pm, Stefan Akatyschew  wrote:

> Hi Gedare,
> thanks a lot for your answer!
>> Hi Stefan,
>> 
>> On Sun, Feb 28, 2021 at 8:04 AM Stefan Akatyschew
>>  wrote:
>>> 
>>> Hello together,
>>> after I could successfully fiddle around with some tasks on a single
>>> core, I tried to get some basic SMP application running.
>>> I use as before trace32 to load the program and added parts from the
>>> lauterbach iMX7-sabre SMP startup script. With that I at get both cores
>>> running. And also my RTEMS 5 compiler tells me, that RTEMS_SMP is defined.
>>> 
>> And it should work on iMX7
>> https://docs.rtems.org/branches/master/cpu-supplement/arm.html#symmetric-multiprocessing
>> 
>> I don't personally have experience with that, so I can only give some
>> general advice.
> 
> Any advice is appreciated and helps :)
> I tried it now also with the rtems 6 master and I have the same problem
> with it. I also checked as suggested the bspsmp.c files a bit, also
> looked for other maybe significant differences in the dtf, but couldn't
> spot any. But I'm also not really familiar with it.
> 
>>> For my application code, I oriented myself on the "smp01" example. 
>>> https://git.rtems.org/rtems/tree/testsuites/smptests/smp01
>>> Unfortunately I see that core 0 is stuck in the "smpmulticastaction.c"
>>> in some loading functions, I can't really wrap my head around? While
>> Which function? can you backtrace?
> 
> That are actually a few, it circles around those:
> rtems/score/cpuimpl.h:101 Per_CPU_Control
> *_ARM_Get_current_per_CPU_control( void )
> rtems/score/cpustdatomic.h:250 long _CPU_atomic_Load_ulong( const
> CPU_atomic_Ulong *obj, CPU_atomic_Order order )
> rtems/score/src/smpmulticastaction.c:88 _Per_CPU_Try_perform_jobs(
> Per_CPU_Control *cpu_self )
> rtems/cpukit/score/src/smpmulticastaction.c:110 void
> _Per_CPU_Wait_for_job(const Per_CPU_Control *cpu, const Per_CPU_Job *job)
> rtems/score/cpu.h:252 void _ARM_Data_synchronization_barrier( void )
> rtems/score/cpu.h:492 void _ARM_Send_event( void )
> (attached rtems5-smp.png)
> I can also see that none of my threads is actually running, only
> _CPU_Thread_Idle_body (attached picture rtems5-smp-threads.png)
> 
> 
>>> core 1 is stuck at an IRQ intialisation routine (in irq/irq-gic.c) for
>> ditto?
> 
> I can't really debug the second core somehow. Though Trace32 is supposed
> to step through core 0 and 1 simultaniously (in SMP), it does only work
> on core 0 for me. Trying to do that on core 1 results in bus error for me...
> All I see is it being stuck at : irq/irq-gic.c:157
> BSP_START_TEXT_SECTION void arm_gic_irq_initialize_secondary_cpu(void)
> 
>>> the second core.
>>> I tried fiddeling around with the configuration and different taks, but
>>> get always the same response. I've gone through the user manual and the
>>> API guide, but couldn't find any problems.
>>> The application as is works fine on a single core, if I set the
>>> CONFIGURE_MAXIMUM_PROCESSORS to 1.
>>> 
>>> Any ideas what I'm doing wrong? I attached my two source files and the
>>> practice Script.
>>> 
>> 
>> Unfortunately, I don't think the SMP boot sequence is well-documented.
>> You probably have to work your way through the code.
>> bsps/arm/shared/start/arm-a9mpcore-smp.c
>> 
>> There is some doxygen that might help you too:
>> https://docs.rtems.org/doxygen/branches/master/group__ScoreSMP.html
>> 
>> and you can check out the bspsmp.c files beneath bsps/ of some other
>> implementations for some ideas.
>> 
>> We probably need a section related to SMP initialization added to
>> https://docs.rtems.org/branches/master/bsp-howto/index.html
>> 
>> Maybe someone with more experience on this particular board or with
>> arm/SMP will be able to suggest better insight.
>> 
>> -Gedare
>> 
>>> Thanks a lot for your help.
>>> Kind regards,
>>> Stefan___
>>> users mailing list
>>> users@rtems.org
>>> http://lists.rtems.org/mailman/listinfo/users
>> 
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users


Re: Issues with configuring BSP with waf

2021-03-11 Thread Ida Delphine
Okay. Thank you :)

On Thu, 11 Mar 2021, 5:57 pm Gedare Bloom,  wrote:

> On Thu, Mar 11, 2021 at 9:48 AM Ida Delphine  wrote:
> >
> > Thank you for your response. I am not working on the rtems.git/master
> branch. I'm not using it because earlier I tried downloading sources with
> it but I got this error
> > error: shell macro failed:
> /home/idadel/quick-start/src/rsb/source-builder/sb/rtems-build-dep -c gcc
> -l : 2: error: no library (-l) provided
> > So I decided to use the other alternative(get the sources from releases)
> >
> > Since I'm a GSoC applicant should I wait till the issue at the master
> branch is resolved?
> >
> Yes, that issue has been resolved so please try again. Hopefully,
> things work a bit better. We try not to break things, but unexpected
> problems come up from time to time, especially based on host OS
> dependencies.
>
> > Cheers,
> > Ida.
> >
> > On Thu, Mar 11, 2021 at 4:18 PM Gedare Bloom  wrote:
> >>
> >> On Thu, Mar 11, 2021 at 7:33 AM Ida Delphine  wrote:
> >> >
> >> > Hello everyone,
> >> > Was following the quick build documentation and had issues around
> where I have to do a manual BSP build.  In the last step of configuring the
> BSP, I ran this command:
> >> >
> >> > ./waf configure --prefix=$HOME/quick-start/rtems/5
> >> >
> >> Are you working on rtems.git/master branch or /5 branch? Note that you
> >> need to be sure to use a consistent compiler toolchain based on the
> >> version of RTEMS that you use.
> >>
> >> In rtems/5 branch we don't have waf support integrated yet. The
> >> upgrade to waf is happening currently on the master branch, which will
> >> eventually become the RTEMS version 6 release.
> >>
> >> For GSoC students we expect development to happen on the development
> >> head and not a release, so please make sure that you have the
> >> toolchain built from rtems-source-builder.git/master and the rtems
> >> source tree from rtems.git/master.
> >>
> >> > It didn't produce the expected output. I instead got:
> >> > bash: ./waf: No such file or directory
> >> > As a result I downloaded it with the command:
> >> > curl https://waf.io/waf-2.0.19 > waf
> >>
> >> https://git.rtems.org/rtems/tree/waf
> >>
> >> Currently, the waf-based build of rtems only supports "in tree"
> >> builds, which means you need to run waf from within the rtems.git/
> >> root of your source. This is a limitation of the waf build.
> >>
> >> FWIW, waf build improvements could also fall under GSoC effort,
> >> although no one has written it up as a task yet. It would be mostly
> >> Python.
> >>
> >> > I ran  the last command to configure the BSP again but still did not
> get the expected  output. I got this rather:
> >> > Waf: Run from a folder containing a 'wscript' file (or try -h for the
> generic options)
> >> > Please how do I fix this? What am I missing?
> >> > I have tried looking for solutions but to no avail.
> >> >
> >> Sometimes the solutions only exist inside other people's heads, so
> >> asking questions is encouraged.
> >>
> >> > Thanks,
> >> > Ida.
> >> > ___
> >> > users mailing list
> >> > users@rtems.org
> >> > http://lists.rtems.org/mailman/listinfo/users
>
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: Issues with configuring BSP with waf

2021-03-11 Thread Gedare Bloom
On Thu, Mar 11, 2021 at 9:48 AM Ida Delphine  wrote:
>
> Thank you for your response. I am not working on the rtems.git/master branch. 
> I'm not using it because earlier I tried downloading sources with it but I 
> got this error
> error: shell macro failed: 
> /home/idadel/quick-start/src/rsb/source-builder/sb/rtems-build-dep -c gcc  -l 
> : 2: error: no library (-l) provided
> So I decided to use the other alternative(get the sources from releases)
>
> Since I'm a GSoC applicant should I wait till the issue at the master branch 
> is resolved?
>
Yes, that issue has been resolved so please try again. Hopefully,
things work a bit better. We try not to break things, but unexpected
problems come up from time to time, especially based on host OS
dependencies.

> Cheers,
> Ida.
>
> On Thu, Mar 11, 2021 at 4:18 PM Gedare Bloom  wrote:
>>
>> On Thu, Mar 11, 2021 at 7:33 AM Ida Delphine  wrote:
>> >
>> > Hello everyone,
>> > Was following the quick build documentation and had issues around where I 
>> > have to do a manual BSP build.  In the last step of configuring the BSP, I 
>> > ran this command:
>> >
>> > ./waf configure --prefix=$HOME/quick-start/rtems/5
>> >
>> Are you working on rtems.git/master branch or /5 branch? Note that you
>> need to be sure to use a consistent compiler toolchain based on the
>> version of RTEMS that you use.
>>
>> In rtems/5 branch we don't have waf support integrated yet. The
>> upgrade to waf is happening currently on the master branch, which will
>> eventually become the RTEMS version 6 release.
>>
>> For GSoC students we expect development to happen on the development
>> head and not a release, so please make sure that you have the
>> toolchain built from rtems-source-builder.git/master and the rtems
>> source tree from rtems.git/master.
>>
>> > It didn't produce the expected output. I instead got:
>> > bash: ./waf: No such file or directory
>> > As a result I downloaded it with the command:
>> > curl https://waf.io/waf-2.0.19 > waf
>>
>> https://git.rtems.org/rtems/tree/waf
>>
>> Currently, the waf-based build of rtems only supports "in tree"
>> builds, which means you need to run waf from within the rtems.git/
>> root of your source. This is a limitation of the waf build.
>>
>> FWIW, waf build improvements could also fall under GSoC effort,
>> although no one has written it up as a task yet. It would be mostly
>> Python.
>>
>> > I ran  the last command to configure the BSP again but still did not get 
>> > the expected  output. I got this rather:
>> > Waf: Run from a folder containing a 'wscript' file (or try -h for the 
>> > generic options)
>> > Please how do I fix this? What am I missing?
>> > I have tried looking for solutions but to no avail.
>> >
>> Sometimes the solutions only exist inside other people's heads, so
>> asking questions is encouraged.
>>
>> > Thanks,
>> > Ida.
>> > ___
>> > users mailing list
>> > users@rtems.org
>> > http://lists.rtems.org/mailman/listinfo/users
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users


Re: Offline download of sources fails

2021-03-11 Thread Ida Delphine
Thank you. Will do that.

On Thu, Mar 11, 2021 at 5:55 PM Gedare Bloom  wrote:

> On Thu, Mar 11, 2021 at 8:31 AM Gedare Bloom  wrote:
> >
> > On Thu, Mar 11, 2021 at 8:12 AM Gedare Bloom  wrote:
> > >
> > > On Thu, Mar 11, 2021 at 4:33 AM  wrote:
> > > >
> > > >
> > > > > -Original Message-
> > > > > From: users  On Behalf Of Chris Johns
> > > > > Sent: Thursday, March 11, 2021 6:07 AM
> > > > > To: Ida Delphine 
> > > > > Cc: rtems-us...@rtems.org 
> > > > > Subject: Re: Offline download of sources fails
> > > > >
> > > > >
> > > > >
> > > > > On 11/3/21 3:34 pm, Ida Delphine wrote:
> > > > > > Hello again,
> > > > > >
> > > > > > So I started over and downloaded all the required packages for
> my host
> > > > > > (Ubuntu
> > > > > > 20.04) and still have offline download issues...
> > > > > > Please take a look at the error message:
> > > > > >
> > > > > > RTEMS Source Builder - Set Builder, 6 (fe2d13b6daf3) Build Set:
> > > > > > 6/rtems-sparc Build Set: 6/rtems-autotools.bset Build Set:
> > > > > > 6/rtems-autotools-internal.bset
> > > > > > config: tools/rtems-autoconf-2.69-1.cfg
> > > > > > config: tools/rtems-automake-1.12.6-1.cfg Build Sizes: usage:
> 0.000B
> > > > > > total: 19.014KB (sources: 0.000B, patches: 19.014KB, installed
> 0.000B)
> > > > > > Build Set: Time 0:00:00.933172 Build Set:
> 6/rtems-autotools-base.bset
> > > > > > config: tools/rtems-autoconf-2.69-1.cfg
> > > > > > config: tools/rtems-automake-1.12.6-1.cfg Build Sizes: usage:
> 0.000B
> > > > > > total: 19.014KB (sources: 0.000B, patches: 19.014KB, installed
> 0.000B)
> > > > > > Build Set: Time 0:00:00.840448 Build Set: Time 0:00:01.777350
> > > > > > config: devel/expat-2.1.0-1.cfg
> > > > > > package: expat-2.1.0-x86_64-linux-gnu-1 Creating source
> directory:
> > > > > > sources
> > > > > > download:
> > > > > >
> https://github.com/libexpat/libexpat/releases/download/R_2_1_0/expat-
> > > > > 2
> > > > > > .1.0.tar.gz
> > > > > >
> > > > > <
> https://github.com/libexpat/libexpat/releases/download/R_2_1_0/expat-
> > > > > > 2.1.0.tar.gz>
> > > > > > -> sources/expat-2.1.0.tar.gz
> > > > > >  redirect:
> > > > > >
> https://github-releases.githubusercontent.com/80314213/0186bc60-b675-
> > > > > 11e7-83c0-13aced4..
> > > > > > <
> https://github-releases.githubusercontent.com/80314213/0186bc60-
> > > > > b675-
> > > > > > 11e7-83c0-13aced4..>. > > > > > log>
> > > > > > downloading: sources/expat-2.1.0.tar.gz - 549.4kB of 549.4kB
> (100%)
> > > > > > reporting: devel/expat-2.1.0-1.cfg ->
> > > > > > expat-2.1.0-x86_64-linux-gnu-1.txt
> > > > > > reporting: devel/expat-2.1.0-1.cfg ->
> > > > > > expat-2.1.0-x86_64-linux-gnu-1.xml
> > > > > > config: devel/gmp-6.1.0.cfg
> > > > > > package: gmp-6.1.0-x86_64-linux-gnu-1
> > > > > > download:
> https://gcc.gnu.org/pub/gcc/infrastructure/gmp-6.1.0.tar.bz2
> > > > > > 
> ->
> > > > > > sources/gmp-6.1.0.tar.bz2
> > > > > > downloading: sources/gmp-6.1.0.tar.bz2 - 2.3MB of 2.3MB (100%)
> > > > > > reporting: devel/gmp-6.1.0.cfg ->
> gmp-6.1.0-x86_64-linux-gnu-1.txt
> > > > > > reporting: devel/gmp-6.1.0.cfg ->
> gmp-6.1.0-x86_64-linux-gnu-1.xml
> > > > > > config: tools/rtems-gdb-10.cfg
> > > > > > error: shell macro failed:
> > > > > >
> /home/idadel/quick-start/src/rsb/source-builder/sb/rtems-build-dep -c
> > > > > gcc  -l :
> > > > > > 2: error: no library (-l) provided
> > > > >
> > > > > I think this looks like something with Windows and the shell.
> > > > >
> > > >
> > > > Our nightly test build ran into the same problem.
> > > > The runner uses Ubuntu 18.04.
> > > > I ran again with the trace option and the error source in question
> seems to be here:
> > > >
> > > > config: source-builder/config/gdb-common-1.cfg: 118:>%define
> gdb-python-lib-check %(%{_sbdir}/sb/rtems-build-dep -c %{__cc}
> %{gdb-host-libs} -l %{gdb-python-config-libs}) [True]
> > > > exe: shell:
> /tmp/rtems-source-builder/source-builder/sb/rtems-build-dep -c gcc  -l
> > > > exe: /tmp/rtems-source-builder/source-builder/sb/rtems-build-dep -c
> gcc  -l
> > > > shell-output: 2 error: no library (-l) provided
> > > > error: shell macro failed:
> /tmp/rtems-source-builder/source-builder/sb/rtems-build-dep -c gcc  -l : 2:
> error: no library (-l) provided
> > > > Build Set: Time 0:00:35.508777
> > > >
> > >
> > > It means %{gdb-python-config-libs} is empty/missing. Would need to
> > > back out from there to figure out why.
> > >
> >
> > https://devel.rtems.org/ticket/4335
> >
> > The fix is coming shortly.
> >
>
> This has been fixed on 5 and master, please `git pull` to update RSB
> and try again.
>
> > > > I also tried a few earlier commits.
> > > > The last working commit for me is
> > > > 47d540e - (2 days ago) 7: Update tool chain - Sebastian Huber
> > > >
> > > > I don't know very much about the rsb internals, but hope this might
> help someone who does.
> > > >
> > > > Best regards,
> > > >
> > > > Jan
> > > >
> > > > > Could you

Re: Issues with configuring BSP with waf

2021-03-11 Thread Vijay Kumar Banerjee
Hello Ida,


On Thu, Mar 11, 2021 at 9:48 AM Ida Delphine  wrote:
>
> Thank you for your response. I am not working on the rtems.git/master branch. 
> I'm not using it because earlier I tried downloading sources with it but I 
> got this error
> error: shell macro failed: 
> /home/idadel/quick-start/src/rsb/source-builder/sb/rtems-build-dep -c gcc  -l 
> : 2: error: no library (-l) provided
> So I decided to use the other alternative(get the sources from releases)
>
> Since I'm a GSoC applicant should I wait till the issue at the master branch 
> is resolved?
>
The wait is over. The issue has been resolved upstream and hopefully,
you'll be able to build it without issue.

Best regards,
Vijay

> Cheers,
> Ida.
>
> On Thu, Mar 11, 2021 at 4:18 PM Gedare Bloom  wrote:
>>
>> On Thu, Mar 11, 2021 at 7:33 AM Ida Delphine  wrote:
>> >
>> > Hello everyone,
>> > Was following the quick build documentation and had issues around where I 
>> > have to do a manual BSP build.  In the last step of configuring the BSP, I 
>> > ran this command:
>> >
>> > ./waf configure --prefix=$HOME/quick-start/rtems/5
>> >
>> Are you working on rtems.git/master branch or /5 branch? Note that you
>> need to be sure to use a consistent compiler toolchain based on the
>> version of RTEMS that you use.
>>
>> In rtems/5 branch we don't have waf support integrated yet. The
>> upgrade to waf is happening currently on the master branch, which will
>> eventually become the RTEMS version 6 release.
>>
>> For GSoC students we expect development to happen on the development
>> head and not a release, so please make sure that you have the
>> toolchain built from rtems-source-builder.git/master and the rtems
>> source tree from rtems.git/master.
>>
>> > It didn't produce the expected output. I instead got:
>> > bash: ./waf: No such file or directory
>> > As a result I downloaded it with the command:
>> > curl https://waf.io/waf-2.0.19 > waf
>>
>> https://git.rtems.org/rtems/tree/waf
>>
>> Currently, the waf-based build of rtems only supports "in tree"
>> builds, which means you need to run waf from within the rtems.git/
>> root of your source. This is a limitation of the waf build.
>>
>> FWIW, waf build improvements could also fall under GSoC effort,
>> although no one has written it up as a task yet. It would be mostly
>> Python.
>>
>> > I ran  the last command to configure the BSP again but still did not get 
>> > the expected  output. I got this rather:
>> > Waf: Run from a folder containing a 'wscript' file (or try -h for the 
>> > generic options)
>> > Please how do I fix this? What am I missing?
>> > I have tried looking for solutions but to no avail.
>> >
>> Sometimes the solutions only exist inside other people's heads, so
>> asking questions is encouraged.
>>
>> > Thanks,
>> > Ida.
>> > ___
>> > users mailing list
>> > users@rtems.org
>> > http://lists.rtems.org/mailman/listinfo/users
>
> ___
> users mailing list
> users@rtems.org
> http://lists.rtems.org/mailman/listinfo/users
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users


Re: Offline download of sources fails

2021-03-11 Thread Gedare Bloom
On Thu, Mar 11, 2021 at 8:31 AM Gedare Bloom  wrote:
>
> On Thu, Mar 11, 2021 at 8:12 AM Gedare Bloom  wrote:
> >
> > On Thu, Mar 11, 2021 at 4:33 AM  wrote:
> > >
> > >
> > > > -Original Message-
> > > > From: users  On Behalf Of Chris Johns
> > > > Sent: Thursday, March 11, 2021 6:07 AM
> > > > To: Ida Delphine 
> > > > Cc: rtems-us...@rtems.org 
> > > > Subject: Re: Offline download of sources fails
> > > >
> > > >
> > > >
> > > > On 11/3/21 3:34 pm, Ida Delphine wrote:
> > > > > Hello again,
> > > > >
> > > > > So I started over and downloaded all the required packages for my host
> > > > > (Ubuntu
> > > > > 20.04) and still have offline download issues...
> > > > > Please take a look at the error message:
> > > > >
> > > > > RTEMS Source Builder - Set Builder, 6 (fe2d13b6daf3) Build Set:
> > > > > 6/rtems-sparc Build Set: 6/rtems-autotools.bset Build Set:
> > > > > 6/rtems-autotools-internal.bset
> > > > > config: tools/rtems-autoconf-2.69-1.cfg
> > > > > config: tools/rtems-automake-1.12.6-1.cfg Build Sizes: usage: 0.000B
> > > > > total: 19.014KB (sources: 0.000B, patches: 19.014KB, installed 0.000B)
> > > > > Build Set: Time 0:00:00.933172 Build Set: 6/rtems-autotools-base.bset
> > > > > config: tools/rtems-autoconf-2.69-1.cfg
> > > > > config: tools/rtems-automake-1.12.6-1.cfg Build Sizes: usage: 0.000B
> > > > > total: 19.014KB (sources: 0.000B, patches: 19.014KB, installed 0.000B)
> > > > > Build Set: Time 0:00:00.840448 Build Set: Time 0:00:01.777350
> > > > > config: devel/expat-2.1.0-1.cfg
> > > > > package: expat-2.1.0-x86_64-linux-gnu-1 Creating source directory:
> > > > > sources
> > > > > download:
> > > > > https://github.com/libexpat/libexpat/releases/download/R_2_1_0/expat-
> > > > 2
> > > > > .1.0.tar.gz
> > > > >
> > > >  > > > > 2.1.0.tar.gz>
> > > > > -> sources/expat-2.1.0.tar.gz
> > > > >  redirect:
> > > > > https://github-releases.githubusercontent.com/80314213/0186bc60-b675-
> > > > 11e7-83c0-13aced4..
> > > > >  > > > b675-
> > > > > 11e7-83c0-13aced4..>. > > > > log>
> > > > > downloading: sources/expat-2.1.0.tar.gz - 549.4kB of 549.4kB (100%)
> > > > > reporting: devel/expat-2.1.0-1.cfg ->
> > > > > expat-2.1.0-x86_64-linux-gnu-1.txt
> > > > > reporting: devel/expat-2.1.0-1.cfg ->
> > > > > expat-2.1.0-x86_64-linux-gnu-1.xml
> > > > > config: devel/gmp-6.1.0.cfg
> > > > > package: gmp-6.1.0-x86_64-linux-gnu-1
> > > > > download: https://gcc.gnu.org/pub/gcc/infrastructure/gmp-6.1.0.tar.bz2
> > > > >  ->
> > > > > sources/gmp-6.1.0.tar.bz2
> > > > > downloading: sources/gmp-6.1.0.tar.bz2 - 2.3MB of 2.3MB (100%)
> > > > > reporting: devel/gmp-6.1.0.cfg -> gmp-6.1.0-x86_64-linux-gnu-1.txt
> > > > > reporting: devel/gmp-6.1.0.cfg -> gmp-6.1.0-x86_64-linux-gnu-1.xml
> > > > > config: tools/rtems-gdb-10.cfg
> > > > > error: shell macro failed:
> > > > > /home/idadel/quick-start/src/rsb/source-builder/sb/rtems-build-dep -c
> > > > gcc  -l :
> > > > > 2: error: no library (-l) provided
> > > >
> > > > I think this looks like something with Windows and the shell.
> > > >
> > >
> > > Our nightly test build ran into the same problem.
> > > The runner uses Ubuntu 18.04.
> > > I ran again with the trace option and the error source in question seems 
> > > to be here:
> > >
> > > config: source-builder/config/gdb-common-1.cfg: 118:>%define 
> > > gdb-python-lib-check %(%{_sbdir}/sb/rtems-build-dep -c %{__cc} 
> > > %{gdb-host-libs} -l %{gdb-python-config-libs}) [True]
> > > exe: shell: /tmp/rtems-source-builder/source-builder/sb/rtems-build-dep 
> > > -c gcc  -l
> > > exe: /tmp/rtems-source-builder/source-builder/sb/rtems-build-dep -c gcc  
> > > -l
> > > shell-output: 2 error: no library (-l) provided
> > > error: shell macro failed: 
> > > /tmp/rtems-source-builder/source-builder/sb/rtems-build-dep -c gcc  -l : 
> > > 2: error: no library (-l) provided
> > > Build Set: Time 0:00:35.508777
> > >
> >
> > It means %{gdb-python-config-libs} is empty/missing. Would need to
> > back out from there to figure out why.
> >
>
> https://devel.rtems.org/ticket/4335
>
> The fix is coming shortly.
>

This has been fixed on 5 and master, please `git pull` to update RSB
and try again.

> > > I also tried a few earlier commits.
> > > The last working commit for me is
> > > 47d540e - (2 days ago) 7: Update tool chain - Sebastian Huber
> > >
> > > I don't know very much about the rsb internals, but hope this might help 
> > > someone who does.
> > >
> > > Best regards,
> > >
> > > Jan
> > >
> > > > Could you please run with --trace and then search the log file for this 
> > > > the
> > > > above line. The shell macro should be present that failed.
> > > >
> > > > > Build FAILED
> > > > > Build Set: Time 0:00:12.713688
> > > > > Build FAILED
> > > > >
> > > > > Also for some reason when I run "sb-

Re: Issues with configuring BSP with waf

2021-03-11 Thread Ida Delphine
Thank you for your response. I am not working on the rtems.git/master
branch. I'm not using it because earlier I tried downloading sources with
it but I got this error
error: shell macro failed:
/home/idadel/quick-start/src/rsb/source-builder/sb/rtems-build-dep -c gcc
 -l : 2: error: no library (-l) provided
So I decided to use the other alternative(get the sources from releases)

Since I'm a GSoC applicant should I wait till the issue at the master
branch is resolved?

Cheers,
Ida.

On Thu, Mar 11, 2021 at 4:18 PM Gedare Bloom  wrote:

> On Thu, Mar 11, 2021 at 7:33 AM Ida Delphine  wrote:
> >
> > Hello everyone,
> > Was following the quick build documentation and had issues around where
> I have to do a manual BSP build.  In the last step of configuring the BSP,
> I ran this command:
> >
> > ./waf configure --prefix=$HOME/quick-start/rtems/5
> >
> Are you working on rtems.git/master branch or /5 branch? Note that you
> need to be sure to use a consistent compiler toolchain based on the
> version of RTEMS that you use.
>
> In rtems/5 branch we don't have waf support integrated yet. The
> upgrade to waf is happening currently on the master branch, which will
> eventually become the RTEMS version 6 release.
>
> For GSoC students we expect development to happen on the development
> head and not a release, so please make sure that you have the
> toolchain built from rtems-source-builder.git/master and the rtems
> source tree from rtems.git/master.
>
> > It didn't produce the expected output. I instead got:
> > bash: ./waf: No such file or directory
> > As a result I downloaded it with the command:
> > curl https://waf.io/waf-2.0.19 > waf
>
> https://git.rtems.org/rtems/tree/waf
>
> Currently, the waf-based build of rtems only supports "in tree"
> builds, which means you need to run waf from within the rtems.git/
> root of your source. This is a limitation of the waf build.
>
> FWIW, waf build improvements could also fall under GSoC effort,
> although no one has written it up as a task yet. It would be mostly
> Python.
>
> > I ran  the last command to configure the BSP again but still did not get
> the expected  output. I got this rather:
> > Waf: Run from a folder containing a 'wscript' file (or try -h for the
> generic options)
> > Please how do I fix this? What am I missing?
> > I have tried looking for solutions but to no avail.
> >
> Sometimes the solutions only exist inside other people's heads, so
> asking questions is encouraged.
>
> > Thanks,
> > Ida.
> > ___
> > users mailing list
> > users@rtems.org
> > http://lists.rtems.org/mailman/listinfo/users
>
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: Offline download of sources fails

2021-03-11 Thread Gedare Bloom
On Thu, Mar 11, 2021 at 8:12 AM Gedare Bloom  wrote:
>
> On Thu, Mar 11, 2021 at 4:33 AM  wrote:
> >
> >
> > > -Original Message-
> > > From: users  On Behalf Of Chris Johns
> > > Sent: Thursday, March 11, 2021 6:07 AM
> > > To: Ida Delphine 
> > > Cc: rtems-us...@rtems.org 
> > > Subject: Re: Offline download of sources fails
> > >
> > >
> > >
> > > On 11/3/21 3:34 pm, Ida Delphine wrote:
> > > > Hello again,
> > > >
> > > > So I started over and downloaded all the required packages for my host
> > > > (Ubuntu
> > > > 20.04) and still have offline download issues...
> > > > Please take a look at the error message:
> > > >
> > > > RTEMS Source Builder - Set Builder, 6 (fe2d13b6daf3) Build Set:
> > > > 6/rtems-sparc Build Set: 6/rtems-autotools.bset Build Set:
> > > > 6/rtems-autotools-internal.bset
> > > > config: tools/rtems-autoconf-2.69-1.cfg
> > > > config: tools/rtems-automake-1.12.6-1.cfg Build Sizes: usage: 0.000B
> > > > total: 19.014KB (sources: 0.000B, patches: 19.014KB, installed 0.000B)
> > > > Build Set: Time 0:00:00.933172 Build Set: 6/rtems-autotools-base.bset
> > > > config: tools/rtems-autoconf-2.69-1.cfg
> > > > config: tools/rtems-automake-1.12.6-1.cfg Build Sizes: usage: 0.000B
> > > > total: 19.014KB (sources: 0.000B, patches: 19.014KB, installed 0.000B)
> > > > Build Set: Time 0:00:00.840448 Build Set: Time 0:00:01.777350
> > > > config: devel/expat-2.1.0-1.cfg
> > > > package: expat-2.1.0-x86_64-linux-gnu-1 Creating source directory:
> > > > sources
> > > > download:
> > > > https://github.com/libexpat/libexpat/releases/download/R_2_1_0/expat-
> > > 2
> > > > .1.0.tar.gz
> > > >
> > >  > > > 2.1.0.tar.gz>
> > > > -> sources/expat-2.1.0.tar.gz
> > > >  redirect:
> > > > https://github-releases.githubusercontent.com/80314213/0186bc60-b675-
> > > 11e7-83c0-13aced4..
> > > >  > > b675-
> > > > 11e7-83c0-13aced4..>. > > > log>
> > > > downloading: sources/expat-2.1.0.tar.gz - 549.4kB of 549.4kB (100%)
> > > > reporting: devel/expat-2.1.0-1.cfg ->
> > > > expat-2.1.0-x86_64-linux-gnu-1.txt
> > > > reporting: devel/expat-2.1.0-1.cfg ->
> > > > expat-2.1.0-x86_64-linux-gnu-1.xml
> > > > config: devel/gmp-6.1.0.cfg
> > > > package: gmp-6.1.0-x86_64-linux-gnu-1
> > > > download: https://gcc.gnu.org/pub/gcc/infrastructure/gmp-6.1.0.tar.bz2
> > > >  ->
> > > > sources/gmp-6.1.0.tar.bz2
> > > > downloading: sources/gmp-6.1.0.tar.bz2 - 2.3MB of 2.3MB (100%)
> > > > reporting: devel/gmp-6.1.0.cfg -> gmp-6.1.0-x86_64-linux-gnu-1.txt
> > > > reporting: devel/gmp-6.1.0.cfg -> gmp-6.1.0-x86_64-linux-gnu-1.xml
> > > > config: tools/rtems-gdb-10.cfg
> > > > error: shell macro failed:
> > > > /home/idadel/quick-start/src/rsb/source-builder/sb/rtems-build-dep -c
> > > gcc  -l :
> > > > 2: error: no library (-l) provided
> > >
> > > I think this looks like something with Windows and the shell.
> > >
> >
> > Our nightly test build ran into the same problem.
> > The runner uses Ubuntu 18.04.
> > I ran again with the trace option and the error source in question seems to 
> > be here:
> >
> > config: source-builder/config/gdb-common-1.cfg: 118:>%define 
> > gdb-python-lib-check %(%{_sbdir}/sb/rtems-build-dep -c %{__cc} 
> > %{gdb-host-libs} -l %{gdb-python-config-libs}) [True]
> > exe: shell: /tmp/rtems-source-builder/source-builder/sb/rtems-build-dep -c 
> > gcc  -l
> > exe: /tmp/rtems-source-builder/source-builder/sb/rtems-build-dep -c gcc  -l
> > shell-output: 2 error: no library (-l) provided
> > error: shell macro failed: 
> > /tmp/rtems-source-builder/source-builder/sb/rtems-build-dep -c gcc  -l : 2: 
> > error: no library (-l) provided
> > Build Set: Time 0:00:35.508777
> >
>
> It means %{gdb-python-config-libs} is empty/missing. Would need to
> back out from there to figure out why.
>

https://devel.rtems.org/ticket/4335

The fix is coming shortly.

> > I also tried a few earlier commits.
> > The last working commit for me is
> > 47d540e - (2 days ago) 7: Update tool chain - Sebastian Huber
> >
> > I don't know very much about the rsb internals, but hope this might help 
> > someone who does.
> >
> > Best regards,
> >
> > Jan
> >
> > > Could you please run with --trace and then search the log file for this 
> > > the
> > > above line. The shell macro should be present that failed.
> > >
> > > > Build FAILED
> > > > Build Set: Time 0:00:12.713688
> > > > Build FAILED
> > > >
> > > > Also for some reason when I run "sb-check" it tells me "command not
> > > found"
> > >
> > > This looks like a Windows issue.
> > >
> > > Chris
> > > ___
> > > users mailing list
> > > users@rtems.org
> > > http://lists.rtems.org/mailman/listinfo/users
> > ___
> > users mailing list
> > users@rtems.org
> > http://lists.rtems.org/

Re: Issues with configuring BSP with waf

2021-03-11 Thread Gedare Bloom
On Thu, Mar 11, 2021 at 7:33 AM Ida Delphine  wrote:
>
> Hello everyone,
> Was following the quick build documentation and had issues around where I 
> have to do a manual BSP build.  In the last step of configuring the BSP, I 
> ran this command:
>
> ./waf configure --prefix=$HOME/quick-start/rtems/5
>
Are you working on rtems.git/master branch or /5 branch? Note that you
need to be sure to use a consistent compiler toolchain based on the
version of RTEMS that you use.

In rtems/5 branch we don't have waf support integrated yet. The
upgrade to waf is happening currently on the master branch, which will
eventually become the RTEMS version 6 release.

For GSoC students we expect development to happen on the development
head and not a release, so please make sure that you have the
toolchain built from rtems-source-builder.git/master and the rtems
source tree from rtems.git/master.

> It didn't produce the expected output. I instead got:
> bash: ./waf: No such file or directory
> As a result I downloaded it with the command:
> curl https://waf.io/waf-2.0.19 > waf

https://git.rtems.org/rtems/tree/waf

Currently, the waf-based build of rtems only supports "in tree"
builds, which means you need to run waf from within the rtems.git/
root of your source. This is a limitation of the waf build.

FWIW, waf build improvements could also fall under GSoC effort,
although no one has written it up as a task yet. It would be mostly
Python.

> I ran  the last command to configure the BSP again but still did not get the 
> expected  output. I got this rather:
> Waf: Run from a folder containing a 'wscript' file (or try -h for the generic 
> options)
> Please how do I fix this? What am I missing?
> I have tried looking for solutions but to no avail.
>
Sometimes the solutions only exist inside other people's heads, so
asking questions is encouraged.

> Thanks,
> Ida.
> ___
> users mailing list
> users@rtems.org
> http://lists.rtems.org/mailman/listinfo/users
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users


Re: Offline download of sources fails

2021-03-11 Thread Gedare Bloom
On Thu, Mar 11, 2021 at 4:33 AM  wrote:
>
>
> > -Original Message-
> > From: users  On Behalf Of Chris Johns
> > Sent: Thursday, March 11, 2021 6:07 AM
> > To: Ida Delphine 
> > Cc: rtems-us...@rtems.org 
> > Subject: Re: Offline download of sources fails
> >
> >
> >
> > On 11/3/21 3:34 pm, Ida Delphine wrote:
> > > Hello again,
> > >
> > > So I started over and downloaded all the required packages for my host
> > > (Ubuntu
> > > 20.04) and still have offline download issues...
> > > Please take a look at the error message:
> > >
> > > RTEMS Source Builder - Set Builder, 6 (fe2d13b6daf3) Build Set:
> > > 6/rtems-sparc Build Set: 6/rtems-autotools.bset Build Set:
> > > 6/rtems-autotools-internal.bset
> > > config: tools/rtems-autoconf-2.69-1.cfg
> > > config: tools/rtems-automake-1.12.6-1.cfg Build Sizes: usage: 0.000B
> > > total: 19.014KB (sources: 0.000B, patches: 19.014KB, installed 0.000B)
> > > Build Set: Time 0:00:00.933172 Build Set: 6/rtems-autotools-base.bset
> > > config: tools/rtems-autoconf-2.69-1.cfg
> > > config: tools/rtems-automake-1.12.6-1.cfg Build Sizes: usage: 0.000B
> > > total: 19.014KB (sources: 0.000B, patches: 19.014KB, installed 0.000B)
> > > Build Set: Time 0:00:00.840448 Build Set: Time 0:00:01.777350
> > > config: devel/expat-2.1.0-1.cfg
> > > package: expat-2.1.0-x86_64-linux-gnu-1 Creating source directory:
> > > sources
> > > download:
> > > https://github.com/libexpat/libexpat/releases/download/R_2_1_0/expat-
> > 2
> > > .1.0.tar.gz
> > >
> >  > > 2.1.0.tar.gz>
> > > -> sources/expat-2.1.0.tar.gz
> > >  redirect:
> > > https://github-releases.githubusercontent.com/80314213/0186bc60-b675-
> > 11e7-83c0-13aced4..
> > >  > b675-
> > > 11e7-83c0-13aced4..>. > > log>
> > > downloading: sources/expat-2.1.0.tar.gz - 549.4kB of 549.4kB (100%)
> > > reporting: devel/expat-2.1.0-1.cfg ->
> > > expat-2.1.0-x86_64-linux-gnu-1.txt
> > > reporting: devel/expat-2.1.0-1.cfg ->
> > > expat-2.1.0-x86_64-linux-gnu-1.xml
> > > config: devel/gmp-6.1.0.cfg
> > > package: gmp-6.1.0-x86_64-linux-gnu-1
> > > download: https://gcc.gnu.org/pub/gcc/infrastructure/gmp-6.1.0.tar.bz2
> > >  ->
> > > sources/gmp-6.1.0.tar.bz2
> > > downloading: sources/gmp-6.1.0.tar.bz2 - 2.3MB of 2.3MB (100%)
> > > reporting: devel/gmp-6.1.0.cfg -> gmp-6.1.0-x86_64-linux-gnu-1.txt
> > > reporting: devel/gmp-6.1.0.cfg -> gmp-6.1.0-x86_64-linux-gnu-1.xml
> > > config: tools/rtems-gdb-10.cfg
> > > error: shell macro failed:
> > > /home/idadel/quick-start/src/rsb/source-builder/sb/rtems-build-dep -c
> > gcc  -l :
> > > 2: error: no library (-l) provided
> >
> > I think this looks like something with Windows and the shell.
> >
>
> Our nightly test build ran into the same problem.
> The runner uses Ubuntu 18.04.
> I ran again with the trace option and the error source in question seems to 
> be here:
>
> config: source-builder/config/gdb-common-1.cfg: 118:>%define 
> gdb-python-lib-check %(%{_sbdir}/sb/rtems-build-dep -c %{__cc} 
> %{gdb-host-libs} -l %{gdb-python-config-libs}) [True]
> exe: shell: /tmp/rtems-source-builder/source-builder/sb/rtems-build-dep -c 
> gcc  -l
> exe: /tmp/rtems-source-builder/source-builder/sb/rtems-build-dep -c gcc  -l
> shell-output: 2 error: no library (-l) provided
> error: shell macro failed: 
> /tmp/rtems-source-builder/source-builder/sb/rtems-build-dep -c gcc  -l : 2: 
> error: no library (-l) provided
> Build Set: Time 0:00:35.508777
>

It means %{gdb-python-config-libs} is empty/missing. Would need to
back out from there to figure out why.

> I also tried a few earlier commits.
> The last working commit for me is
> 47d540e - (2 days ago) 7: Update tool chain - Sebastian Huber
>
> I don't know very much about the rsb internals, but hope this might help 
> someone who does.
>
> Best regards,
>
> Jan
>
> > Could you please run with --trace and then search the log file for this the
> > above line. The shell macro should be present that failed.
> >
> > > Build FAILED
> > > Build Set: Time 0:00:12.713688
> > > Build FAILED
> > >
> > > Also for some reason when I run "sb-check" it tells me "command not
> > found"
> >
> > This looks like a Windows issue.
> >
> > Chris
> > ___
> > users mailing list
> > users@rtems.org
> > http://lists.rtems.org/mailman/listinfo/users
> ___
> users mailing list
> users@rtems.org
> http://lists.rtems.org/mailman/listinfo/users
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users


Issues with configuring BSP with waf

2021-03-11 Thread Ida Delphine
Hello everyone,
Was following the quick build documentation and had issues around where I
have to do a manual BSP build.  In the last step of configuring the BSP, I
ran this command:

./waf configure --prefix=$HOME/quick-start/rtems/5

It didn't produce the expected output. I instead got:
bash: ./waf: No such file or directory
As a result I downloaded it with the command:
curl https://waf.io/waf-2.0.19 > waf
I ran  the last command to configure the BSP again but still did not get
the expected  output. I got this rather:
Waf: Run from a folder containing a 'wscript' file (or try -h for the
generic options)
Please how do I fix this? What am I missing?
I have tried looking for solutions but to no avail.

Thanks,
Ida.
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

RE: Offline download of sources fails

2021-03-11 Thread Jan.Sommer

> -Original Message-
> From: users  On Behalf Of Chris Johns
> Sent: Thursday, March 11, 2021 6:07 AM
> To: Ida Delphine 
> Cc: rtems-us...@rtems.org 
> Subject: Re: Offline download of sources fails
> 
> 
> 
> On 11/3/21 3:34 pm, Ida Delphine wrote:
> > Hello again,
> >
> > So I started over and downloaded all the required packages for my host
> > (Ubuntu
> > 20.04) and still have offline download issues...
> > Please take a look at the error message:
> >
> > RTEMS Source Builder - Set Builder, 6 (fe2d13b6daf3) Build Set:
> > 6/rtems-sparc Build Set: 6/rtems-autotools.bset Build Set:
> > 6/rtems-autotools-internal.bset
> > config: tools/rtems-autoconf-2.69-1.cfg
> > config: tools/rtems-automake-1.12.6-1.cfg Build Sizes: usage: 0.000B
> > total: 19.014KB (sources: 0.000B, patches: 19.014KB, installed 0.000B)
> > Build Set: Time 0:00:00.933172 Build Set: 6/rtems-autotools-base.bset
> > config: tools/rtems-autoconf-2.69-1.cfg
> > config: tools/rtems-automake-1.12.6-1.cfg Build Sizes: usage: 0.000B
> > total: 19.014KB (sources: 0.000B, patches: 19.014KB, installed 0.000B)
> > Build Set: Time 0:00:00.840448 Build Set: Time 0:00:01.777350
> > config: devel/expat-2.1.0-1.cfg
> > package: expat-2.1.0-x86_64-linux-gnu-1 Creating source directory:
> > sources
> > download:
> > https://github.com/libexpat/libexpat/releases/download/R_2_1_0/expat-
> 2
> > .1.0.tar.gz
> >
>  > 2.1.0.tar.gz>
> > -> sources/expat-2.1.0.tar.gz
> >  redirect:
> > https://github-releases.githubusercontent.com/80314213/0186bc60-b675-
> 11e7-83c0-13aced4..
> >  b675-
> > 11e7-83c0-13aced4..>. > log>
> > downloading: sources/expat-2.1.0.tar.gz - 549.4kB of 549.4kB (100%)
> > reporting: devel/expat-2.1.0-1.cfg ->
> > expat-2.1.0-x86_64-linux-gnu-1.txt
> > reporting: devel/expat-2.1.0-1.cfg ->
> > expat-2.1.0-x86_64-linux-gnu-1.xml
> > config: devel/gmp-6.1.0.cfg
> > package: gmp-6.1.0-x86_64-linux-gnu-1
> > download: https://gcc.gnu.org/pub/gcc/infrastructure/gmp-6.1.0.tar.bz2
> >  ->
> > sources/gmp-6.1.0.tar.bz2
> > downloading: sources/gmp-6.1.0.tar.bz2 - 2.3MB of 2.3MB (100%)
> > reporting: devel/gmp-6.1.0.cfg -> gmp-6.1.0-x86_64-linux-gnu-1.txt
> > reporting: devel/gmp-6.1.0.cfg -> gmp-6.1.0-x86_64-linux-gnu-1.xml
> > config: tools/rtems-gdb-10.cfg
> > error: shell macro failed:
> > /home/idadel/quick-start/src/rsb/source-builder/sb/rtems-build-dep -c
> gcc  -l :
> > 2: error: no library (-l) provided
> 
> I think this looks like something with Windows and the shell.
> 

Our nightly test build ran into the same problem.
The runner uses Ubuntu 18.04.
I ran again with the trace option and the error source in question seems to be 
here:

config: source-builder/config/gdb-common-1.cfg: 118:>%define 
gdb-python-lib-check %(%{_sbdir}/sb/rtems-build-dep -c %{__cc} %{gdb-host-libs} 
-l %{gdb-python-config-libs}) [True]
exe: shell: /tmp/rtems-source-builder/source-builder/sb/rtems-build-dep -c gcc  
-l
exe: /tmp/rtems-source-builder/source-builder/sb/rtems-build-dep -c gcc  -l
shell-output: 2 error: no library (-l) provided
error: shell macro failed: 
/tmp/rtems-source-builder/source-builder/sb/rtems-build-dep -c gcc  -l : 2: 
error: no library (-l) provided
Build Set: Time 0:00:35.508777

I also tried a few earlier commits.
The last working commit for me is
47d540e - (2 days ago) 7: Update tool chain - Sebastian Huber

I don't know very much about the rsb internals, but hope this might help 
someone who does.

Best regards,

Jan

> Could you please run with --trace and then search the log file for this the
> above line. The shell macro should be present that failed.
> 
> > Build FAILED
> > Build Set: Time 0:00:12.713688
> > Build FAILED
> >
> > Also for some reason when I run "sb-check" it tells me "command not
> found"
> 
> This looks like a Windows issue.
> 
> Chris
> ___
> users mailing list
> users@rtems.org
> http://lists.rtems.org/mailman/listinfo/users
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users