[PATCH] Added documentation for rtems-tester in rtems-docs
This documentation is in ReST and has been ported
from rtems-tools.git. There are a few changes and
it contains the format for the ini configuration
files.
---
images/user/rtemswhitebg.jpg | Bin 0 -> 117890 bytes
user/tools/rtems-tester.rst | 639 +++
2 files changed, 639 insertions(+)
create mode 100644 images/user/rtemswhitebg.jpg
create mode 100644 user/tools/rtems-tester.rst
diff --git a/images/user/rtemswhitebg.jpg b/images/user/rtemswhitebg.jpg
new file mode 100644
index
..f883f2c495d4d91ef94d35e28995b9d2b7a863f7
GIT binary patch
literal 117890
zcmeFZ2V4}%wm;tF43dMupyX^KNf;4HA|go?gi#OykqnY&35)?%QB?yQx3J6FV
za!_C-tHdE^7~%jEevP|#ckk}Ld+&Sy_ul8e&wtxb569}N?mDMVo%){Br<(kgJO&&%
zt7oVOP*6|+2H-z{JkET{P)7%L!OTR@@SHAq0RWf{&bhdIP#ypPH+NreGyT&dmo8h2
z&~*Zo00Te^90h=D4nCg7=6V(Yco^#Hi1>h&_UWGw@E%+J0Qd_4J@N(@L_~fr|5yL8
zJ9v8g0szGYu)*=`jy?_`9R||3{Cz$5%U3~~%ieXLrlj7dy}=HGG~Yh$^b;-jqs~wC
zseSsooBMUJ&VHXgue)8}ryD`~!EHZBkfu5Z(h;{^9Q{GM7o^2*`MJ4(G#;e6+#Ij@
z001@fez~usgEL4U0cmD$3o{*%)&Kx{W~blK_P?Qh9Rt9A0)UQ(XP~!>le4dgl!LU$
zQ8hJH5d%m6TaLcI@)xc-xL)(VE~4Y%=6TIM5CDGSdA}9Fu`gQ@P{_(h)s&Uxk12rS
z|K<3H7k{bskBR-U{i(*f>5nm^;A#K0?ANxxmU(0Vfa)eFn@7Kv**^n-vTy+4`~GX0
z*h>Il3j=^s%y0PN+1D3mUtiCYii-aJ{t7OR4hs7M{pI+l6@IDt9}~ZMp2Gg~evzHX
z8OIyf{BHS*>yv0K)}PEwuyGoJ;`Kl{D}Q
z#V_M_j^QG(Kl7|0Ge7A)NQ2jZ{Qlh!B@+BErH_k~$bPYonT3dhpZD#38k`gRKQsU%
zzy@#u{D3eZ3P=I+z%f7tPzO!{y1-e$1h4=u19pG|;0(9{-he+40^9{6fEeHr@EAw|
z(t#`>4=4nRfHI&8r~{gT&%hU;4;Tc-fGJ=BSOvC#JOQt(qiD8wmbDUMO7
zQfN`=QkCJRETycY{7l(LIYzla
zxk&|3F;VeQ9ioz_Ql-+NGNH1jx!RY+Aq)k4)nHAb~awL?uy%}Fgn
zEl;gZZ9r{F?Lh5C4X2K!PNB}FE~Rdy?xDs~uTqm}SZD-kWNA*)7}8v#aia03iJ*Bx
z^P1)ZO%qKY%@oZREiEk%tt71qtpV+2+MBe&w6U}=Xi>Dav|Y3lw3~Evbo_L(beeP~
zbl2#7=_2T!(Y>WZ({D}q?(LbSoLtjJRO+Q1w$8dl_oZ%#c
z3Bz@UKn5g37DELChGB|fkCB~Gl2MbL#rTM*k5wqiC6+u{L+0}=;x4qQ6`Kk)p(#{&Zg
zHrYAZkFuMvyRpZzzhQ4A-oPGmEo{bBc?W
zOOnfw>n2wWR{>Wi*D5y$_X+Nc+yUIrxvROyc&K;u5GX>iPH-&_S^o2Zyo(VMwEei7ppAx<)oFrT$JO|-~XhB>c
zNf0z-UW8jjTjZ9=Q;|lI)kA`Z3=a7ndUdGt(B5Im!bP~FF7Q|A_bN5lFE?k
zm8O+em3EbWA^k;$QbtL}S?0M6MwU`mS=L4Ng>07`jhvdCyIh9cfIPFjw)}1Re0i(_
zkHR^HdkSR=%Zg%(){60pEsCTgN=I%T$vQH4l;h~xqxX(h99=smbIjq`^JBfoS&r)+
zM;tFdjyoZH!tq4fiLXkWO2$f&O7%)aWff&_h-A^ZE5YB+HbX&Paiq$efq=cZJm=kp*po^sLtr0i9XY*%b{zjo1#0S
zcUaF!FJEs}Ur9e$zt(`pz{nupV8Bqw(7`azaP_Rp+0e6%M$AU$Mkz+)=VZ=#pQ|vY
zG(KybXgqXY{Ji`5G84eW&?M1h_=4mGuM3r?w5AtKpPNpb9W@IvYcc0Ehnc@I-?BJu
zfwUO3l(O`*tiQ;1@yf-#i`!ObtP-roE-79Lz4ZCAz-5=q<<@l87p-4gZ`$bEJhqv-
zqI4zVO24h7ZGdf?oq*jfyJ{F4>>8~2D$P}^t8cCnu9;lRxVC9;XrF4o>Y(G0?67eC
z)b*t6bB>yh363*2G;bu_n03;0N_3iYhB`lSUUboMNpZp5G`N|5bKBL#HOG~F%jy=&
zjo$65+edc}cUSjD4`Gi0k1kJH&j`;kuajPny;i-AykGlJ_}KcC`*ML`s@+e@FWe7%
zTkH1o+j#$r{>1_80qz0qfii(nfippRLD|97!4ARoA%{ZlhG0XrLtnuu;P&u(geW2m
zF?C1(PVQaCyRLUT?j5<8aBt(j)%}Vvp|Cq)6XE*d`4OxU-VpXGRWs2{jI=!`lZ
z^(=}MeLeb9%#oNUF@#u$*iR3SK79I+9CstG6RC_$dqn%l{ZW5BG(I~Y(Z6Hn5U8I%2z$DW>hTK-Jz*`sHK6z7z_=ck{eQUz0^Qnz1Rf6<+G
zDy=YGC_N^9_od6rudno9m1am}JjtZZyq!6nbup_YTQxiHwZQ9`*Tfw6oUvT9+{QeW
zyu3GpZ;<(v`F{CxZ?C-lQgEiAyimUI6^aKH^A33D_iq0E)%X2HMn(0-s>OvR;w7mc
zI6p*}Qj`Xku9i8Mjg?<6@A`Q5V||5s#fM6T%ABf0RnM!rtC2N~HDNVmbP#&8*0Xl8
z&Z%yq9#%itaH*lU(X_F%$*8HdS+BXFMY{#vs@YoAcCzi`C)H17pOrtCwkx%N=uqnT
z(5c*6ic!Ioe^L8V(WTK<(+%ye>p9cY+-unTx$k^mSHETd*MTboV_&a-o&9#}8}9q<
z?|XxHhG>SOhYt)t84(=G7?mDHjVX^+W6xmQ$IZtFCmbdgCVeIeQ(@CA(@$m~GkLSe
zW~=7(=Dy6^%ug+NF6=EvEU_=8E=w(!tejeDU%j+Ch4aRd*J9WC*K;;bY}9XF*c{n%
z+uGZX#`EKIcT{&;cCB`2_WTKSgr`JlVg<>FG(>hIlgU`1S2w`r1^^fv12P~Qpaxm@rIML%S|6&zuW!+fkF4f
z!XqLdL`5egCOv+V{PbB$MrKy_>zv%YH$}xIA4<#0KUUN?G&VK2w6=Zf?&w>@Gdm>G)Ug>lj3jo2_!&dv`JNh@HTS&S(n9)`e><_lz*N7{xV20
zq)ke-P{319N1P~ZaycDmY#BWKY)r}gW4Wc7&-afuL{o>T2ku7~E?K_S-YkUlqgRYgS#6n);Oc*ZOJx$uVxVetXN<42KWf_{a2jlAL_i09mED{&ug
zL`$Osf;Uhv+TXL%6Yt+!Q;N#x>cZfW&EpJ^?Q%k})l*{}H_u#>$!M=tEPkPhqe-sv
zx?~zU3Pn+gOI^r?j41mDTg_Y=!Zin{e|z*V11F@gkqNzGVKUHj%PD%8XAv
z&pFekwYlSlHQ_zC-Suc@9aW@3fjU7tKP|HBG-vnP{P`!hn<0u1w1my;wM&pSCyezw
z42p(bzbxHgzMr-^2IsDJ5kbm-@kcrL2$mQaVhZ5l_uot+C(;go?h|-;Y5vP{UFS{f
z0`{GNe9inG{U*c9;asNLhjh6vQ2cfN+sc4i0dd=vV}s-2M!~?9ytmIwT1CGXJsSwS
z9Y1L&ZswLg2NMa=O_2(jok~%ilzmii_V->dK*{dHLj)j-h_Kaj(>g6TY3QZEY>wc#dvL&R&@t~$}?=_{o
zyy1A&nVT1HJL%HbrxcyEV5lX?cy(8Yzuy@e{#s(Hd+aaF@b8VAXg`=gI~F#PYB@w@
z`tB3N`k6da*kY%OS&1V1M5@)e6M>6%baAxQBhn(4XVtF~F*!9$dc2pXp$ua6EE5b0;0>(&fg#BII(ZJJeEf6Xnk)7?4KVj~2cyY_njMIqS^F
zH9xB#$7QMu{B{1D%it+j$pz|j(ZN>OZ30*JY0|JT7vMmWGJ+8m(5Rs+RItd=RkIPO
zJDPzEe2oMRV)no$?n($6E54h#KFTFd2I$RTBT+jOx?EP+$aMp&f)Hwc;ztrw-fT!<
z<_sC2dW8~4S>tKQfMnmQ4XLFALI#Xp6;{#hbwF{79YWt6$iS^^k`&3A^!)MBC399i
z6N$$`W&<1J(4xU|(CcmdONai=b?E1L&W#TSjgmYWNL*M=CqB51-nB)*$}Rt_l(%Jc
zO&T$-Ka(bfXpMu7|Exbw>lZ-%p#twPhX?QDFcJ^y+n0fafj=p`BKC+HkgV$xqq^M6BW_Q&b}tm5#$PQ=irOy2KNx;%At)Hh99`HKCw
z>+fkFl3o{g)IsV;A0N3g^^s-AwB2QqKNlj}pUQgko>94HR$sV1BJ9hH_8|c|Q)5`=
z`PZlZ3h({zhWD(nD+I1Gk_oCFv32M>8JP1U!m)o+7y^SJTC>SO6eKO+6&X0JhKQD&
zdB|l73s3LRw)?QkMl#76Dv>y`mfhbejea|6oY@`AcDCNwjC=eHL>F`cTNJoTCQ`c2GIF#6+7c)U5^iwXXgAc7)}m%!yP
zF;XCh{(9SvVYRv#@n%meX`AECUP;lh_uJp;%1|k`@FD02mR3I~=Tx*ZiI1R}qmO*W
zvqN;9n#V^zZu%w-J%hf8j75zX8q+y9dv6$RCO}^m>|
Building RISC-V BSP
Hello, I am trying to build RTEMS for RISC-V BSP. I applied Hesham's patch for RSB and built RSB. But when I am trying to build rtems-generic target I get the mistake. This is my sequence of steps: git clone git://git.rtems.org/rtems-source-builder.git #patch applied here mkdir -p ./development/rtems/kernel cd ./development/rtems/kernel export RTEMS_DEV=~Projects/riscv/rtems/development git clone https://github.com/heshamelmatary/rtems-riscv.git cd .. mkdir rsb mv ../../rtems-source-builder/ ./rsb/ cd rsb/rtems-source-builder/rtems/ ../source-builder/sb-set-builder --prefix=$RTEMS_DEV/rtems/4.12 4.12/rtems-riscv32 cd ./../../../kernel/rtems-riscv/ ./bootstrap -c && ./bootstrap -p && $RTEMS_DEV/rtems/rsb/rtems-source-builder/source-builder/sb-bootstrap cd ../ mkdir riscv32 cd riscv32/ $RTEMS_DEV/rtems/kernel/rtems-riscv/configure --target=riscv32-rtems4.12 --disable-posix --disable-networking --disable-itron --enable-rtemsbsp=riscv_generic make # error here : Making all in riscv_generic make[2]: Entering directory '~/Projects/riscv/rtems/development/rtems/kernel/riscv32/riscv32-rtems4.12/c/riscv_generic' make[2]: *** No rule to make target 'all'. Stop. make[2]: Leaving directory '~/Projects/riscv/rtems/development/rtems/kernel/riscv32/riscv32-rtems4.12/c/riscv_generic' Makefile:348: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '~/Projects/riscv/rtems/development/rtems/kernel/riscv32/riscv32-rtems4.12/c' Makefile:473: recipe for target 'all-recursive' failed make: *** [all-recursive] Error 1 Am I doing something wrong? What is the possible cause of the error? -- Regards, Denis Obrezkov ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: [PATCH] Add support to build riscv32 toolchain
Unrelatedly to the contents, please use -v2 to identify revised patches. On Tue, May 30, 2017 at 2:01 AM, Sebastian Huber wrote: > Hello Hesham, > > thanks for your RISCV support. > > - Am 30. Mai 2017 um 3:51 schrieb Hesham Almatary > heshamelmat...@gmail.com: > >> --- >> rtems/config/4.12/rtems-riscv32.bset | 32 +++ >> rtems/config/tools/rtems-binutils-2.28-1.cfg | 22 >> .../rtems-gcc-7.1.0-newlib-2.5.0.20170323-1.cfg| 65 >> ++ > [...] >> +# >> +# Patches for gcc and newlib >> +# >> +%patch add gcc -p1 >> https://raw.githubusercontent.com/heshamelmatary/riscv-rtems-patches/master/gcc-rtems-riscv.patch > > Do you have a copyright assignment with the FSF? If not and you don't want to > do this, then I can try to add the RISCV support to GCC without locking at > your GCC patches. We should commit the things first into GCC. > >> +%patch add newlib -p1 >> https://raw.githubusercontent.com/heshamelmatary/riscv-rtems-patches/master/0001-Import-risc-v-from-https-github.com-riscv.patch > > Are there plans by the RISCV people to add this to upstream Newlib soon? Due > to the RISCV support in FSF Binutils and GCC, there should be no problems. > ___ > 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: Building RISC-V BSP
On Tue, May 30, 2017 at 7:49 AM, Denis Obrezkov wrote: > Hello, > I am trying to build RTEMS for RISC-V BSP. I applied Hesham's patch for RSB > and built RSB. But when I am trying to build rtems-generic target I get the > mistake. > This is my sequence of steps: > > git clone git://git.rtems.org/rtems-source-builder.git > > #patch applied here > > mkdir -p ./development/rtems/kernel > > cd ./development/rtems/kernel > > export RTEMS_DEV=~Projects/riscv/rtems/development > > git clone https://github.com/heshamelmatary/rtems-riscv.git > > cd .. > > mkdir rsb > > mv ../../rtems-source-builder/ ./rsb/ > > cd rsb/rtems-source-builder/rtems/ > > ../source-builder/sb-set-builder --prefix=$RTEMS_DEV/rtems/4.12 > 4.12/rtems-riscv32 > is $RTEMS_DEV/rtems/4.12/bin in your $PATH? > cd ./../../../kernel/rtems-riscv/ > I have no clue where you are in your directory tree. It is a bit confusing/deep paths. > ./bootstrap -c && ./bootstrap -p && > $RTEMS_DEV/rtems/rsb/rtems-source-builder/source-builder/sb-bootstrap > > cd ../ > > mkdir riscv32 > > cd riscv32/ > > $RTEMS_DEV/rtems/kernel/rtems-riscv/configure --target=riscv32-rtems4.12 > --disable-posix --disable-networking --disable-itron > --enable-rtemsbsp=riscv_generic > You should use --enable-posix probably. The --disable-itron is obsolete / does nothing. Check that your configure ended with something stating it was ready to make 'riscv_generic' BSP. > make > > # error here : > > Making all in riscv_generic > > make[2]: Entering directory > '~/Projects/riscv/rtems/development/rtems/kernel/riscv32/riscv32-rtems4.12/c/riscv_generic' > > make[2]: *** No rule to make target 'all'. Stop. > > make[2]: Leaving directory > '~/Projects/riscv/rtems/development/rtems/kernel/riscv32/riscv32-rtems4.12/c/riscv_generic' > > Makefile:348: recipe for target 'all-recursive' failed > > make[1]: *** [all-recursive] Error 1 > > make[1]: Leaving directory > '~/Projects/riscv/rtems/development/rtems/kernel/riscv32/riscv32-rtems4.12/c' > > Makefile:473: recipe for target 'all-recursive' failed > > make: *** [all-recursive] Error 1 > This is not enough of the error output to tell what went wrong. It appears to be a problem earlier though, likely during configure. > > Am I doing something wrong? What is the possible cause of the error? > > -- > 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
Re: Building RISC-V BSP
2017-05-30 18:31 GMT+03:00 Gedare Bloom : > On Tue, May 30, 2017 at 7:49 AM, Denis Obrezkov > wrote: > > Hello, > > I am trying to build RTEMS for RISC-V BSP. I applied Hesham's patch for > RSB > > and built RSB. But when I am trying to build rtems-generic target I get > the > > mistake. > > This is my sequence of steps: > > > > git clone git://git.rtems.org/rtems-source-builder.git > > > > #patch applied here > > > > mkdir -p ./development/rtems/kernel > > > > cd ./development/rtems/kernel > > > > export RTEMS_DEV=~Projects/riscv/rtems/development > > > > git clone https://github.com/heshamelmatary/rtems-riscv.git > > > > cd .. > > > > mkdir rsb > > > > mv ../../rtems-source-builder/ ./rsb/ > > > > cd rsb/rtems-source-builder/rtems/ > > > > ../source-builder/sb-set-builder --prefix=$RTEMS_DEV/rtems/4.12 > > 4.12/rtems-riscv32 > > > is $RTEMS_DEV/rtems/4.12/bin in your $PATH? > > You are right, somehow it wasn't there. Now I have another issue during make: checking for RTEMS_CPU_MODEL... checking for RTEMS_BSP_FAMILY... riscv_generic checking for CPU_CFLAGS... (cached) -m32 -march=I checking for CFLAGS_OPTIMIZE_V... (cached) -O0 -g checking for style of include used by make... GNU checking for riscv32-rtems4.12-gcc... riscv32-rtems4.12-gcc checking for riscv32-rtems4.12-gcc... (cached) riscv32-rtems4.12-gcc checking whether the C compiler works... no configure: error: in `/home/reprofy/Projects/riscv/rtems/development/rtems/kernel/riscv32/riscv32-rtems4.12/c/riscv_generic': configure: error: C compiler cannot create executables Now I can see the error - there is no such an option "-m32" in 32-bit gcc. But what does "(cached)" mean? -- Regards, Denis Obrezkov ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: Building RISC-V BSP
On Tue, May 30, 2017 at 12:09 PM, Denis Obrezkov wrote: > 2017-05-30 18:31 GMT+03:00 Gedare Bloom : >> >> On Tue, May 30, 2017 at 7:49 AM, Denis Obrezkov >> wrote: >> > Hello, >> > I am trying to build RTEMS for RISC-V BSP. I applied Hesham's patch for >> > RSB >> > and built RSB. But when I am trying to build rtems-generic target I get >> > the >> > mistake. >> > This is my sequence of steps: >> > >> > git clone git://git.rtems.org/rtems-source-builder.git >> > >> > #patch applied here >> > >> > mkdir -p ./development/rtems/kernel >> > >> > cd ./development/rtems/kernel >> > >> > export RTEMS_DEV=~Projects/riscv/rtems/development >> > >> > git clone https://github.com/heshamelmatary/rtems-riscv.git >> > >> > cd .. >> > >> > mkdir rsb >> > >> > mv ../../rtems-source-builder/ ./rsb/ >> > >> > cd rsb/rtems-source-builder/rtems/ >> > >> > ../source-builder/sb-set-builder --prefix=$RTEMS_DEV/rtems/4.12 >> > 4.12/rtems-riscv32 >> > >> is $RTEMS_DEV/rtems/4.12/bin in your $PATH? >> > You are right, somehow it wasn't there. > > Now I have another issue during make: > > checking for RTEMS_CPU_MODEL... > checking for RTEMS_BSP_FAMILY... riscv_generic > checking for CPU_CFLAGS... (cached) -m32 -march=I > checking for CFLAGS_OPTIMIZE_V... (cached) -O0 -g > checking for style of include used by make... GNU > checking for riscv32-rtems4.12-gcc... riscv32-rtems4.12-gcc > checking for riscv32-rtems4.12-gcc... (cached) riscv32-rtems4.12-gcc > checking whether the C compiler works... no > configure: error: in > `/home/reprofy/Projects/riscv/rtems/development/rtems/kernel/riscv32/riscv32-rtems4.12/c/riscv_generic': > configure: error: C compiler cannot create executables > > Now I can see the error - there is no such an option "-m32" in 32-bit gcc. > But what does "(cached)" mean? > I think it means configure previously made this check and uses the cached result of the previous check. > > > -- > Regards, Denis Obrezkov ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: [PATCH] Added documentation for rtems-tester in rtems-docs
On Tue, May 30, 2017 at 1:10 PM, Tanu Hari Dixit wrote: > Hello Gedare, > > I just added the image following what was already in rtems-tools.git > repo. Maybe it is not really needed there. Maybe it was added to the > previous doc because it was a stand-alone doc. I will pull that out. > What do you think? What does Chris think? > > Regards, > Tanu. > Send the text change separately for review from the image. thanks. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
[PATCH] Added documentation for rtems-tester in rtems-docs
Contains the ReST file for documentation for rtems-tester.
Also contains the new format for the ini configuration files.
---
user/tools/rtems-tester.rst | 639
1 file changed, 639 insertions(+)
create mode 100644 user/tools/rtems-tester.rst
diff --git a/user/tools/rtems-tester.rst b/user/tools/rtems-tester.rst
new file mode 100644
index 000..24c62dd
--- /dev/null
+++ b/user/tools/rtems-tester.rst
@@ -0,0 +1,639 @@
+RTEMS Tester
+
+
+.. image:: ../../images/user/rtemswhitebg.jpg
+ :width: 400
+ :align: center
+
+Chris Johns
+1.0, June 2014
+
+RTEMS Tester
+
+
+The RTEMS Tester is a test framework. It includes a command line interface to
+run tests on supported targets. The framework provides back-end support for
+common simulators and debuggers. The board support package (BSP) configurations
+for RTEMS are provided and can be used to run all the tests provided with
+RTEMS. The framework is not specific to RTEMS and can be configured to run any
+suitable application.
+
+RTEMS is an embedded operating system and is cross-compiled on a range of host
+machines. The executables run on the target hardware and this can vary widely
+from open source simulators, commercial simulators, debuggers with simulators,
+to debuggers with hardware specific pods and devices. Testing RTEMS requires
+the cross-compiled test executable is transferred to the target hardware,
+executed and the output returned to the host where it is analyzed to determine
+the test result. The RTEMS Tester provides a framework to do this.
+
+Running all the RTEMS tests on your target is very important. It provides you
+with a traceable record showing that your RTEMS version and its tools are
+working at the level the RTEMS development team expect when releasing
+RTEMS. Being able to easily run the tests and verify the results is critical in
+maintaining a high standard.
+
+The RTEMS Tester contains:
+
+* Command line tool (``rtems-test``)
+* BSP Configuration scripts
+* Back-end Configuration scripts
+* Back-end Python classes
+* Python based framework
+
+This document is for users of the RTEMS Tester as well as those wanting to
+develop, extend and investigate the RTEMS Tester.
+
+License
+===
+
+The RTEMS Tester is part of the RTEMS Tools Project. The code is released under
+the OSI approved "The BSD 2-Clause License". It is free to use and we encourage
+this, including on operating systems other than RTEMS.
+
+The code and command line tools must retain the same names and always reference
+the RTEMS Tools Project.
+
+Quick Start
+===
+
+The quick start will show you how to run the test suite for a BSP. It will
+explain how to get the RTEMS Tester, set it up and run the tests for the erc32
+BSP. It assumes you have a valid SPARC tool chain and have built the erc32 BSP
+version of RTEMS 4.12.
+
+Setup
+=
+
+Set up a development work space:
+
+.. code-block:: shell
+
+$ cd
+$ mkdir -p development/rtems/test
+$ cd development/rtems/test
+
+First fetch the RTEMS tester from the RTEMS Tools repository:
+
+.. code-block:: shell
+
+$ git clone git://git.rtems.org/rtems-tools.git rtems-tools.git
+$ cd rtems-tools.git/tester
+
+Available BSP testers
+=
+
+You can list the available BSP testers with:
+
+.. code-block:: shell
+
+$ ./rtems-test --list-bsps
+arm920
+beagleboardxm
+jmr3904-run
+jmr3904
+mcf5235
+psim-run
+psim
+realview_pbx_a9_qemu
+sis-run
+sis
+xilinx_zynq_a9_qemu
+xilinx_zynq_a9_qemu_smp
+xilinx_zynq_zc706
+xilinx_zynq_zc706_qemu
+
+.. note:: The list is growing all the time and if your BSP is not supported we
+ encourage you to add it and submit the configuration back to the
project.
+
+Some of the BSPs may appear more than once in the list. These are aliased BSP
+configurations that may use a different back-end. An example is the SPARC
+Instruction Simulator (SIS) BSP. There is the 'sis' tester which uses the GDB
+back-end and the 'sis-run' tester which uses the command line version of the
SIS
+simulator. We will show how to use ``rtems-test`` command with the SIS BSP
+because it is easy to build an use.
+
+Adding support for a BSP to the tester
+==
+
+To add support for a BSP, one should add a configuration file in
+``rtems-tools.git/tester/rtems/testing/bsps``. The configuration files
+should be specified in an INI file. The configuration files provide a
+means to the backend of `rtems-tester` to automate the running of tests.
+There is the tester which uses the GDB back-end and the
``-run``
+tester which uses the command line version of the respective simulator.
+The general format for specifying an INI configuration file is as follows:
+
+.ini:
+
+.. code-block:: shell
+
+[]
+bsp = ''
+gdb = '%{_rtscripts}/gdb.cfg'
+arch = ''
+
+[gdb_script]
+gdb_script ='_g
[PATCH 2/2] Added the logo for documentation of rtems-tester
---
images/user/rtemswhitebg.jpg | Bin 0 -> 117890 bytes
1 file changed, 0 insertions(+), 0 deletions(-)
create mode 100644 images/user/rtemswhitebg.jpg
diff --git a/images/user/rtemswhitebg.jpg b/images/user/rtemswhitebg.jpg
new file mode 100644
index
..f883f2c495d4d91ef94d35e28995b9d2b7a863f7
GIT binary patch
literal 117890
zcmeFZ2V4}%wm;tF43dMupyX^KNf;4HA|go?gi#OykqnY&35)?%QB?yQx3J6FV
za!_C-tHdE^7~%jEevP|#ckk}Ld+&Sy_ul8e&wtxb569}N?mDMVo%){Br<(kgJO&&%
zt7oVOP*6|+2H-z{JkET{P)7%L!OTR@@SHAq0RWf{&bhdIP#ypPH+NreGyT&dmo8h2
z&~*Zo00Te^90h=D4nCg7=6V(Yco^#Hi1>h&_UWGw@E%+J0Qd_4J@N(@L_~fr|5yL8
zJ9v8g0szGYu)*=`jy?_`9R||3{Cz$5%U3~~%ieXLrlj7dy}=HGG~Yh$^b;-jqs~wC
zseSsooBMUJ&VHXgue)8}ryD`~!EHZBkfu5Z(h;{^9Q{GM7o^2*`MJ4(G#;e6+#Ij@
z001@fez~usgEL4U0cmD$3o{*%)&Kx{W~blK_P?Qh9Rt9A0)UQ(XP~!>le4dgl!LU$
zQ8hJH5d%m6TaLcI@)xc-xL)(VE~4Y%=6TIM5CDGSdA}9Fu`gQ@P{_(h)s&Uxk12rS
z|K<3H7k{bskBR-U{i(*f>5nm^;A#K0?ANxxmU(0Vfa)eFn@7Kv**^n-vTy+4`~GX0
z*h>Il3j=^s%y0PN+1D3mUtiCYii-aJ{t7OR4hs7M{pI+l6@IDt9}~ZMp2Gg~evzHX
z8OIyf{BHS*>yv0K)}PEwuyGoJ;`Kl{D}Q
z#V_M_j^QG(Kl7|0Ge7A)NQ2jZ{Qlh!B@+BErH_k~$bPYonT3dhpZD#38k`gRKQsU%
zzy@#u{D3eZ3P=I+z%f7tPzO!{y1-e$1h4=u19pG|;0(9{-he+40^9{6fEeHr@EAw|
z(t#`>4=4nRfHI&8r~{gT&%hU;4;Tc-fGJ=BSOvC#JOQt(qiD8wmbDUMO7
zQfN`=QkCJRETycY{7l(LIYzla
zxk&|3F;VeQ9ioz_Ql-+NGNH1jx!RY+Aq)k4)nHAb~awL?uy%}Fgn
zEl;gZZ9r{F?Lh5C4X2K!PNB}FE~Rdy?xDs~uTqm}SZD-kWNA*)7}8v#aia03iJ*Bx
z^P1)ZO%qKY%@oZREiEk%tt71qtpV+2+MBe&w6U}=Xi>Dav|Y3lw3~Evbo_L(beeP~
zbl2#7=_2T!(Y>WZ({D}q?(LbSoLtjJRO+Q1w$8dl_oZ%#c
z3Bz@UKn5g37DELChGB|fkCB~Gl2MbL#rTM*k5wqiC6+u{L+0}=;x4qQ6`Kk)p(#{&Zg
zHrYAZkFuMvyRpZzzhQ4A-oPGmEo{bBc?W
zOOnfw>n2wWR{>Wi*D5y$_X+Nc+yUIrxvROyc&K;u5GX>iPH-&_S^o2Zyo(VMwEei7ppAx<)oFrT$JO|-~XhB>c
zNf0z-UW8jjTjZ9=Q;|lI)kA`Z3=a7ndUdGt(B5Im!bP~FF7Q|A_bN5lFE?k
zm8O+em3EbWA^k;$QbtL}S?0M6MwU`mS=L4Ng>07`jhvdCyIh9cfIPFjw)}1Re0i(_
zkHR^HdkSR=%Zg%(){60pEsCTgN=I%T$vQH4l;h~xqxX(h99=smbIjq`^JBfoS&r)+
zM;tFdjyoZH!tq4fiLXkWO2$f&O7%)aWff&_h-A^ZE5YB+HbX&Paiq$efq=cZJm=kp*po^sLtr0i9XY*%b{zjo1#0S
zcUaF!FJEs}Ur9e$zt(`pz{nupV8Bqw(7`azaP_Rp+0e6%M$AU$Mkz+)=VZ=#pQ|vY
zG(KybXgqXY{Ji`5G84eW&?M1h_=4mGuM3r?w5AtKpPNpb9W@IvYcc0Ehnc@I-?BJu
zfwUO3l(O`*tiQ;1@yf-#i`!ObtP-roE-79Lz4ZCAz-5=q<<@l87p-4gZ`$bEJhqv-
zqI4zVO24h7ZGdf?oq*jfyJ{F4>>8~2D$P}^t8cCnu9;lRxVC9;XrF4o>Y(G0?67eC
z)b*t6bB>yh363*2G;bu_n03;0N_3iYhB`lSUUboMNpZp5G`N|5bKBL#HOG~F%jy=&
zjo$65+edc}cUSjD4`Gi0k1kJH&j`;kuajPny;i-AykGlJ_}KcC`*ML`s@+e@FWe7%
zTkH1o+j#$r{>1_80qz0qfii(nfippRLD|97!4ARoA%{ZlhG0XrLtnuu;P&u(geW2m
zF?C1(PVQaCyRLUT?j5<8aBt(j)%}Vvp|Cq)6XE*d`4OxU-VpXGRWs2{jI=!`lZ
z^(=}MeLeb9%#oNUF@#u$*iR3SK79I+9CstG6RC_$dqn%l{ZW5BG(I~Y(Z6Hn5U8I%2z$DW>hTK-Jz*`sHK6z7z_=ck{eQUz0^Qnz1Rf6<+G
zDy=YGC_N^9_od6rudno9m1am}JjtZZyq!6nbup_YTQxiHwZQ9`*Tfw6oUvT9+{QeW
zyu3GpZ;<(v`F{CxZ?C-lQgEiAyimUI6^aKH^A33D_iq0E)%X2HMn(0-s>OvR;w7mc
zI6p*}Qj`Xku9i8Mjg?<6@A`Q5V||5s#fM6T%ABf0RnM!rtC2N~HDNVmbP#&8*0Xl8
z&Z%yq9#%itaH*lU(X_F%$*8HdS+BXFMY{#vs@YoAcCzi`C)H17pOrtCwkx%N=uqnT
z(5c*6ic!Ioe^L8V(WTK<(+%ye>p9cY+-unTx$k^mSHETd*MTboV_&a-o&9#}8}9q<
z?|XxHhG>SOhYt)t84(=G7?mDHjVX^+W6xmQ$IZtFCmbdgCVeIeQ(@CA(@$m~GkLSe
zW~=7(=Dy6^%ug+NF6=EvEU_=8E=w(!tejeDU%j+Ch4aRd*J9WC*K;;bY}9XF*c{n%
z+uGZX#`EKIcT{&;cCB`2_WTKSgr`JlVg<>FG(>hIlgU`1S2w`r1^^fv12P~Qpaxm@rIML%S|6&zuW!+fkF4f
z!XqLdL`5egCOv+V{PbB$MrKy_>zv%YH$}xIA4<#0KUUN?G&VK2w6=Zf?&w>@Gdm>G)Ug>lj3jo2_!&dv`JNh@HTS&S(n9)`e><_lz*N7{xV20
zq)ke-P{319N1P~ZaycDmY#BWKY)r}gW4Wc7&-afuL{o>T2ku7~E?K_S-YkUlqgRYgS#6n);Oc*ZOJx$uVxVetXN<42KWf_{a2jlAL_i09mED{&ug
zL`$Osf;Uhv+TXL%6Yt+!Q;N#x>cZfW&EpJ^?Q%k})l*{}H_u#>$!M=tEPkPhqe-sv
zx?~zU3Pn+gOI^r?j41mDTg_Y=!Zin{e|z*V11F@gkqNzGVKUHj%PD%8XAv
z&pFekwYlSlHQ_zC-Suc@9aW@3fjU7tKP|HBG-vnP{P`!hn<0u1w1my;wM&pSCyezw
z42p(bzbxHgzMr-^2IsDJ5kbm-@kcrL2$mQaVhZ5l_uot+C(;go?h|-;Y5vP{UFS{f
z0`{GNe9inG{U*c9;asNLhjh6vQ2cfN+sc4i0dd=vV}s-2M!~?9ytmIwT1CGXJsSwS
z9Y1L&ZswLg2NMa=O_2(jok~%ilzmii_V->dK*{dHLj)j-h_Kaj(>g6TY3QZEY>wc#dvL&R&@t~$}?=_{o
zyy1A&nVT1HJL%HbrxcyEV5lX?cy(8Yzuy@e{#s(Hd+aaF@b8VAXg`=gI~F#PYB@w@
z`tB3N`k6da*kY%OS&1V1M5@)e6M>6%baAxQBhn(4XVtF~F*!9$dc2pXp$ua6EE5b0;0>(&fg#BII(ZJJeEf6Xnk)7?4KVj~2cyY_njMIqS^F
zH9xB#$7QMu{B{1D%it+j$pz|j(ZN>OZ30*JY0|JT7vMmWGJ+8m(5Rs+RItd=RkIPO
zJDPzEe2oMRV)no$?n($6E54h#KFTFd2I$RTBT+jOx?EP+$aMp&f)Hwc;ztrw-fT!<
z<_sC2dW8~4S>tKQfMnmQ4XLFALI#Xp6;{#hbwF{79YWt6$iS^^k`&3A^!)MBC399i
z6N$$`W&<1J(4xU|(CcmdONai=b?E1L&W#TSjgmYWNL*M=CqB51-nB)*$}Rt_l(%Jc
zO&T$-Ka(bfXpMu7|Exbw>lZ-%p#twPhX?QDFcJ^y+n0fafj=p`BKC+HkgV$xqq^M6BW_Q&b}tm5#$PQ=irOy2KNx;%At)Hh99`HKCw
z>+fkFl3o{g)IsV;A0N3g^^s-AwB2QqKNlj}pUQgko>94HR$sV1BJ9hH_8|c|Q)5`=
z`PZlZ3h({zhWD(nD+I1Gk_oCFv32M>8JP1U!m)o+7y^SJTC>SO6eKO+6&X0JhKQD&
zdB|l73s3LRw)?QkMl#76Dv>y`mfhbejea|6oY@`AcDCNwjC=eHL>F`cTNJoTCQ`c2GIF#6+7c)U5^iwXXgAc7)}m%!yP
zF;XCh{(9SvVYRv#@n%meX`AECUP;lh_uJp;%1|k`@FD02mR3I~=Tx*ZiI1R}qmO*W
zvqN;9n#V^zZu%w-J%hf8j75zX8q+y9dv6$RCO}^m>|_sxF6?xYfrw8;a1zYEnNPhGkcIdeL
z6l{GS;fvT2-90)KI{RyfUPJ#;f1u-{Q)B>a8MzZl(5=cRg_5H#3ul?)sq0}sj`BQSYH
zuzQop*%q(uOs{R!jQXE-pXKr1IYgIbA9U5$i3~J5gKd$?WB`*#f=okjJZq?(O=ty_
z5KrV=*4l8_+9b^UL7Y%*5!wa0D^rm}VtPvk@Es5w`x+Sl8#WL?QIA-HqR!dYCj$x4
zOre&Mhb<%M)RjN>|4+pI(=g@W5l<0~HlNTly`
Re: [PATCH] Added documentation for rtems-tester in rtems-docs
Hello Gedare, I have sent the patches separately. Thank you, Tanu. On Tue, May 30, 2017 at 10:50 PM, Gedare Bloom wrote: > On Tue, May 30, 2017 at 1:10 PM, Tanu Hari Dixit > wrote: >> Hello Gedare, >> >> I just added the image following what was already in rtems-tools.git >> repo. Maybe it is not really needed there. Maybe it was added to the >> previous doc because it was a stand-alone doc. I will pull that out. >> What do you think? What does Chris think? >> >> Regards, >> Tanu. >> > > Send the text change separately for review from the image. thanks. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
rtems-test runtime errors qemu.cfg
Hi,
I'm trying to run rtems-test for pc386 with the added --coverage tag for
couverture-qemu. All tests default to dry-run because of errors in qemu.cfg
error: qemu.cfg:81: execute failed: qemu-system-i386 -m 128 -boot b -hda
/home/cpod/development/rtems/test/rtems-tools/tester/rtems/testing/coverage/rtems-boot.img
-no-reboot -serial null -serial mon:stdio -nographic -append
"--console=com1;boot;" -kernel
/home/cpod/development/rtems/pc386/i386-rtems4.12/c/pc386/testsuites/samples/unlimited/unlimited.exe
-exec-trace coverage/unlimited.exe.cov: exit-code:2
warning: switched to dry run due to errors
The exit code I believe refers to 'no such file or directory'. In qemu.cfg
the line is:
%execute %{qemu_cmd} %{qemu_opts} -kernel %{test_executable} %{coverage_arg}
It's a bit tricky to trace those macros back to different files and see
what they have. Is there any way to just print those out when it runs so I
can take a look at them.
I tried %print %{qemu_cmd} and %echo %{qemu_cmd}. Is there any way to do
this in a config file?
Thanks,
Cillian.
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
Re: rtems-test runtime errors qemu.cfg
Hi Cillian,
I usually do a git grep -i "" to find out where possibly a
macro or variable is used elsewhere in the code. Not the best way, but
works mostly.
Also %{qemu_cmd} has been defined here in the same file
(https://devel.rtems.org/browser/rtems-tools/tester/rtems/testing/qemu.cfg#L60).
I also sometimes use winpdb to see what value a macro has but this is
a long process to step into each line.
I wanted to ask what command did you use exactly with rtems-test? I
couldn't find a recipe for qemu simulation for pc386 in
rtems-tools.git/tester/rtems/testing/bsps.
Regards,
Tanu Hari Dixit.
On Wed, May 31, 2017 at 12:42 AM, Cillian O'Donnell
wrote:
> Hi,
>
> I'm trying to run rtems-test for pc386 with the added --coverage tag for
> couverture-qemu. All tests default to dry-run because of errors in qemu.cfg
>
> error: qemu.cfg:81: execute failed: qemu-system-i386 -m 128 -boot b -hda
> /home/cpod/development/rtems/test/rtems-tools/tester/rtems/testing/coverage/rtems-boot.img
> -no-reboot -serial null -serial mon:stdio -nographic -append
> "--console=com1;boot;" -kernel
> /home/cpod/development/rtems/pc386/i386-rtems4.12/c/pc386/testsuites/samples/unlimited/unlimited.exe
> -exec-trace coverage/unlimited.exe.cov: exit-code:2
> warning: switched to dry run due to errors
>
> The exit code I believe refers to 'no such file or directory'. In qemu.cfg
> the line is:
>
> %execute %{qemu_cmd} %{qemu_opts} -kernel %{test_executable} %{coverage_arg}
>
> It's a bit tricky to trace those macros back to different files and see what
> they have. Is there any way to just print those out when it runs so I can
> take a look at them.
>
> I tried %print %{qemu_cmd} and %echo %{qemu_cmd}. Is there any way to do
> this in a config file?
>
> 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: Building RISC-V BSP
Hi Denis, Yes, that's a leftover flag that used to exist in the 2-year-old toolchain. There's no m32 (or m64) flag anymore. I submitted a fix (54bf80e) to my repo. You'll most likely get similar issues though in later stages. Fix-ups are welcome. Cheers, Hesham On Wed, May 31, 2017 at 3:19 AM, Gedare Bloom wrote: > On Tue, May 30, 2017 at 12:09 PM, Denis Obrezkov > wrote: >> 2017-05-30 18:31 GMT+03:00 Gedare Bloom : >>> >>> On Tue, May 30, 2017 at 7:49 AM, Denis Obrezkov >>> wrote: >>> > Hello, >>> > I am trying to build RTEMS for RISC-V BSP. I applied Hesham's patch for >>> > RSB >>> > and built RSB. But when I am trying to build rtems-generic target I get >>> > the >>> > mistake. >>> > This is my sequence of steps: >>> > >>> > git clone git://git.rtems.org/rtems-source-builder.git >>> > >>> > #patch applied here >>> > >>> > mkdir -p ./development/rtems/kernel >>> > >>> > cd ./development/rtems/kernel >>> > >>> > export RTEMS_DEV=~Projects/riscv/rtems/development >>> > >>> > git clone https://github.com/heshamelmatary/rtems-riscv.git >>> > >>> > cd .. >>> > >>> > mkdir rsb >>> > >>> > mv ../../rtems-source-builder/ ./rsb/ >>> > >>> > cd rsb/rtems-source-builder/rtems/ >>> > >>> > ../source-builder/sb-set-builder --prefix=$RTEMS_DEV/rtems/4.12 >>> > 4.12/rtems-riscv32 >>> > >>> is $RTEMS_DEV/rtems/4.12/bin in your $PATH? >>> >> You are right, somehow it wasn't there. >> >> Now I have another issue during make: >> >> checking for RTEMS_CPU_MODEL... >> checking for RTEMS_BSP_FAMILY... riscv_generic >> checking for CPU_CFLAGS... (cached) -m32 -march=I >> checking for CFLAGS_OPTIMIZE_V... (cached) -O0 -g >> checking for style of include used by make... GNU >> checking for riscv32-rtems4.12-gcc... riscv32-rtems4.12-gcc >> checking for riscv32-rtems4.12-gcc... (cached) riscv32-rtems4.12-gcc >> checking whether the C compiler works... no >> configure: error: in >> `/home/reprofy/Projects/riscv/rtems/development/rtems/kernel/riscv32/riscv32-rtems4.12/c/riscv_generic': >> configure: error: C compiler cannot create executables >> >> Now I can see the error - there is no such an option "-m32" in 32-bit gcc. >> But what does "(cached)" mean? >> > I think it means configure previously made this check and uses the > cached result of the previous check. > >> >> >> -- >> Regards, Denis Obrezkov -- Hesham ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: [PATCH] Add support to build riscv32 toolchain
Hi Sebastian, On Tue, May 30, 2017 at 4:01 PM, Sebastian Huber wrote: > Hello Hesham, > > thanks for your RISCV support. > > - Am 30. Mai 2017 um 3:51 schrieb Hesham Almatary > heshamelmat...@gmail.com: > >> --- >> rtems/config/4.12/rtems-riscv32.bset | 32 +++ >> rtems/config/tools/rtems-binutils-2.28-1.cfg | 22 >> .../rtems-gcc-7.1.0-newlib-2.5.0.20170323-1.cfg| 65 >> ++ > [...] >> +# >> +# Patches for gcc and newlib >> +# >> +%patch add gcc -p1 >> https://raw.githubusercontent.com/heshamelmatary/riscv-rtems-patches/master/gcc-rtems-riscv.patch > > Do you have a copyright assignment with the FSF? If not and you don't want to > do this, then I can try to add the RISCV support to GCC without locking at > your GCC patches. We should commit the things first into GCC. I do, just need to update my employment status, already talked to FSF people. Also, this should be merged part of the next gcc-riscv release [1]. [1] https://github.com/riscv/riscv-gcc/commit/443291274e05821a3425576d5393f3c776069cab > >> +%patch add newlib -p1 >> https://raw.githubusercontent.com/heshamelmatary/riscv-rtems-patches/master/0001-Import-risc-v-from-https-github.com-riscv.patch > > Are there plans by the RISCV people to add this to upstream Newlib soon? Due > to the RISCV support in FSF Binutils and GCC, there should be no problems. I've asked about that, don't have an answer yet -- Hesham ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: [PATCH] Add support to build riscv32 toolchain
On Wed, May 31, 2017 at 1:21 AM, Gedare Bloom wrote: > Unrelatedly to the contents, please use -v2 to identify revised patches. > Yes please ignore the first patch, thanks for the reminder. > On Tue, May 30, 2017 at 2:01 AM, Sebastian Huber > wrote: >> Hello Hesham, >> >> thanks for your RISCV support. >> >> - Am 30. Mai 2017 um 3:51 schrieb Hesham Almatary >> heshamelmat...@gmail.com: >> >>> --- >>> rtems/config/4.12/rtems-riscv32.bset | 32 +++ >>> rtems/config/tools/rtems-binutils-2.28-1.cfg | 22 >>> .../rtems-gcc-7.1.0-newlib-2.5.0.20170323-1.cfg| 65 >>> ++ >> [...] >>> +# >>> +# Patches for gcc and newlib >>> +# >>> +%patch add gcc -p1 >>> https://raw.githubusercontent.com/heshamelmatary/riscv-rtems-patches/master/gcc-rtems-riscv.patch >> >> Do you have a copyright assignment with the FSF? If not and you don't want >> to do this, then I can try to add the RISCV support to GCC without locking >> at your GCC patches. We should commit the things first into GCC. >> >>> +%patch add newlib -p1 >>> https://raw.githubusercontent.com/heshamelmatary/riscv-rtems-patches/master/0001-Import-risc-v-from-https-github.com-riscv.patch >> >> Are there plans by the RISCV people to add this to upstream Newlib soon? Due >> to the RISCV support in FSF Binutils and GCC, there should be no problems. >> ___ >> devel mailing list >> devel@rtems.org >> http://lists.rtems.org/mailman/listinfo/devel -- Hesham ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: rtems-test runtime errors qemu.cfg
Hi Tanu,
Thanks for the help, I had been grepping through the files and backtracking
through the definitions. I was just wondering was there a quick way to just
print it out that I didn't know about.
I also couldn't find the recipe for the bsp but the previous work I'm
continuing on from worked for pc386 and leon2, the command I'm using is the
standard command with an extra --coverage flag thats added in the work I'm
continuing, it definitely worked in 2015.
$HOME/development/rtems/test/rtems-tools/tester/rtems-test --rtems-bsp=pc386 \
--log=log_pc386 --coverage \
--rtems-tools=$HOME/development/rtems/4.12 \
$HOME/development/rtems/pc386/i386-rtems4.12/c/pc386/testsuites/
On 30 May 2017 at 20:34, Tanu Hari Dixit wrote:
> Hi Cillian,
>
> I usually do a git grep -i "" to find out where possibly a
> macro or variable is used elsewhere in the code. Not the best way, but
> works mostly.
> Also %{qemu_cmd} has been defined here in the same file
> (https://devel.rtems.org/browser/rtems-tools/tester/
> rtems/testing/qemu.cfg#L60).
> I also sometimes use winpdb to see what value a macro has but this is
> a long process to step into each line.
> I wanted to ask what command did you use exactly with rtems-test? I
> couldn't find a recipe for qemu simulation for pc386 in
> rtems-tools.git/tester/rtems/testing/bsps.
>
> Regards,
> Tanu Hari Dixit.
>
> On Wed, May 31, 2017 at 12:42 AM, Cillian O'Donnell
> wrote:
> > Hi,
> >
> > I'm trying to run rtems-test for pc386 with the added --coverage tag for
> > couverture-qemu. All tests default to dry-run because of errors in
> qemu.cfg
> >
> > error: qemu.cfg:81: execute failed: qemu-system-i386 -m 128 -boot b -hda
> > /home/cpod/development/rtems/test/rtems-tools/tester/rtems/
> testing/coverage/rtems-boot.img
> > -no-reboot -serial null -serial mon:stdio -nographic -append
> > "--console=com1;boot;" -kernel
> > /home/cpod/development/rtems/pc386/i386-rtems4.12/c/pc386/
> testsuites/samples/unlimited/unlimited.exe
> > -exec-trace coverage/unlimited.exe.cov: exit-code:2
> > warning: switched to dry run due to errors
> >
> > The exit code I believe refers to 'no such file or directory'. In
> qemu.cfg
> > the line is:
> >
> > %execute %{qemu_cmd} %{qemu_opts} -kernel %{test_executable}
> %{coverage_arg}
> >
> > It's a bit tricky to trace those macros back to different files and see
> what
> > they have. Is there any way to just print those out when it runs so I can
> > take a look at them.
> >
> > I tried %print %{qemu_cmd} and %echo %{qemu_cmd}. Is there any way to do
> > this in a config file?
> >
> > 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: rtems-test runtime errors qemu.cfg
Ah nevermind.. just realised its already printing them out.
On 30 May 2017 9:50 pm, "Cillian O'Donnell" wrote:
> Hi Tanu,
>
> Thanks for the help, I had been grepping through the files and
> backtracking through the definitions. I was just wondering was there a
> quick way to just print it out that I didn't know about.
>
> I also couldn't find the recipe for the bsp but the previous work I'm
> continuing on from worked for pc386 and leon2, the command I'm using is the
> standard command with an extra --coverage flag thats added in the work I'm
> continuing, it definitely worked in 2015.
>
> $HOME/development/rtems/test/rtems-tools/tester/rtems-test --rtems-bsp=pc386 \
> --log=log_pc386 --coverage \
> --rtems-tools=$HOME/development/rtems/4.12 \
> $HOME/development/rtems/pc386/i386-rtems4.12/c/pc386/testsuites/
>
>
> On 30 May 2017 at 20:34, Tanu Hari Dixit wrote:
>
>> Hi Cillian,
>>
>> I usually do a git grep -i "" to find out where possibly a
>> macro or variable is used elsewhere in the code. Not the best way, but
>> works mostly.
>> Also %{qemu_cmd} has been defined here in the same file
>> (https://devel.rtems.org/browser/rtems-tools/tester/rtems/
>> testing/qemu.cfg#L60).
>> I also sometimes use winpdb to see what value a macro has but this is
>> a long process to step into each line.
>> I wanted to ask what command did you use exactly with rtems-test? I
>> couldn't find a recipe for qemu simulation for pc386 in
>> rtems-tools.git/tester/rtems/testing/bsps.
>>
>> Regards,
>> Tanu Hari Dixit.
>>
>> On Wed, May 31, 2017 at 12:42 AM, Cillian O'Donnell
>> wrote:
>> > Hi,
>> >
>> > I'm trying to run rtems-test for pc386 with the added --coverage tag for
>> > couverture-qemu. All tests default to dry-run because of errors in
>> qemu.cfg
>> >
>> > error: qemu.cfg:81: execute failed: qemu-system-i386 -m 128 -boot b -hda
>> > /home/cpod/development/rtems/test/rtems-tools/tester/rtems/t
>> esting/coverage/rtems-boot.img
>> > -no-reboot -serial null -serial mon:stdio -nographic -append
>> > "--console=com1;boot;" -kernel
>> > /home/cpod/development/rtems/pc386/i386-rtems4.12/c/pc386/te
>> stsuites/samples/unlimited/unlimited.exe
>> > -exec-trace coverage/unlimited.exe.cov: exit-code:2
>> > warning: switched to dry run due to errors
>> >
>> > The exit code I believe refers to 'no such file or directory'. In
>> qemu.cfg
>> > the line is:
>> >
>> > %execute %{qemu_cmd} %{qemu_opts} -kernel %{test_executable}
>> %{coverage_arg}
>> >
>> > It's a bit tricky to trace those macros back to different files and see
>> what
>> > they have. Is there any way to just print those out when it runs so I
>> can
>> > take a look at them.
>> >
>> > I tried %print %{qemu_cmd} and %echo %{qemu_cmd}. Is there any way to
>> do
>> > this in a config file?
>> >
>> > 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: [PATCH] Add support to build riscv32 toolchain
- Am 30. Mai 2017 um 22:41 schrieb Hesham Almatary heshamelmat...@gmail.com: > Hi Sebastian, > > On Tue, May 30, 2017 at 4:01 PM, Sebastian Huber > wrote: >> Hello Hesham, >> >> thanks for your RISCV support. >> >> - Am 30. Mai 2017 um 3:51 schrieb Hesham Almatary >> heshamelmat...@gmail.com: >> >>> --- >>> rtems/config/4.12/rtems-riscv32.bset | 32 +++ >>> rtems/config/tools/rtems-binutils-2.28-1.cfg | 22 >>> .../rtems-gcc-7.1.0-newlib-2.5.0.20170323-1.cfg| 65 >>> ++ >> [...] >>> +# >>> +# Patches for gcc and newlib >>> +# >>> +%patch add gcc -p1 >>> https://raw.githubusercontent.com/heshamelmatary/riscv-rtems-patches/master/gcc-rtems-riscv.patch >> >> Do you have a copyright assignment with the FSF? If not and you don't want >> to do >> this, then I can try to add the RISCV support to GCC without locking at your >> GCC patches. We should commit the things first into GCC. > I do, just need to update my employment status, already talked to FSF > people. Also, this should be merged part of the next gcc-riscv release > [1]. Ok, I checked in your patch. Could you please try to move the RTEMS support into the standard ELF target support, see ARM support for RTEMS as an example. Using the ELF section helps to get updates for free or at least someone asks us before changing things. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Time of the next GSoC meetings
Hello Gedare, could you announce the time of the next GSoC meeting(s)? -- Regards, Denis Obrezkov ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: Time of the next GSoC meetings
Yes, tomorrow at 11am EST (GMT-4) again. These will be recurring events every Wednesday at the same time (unless I/Joel don't show up!) On Tue, May 30, 2017 at 6:51 PM, Denis Obrezkov wrote: > Hello Gedare, > > could you announce the time of the next GSoC meeting(s)? > > -- > Regards, Denis Obrezkov ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: Time of the next GSoC meetings
EDIT: 10am EST (GMT-4) 10a-11a. On Tue, May 30, 2017 at 7:25 PM, Gedare Bloom wrote: > Yes, tomorrow at 11am EST (GMT-4) again. These will be recurring > events every Wednesday at the same time (unless I/Joel don't show up!) > > On Tue, May 30, 2017 at 6:51 PM, Denis Obrezkov > wrote: >> Hello Gedare, >> >> could you announce the time of the next GSoC meeting(s)? >> >> -- >> Regards, Denis Obrezkov ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: [PATCH] Added documentation for rtems-tester in rtems-docs
Thanks. Next time use the -v2 flag to specify a revised version of a patch. On Tue, May 30, 2017 at 2:55 PM, Tanu Hari Dixit wrote: > Hello Gedare, > > I have sent the patches separately. > > Thank you, > Tanu. > > On Tue, May 30, 2017 at 10:50 PM, Gedare Bloom wrote: >> On Tue, May 30, 2017 at 1:10 PM, Tanu Hari Dixit >> wrote: >>> Hello Gedare, >>> >>> I just added the image following what was already in rtems-tools.git >>> repo. Maybe it is not really needed there. Maybe it was added to the >>> previous doc because it was a stand-alone doc. I will pull that out. >>> What do you think? What does Chris think? >>> >>> Regards, >>> Tanu. >>> >> >> Send the text change separately for review from the image. thanks. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: rtems-test runtime errors qemu.cfg
Does it work without --coverage flag?
On Tue, May 30, 2017 at 5:23 PM, Cillian O'Donnell
wrote:
> Ah nevermind.. just realised its already printing them out.
>
> On 30 May 2017 9:50 pm, "Cillian O'Donnell" wrote:
>>
>> Hi Tanu,
>>
>> Thanks for the help, I had been grepping through the files and
>> backtracking through the definitions. I was just wondering was there a quick
>> way to just print it out that I didn't know about.
>>
>> I also couldn't find the recipe for the bsp but the previous work I'm
>> continuing on from worked for pc386 and leon2, the command I'm using is the
>> standard command with an extra --coverage flag thats added in the work I'm
>> continuing, it definitely worked in 2015.
>>
>> $HOME/development/rtems/test/rtems-tools/tester/rtems-test
>> --rtems-bsp=pc386 \
>> --log=log_pc386 --coverage \
>> --rtems-tools=$HOME/development/rtems/4.12 \
>> $HOME/development/rtems/pc386/i386-rtems4.12/c/pc386/testsuites/
>>
>>
>> On 30 May 2017 at 20:34, Tanu Hari Dixit wrote:
>>>
>>> Hi Cillian,
>>>
>>> I usually do a git grep -i "" to find out where possibly a
>>> macro or variable is used elsewhere in the code. Not the best way, but
>>> works mostly.
>>> Also %{qemu_cmd} has been defined here in the same file
>>>
>>> (https://devel.rtems.org/browser/rtems-tools/tester/rtems/testing/qemu.cfg#L60).
>>> I also sometimes use winpdb to see what value a macro has but this is
>>> a long process to step into each line.
>>> I wanted to ask what command did you use exactly with rtems-test? I
>>> couldn't find a recipe for qemu simulation for pc386 in
>>> rtems-tools.git/tester/rtems/testing/bsps.
>>>
>>> Regards,
>>> Tanu Hari Dixit.
>>>
>>> On Wed, May 31, 2017 at 12:42 AM, Cillian O'Donnell
>>> wrote:
>>> > Hi,
>>> >
>>> > I'm trying to run rtems-test for pc386 with the added --coverage tag
>>> > for
>>> > couverture-qemu. All tests default to dry-run because of errors in
>>> > qemu.cfg
>>> >
>>> > error: qemu.cfg:81: execute failed: qemu-system-i386 -m 128 -boot b
>>> > -hda
>>> >
>>> > /home/cpod/development/rtems/test/rtems-tools/tester/rtems/testing/coverage/rtems-boot.img
>>> > -no-reboot -serial null -serial mon:stdio -nographic -append
>>> > "--console=com1;boot;" -kernel
>>> >
>>> > /home/cpod/development/rtems/pc386/i386-rtems4.12/c/pc386/testsuites/samples/unlimited/unlimited.exe
>>> > -exec-trace coverage/unlimited.exe.cov: exit-code:2
>>> > warning: switched to dry run due to errors
>>> >
>>> > The exit code I believe refers to 'no such file or directory'. In
>>> > qemu.cfg
>>> > the line is:
>>> >
>>> > %execute %{qemu_cmd} %{qemu_opts} -kernel %{test_executable}
>>> > %{coverage_arg}
>>> >
>>> > It's a bit tricky to trace those macros back to different files and see
>>> > what
>>> > they have. Is there any way to just print those out when it runs so I
>>> > can
>>> > take a look at them.
>>> >
>>> > I tried %print %{qemu_cmd} and %echo %{qemu_cmd}. Is there any way to
>>> > do
>>> > this in a config file?
>>> >
>>> > 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
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
Re: [PATCH] Added documentation for rtems-tester in rtems-docs
On 31/05/2017 03:10, Tanu Hari Dixit wrote: I just added the image following what was already in rtems-tools.git repo. Maybe it is not really needed there. Maybe it was added to the previous doc because it was a stand-alone doc. Yes this is correct. The User Manual is newer and has a consistent feel we must maintain. I will pull that out. What do you think? What does Chris think? The text needs to be merged into the User Manual converting it to ReST format. I suggest you review the RTEMS BSP Builder [1] command as an example. That format _must_ be followed for the Tools. Please create a new file for this command and include after the RTEMS BSP Builder command. Thanks Chris [1] https://docs.rtems.org/branches/master/user/tools/index.html#rtems-bsp-builder ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: [PATCH] Fixes typos in README.txt
On 29/05/2017 22:29, Tanu Hari Dixit wrote: From: tokencolour Could we please have your name in the commit? It make the git log much more meaningful. For example: From: Tanu Hari Dixit Thanks Chris 2 typos fixed --- README.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.txt b/README.txt index f09317e..c1b7e6f 100644 --- a/README.txt +++ b/README.txt @@ -316,7 +316,7 @@ existing documentation for an example and if unsure ask. Heading Description 1 ## Part 2 ** Section - 3 == Sub-ection + 3 == Sub-section 4 -- Sub-sub-section 5 ^^ Sub-sub-sub-section 6 ~~ Sub-sub-sub-sub-section @@ -392,7 +392,7 @@ existing documentation for an example and if unsure ask. users: Users Mailing List vc : Version Control Mailing List - The valif URLs are: + The valid URLs are: trac : https://devel.rtems.org/ devel: https://devel.rtems.org/ ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: rtems-tools build errors after coverage tools patches
On 29/05/2017 19:39, Cillian O'Donnell wrote: I added #include "rld.h" in rtemstoolkit/rld-process.h and that was it, build successful, happy days! Excellent work. Could you please post a patch for rtems-tools.git master to fix this? Thanks Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
RTEMS 4.12 gcc-7.1.0/binutils-2.28 test results
Hi, I am testing RSB patches to move 4.12 to gcc 7.1.0/binutils-2.28. The SH arch fails to build on FreeBSD 11.0. The issue is https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80923. RTEMS BSP Builder results summary for: $ rtems-bsp-builder --rtems-tools=/build/rtems/tools/4.12-7.1 --rtems=/opt/work/chris/rtems/kernel/rtems.git --log=everything-standard-7.1 --profile=everything --build=standard --jobs=7/6 Total: Warnings:8682 exes:1996 objs:249031 libs:11855 Failures: 1 standard powerpc/mcp750 build: configure: /opt/work/chris/rtems/kernel/rtems.git/configure --target\ =powerpc-rtems4.12 --enable-rtemsbsp=mcp750 --prefix=/opt/rtems/4.12 2 standard powerpc/mtx603e build: configure: /opt/work/chris/rtems/kernel/rtems.git/configure --target\ =powerpc-rtems4.12 --enable-rtemsbsp=mtx603e\ --prefix=/opt/rtems/4.12 3 standard powerpc/mvme2100 build: configure: /opt/work/chris/rtems/kernel/rtems.git/configure --target\ =powerpc-rtems4.12 --enable-rtemsbsp=mvme2100\ --prefix=/opt/rtems/4.12 4 standard powerpc/mvme2307 build: configure: /opt/work/chris/rtems/kernel/rtems.git/configure --target\ =powerpc-rtems4.12 --enable-rtemsbsp=mvme2307\ --prefix=/opt/rtems/4.12 5 standard powerpc/qemuprep-altivec build: configure: /opt/work/chris/rtems/kernel/rtems.git/configure --target\ =powerpc-rtems4.12 --enable-rtemsbsp=qemuprep-altivec\ --prefix=/opt/rtems/4.12 6 standard powerpc/qemuprep build: configure: /opt/work/chris/rtems/kernel/rtems.git/configure --target\ =powerpc-rtems4.12 --enable-rtemsbsp=qemuprep\ --prefix=/opt/rtems/4.12 7 standard sh/gensh1 build: configure: /opt/work/chris/rtems/kernel/rtems.git/configure --target\ =sh-rtems4.12 --enable-rtemsbsp=gensh1 --prefix=/opt/rtems/4.12 8 standard sh/gensh2 build: configure: /opt/work/chris/rtems/kernel/rtems.git/configure --target\ =sh-rtems4.12 --enable-rtemsbsp=gensh2 --prefix=/opt/rtems/4.12 9 standard sh/gensh4 build: configure: /opt/work/chris/rtems/kernel/rtems.git/configure --target\ =sh-rtems4.12 --enable-rtemsbsp=gensh4 --prefix=/opt/rtems/4.12 10 standard sh/simsh1 build: configure: /opt/work/chris/rtems/kernel/rtems.git/configure --target\ =sh-rtems4.12 --enable-rtemsbsp=simsh1 --prefix=/opt/rtems/4.12 11 standard sh/simsh2 build: configure: /opt/work/chris/rtems/kernel/rtems.git/configure --target\ =sh-rtems4.12 --enable-rtemsbsp=simsh2 --prefix=/opt/rtems/4.12 12 standard sh/simsh2e build: configure: /opt/work/chris/rtems/kernel/rtems.git/configure --target\ =sh-rtems4.12 --enable-rtemsbsp=simsh2e --prefix=/opt/rtems/4.12 13 standard sh/simsh4 build: configure: /opt/work/chris/rtems/kernel/rtems.git/configure --target\ =sh-rtems4.12 --enable-rtemsbsp=simsh4 --prefix=/opt/rtems/4.12 Average BSP Build Time: 0:00:17.431351 Total Time 0:49:23.329735 Passes: 157 Failures: 13 The SH failures are expected because there are no tools. I have reached out to find a solution here. The PowerPC failures are due to using binutils-2.28 and linking the bootloader. It is broken. The linker is generating lots of messages like: /opt/work/chris/rtems/kernel/rtems.git/c/src/lib/libbsp/powerpc/motorola_powerpc/bootloader/../../../powerpc/shared/bootloader/head.S:140:(.text+0x8a): dangerous relocation: generic linker can't handle R_PPC_SECTOFF_HA This bug exposes a PowerPC BSP build system error where running make again does not generate the error. It seems the RALF file rules are broken. I am happy to push the patches to update to gcc-7.1.0 and binutils-2.28 and keep SH on the current tools and the PowerPC on binutils-2.27. I will run a build of everything with tests. Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: Building RISC-V BSP
Hi Denis, Please use priv-1.10 branch. I rebased it (against master) and added some fixes to make the build progress. Still, there's more work needed. Your contributions are welcomed. Cheers, Hesham . On Wed, May 31, 2017 at 6:16 AM, Hesham Almatary wrote: > Hi Denis, > > Yes, that's a leftover flag that used to exist in the 2-year-old > toolchain. There's no m32 (or m64) flag anymore. I submitted a fix > (54bf80e) to my repo. You'll most likely get similar issues though in > later stages. Fix-ups are welcome. > > Cheers, > Hesham > > On Wed, May 31, 2017 at 3:19 AM, Gedare Bloom wrote: >> On Tue, May 30, 2017 at 12:09 PM, Denis Obrezkov >> wrote: >>> 2017-05-30 18:31 GMT+03:00 Gedare Bloom : On Tue, May 30, 2017 at 7:49 AM, Denis Obrezkov wrote: > Hello, > I am trying to build RTEMS for RISC-V BSP. I applied Hesham's patch for > RSB > and built RSB. But when I am trying to build rtems-generic target I get > the > mistake. > This is my sequence of steps: > > git clone git://git.rtems.org/rtems-source-builder.git > > #patch applied here > > mkdir -p ./development/rtems/kernel > > cd ./development/rtems/kernel > > export RTEMS_DEV=~Projects/riscv/rtems/development > > git clone https://github.com/heshamelmatary/rtems-riscv.git > > cd .. > > mkdir rsb > > mv ../../rtems-source-builder/ ./rsb/ > > cd rsb/rtems-source-builder/rtems/ > > ../source-builder/sb-set-builder --prefix=$RTEMS_DEV/rtems/4.12 > 4.12/rtems-riscv32 > is $RTEMS_DEV/rtems/4.12/bin in your $PATH? >>> You are right, somehow it wasn't there. >>> >>> Now I have another issue during make: >>> >>> checking for RTEMS_CPU_MODEL... >>> checking for RTEMS_BSP_FAMILY... riscv_generic >>> checking for CPU_CFLAGS... (cached) -m32 -march=I >>> checking for CFLAGS_OPTIMIZE_V... (cached) -O0 -g >>> checking for style of include used by make... GNU >>> checking for riscv32-rtems4.12-gcc... riscv32-rtems4.12-gcc >>> checking for riscv32-rtems4.12-gcc... (cached) riscv32-rtems4.12-gcc >>> checking whether the C compiler works... no >>> configure: error: in >>> `/home/reprofy/Projects/riscv/rtems/development/rtems/kernel/riscv32/riscv32-rtems4.12/c/riscv_generic': >>> configure: error: C compiler cannot create executables >>> >>> Now I can see the error - there is no such an option "-m32" in 32-bit gcc. >>> But what does "(cached)" mean? >>> >> I think it means configure previously made this check and uses the >> cached result of the previous check. >> >>> >>> >>> -- >>> Regards, Denis Obrezkov > > > > -- > Hesham -- Hesham ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
