Re: Xilinx MPSoC, CAN, CAN-FD
On 2023-09-19 09:36, Kinsey Moore wrote: On Tue, Sep 19, 2023 at 7:25 AM emanuel stiebler <mailto:e...@e-bbes.com>> wrote: Anybody using CAN on the xilinx MPSoC? Does CON-FD work too? Hi Emanuel, Those drivers haven't been ported in from the embeddedsw repository yet since I haven't had a need for them. If you want to try porting them into RTEMS, the framework for them is already in place and used by the QSPI and static memory controller (NAND) drivers so it shouldn't be all that complicated. If you decide you want to attempt this, please also be aware of the recent HAL discussion on this list. Just checked again in the DataSheet of the Xilinx MPSoC, and it doesn't support CAN FD (Flexible DataRate) , only CAN :( ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: ADA, gnat, rtems 6, ubuntu 22LTS
On 2023-10-05 12:42, Frank Kühndel wrote:
Hello Emanuel,
I cannot say anything about your specific issue. I can just provide this
information:
Our CI/CD builds rtems-tools with ADA on Ubuntu 22.04 for RSB, Git
commit 35c73203df1e0bc7f0935cfb37ebc6581d8f1103 for aarch64, arm, bfin,
i386, m68k, mips, moxie, nios2, or1k, powerpc, riskv, sparc, x86_64. The
other architectures seem to have problems. Moreover, ADA is only build
but not tested.
The big issue between building with and without ADA comes down to have
Ubuntu specially setup for the RTEMS Source Builder to being able to
build ADA. I need these packages:
bzip2
gcc-12
g++-12
gnat-12
And I need the following links (all g** compiler tools must have the
same version 12 and all must be available without the "-12" postfix):
ln -s gcc /usr/bin/cc
for exe in /usr/bin/gcc*12 /usr/bin/gcov*12 /usr/bin/g++*12; do
ln -s $exe ${exe%-12}
done
This did the trick, at least I can get the tools to compile.
We probably should mention that somewhere in the ADA set ups.
One glitch I noticed, that as soon as ubuntu updates the compiler again,
the links get removed, so the soft links has to be made again.
THANKS, emanuel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
ADA, gnat, rtems 6, ubuntu 22LTS
I just tried to compile the tools for rtems6, and just with "C", everything(?) works. Trying to add ADA to the tools, it fails, complaining about gnat not being installed. In the logfile: hecking for objdir... .libs configure: WARNING: using in-tree isl, disabling version check configure: error: GNAT is required to build ada shell cmd failed: /bin/sh -ex /AD1/PUB/RTEMS.work/rsb/rtems/build/aarch64-rtems6-gcc-506cb58-newlib-a021448-x86_64-linux-gnu-1/do-build error: building aarch64-rtems6-gcc-506cb58-newlib-a021448-x86_64-linux-gnu-1emu@W531:/AD1/PUB/RTEMS.work/rsb/rtems$ but "gnat" gives me: DDD@W531:/AD1/PUB/RTEMS.work/rsb/rtems$ gnat GNAT 12.3.0 Copyright 1996-2022, Free Software Foundation, Inc. To list Ada build switches use --help-ada List of available commands gnat bind x86_64-linux-gnu-gnatbind-12 gnat chop x86_64-linux-gnu-gnatchop-12 gnat clean x86_64-linux-gnu-gnatclean-12 gnat compilex86_64-linux-gnu-gnatmake-12 -f -u -c gnat check x86_64-linux-gnu-gnatcheck-12 gnat elim x86_64-linux-gnu-gnatelim-12 gnat find x86_64-linux-gnu-gnatfind-12 gnat krunch x86_64-linux-gnu-gnatkr-12 gnat link x86_64-linux-gnu-gnatlink-12 gnat list x86_64-linux-gnu-gnatls-12 gnat make x86_64-linux-gnu-gnatmake-12 gnat metric x86_64-linux-gnu-gnatmetric-12 gnat name x86_64-linux-gnu-gnatname-12 gnat preprocess x86_64-linux-gnu-gnatprep-12 gnat pretty x86_64-linux-gnu-gnatpp-12 gnat stack x86_64-linux-gnu-gnatstack-12 gnat stub x86_64-linux-gnu-gnatstub-12 gnat test x86_64-linux-gnu-gnattest-12 gnat xref x86_64-linux-gnu-gnatxref-12 Report bugs to rep...@adacore.com What am I missing? (GIT version of yesterday ...) Cheers & Thanks ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Xilinx MPSoC, programmable logic download
Hi all, are there any tools in RTEMS to download the bit stream into the logic part of the FPGA, after boot? Thanks! ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Xilinx MPSoC, CAN, CAN-FD
Anybody using CAN on the xilinx MPSoC? Does CON-FD work too? Thanks, Emanuel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: RISC-V double float alignment
On 2019-02-01 10:08, Jiri Gaisler wrote: > Hello, > > As far as I understand, RISC-V does not require any particular alignment > of data structures in memory. [ ... ] RISC-V explicitly states somewhere in the manuals, (?) that it supports unaligned access to memory, but it could be emulated in software, and accesses should/will be fastest on aligned addresses Actually, writing it I found it on wiki & the manual ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: BSP for Xilinx Zynq UltraScale+ MPSoC platform
On 2019-01-23 03:34, Sebastian Huber wrote: > Hello, > > we will very likely soon work a BSP for the Xilinx Zynq UltraScale+ > MPSoC platform: > https://devel.rtems.org/ticket/3682 Excellent! > Please let me know, if you are interested in support for the Cortex-R5 > processors or AArch64 mode. I think, the AARch64 is more rewarding, as the R5 should be easy afterwards (same peripherals(?)). And I think we discussed it already before, the big step is to get the 64bit version of all the tools? > The development platform will be this evaluation kit: > https://www.xilinx.com/products/boards-and-kits/zcu104.html Nice! ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
source-builder-documentation
Did it move? both links on the wiki https://devel.rtems.org/wiki/Developer/Tools/RSB go nowhere (https://docs.rtems.org/rsb) Thanks ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
xilinx microblaze
Hi all, should it still work, didn't see anything about it for a while on this list, tried yesterday, and the source-builder failed in newlib: microblaze-rtems4.11-ar rc ../libc.a *.o microblaze-rtems4.11-ranlib libc.a rm -rf tmp make[8]: Leaving directory '/cygdrive/d/_home/emu/RTEMS.Work/rtems-source-builder/rtems/build/microblaze-rtems4.11-gcc-4.9.3-newlib-2.2.0.20150423-x86_64-pc-cygwin-1/build/microblaze-rtems4.11/m/mh/le/newlib/libc' Makefile:675: recipe for target 'all-recursive' failed make[7]: Leaving directory '/cygdrive/d/_home/emu/RTEMS.Work/rtems-source-builder/rtems/build/microblaze-rtems4.11-gcc-4.9.3-newlib-2.2.0.20150423-x86_64-pc-cygwin-1/build/microblaze-rtems4.11/m/mh/le/newlib/libc' make[7]: *** [all-recursive] Error 1 Makefile:627: recipe for target 'all-recursive' failed make[6]: *** [all-recursive] Error 1 make[6]: Leaving directory '/cygdrive/d/_home/emu/RTEMS.Work/rtems-source-builder/rtems/build/microblaze-rtems4.11-gcc-4.9.3-newlib-2.2.0.20150423-x86_64-pc-cygwin-1/build/microblaze-rtems4.11/m/mh/le/newlib' make[5]: *** [all] Error 2 Makefile:450: recipe for target 'all' failed make[5]: Leaving directory '/cygdrive/d/_home/emu/RTEMS.Work/rtems-source-builder/rtems/build/microblaze-rtems4.11-gcc-4.9.3-newlib-2.2.0.20150423-x86_64-pc-cygwin-1/build/microblaze-rtems4.11/m/mh/le/newlib' make[4]: *** [multi-do] Error 1 Makefile:1188: recipe for target 'multi-do' failed make[4]: Leaving directory '/cygdrive/d/_home/emu/RTEMS.Work/rtems-source-builder/rtems/build/microblaze-rtems4.11-gcc-4.9.3-newlib-2.2.0.20150423-x86_64-pc-cygwin-1/build/microblaze-rtems4.11/newlib' make[3]: *** [all-multi] Error 2 Makefile:1104: recipe for target 'all-multi' failed make[3]: Leaving directory '/cygdrive/d/_home/emu/RTEMS.Work/rtems-source-builder/rtems/build/microblaze-rtems4.11-gcc-4.9.3-newlib-2.2.0.20150423-x86_64-pc-cygwin-1/build/microblaze-rtems4.11/newlib' make[2]: *** [all] Error 2 Makefile:450: recipe for target 'all' failed make[2]: Leaving directory '/cygdrive/d/_home/emu/RTEMS.Work/rtems-source-builder/rtems/build/microblaze-rtems4.11-gcc-4.9.3-newlib-2.2.0.20150423-x86_64-pc-cygwin-1/build/microblaze-rtems4.11/newlib' Makefile:11086: recipe for target 'all-target-newlib' failed make[1]: Leaving directory '/cygdrive/d/_home/emu/RTEMS.Work/rtems-source-builder/rtems/build/microblaze-rtems4.11-gcc-4.9.3-newlib-2.2.0.20150423-x86_64-pc-cygwin-1/build' make[1]: *** [all-target-newlib] Error 2 Makefile:866: recipe for target 'all' failed make: *** [all] Error 2 shell cmd failed: sh -ex /cygdrive/d/_home/emu/RTEMS.Work/rtems-source-builder/rtems/build/microblaze-rtems4.11-gcc-4.9.3-newlib-2.2.0.20150423-x86_64-pc-cygwin-1/doit error: building microblaze-rtems4.11-gcc-4.9.3-newlib-2.2.0.20150423-x86_64-pc-cygwin-1 See error report: rsb-report-microblaze-rtems4.11-gcc-4.9.3-newlib-2.2.0.20150423-x86_64-pc-cygwin-1.txt Build Set: Time 2:12:55.482808 ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: rtems-source-builder on cygwin/64, WAF?
On 2015-03-17 22:38, Chris Johns wrote: On 18/03/2015 7:28 am, Chris Johns wrote: I am testing this now as I needed to add 'merge' to the git module. Pushed as https://git.rtems.org/rtems-source-builder/commit/?id=b0f9e30fa46a8025b76bf86321ebe585de8972f4 OK, so I managed to compile the toolchains for arm, m68k and mips today. (and also compiled RTEMS for arm and two BSPs) So I guess it is working. Thanks! ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: rtems-source-builder on cygwin/64, WAF?
On 2015-03-17 17:37, Joel Sherrill wrote: On 3/17/2015 11:30 AM, emanuel stiebler wrote: On 2015-03-17 11:41, Chris Johns wrote: On 17/03/2015 2:48 am, Joel Sherrill wrote: Hmmm.. copying from the log you attached: This looks like somehow the the contents of ./rtemstoolkit/elftoolchain/libelf/_libelf_config.h are not being tripped by whatever conditionals are set on your host. I see FreeBSD, Apple, and Linux sections of the file. You can build rtems-tools by hand easily and see what's going wrong in that file. It may be as easy as adding || defined(__cygwin__) or similar in the right place. I have pushed a fix for this. It is building on Cygwin. Which one did you update? I did a git pull on rtems-source-builder, and still got the same error ... This was an issue in rtems-tools. Can you see if you can update that and build it by hand? RSB may need a hash tag updated and Chris might not have done that. *** note sure on this *** On 2015-03-17 17:37, Joel Sherrill wrote: This was an issue in rtems-tools. Can you see if you can update that and build it by hand? RSB may need a hash tag updated and Chris might not have done that. *** note sure on this *** OK, this time it went through! Thanks! ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: rtems-source-builder on cygwin/64, WAF?
On 2015-03-17 11:41, Chris Johns wrote: On 17/03/2015 2:48 am, Joel
Sherrill wrote:
Hmmm.. copying from the log you attached:
This looks like somehow the the contents of
./rtemstoolkit/elftoolchain/libelf/_libelf_config.h are not being
tripped by whatever conditionals are set on your host. I see FreeBSD,
Apple, and Linux sections of the file.
You can build rtems-tools by hand easily and see what's going
wrong in that file. It may be as easy as adding || defined(__cygwin__)
or similar in the right place.
I have pushed a fix for this. It is building on Cygwin.
Which one did you update? I did a git pull on rtems-source-builder,
and still got the same error ...
RTEMS Tools Project - Source Builder Error Report
Build: error: building rtems-tools-HEAD-1
Command Line: ../source-builder/sb-set-builder --log=l-arm.txt --jobs=4
--prefix=/opt/rtems-4.11 4.11/rtems-arm --no-clean
Python: 2.7.8 (default, Jul 25 2014, 14:04:36) [GCC 4.8.3]
git://git.rtems.org/rtems-source-builder.git/origin/7f7d388af88f56139d7c6a832b551c5366adcefc-modified
CYGWIN_NT-6.1 w530 1.7.35(0.287/5/3) 2015-03-04 12:09 x86_64
Tail of the build log:
script: 80: build_top=$(pwd)
script: 81: source_dir_rtems_tools=rtems-tools-HEAD-1
source setup: rtems-tools-HEAD-1: source rtems-tools -q -D -n rtems-tools-HEAD-1
making dir:
/cygdrive/d/_home/emu/RTEMS.Work/rtems-source-builder/rtems/sources/git
git: fetch: git://git.rtems.org/rtems-tools.git - sources/git/rtems-tools.git
git: reset: git://git.rtems.org/rtems-tools.git
git: checkout: git://git.rtems.org/rtems-tools.git = master
script: 82: cd
/cygdrive/d/_home/emu/RTEMS.Work/rtems-source-builder/rtems/build/rtems-tools-HEAD-1
script: 83: ln -s
/cygdrive/d/_home/emu/RTEMS.Work/rtems-source-builder/rtems/sources/git/rtems-tools.git
${source_dir_rtems_tools}
script: 84: cd rtems-tools-HEAD-1
script: 85: chmod -R a+rX,g-w,o-w .
script: 86: cd ${build_top}
script: 87: SB_CXC=no
script: 88: echo == clean %{buildroot}: ${SB_BUILD_ROOT}
script: 89: rm -rf ${SB_BUILD_ROOT}
script: 90: /bin/mkdir -p ${SB_BUILD_ROOT}
script: 91: echo == %build:
script: 92: build_top=$(pwd)
script: 93: if test x86_64-pc-cygwin != x86_64-pc-cygwin ; then
script: 94: RT_HOST=-host=x86_64-pc-cygwin
script: 95: else
script: 96: RT_HOST=
script: 97: fi
script: 98: cd ${source_dir_rtems_tools}
script: 99: ./waf configure ${RT_HOST} --prefix=/opt/rtems-4.11
script:100: ./waf
script:101: cd ${build_top}
script:102: echo == %install:
script:103: build_top=$(pwd)
script:104: rm -rf $SB_BUILD_ROOT
script:105: cd ${source_dir_rtems_tools}
script:106: ./waf --destdir=$SB_BUILD_ROOT install
script:107: cd ${build_top}
removing:
/cygdrive/d/_home/emu/RTEMS.Work/rtems-source-builder/rtems/build/rtems-tools-HEAD-1
making dir:
/cygdrive/d/_home/emu/RTEMS.Work/rtems-source-builder/rtems/build/rtems-tools-HEAD-1
write script:
/cygdrive/d/_home/emu/RTEMS.Work/rtems-source-builder/rtems/build/rtems-tools-HEAD-1/doit
building: rtems-tools-HEAD-1
run: sh -ex
/cygdrive/d/_home/emu/RTEMS.Work/rtems-source-builder/rtems/build/rtems-tools-HEAD-1/doit
+ export
'SB_ORIG_PATH=/opt/rtems-4.11/bin:/usr/local/bin:/usr/bin:/cygdrive/c/ProgramData/Oracle/Java/javapath:/cygdrive/c/PROGRAM
FILES/COMMON FILES/MICROSOFT SHARED/WINDOWS LIVE:/cygdrive/c/PROGRAM FILES
(X86)/COMMON FILES/MICROSOFT SHARED/WINDOWS LIVE:/cygdrive/c/PROGRAM FILES
(X86)/INTEL/ICLS CLIENT:/cygdrive/c/PROGRAM FILES/INTEL/ICLS
CLIENT:/cygdrive/c/windows/SYSTEM32:/cygdrive/c/windows:/cygdrive/c/windows/SYSTEM32/WBEM:/cygdrive/c/windows/SYSTEM32/WINDOWSPOWERSHELL/V1.0:/cygdrive/c/PROGRAM
FILES/INTEL/INTEL(R) MANAGEMENT ENGINE COMPONENTS/DAL:/cygdrive/c/PROGRAM
FILES/INTEL/INTEL(R) MANAGEMENT ENGINE COMPONENTS/IPT:/cygdrive/c/PROGRAM FILES
(X86)/INTEL/INTEL(R) MANAGEMENT ENGINE COMPONENTS/DAL:/cygdrive/c/PROGRAM FILES
(X86)/INTEL/INTEL(R) MANAGEMENT ENGINE COMPONENTS/IPT:/cygdrive/c/PROGRAM FILES
(X86)/INTEL/OPENCL SDK/2.0/BIN/X86:/cygdrive/c/PROGRAM FILES (X86)/INTEL/OPENCL
SDK/2.0/BIN/X64:/cygdrive/c/PROGRAM FILES/COMMON
FILES/LENOVO:/cygdrive/c/PROGRAM FILES (X86)/COMMON FILES/ULEAD
SYSTEMS/MPEG:/cygdrive/c/PROGRAM FILES (X86)/WINDOWS
LIVE/SHARED:/cygdrive/c/SWTOOLS/READYAPPS:/cygdrive/c/PROGRAM FILES
(X86)/SYMANTEC/VIP ACCESS CLIENT:/cygdrive/c/PROGRAM FILES (X86)/COMMON
FILES/LENOVO:/cygdrive/c/Program Files/ThinkPad/Bluetooth
Software:/cygdrive/c/Program Files/ThinkPad/Bluetooth
Software/syswow64:/cygdrive/c/Program Files (x86)/Intel/OpenCL
SDK/2.0/bin/x86:/cygdrive/c/Program Files (x86)/Intel/OpenCL
SDK/2.0/bin/x64:/cygdrive/c/Program Files/Intel/Intel(R) Management Engine
Components/DAL:/cygdrive/c/Program Files/Intel/Intel(R) Management Engine
Components/IPT:/cygdrive/c/Program Files (x86)/Intel/Intel(R) Management Engine
Components/DAL:/cygdrive/c/Program Files (x86)/Intel/Intel(R) Management Engine
Components/IPT:/cygdrive/c/Program Files (x86)/Common
Re: rtems-source-builder on cygwin/64
On 2015-03-15 22:19, Chris Johns wrote: [ back on list ] I wasn't sure, people like to read this long log files ;-) Thanks. Can you please try the attached windows.py ? Sure. It seems to work. Is plowing through the sources for hours now ... Will report, if it really works later ... RTEMS Source Builder - Set Builder, v0.5.0 Build Set: 4.11/rtems-arm Build Set: 4.11/rtems-autotools.bset Build Set: 4.11/rtems-autotools-internal.bset config: tools/rtems-autoconf-2.69-1.cfg package: autoconf-2.69-x86_64-pc-cygwin-1 building: autoconf-2.69-x86_64-pc-cygwin-1 config: tools/rtems-automake-1.12.6-1.cfg package: automake-1.12.6-x86_64-pc-cygwin-1 building: automake-1.12.6-x86_64-pc-cygwin-1 cleaning: autoconf-2.69-x86_64-pc-cygwin-1 cleaning: automake-1.12.6-x86_64-pc-cygwin-1 Build Set: Time 0:01:01.136507 Build Set: 4.11/rtems-autotools-base.bset config: tools/rtems-autoconf-2.69-1.cfg package: autoconf-2.69-x86_64-pc-cygwin-1 building: autoconf-2.69-x86_64-pc-cygwin-1 config: tools/rtems-automake-1.12.6-1.cfg package: automake-1.12.6-x86_64-pc-cygwin-1 building: automake-1.12.6-x86_64-pc-cygwin-1 installing: autoconf-2.69-x86_64-pc-cygwin-1 - /opt/rtems-4.11 installing: automake-1.12.6-x86_64-pc-cygwin-1 - /opt/rtems-4.11 cleaning: autoconf-2.69-x86_64-pc-cygwin-1 cleaning: automake-1.12.6-x86_64-pc-cygwin-1 Build Set: Time 0:01:00.793307 Build Set: Time 0:02:01.929814 config: tools/rtems-binutils-2.24-1.cfg package: arm-rtems4.11-binutils-2.24-x86_64-pc-cygwin-1 building: arm-rtems4.11-binutils-2.24-x86_64-pc-cygwin-1 config: tools/rtems-gcc-4.9.2-newlib-git-1.cfg package: arm-rtems4.11-gcc-4.9.2-newlib-b75c57950318ed657807f87a4c694e7b8d68fcae-x86_64-pc-cygwin-1 git: fetch: git://sourceware.org/git/newlib.git - sources/git/newlib.git git: reset: git://sourceware.org/git/newlib.git git: checkout: git://sourceware.org/git/newlib.git = master git: checkout: git://sourceware.org/git/newlib.git = b75c57950318ed657807f87a4c694e7b8d68fcae building: arm-rtems4.11-gcc-4.9.2-newlib-b75c57950318ed657807f87a4c694e7b8d68fcae-x86_64-pc-cygwin-1 ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: rtems-source-builder on cygwin/64
On 2015-03-14 00:59, Chris Johns wrote: On 13/03/2015 7:37 pm, emanuel stiebler wrote: On 2015-03-13 05:55, Chris Johns wrote: Have a look in this line ... https://git.rtems.org/rtems-source-builder/tree/source-builder/sb/windows.py#n56 .. and remove line 57 and make line 58 'host_triple = build_triple' so the host and build names are the same by default. If this works you might then be able to remove line 53 and allow 32bit or 64bit. error: failed to load CYGWIN_NT-6.1 host support Build FAILED So I guess there more to copy ... I suspect an error in the editing. Any issue importing the module gives this exception. I suggest you run the Windows module directly using something like: $ python windows.py It should show the error. Hi, it was an error in some white spaces, after editing the same in again it didn't complain anymore ... But, anyway, it still thinks it is on MinGW? RTEMS Source Builder - Set Builder, v0.5.0 Build Set: 4.11/rtems-arm Build Set: 4.11/rtems-autotools.bset Build Set: 4.11/rtems-autotools-internal.bset config: tools/rtems-autoconf-2.69-1.cfg package: autoconf-2.69-x86_64-w64-mingw32-1 building: autoconf-2.69-x86_64-w64-mingw32-1 config: tools/rtems-automake-1.12.6-1.cfg package: automake-1.12.6-x86_64-w64-mingw32-1 building: automake-1.12.6-x86_64-w64-mingw32-1 cleaning: autoconf-2.69-x86_64-w64-mingw32-1 cleaning: automake-1.12.6-x86_64-w64-mingw32-1 Build Set: Time 0:00:59.248904 Build Set: 4.11/rtems-autotools-base.bset config: tools/rtems-autoconf-2.69-1.cfg package: autoconf-2.69-x86_64-w64-mingw32-1 building: autoconf-2.69-x86_64-w64-mingw32-1 config: tools/rtems-automake-1.12.6-1.cfg package: automake-1.12.6-x86_64-w64-mingw32-1 building: automake-1.12.6-x86_64-w64-mingw32-1 installing: autoconf-2.69-x86_64-w64-mingw32-1 - /opt/rtems-4.11 installing: automake-1.12.6-x86_64-w64-mingw32-1 - /opt/rtems-4.11 cleaning: autoconf-2.69-x86_64-w64-mingw32-1 cleaning: automake-1.12.6-x86_64-w64-mingw32-1 Build Set: Time 0:01:00.049505 Build Set: Time 0:01:59.298409 config: tools/rtems-binutils-2.24-1.cfg package: arm-rtems4.11-binutils-2.24-x86_64-w64-mingw32-1 download: ftp://ftp.gnu.org/gnu/binutils/binutils-2.24.tar.bz2 - sources/binutils-2.24.tar.bz2 downloading: sources/binutils-2.24.tar.bz2 - 21.7MB of 21.7MB (100%) building: arm-rtems4.11-binutils-2.24-x86_64-w64-mingw32-1 error: building arm-rtems4.11-binutils-2.24-x86_64-w64-mingw32-1 Build FAILED See error report: rsb-report-arm-rtems4.11-binutils-2.24-x86_64-w64-mingw32-1.txt error: building arm-rtems4.11-binutils-2.24-x86_64-w64-mingw32-1 Build Set: Time 0:06:50.131120 Build FAILED And the failure is in binutils, because it doesn't know: gcc -O2 -pipe -I/cygdrive/d/_home/emu/RTEMS.Work/rtems-source-builder/rtems/build/tmp/sb-emu/4.11/rtems-arm/opt/rtems-4.11/include -c -DHAVE_CONFIG_H -g -O2 -D__USE_MINGW_ACCESS -I. -I../../binutils-2.24/libiberty/../include -W -Wall -Wwrite-strings -Wc++-compat -Wstrict-prototypes -pedantic ../../binutils-2.24/libiberty/pex-win32.c -o pex-win32.o ../../binutils-2.24/libiberty/pex-win32.c: In function 'pex_win32_open_read': ../../binutils-2.24/libiberty/pex-win32.c:122:3: warning: implicit declaration of function '_open' [-Wimplicit-function-declaration] return _open (name, _O_RDONLY | (binary ? _O_BINARY : _O_TEXT)); ^ ../../binutils-2.24/libiberty/pex-win32.c:122:23: error: '_O_RDONLY' undeclared (first use in this function) return _open (name, _O_RDONLY | (binary ? _O_BINARY : _O_TEXT)); ^ ../../binutils-2.24/libiberty/pex-win32.c:122:23: note: each undeclared identifier is reported only once for each function it appears in ../../binutils-2.24/libiberty/pex-win32.c:122:45: error: '_O_BINARY' undeclared (first use in this function) return _open (name, _O_RDONLY | (binary ? _O_BINARY : _O_TEXT)); So, probably still some mixup with the environment ... Thanks for you help!!! ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: rtems-source-builder on cygwin/64
On 2015-03-13 05:55, Chris Johns wrote: Have a look in this line ... https://git.rtems.org/rtems-source-builder/tree/source-builder/sb/windows.py#n56 .. and remove line 57 and make line 58 'host_triple = build_triple' so the host and build names are the same by default. If this works you might then be able to remove line 53 and allow 32bit or 64bit. error: failed to load CYGWIN_NT-6.1 host support Build FAILED So I guess there more to copy ... ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
rtems-source-builder on cygwin/64
Hi all, should it work at the moment? All the best, emanuel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: rtems-source-builder on cygwin/64
On 2015-03-11 18:40, Joel Sherrill wrote: On 3/11/2015 12:12 PM, emanuel stiebler wrote: Hi all, should it work at the moment? Since Chris is likely the best one to answer that and he won't be online for at least a a few hours, give it a try. You will know the answer before he wakes up. :) I'm on cygwin, and it sits after just few hundred lines in /bin/sh ./libtool --silent --mode=link gcc -O2 -pipe -I/cygdrive/d/_home/emu/RTEMS.Work/rtems-source-builder/rtems/build/tmp/sb-emu/4.10/rtems-arm/opt/rtems-4.11/include -std=gnu99 -I./lib -I. -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H -no-undefined -version-info 7:0:6 -rpath /opt/rtems-4.11/lib -L/cygdrive/d/_home/emu/RTEMS.Work/rtems-source-builder/rtems/build/tmp/sb-emu/4.10/rtems-arm/opt/rtems-4.11/lib -o libexpat.la lib/xmlparse.lo lib/xmltok.lo lib/xmlrole.lo and cpu usage goes back to 0% ... ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: Zynq BSP
On 2014-07-24 03:06, Chris Johns wrote: On 22/07/2014 1:00 am, emanuel stiebler wrote: On 2014-07-18 18:54, Chris Johns wrote: We still use the U-Boot to load it? I do not use uboot, rather we have a taken the Xilinx FSBL and reworked it. Could you at least share this part? And thanks for this already, I thought that I had to use u-boot. (which I don't mind, it just one more layer of work ;-) ) The code is based on Xilinx's FSBL and so I need to sort the licensing out before I can make it public. OK. I would like to do a write up of the whole process but it is not a priority for my unfunded work. :( Do not be too unhappy, dealing with the licenses is taking my time and that is a good thing. Hello Chris, thanks for letting us know. I'm glad somebody is working on the license issues. Thanks again ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: Tool chain for RTEMS 4.11
On 2013-07-16 09:34, Rempel, Cynthia wrote: Moving forward we should keep patches separated in such a way as they are easier to upstream, this will require an update to the http://www.rtems.org/wiki/index.php/Building_Tools tutorial, but hopefully, updating the tutorial won't be too difficult. Why not just automatically update the RTEMS-Source-Builder? Just one tool to update, and people wouldn't even notice new updates. ___ rtems-devel mailing list rtems-devel@rtems.org http://www.rtems.org/mailman/listinfo/rtems-devel
Re: BSP lm3s6965 broken
On 2013-07-15 02:36, Sebastian Huber wrote: I don't get a build error. What is the error in your case? gmake[2]: *** No rule to make target `all'. Stop. And it stops, not building anything ... ___ rtems-devel mailing list rtems-devel@rtems.org http://www.rtems.org/mailman/listinfo/rtems-devel
Re: BSP lm3s6965 broken
On 2013-07-15 09:56, Joel Sherrill wrote: On 7/15/2013 10:45 AM, emanuel stiebler wrote: On 2013-07-15 02:36, Sebastian Huber wrote: I don't get a build error. What is the error in your case? gmake[2]: *** No rule to make target `all'. Stop. And it stops, not building anything ... I just built it. ../rtems/configure --target=arm-rtems4.11 --enable-rtemsbsp=lm3s6965 \ --disable-posix \ --enable-networking \ --prefix=/home/rtems/rtems-4.11-work/bsp-install \ --enable-tests=samples c.log 21 \ make b.log 21 Was there something in the configure output that wasn't right? No, I don't remember seeing any warnings. But after deleting my whole tree, and cloning again a fresh copy it works again. BTW, yesterday after a compile, the hello.exe and hello.ralf were the same file. Today with the fresh clone, it is correctly made into a binary version of .exe ... Cheers Thanks ___ rtems-devel mailing list rtems-devel@rtems.org http://www.rtems.org/mailman/listinfo/rtems-devel
BSP lm3s6965 broken
Making all in lm3s6965 gmake[2]: Entering directory `/AD1/SHARED/RTEMS/BUILD/arm-rtems4.11/c/lm3s6965' gmake[2]: *** No rule to make target `all'. Stop. gmake[2]: Leaving directory `/AD1/SHARED/RTEMS/BUILD/arm-rtems4.11/c/lm3s6965' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/AD1/SHARED/RTEMS/BUILD/arm-rtems4.11/c' make: *** [all-recursive] Error 1 I think it was working days/week ago. Was this broken during the cleanup? lm3s6965_qemu and lm3s3749 are still working. Cheers ___ rtems-devel mailing list rtems-devel@rtems.org http://www.rtems.org/mailman/listinfo/rtems-devel
cygwin gcc as arm-rtems4.11-gcc and arm-rtemseabi4.11gcc
Which is the correct to use on cygwin? The ...eabi or the plain version? On linux, only the plain version is offered ... Thanks! ___ rtems-devel mailing list rtems-devel@rtems.org http://www.rtems.org/mailman/listinfo/rtems-devel
