Re: "ARM/atsam" Doxygen Update
Hello , someone please review this or push it. On Fri, Nov 9, 2018 at 9:55 PM Shashvat Jain wrote: > all the files on this link : > > > https://github.com/joelsherrill/gci_tasks/blob/master/2018/doxygen_c_header_tasks/file_lists/arm_atsam_Add_Doxygen_Headers_Task_00.txt > > have been given a Doxygen header , > please commit this into the main repository , the patch is given in the > attachment. > ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
psxtmtests_plan.csv: Add pthread mutexattr test cases(GCI 2018)
Hi guys, Here is the new test cases from Thanks Himanshu Sekhar Nayak From b612901197b361114406ed730c8f994f484c099b Mon Sep 17 00:00:00 2001 From: Himanshu40 Date: Mon, 12 Nov 2018 01:49:12 +0530 Subject: [PATCH] psxtmtests_plan.csv: Add pthread mutexattr test cases(GCI 2018) --- testsuites/psxtmtests/psxtmtests_plan.csv | 16 1 file changed, 16 insertions(+) diff --git a/testsuites/psxtmtests/psxtmtests_plan.csv b/testsuites/psxtmtests/psxtmtests_plan.csv index 09888da24f..3211503947 100644 --- a/testsuites/psxtmtests/psxtmtests_plan.csv +++ b/testsuites/psxtmtests/psxtmtests_plan.csv @@ -13,6 +13,22 @@ "pthread_mutex_setprioceiling","psxtmmutex07","psxtmtest_single","Yes" "pthread_mutex_getprioceiling","psxtmmutex07","psxtmtest_single","Yes" +"pthread_mutexattr_init: only case","psxtmmutexattr01","psxtmtest_single","No" +"pthread_mutexattr_destroy: only case","psxtmmutexattr01","psxtmtest_single","No" +"pthread_mutexattr_getprioceiling: only case","psxtmmutexattr01","psxtmtest_single","No" +"pthread_mutexattr_setprioceiling: only case","psxtmmutexattr01","psxtmtest_single","No" +"pthread_mutexattr_getprotocol: only case","psxtmmutexattr01","psxtmtest_single","No" +"pthread_mutexattr_setprotocol: only case","psxtmmutexattr01","psxtmtest_single","No" +"pthread_mutexattr_getpshared: only case","psxtmmutexattr01","psxtmtest_single","No" +"pthread_mutexattr_setpshared: only case","psxtmmutexattr01","psxtmtest_single","No" +"pthread_mutexattr_getrobust: only case","psxtmmutexattr01","psxtmtest_single","No" +"pthread_mutexattr_setrobust: only case","psxtmmutexattr01","psxtmtest_single","No" +"pthread_mutexattr_getrobust_np: only case","psxtmmutexattr01","psxtmtest_single","No" +"pthread_mutexattr_setrobust_np: only case","psxtmmutexattr01","psxtmtest_single","No" +"pthread_mutexattr_gettype: only case","psxtmmutexattr01","psxtmtest_single","No" +"pthread_mutexattr_settype: only case","psxtmmutexattr01","psxtmtest_single","No" + + "pthread_cond_init: only case","psxtmcond01","psxtmtest_init_destroy","Yes" "pthread_cond_destroy: only case","psxtmcond01","psxtmtest_init_destroy","Yes" "pthread_cond_signal: no threads waiting","psxtmcond02","psxtmtest_single","Yes" -- 2.17.2 ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: [PATCH] rsb: Update RISC-V's Spike revision
On 09/11/2018 21:22, Hesham Almatary wrote: > --- > bare/config/devel/spike-1.1.0.cfg | 4 ++-- > source-builder/config/spike-1-1.cfg | 20 ++-- > 2 files changed, 12 insertions(+), 12 deletions(-) OK to push. Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: arm/csb337 Doxygen Update
On 10/11/2018 15:55, Shashvat Jain wrote: > the patch in the attachment gives doxygen header to files in the > csb337/include > diectory > please check the changes made and if everything looks right , approve it. Approved by Joel, pushed. Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Thanks for proper dependency checking in the testsuite
Hi, This is a big thank you to Sebastian for the clean up work in the build system so we have proper dependencies to the tests in the testsuite against the cpukit and other libraries. This has been missing for years, even decades. Working on the build system is one of those areas in RTEMS that does not attract wide attention or funding and yet is it so important to all developers and so all users. Sebastian, thank you. Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
RTEMS State of the World Presentation
Hi Each year at the Flight Software Workshop I give a presentation on what has happened with RTEMS in the past year or so, things that need highlighting, and what needs attention and love. This year I have a request for similar slides for someone to present at an EPICS meeting on Thursday. Please help me with ideas and bullets. Slide ideas so far: + Libbsd - what all is there? I'm surprised at what's in there, so info on features, bsps supported, and what's next is appreciated. + Ecosystem - testing, rsb, Eclipse, tracing, etc + New ports and bsps + Infrastructure status and needs + Relicensing Anything else of interest to a random group of RTEMS aware folks and real users. Consider this status and marketing. :) Ideas and meat for presentation appreciated. --joel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: Link RAP file error on zynq BSP
On 12/10/2018 15:45, jameszxj wrote: > HI, > I run RTEMS on my xilinx z7k board and dynamic load application(RAP > format) > from shell. > In recent update, i encount a link error when link the RAP file. > Here is the command and output message: > rtems-ld -n -e PT_Init --base rtems-nsa.elf > wsp/build/nssys.elf > -o wsp/build/nssys.out > error: rap::object: Section index '65522' not found: > wsp/build/nssys.elf I have tracked the section number 65522 to being an uninitialised variable in a module being loaded. For ELF this means: int sym1; creates a symbol record in ELF in libdl of: rtl: sym:elf:24 name:70:sym1 bind:1 type:1 sect:65522 size:4 The readelf version is: 24: 0004 4 OBJECT GLOBAL DEFAULT COM sym1 I have finally managed to find what out where these sections are defined ... https://git.rtems.org/rtems/tree/cpukit/include/sys/exec_elf.h#n538 Peng Fan came across this issue in GSoC 2013 (2012?) on the sparc but we could not find anything in the standards or supporting code to tell what it was and why it existed. We seem to have just missed this detail. The `rtems-ld` linker has support for this section hard coded into it but it is restricted to the sparc architecture. Now I have something in the standard headers to work with I should be able to handle this case cleanly and on all supported archs. James, there is no need for a test case. Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: RTEMS State of the World Presentation
On 12/11/2018 09:04, Joel Sherrill wrote: > Hi > > Each year at the Flight Software Workshop I give a presentation on what has > happened with RTEMS in the past year or so, things that need highlighting, and > what needs attention and love. This year I have a request for similar slides > for > someone to present at an EPICS meeting on Thursday. Please help me with ideas > and bullets. Slide ideas so far: Below is a start with parts needing to be filled out. > + Libbsd - what all is there? I'm surprised at what's in there, so info on > features, bsps supported, and what's next is appreciated. - Drivers and features ported as requested (funded) by users - Tracking FreeBSD 12 - SMP performance improvement with self contained object - Simplified initialisation via /etc/rc.conf. - Networking: - IPv6 - IPsec - Wireless - OpenCrypto - Packet Filter - Drivers: - RE - FXP - E1000 - DC - SMC - Broadcomm - tcpdump - OpenSSL - mDNSResponder (Bonjour) - DHCPD - VLAN - USB - Classes: - Input - Serial - Networking - Wlan - Storage - Devices: - FDT - MMC (eMMC) > + Ecosystem - testing, rsb, Eclipse, tracing, etc - Improved tool building on all hosts: - Windows native and cygwin builds - Support for python2 and python3 - Improved target testing: - Hardware target testing via network downloads on tier 1 targets - Support for GDB testing with hardware - Support for python2 and python3 - User documentation - DWARF access from rtems-tools opening the path to host side analysis and auditing of RTEMS executables, for example coverage > + New ports and bsps + RTEMS Kernel - SMP performance and stability improvements (Seb??) - Removal of pre-installing header files from the build system - Flattening of library building under the cpukit - Improved annotation of test executable for test auditing - Updates: - JFFS2 Chris > + Infrastructure status and needs > > + Relicensing > > Anything else of interest to a random group of RTEMS aware folks and real > users. > Consider this status and marketing. :) > > Ideas and meat for presentation appreciated. > > --joel > > > ___ > 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: arm/csb337 Doxygen Update
Great, thanks! please take a look at the arm/atsam bsp doxygen update. On Mon, Nov 12, 2018 at 3:08 AM Chris Johns wrote: > On 10/11/2018 15:55, Shashvat Jain wrote: > > the patch in the attachment gives doxygen header to files in the > csb337/include > > diectory > > please check the changes made and if everything looks right , approve it. > > Approved by Joel, pushed. > > Chris > ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Adding Benchmark test for the test case " mq_receive: not available: block"(GCI 2018)
hello , multiple test cases have been defined in a single test https://git.rtems.org/rtems/tree/testsuites/psxtmtests/psxtmmq01/psxtmmq01.doc The task instructs me to add a new test , just for clarification , will it be right to add the test case "mq_receive: not available: block" in the same test? thank you --Shashvat ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: Adding Benchmark test for the test case " mq_receive: not available: block"(GCI 2018)
On Sun, Nov 11, 2018, 9:33 PM Shashvat Jain hello , > multiple test cases have been defined in a single test > https://git.rtems.org/rtems/tree/testsuites/psxtmtests/psxtmmq01/psxtmmq01.doc > > The task instructs me to add a new test , just for clarification , will > it be right to add the test case "mq_receive: not available: block" in > the same test? > I don't think so. It would need to follow the same multiple task blocking pattern used by something a mutex or semaphore unavailable and block. Answering from my phone but task blocking and unblocking tests tend to have multiple threads and be standalone tests But if this case is missing, you found a legitimate one to add. --joel > > > thank you > --Shashvat > ___ > 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: qemu build failure - RSB pkg-config failure
On 11/11/2018 00:24, Joel Sherrill wrote: > On CentOS 7, qemu and couverture variant fail to build. They end with this > which > I think indicates that pkg-config is invoked incorrectly. The RSB pkg-config now selects python3 or python2 depending on your set up. Ping me and we can be both take a look and see what is happening. Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: Adding Benchmark test for the test case " mq_receive: not available: block"(GCI 2018)
Thank you for the clarification. :) On Mon, Nov 12, 2018 at 10:15 AM Joel Sherrill wrote: > > > On Sun, Nov 11, 2018, 9:33 PM Shashvat Jain wrote: > >> hello , >> multiple test cases have been defined in a single test >> https://git.rtems.org/rtems/tree/testsuites/psxtmtests/psxtmmq01/psxtmmq01.doc >> >> The task instructs me to add a new test , just for clarification , will >> it be right to add the test case "mq_receive: not available: block" in >> the same test? >> > > I don't think so. It would need to follow the same multiple task blocking > pattern used by something a mutex or semaphore unavailable and block. > > Answering from my phone but task blocking and unblocking tests tend to > have multiple threads and be standalone tests > > But if this case is missing, you found a legitimate one to add. > > --joel > >> >> >> thank you >> --Shashvat >> ___ >> 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
rtems-docs : Build failure
Hello,
I'm getting a waf failure, trying to build the documentation with Fedora 28.
pdfTex version --> pdfTeX 3.14159265-2.6-1.40.19 (TeX Live 2018)
I'm pasting the error below.
===
Build failed
Traceback (most recent call last):
File
"/home/lunatic/development/rtems/docs/rtems-docs/.waf-1.9.7-d2740ebc8bcbca7fcd8f4ae914fb/waflib/Task.py",
line 145, in process
ret=self.run()
File
"/home/lunatic/development/rtems/docs/rtems-docs/.waf-1.9.7-d2740ebc8bcbca7fcd8f4ae914fb/waflib/Tools/tex.py",
line 216, in run
self.call_latex()
File
"/home/lunatic/development/rtems/docs/rtems-docs/.waf-1.9.7-d2740ebc8bcbca7fcd8f4ae914fb/waflib/Tools/tex.py",
line 231, in call_latex
self.check_status('error when calling latex',self.texfun())
File
"/home/lunatic/development/rtems/docs/rtems-docs/.waf-1.9.7-d2740ebc8bcbca7fcd8f4ae914fb/waflib/Tools/tex.py",
line 116, in check_status
raise Errors.WafError('%r command exit status %r'%(msg,retcode))
WafError: 'error when calling latex' command exit status 1
===
-- vijay
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
Re: rtems-docs : Build failure
On 12/11/2018 16:50, Vijay Kumar Banerjee wrote:
> I'm getting a waf failure, trying to build the documentation with Fedora 28.
> pdfTex version --> pdfTeX 3.14159265-2.6-1.40.19 (TeX Live 2018)
>
> I'm pasting the error below.
I cannot tell which manual the build is failing. Can you see which manual?
> ===
> Build failed
> Traceback (most recent call last):
> File
> "/home/lunatic/development/rtems/docs/rtems-docs/.waf-1.9.7-d2740ebc8bcbca7fcd8f4ae914fb/waflib/Task.py",
> line 145, in process
> ret=self.run()
> File
> "/home/lunatic/development/rtems/docs/rtems-docs/.waf-1.9.7-d2740ebc8bcbca7fcd8f4ae914fb/waflib/Tools/tex.py",
> line 216, in run
> self.call_latex()
> File
> "/home/lunatic/development/rtems/docs/rtems-docs/.waf-1.9.7-d2740ebc8bcbca7fcd8f4ae914fb/waflib/Tools/tex.py",
> line 231, in call_latex
> self.check_status('error when calling latex',self.texfun())
> File
> "/home/lunatic/development/rtems/docs/rtems-docs/.waf-1.9.7-d2740ebc8bcbca7fcd8f4ae914fb/waflib/Tools/tex.py",
> line 116, in check_status
> raise Errors.WafError('%r command exit status %r'%(msg,retcode))
> WafError: 'error when calling latex' command exit status 1
Is latex installed? Try:
$ type latex
If this is OK there will be a latex log file in the manual's build directory,
for example for the User manual it is build/user/latex/user.log and the actual
error should be in it.
Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
Re: rtems-docs : Build failure
On Mon, 12 Nov 2018 at 11:26, Chris Johns wrote:
> On 12/11/2018 16:50, Vijay Kumar Banerjee wrote:
> > I'm getting a waf failure, trying to build the documentation with Fedora
> 28.
> > pdfTex version --> pdfTeX 3.14159265-2.6-1.40.19 (TeX Live 2018)
> >
> > I'm pasting the error below.
>
> I cannot tell which manual the build is failing. Can you see which manual?
>
> User manual.
> > ===
> > Build failed
> > Traceback (most recent call last):
> > File
> >
> "/home/lunatic/development/rtems/docs/rtems-docs/.waf-1.9.7-d2740ebc8bcbca7fcd8f4ae914fb/waflib/Task.py",
> > line 145, in process
> > ret=self.run()
> > File
> >
> "/home/lunatic/development/rtems/docs/rtems-docs/.waf-1.9.7-d2740ebc8bcbca7fcd8f4ae914fb/waflib/Tools/tex.py",
> > line 216, in run
> > self.call_latex()
> > File
> >
> "/home/lunatic/development/rtems/docs/rtems-docs/.waf-1.9.7-d2740ebc8bcbca7fcd8f4ae914fb/waflib/Tools/tex.py",
> > line 231, in call_latex
> > self.check_status('error when calling latex',self.texfun())
> > File
> >
> "/home/lunatic/development/rtems/docs/rtems-docs/.waf-1.9.7-d2740ebc8bcbca7fcd8f4ae914fb/waflib/Tools/tex.py",
> > line 116, in check_status
> > raise Errors.WafError('%r command exit status %r'%(msg,retcode))
> > WafError: 'error when calling latex' command exit status 1
>
> Is latex installed? Try:
>
> $ type latex
>
> latex is hashed (/usr/local/texlive/2018/bin/x86_64-linux/latex)
> If this is OK there will be a latex log file in the manual's build
> directory,
> for example for the User manual it is build/user/latex/user.log and the
> actual
> error should be in it.
>
> I only see "Undefined control sequence" errors. (attaching the log)
I have the pdf generated though, but the waf gives this error.
> Chris
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
Re: rtems-docs : Build failure
> On 12 Nov 2018, at 5:30 pm, Vijay Kumar Banerjee > wrote: > > attached log here. Thanks. I will look at this tomorrow. Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
