On 2/14/24 10:22, Miroslaw Dach wrote:
Does anybody have any advice?
Hi Mirek,
Have you tried with a CLI TFTP client?
Since TFTP is generally seen as wildly insecure
these days, default distro. installs of TFTPd
tend to be restrictive.
cf. "man tftpd" and compare with your running
daemon.
h
On 10/17/22 22:50, Chris Johns wrote:
On 18/10/2022 4:42 pm, Sebastian Huber wrote:
On 18/10/2022 06:15, Chris Johns wrote:
On 18/10/2022 2:22 pm, Michael Davidsaver wrote:
On 10/17/22 16:20, Chris Johns wrote:
2. Look at kqueue, it is a better interface for this type of blocking
Maybe not
On 10/17/22 16:20, Chris Johns wrote:
2. Look at kqueue, it is a better interface for this type of blocking
Maybe not relevant in Miroslaw's application, but I've found
that the RTEMS kqueue implementation doesn't notify when a
TCP connection is closed by reset. I think this is a lack
of NOTE_
On 7/19/21 6:17 AM, andre.nahrw...@dlr.de wrote:
> Hello,
>
> I have built RTEMS 5 and its tools for the Xilinx Zynq Zedboard and installed
> the BSP and tools at a certain position on my machine.
> The tools are added to the PATH variable and RTEMS_BSPS is also available in
> the environment.
>
In winding my way through various checks and test of RTEMS 5, I tried linking
some of my executables with '-Wl,--orphan-handling=error'. I've been bitten
in the past by the (imo. unfortunate) default behavior in combination with
an incomplete linker script, so this is on my list of things to try.
On 4/26/21 1:21 AM, Goetz Pfeiffer wrote:
> Hello,
>
> I have used rsb to build my local cross compiler toolchain for RTEMS.
>
> This is a great tool, but it downloads all sources from some internet
> servers. The problem is
> that servers may be down at the time I need them or that the location
fyi. To support EPICS development/maintenance I've been providing pre-built
binaries of the RTEMS toolchain and kernel for use in our continuous
integration builds. Originally travis-ci.org, and more recently, github
actions.
https://github.com/mdavidsaver/rsb/releases
I mention this now as I'v
On 3/10/21 3:30 PM, Chris Johns wrote:
> The patch link looks fine and I can download it with my browser. I wonder if
> this is a Windows thing?
No Windows involved. I'm running this under Debian 10.
___
users mailing list
users@rtems.org
http://lists.r
On 3/10/21 10:55 AM, Chris Johns wrote:
> ...
> Also have a look at the command sb-get-sources. It will fetch the source and
> patches for all hosts and architectures.
Neat. I've been wishing for something like this as I'd like to archive full
source along with toolchain builds. Would it handle
On 2/17/21 7:34 AM, Joel Sherrill wrote:
> And indeed adding -std=c++98 seems to be a workaround.
>
>
> EPICS most likely should use a newer C++ standard than that. C++03 is
> C++98 with corrections. But it does not have long long because C++98
> definition predated C99 finalization and C99
FYI. Excluding the c++ part shows that acoshl() and friends are never defined.
> $ cat mtest.c
> #include
>
> long double x(long double a) { return acoshl(a); }
From the newlib math.h:
> /* Newlib doesn't fully support long double math functions so far.
>On platforms where long double eq
On 8/30/20 7:07 PM, Chris Johns wrote:
> On 30/8/20 2:17 am, Michael Davidsaver wrote:
>> On 8/27/20 5:31 PM, Chris Johns wrote:
>>> On 28/8/20 5:39 am, Michael Davidsaver wrote:
>>>> Is there a way to ask RSB to either build the toolchain
>>>> (ie. gcc
On 8/27/20 5:31 PM, Chris Johns wrote:
> On 28/8/20 5:39 am, Michael Davidsaver wrote:
>> Is there a way to ask RSB to either build the toolchain
>> (ie. gcc itself) without debug symbols, or to strip them
>> prior to install?
>
> Not at the moment but this would be a
Is there a way to ask RSB to either build the toolchain
(ie. gcc itself) without debug symbols, or to strip them
prior to install?
https://github.com/mdavidsaver/rsb/releases/
I keep a set of pre-built RTEMS pc*86 toolchains for use
by CI builders, principally travis-ci.org. In looking
at adding
On 8/14/20 2:19 PM, Chris Johns wrote:
> Hello,
>
> RTEMS 5.1 RC2 is available for testing. You can find the release at:
>
> https://ftp.rtems.org/pub/rtems/releases/5/rc/5.1-rc2
>
> Please report your successes or problems here.
> You can also raise a ticket if you prefer. Please select the 5
On 6/25/20 11:17 PM, Chris Johns wrote:
> Hello,
>
> RTEMS 5 RC1 is available for testing. You can find the release at:
>
> https://ftp.rtems.org/pub/rtems/releases/5/rc/5.1.0-rc1
>
> Please report your successes or problems here. You can also raise a ticket if
> you prefer. Please select the
On 5/24/20 4:32 PM, Chris Johns wrote:
>> Which raises the question of how to build the examples?
>
> Which examples? The ones in RTEMS or the rtems-exmaples.git repo?
https://ftp.rtems.org/pub/rtems/releases/5/5.0.0/5.0.0-m2005-2/sources/rtems-examples-5.0.0-m2005-2.tar.xz
__
On 5/8/20 1:11 AM, Chris Johns wrote:
> Hello,
>
> I have uploaded release snapshot 5.0.0-m2005-2. The path is:
>
> https://ftp.rtems.org/pub/rtems/releases/5/5.0.0/5.0.0-m2005-2/
The "sources" link is broken.
https://ftp.rtems.org/pub/rtems/releases/5/5.0.0/5.0.0-m2005-2/souces
> I hope this
On 3/5/20 9:40 PM, Chris Johns wrote:
>> How would you go about building a toolchain for pc686 with the legacy stack
>> using RSB?
>
> This is a good question as it is missing from the documentation.
>
> A quick command list is:
>
> $ ../source-builder/sb-set-builder \
> --prefix=/opt/rtems/
On 3/4/20 11:08 PM, Chris Johns wrote:
> On 2020-03-05 15:35, Michael Davidsaver wrote:
>> On 3/4/20 12:50 AM, Chris Johns wrote:
>>> However libbsd for the PC will not build for the PC. The release is using
>>> the
>>> 5-freebsd-12 branch of libbsd and thi
On 3/4/20 12:50 AM, Chris Johns wrote:
> However libbsd for the PC will not build for the PC. The release is using the
> 5-freebsd-12 branch of libbsd and this branch does not had the PC patches that
> master has and we cannot back port those patches because master and
> 5-freebsd-12
> use differe
On 3/3/20 1:29 AM, chr...@rtems.org wrote:
> RTEMS Release Build - 5.0.0-m2003
>
> RTEMS 5 Release snapshot m2003 is avaliable for testing.
> It can be found at:
>
> https://ftp.rtems.org/pub/rtems/releases/5/5.0.0/5.0.0-m2003
>
> Please test and report any issues to the u...@rtems.org or de...
On 2/12/20 7:58 PM, Chris Johns wrote:
> It should have worked. I have built the 5/bsps/beagleboneblack build set and
> it
> worked up building libbsd where I have a packaging issue to sort out, so I am
> interested in why you are seeing an error.
Taking this as a starting point, I create config/
This snapshot builds successfully for me on Debian 10 (amd64).
> ../source-builder/sb-set-builder --prefix /home/mdavidsaver/source/rtems/usr
> --rtems-bsp i386/pc386 5/rtems-i386
I did expect that these arguments would also build the RTEMS kernel, but this
seem
not to be case. I also tried (b
On 12/16/19 10:31 PM, Sebastian Huber wrote:
>
> Which packages did you install?
The entry point is "llvm-dev".
> aptitude search llvm|grep ^i
> i A libllvm6.0 - Modular compiler and toolchain technologies, runtime library
> i A libllvm7 - Modular compiler and toolchain technologies, runtime lib
On 12/4/19 8:58 PM, chr...@rtems.org wrote:
> RTEMS Release Build - 5.0.0-m1912
>
> RTEMS 5 Release snapshot m1912 is avaliable for testing.
> It can be found at:
>
> https://ftp.rtems.org/pub/rtems/releases/5/5.0.0/5.0.0-m1912
>
> Please test and report any issues to the u...@rtems.org or de..
On 7/15/19 10:47 AM, Gedare Bloom wrote:
> ...
> If you can file a ticket https://devel.rtems.org/wiki/NewTicket to add
> the -mstrict-align, and even better submit a patch (best: tested!) we
> can try to get it merged in short order. If you want it in 4.10 it is
> still open, and also 4.11, but t
All,
In troubleshooting
https://github.com/epics-base/epics-base/issues/29
two questions have come up.
1. Should all PPC BSPs build with -mstrict-align?
Based on the description in the GCC documentation, I would expect
this to be needed unless the target handles alignment exceptions
to fixup
With a clean checkout of rtems-source-builder I attempted to build
"5/rtems-powerpc.bset", but was eventually greeted with:
> git: checkout: git://git.rtems.org/rtems.git => 5
> error: git command failed (/usr/bin/git): 1
With a little modification of source-builder/sb/git.py to print the _argume
ve
> shown
> thermal regulation issues.
>
> -Matt
>
> On Wed, Jun 6, 2018 at 11:10 AM, Michael Davidsaver
> mailto:mdavidsa...@ospreydcs.com>> wrote:
>
> Hi Matt,
>
> The MVME3100 is based on the MPC8540 processor. This chip doesn't have
&
On 11/08/2017 02:57 PM, Chris Johns wrote:
> On 09/11/2017 06:06, Michael Davidsaver wrote:
>> A hack to skip info creation.
>>
>> https://github.com/mdavidsaver/rsb/commit/f0bf5876ad96417db07a876845fbf833b10ced65
>
> Are you sure `MAKEINFO=true` is correct?
No. May
Hi Joachim,
A hack to skip info creation.
https://github.com/mdavidsaver/rsb/commit/f0bf5876ad96417db07a876845fbf833b10ced65
Michael
On 11/08/2017 05:38 AM, Joachim Rahn wrote:
> Hello,
>
> building rtems-4.9 using the source builder fails (I've attached the log for
> a powerpc build but ev
On 10/27/2017 02:13 PM, Joel Sherrill wrote:
>
>
> On Sun, Oct 22, 2017 at 10:17 PM, Michael Davidsaver
> mailto:mdavidsa...@gmail.com>> wrote:
>
> For awhile now I've had a side project to add emulation of the mvme3100
> board to QEMU with RTEMS
For awhile now I've had a side project to add emulation of the mvme3100
board to QEMU with RTEMS as the guest. I think I have it basically
working* and would be interesting to know if anyone else has a use for
it. One of my goals is running the EPICS unittest suite (which passes).
It might be us
34 matches
Mail list logo
