Common Name (CN)
docs.rtems.org
Organisation (O)
Organisational Unit (OU)
Issued By
Common Name (CN)
R3
Organisation (O)
Let's Encrypt
Organisational Unit (OU)
Validity Period
Issued On
Friday, 12 January 2024 at 20:02:57
Expires On
Thursday, 11 April 2024 at 21:02:56
SHA-256 Fingerprints
machine which is fine. As an alternative I
> have documented using python.org:
>
> https://docs.rtems.org/branches/master/user/hosts/macos.html#python
>
> and a virtual environment.
>
> Chris
>
> On 12/3/2024 2:09 pm, Heinz Junkes wrote:
>>
>> ___
Hi
After updating Xcode and OSX to Sonoma 14.4 the Python libs 'disappeared’ ?
Upgrade/update python on homebrew and brew link python3 fixed it.
Heinz
> On 11. Mar 2024, at 16:27, Heinz Junkes wrote:
>
> Hi,
>
> I am trying to install rc2 on sonoma 14.4 (Apple M2) and unfortunatel
---
Fritz-Haber-Institut| Phone: (+49 30) 8413-4270
Heinz Junkes | Fax (G3+G4): (+49 30) 8413-5900
Faradayweg 4-6| VC: https://zoom.fhi.berlin/junkes
D - 14195 Berlin| E-Mail:jun...@fhi-berlin.mpg.de
Hi,
I tried to build rc2 on OS-X (Ventura Intel) for powerpc and I get the
following error:
RTEMS Tools Project - Source Builder Error Report
Build: error: building
powerpc-rtems6-gcc-13.2.0-newlib-3cacedb-x86_64-apple-darwin22.6.0-1
Command Line: ../source-builder/sb-set-builder
HI,
I can follow Cedric's reasoning. Even if I was the initiator of this discussion.
I use RTEMS in my lectures/exercises, among other things, and have always been
able to give the students
freedom which laptops with which OS they wanted to use. And there are many of
them with used
older
Leads to problems compiling legacy-stack:
Waf: Entering directory
`/home/rtems/MVME6100_6_legacy_INST/rsb/rtems/build/rtems-net-legacy-3a83bcef4bd62fda5c0f9c94dd649fc32d962ab2-powerpc-rtems-1/rtems-net-legacy-3a83bcef4bd62fda5c0f9c94dd649fc32d962ab2/build/powerpc-rtems6-beatnik'
[1/1] Compiling
ay more
information)
-> task in 'objs01' failed with exit status 1 (run with -v to display more
information)
-> task in 'objs01' failed with exit status 1 (run with -v to display more
information)
Heinz
> On 18. Jan 2023, at 08:03, Sebastian Huber
> wrote:
>
> On 17.01.23
t; `share/rtems6` directory.
>
> This is correct and it is a simple and fast key to see if a kernel of a
> specific
> version has been installed.
>
>> On 1/17/23 18:11, Heinz Junkes wrote:
>>> Hi,
>>>
>>> It looks like there is a typo in rtems-l
mple and fast key to see if a kernel of a
> specific
> version has been installed.
>
>> On 1/17/23 18:11, Heinz Junkes wrote:
>>> Hi,
>>>
>>> It looks like there is a typo in rtems-libbsd/rtems_waf/rtems.py.
>>>
>>> rtems_share_rtems_ve
Hi,
It looks like there is a typo in rtems-libbsd/rtems_waf/rtems.py.
rtems_share_rtems_version = os.path.join(rtems_path, 'share', 'rtems' +
rtems_version)
if not os.path.exists(os.path.join(rtems_share_rtems_version)):
ctx.fatal('RTEMS path is not valid, "%s" not found.' %
Hallo Sebastian,
maybe too late, but this is the result of RTEMS 7 rsb on my Mac:
Command Line: ../source-builder/sb-set-builder --jobs=4
--prefix=/Users/heinz/VE/ARM_WORK/rtems/7 7/rtems-arm
Python: 3.8.5 (default, Sep 4 2020, 02:22:02) [Clang 10.0.0 ]
Hallo,
with the new network stack, rtems_rpc_task_init no longer exists.
What must/could be called/initialized instead?
Danke, Heinz
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
Hello Sebastian,
unfortunately I could not build rtems7 on the Mac (as I can for rtems6):
Cloning into 'rsb'...
RTEMS Source Builder - Set Builder, 6 (376bf3247498)
Build Set: 7/rtems-arm
config: devel/dtc-1.6.1-1.cfg
package: dtc-1.6.1-x86_64-apple-darwin21.4.0-1
Creating source directory:
-apple-darwin21.4.0-1
See error report: rsb-report-gettext-0.18.3.1-x86_64-apple-darwin21.4.0-1.txt
Build Set: Time 0:04:14.522148
Gruss Heinz
--
Fritz-Haber-Institut| Phone: (+49 30) 8413-4270
Heinz Junkes
t.
Danke, Heinz
> On 22. Mar 2022, at 21:30, Sebastian Huber
> wrote:
>
> Hello Heinz,
>
> On 19/03/2022 16:54, Heinz Junkes wrote:
>> Waf: Leaving directory
>> `/home/rtems/ARM_TST/kernel/build/arm/xilinx_zynq_a9_qemu'
>> Build failed
>> -> ta
Waf: Leaving directory
`/home/rtems/ARM_TST/kernel/build/arm/xilinx_zynq_a9_qemu'
Build failed
-> task in 'testsuites/fstests/fsdosfsname01.exe' failed with exit status 1
(run with -v to display more information)
[1714/4241] Linking
In the case of the option "nfsv4,minorversion=1" I get an
error 2 (No such file or directory) from
error = kernel_mount(args->ma, MNT_VERIFIED);
in file ./rtemsbsd/fs/nfsclient/nfs.c
Viele Grüße
Heinz Junkes
--
Experience directly varies with equipment ruined.
>
1.14.131.192:/Volumes/Epics on /Volumes/Epics
Viele Grüße
Heinz Junkes
--
Experience directly varies with equipment ruined.
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
Only the comment end ( */ ) is missing
in bsps/include/libchip/disp_hcms29xx.h
at line 14.
Viele Grüße
Heinz Junkes
--
Experience directly varies with equipment ruined.
> On 10. Mar 2022, at 14:39, Heinz Junkes wrote:
>
> I get this at the moment when compiling the kernel:
>
&
nitialization for 'disp_hcms29xx_drv_tbl')
../../../bsps/shared/dev/display/disp_hcms29xx.c:913:3: warning: excess
elements in struct initializer
913 | { /* our private fields */
| ^
../../../bsps/shared/dev/display/disp_hcms29xx.c:913:3: note: (near
initial
Thanks for that. I've been struggling with this for a while ;-)
But there is this comment in the file:
“
#
# BSP specific settings. To be included in application Makefiles
#
# This support will be removed from RTEMS. Please consider other
# ways to build applications.
#
“
I thought this was no
> On 18. Feb 2022, at 17:47, Joel Sherrill wrote:
>
>
> "Normally" the driver initialization entry registers names.
Unfortunately, I cannot confirm that. I don't see any registrations
(rtems_io_register_driver()) of the drivers.
Only rtems_io_initialize() major 0 - > (in my case) 39 is
-
Fritz-Haber-Institut| Phone: (+49 30) 8413-4270
Heinz Junkes | Fax (G3+G4): (+49 30) 8413-5900
Faradayweg 4-6| VC: 102220181...@bjn.vc
D - 14195
IDDLE
);
Heinz
> On 7. Feb 2022, at 14:42, Heinz Junkes wrote:
>
> in bsps/powerpc/mvme3100/start/bspstart.c I can find
>
> RTEMS_SYSINIT_ITEM{
> mvme3100_i2c_initialize,
> RTEMS_SYSINIT_BSP_PRE_DRIVERS,
> RTEMS_SYSINIT_ORDER_MIDDLE
> );
>
> mvme3100_i2c_i
in bsps/powerpc/mvme3100/start/bspstart.c I can find
RTEMS_SYSINIT_ITEM{
mvme3100_i2c_initialize,
RTEMS_SYSINIT_BSP_PRE_DRIVERS,
RTEMS_SYSINIT_ORDER_MIDDLE
);
mvme3100_i2c_initialize calls BSP_i2c_initialize
This can be found in bsps/powerpc/mvme3100/i2c/i2c_init.c
This function calls
Huber
> wrote:
>
> Hello Heinz,
>
> On 03/02/2022 06:57, Heinz Junkes wrote:
>> I think I slept through the latest development. Sorry about that.
>> I wanted to integrate a pull request from Till
>> (https://github.com/RTEMS/rtems/pull/41)
>> into rtems6.
system and until then the
command in rtems.git should be used.
Unfortunately, I'm not getting anywhere with it.
How must/should I proceed?
Danke, Heinz
--
Fritz-Haber-Institut| Phone: (+49 30) 8413-4270
Heinz
on
their private devices. And now you can find on the Internet unfortunately
many (partly old) how to install RTEMS and I have tried to understand the
problems the students have.
Viele Grüße
Heinz Junkes
--
Experience directly varies with equipment ruined.
> On 21. Jun 2021, at 22:18, Joel Sherr
Is there an equivalent to _edata (I still use it for beatnik)?
Danke Heinz
smime.p7s
Description: S/MIME cryptographic signature
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
I have installed the legacy package but the files are not there.
I guess they were just forgotten in the legacy package.
Heinz
> On 4. Mar 2021, at 14:52, Joel Sherrill wrote:
>
> Did you install the legacy package? If you installed it in the same place
> as the RTEMS 5 BSP, I would expect it
Hallo Vijay,
I still have to ask a question ;-)
When building EPICS, we distinguish legacy stack or libbsd with the help of
the target.cfg file. (e.g. powerpc-rtems6/beatnik/make/target.cfg).
Earlier in it was
RTEMS_HAS_NETWORKING = yes (for legacy stack) and no (for new bsd stack).
Now this
the prio 98 or so?
Heinz
> On 23. Feb 2021, at 15:17, Joel Sherrill wrote:
>
>
>
> On Tue, Feb 23, 2021 at 4:25 AM Heinz Junkes wrote:
> what I have just never understood
>
> POSIX Prio 2 ist LOW Priority
> RTEMS Prio 1 is HIGH Priority
>
> In general, RT
what I have just never understood
POSIX Prio 2 ist LOW Priority
RTEMS Prio 1 is HIGH Priority
Heinz
> On 23. Feb 2021, at 09:17, Sebastian Huber
> wrote:
>
> On 23/02/2021 08:36, Heinz Junkes wrote:
>
>> I would have a similar question ;-)
>>
>> What
I would have a similar question ;-)
What is the priority of the POSIX_Init - Task (as Posix-Prio)?
Danke Heinz
> On 23. Feb 2021, at 06:43, Richi Dubey wrote:
>
> Hi,
>
> Just confirming, The initial priority is 1, and when converted to
> _RTEMS_Priority_To_core, it becomes 2 (because of the
Hi Sebastian,
_XOPEN_SOURCE is not set anywhere in the RTEMS header files etc..
Heinz
> On 3. Jan 2021, at 11:04, Sebastian Huber
> wrote:
>
> Hello Heinz,
>
> On 01/01/2021 18:46, Heinz Junkes wrote:
>> Please excuse me if this question has already been answered. But
Please excuse me if this question has already been answered. But unfortunately
I have not been able to find a clear statement.
Why is RTEMS _XOPEN_SOURCE not set with a value when building a BSP with
--enable-posix?
in the rtems-libbsd you can find a definition in some places.
z.B. in
available in freebsd. Probably too rare or I did not search properly.
Viele Grüße
Heinz Junkes
--
Experience directly varies with equipment ruined.
> On 27. Oct 2020, at 05:06, Chris Johns wrote:
>
> On 26/10/20 7:32 pm, Heinz Junkes wrote:
>> Good morning Chris,
>> i will n
boards with the
Qoriq CPU in the pipeline.
For example IFC_1420 from IOxOS
(https://www.ioxos.ch/wp-content/uploads/2018/02/IFC_1420_SDS_A0.pdf). This
is a CPU for MTCA.4 which is used in modern accelerator systems.
Viele Grüße
Heinz Junkes
--
Experience directly varies with equipment ruined
carrier
info: tsec1: waiting for carrier
info: tsec2: waiting for carrier
W���to UP
info: tsec0: carrier acquired
info: DUID 00:01:00:01:e9:6d:a1:84:ec:9e:cd:19:3c:61
info: tsec0: IAID cd:19:3c:61
info: tsec1: link state changed to UP
...
Viele Grüße
Heinz Junkes
--
Experience directly varies wi
us0:
[zone: unpcb] kern.ipc.maxsockets limit reached
info: lo0: link state changed to UP
info: version 6.2.1 starting
err: no valid interfaces found
warning: no interfaces have a carrier
Viele Grüße
Heinz Junkes
--
Experience directly varies with equipment ruined.
> On 27. Oct 2020, at 18:41, Seb
Printing a stack trace for your convenience :-)
0x04158380--> 0x04158380--> 0x00547920--> 0x00548556--> 0x04170612
0x04140740--> 0x00560140--> 0x00559908--> 0x04132912--> 0x00012556
Viele Grüße
Heinz Junkes
--
Experience directly varies with equipment ruined.
> On 27. Oc
ild/rtems-libbsd-d964a6703c705cc92fd053bcefc08bb3b6baa0e2-powerpc-rtems6-1/do-build
error: building
rtems-libbsd-d964a6703c705cc92fd053bcefc08bb3b6baa0e2-powerpc-rtems6-1
Viele Grüße
Heinz Junkes
--
Experience directly varies with equipment ruined.
> On 27. Oct 2020, at 05:06, Chris Johns
Good morning Chris,
i will now try out libbsd on a MVME6100 (beatnik).
Is the mentioned patch in git? Or do I have to prepare something special?
Thanks Heinz
> On 21. Oct 2020, at 02:44, Chris Johns wrote:
>
> On 21/10/20 2:52 am, Sebastian Huber wrote:
>> On 20/10/2020 03:52, chr...@rtems.org
We are using BlueJeans Events for our workshop/meeting.
FHI, Heinz Junkes
> On 4. Oct 2020, at 21:15, Joel Sherrill wrote:
>
>
>
>
>> On Sun, Oct 4, 2020, 12:49 PM Heinz Junkes wrote:
>> Hello, Joel,
>> I am currently organizing a virtual meeting
Hello, Joel,
I am currently organizing a virtual meeting for the EPICS community:
https://indico.fhi-berlin.mpg.de/e/epics2020
This takes place in 2 weeks. If this works well, I would be happy to offer our
platform (and our experience) for an RTEMS workshop.
But the contributions would have to
Here is a mail I received from a colleague.
It concerns thereby an "old" problem which seemed already solved?
FYI. I can run the unit tests, but I'm seeing a couple of hangs.
The first I'm looking at is epicsTimeTest which seems to be
related to c++ exception handling. I recall that there were
Dear Mritunjay,
> On 26. Aug 2020, at 23:34, Mritunjay Sharma
> wrote:
>
> > +Name: epics-base-%{epics_version}-%{_host}-%{release}
> > +Summary: EPICS v%{epics_version} for target %{_target} on host %{_host}
> > +Version: %{epics_version}
> > +Release: %{release}
> > +URL:
Hallo Chris,
yes it works as described. The header file (librtemsNfs.h) is also there.
I must have done something wrong the day before yesterday. Unfortunately
I can't reproduce it anymore. Sorry for the "false alarm”.
I no longer use librtemNfs.h when using the libbsd stack.
It is no longer
”
This header file is in rtems-libbsd which I then had to reinstall and build for
the target.
Then I thought about whether a recipe could/should consider this dependency.
Viele Grüße
Heinz Junkes
--
Experience directly varies with equipment ruined.
> On 24. Aug 2020, at 01:59, Chris Johns wr
Hallo Mritunjay,
that sounds good. But shouldn't the dependencies for the RTEMS basic
installation
be taken into account. Maybe I don't understand the purpose of the
source-builder.
But I thought that the necessary rtems-modules (compiler for architecture,
libbsd, etc.) are checked
and if
= $(RTEMS_TOOLS)/bin/$(CC_FOR_TARGET) -x c -E
AR = $(RTEMS_TOOLS)/bin/$(AR_FOR_TARGET)
LD = $(RTEMS_TOOLS)/bin/$(LD_FOR_TARGET) -r
…
The assumption was that Makefile.inc is present in every BSP.
If it cannot be found in the pc-386 BSP, should the BSP be adapted?
Viele Grüße
Heinz Junkes
Hi Mritunjay,
To define the architecture you can create a file “CONFIG_SITE.local” in
“configure”.
Look at the comment at the end of the file "CONFIG_SITE":
"
...
# Overrides for the settings above may appear in a CONFIG_SITE.local file
-include $(CONFIG)/CONFIG_SITE.local.
“
Heinz
> On 16.
I think you should not make a patch for these two changes but a
simple replacement with e.g. sed.
like
sed -i ’s/^RTEMS_BASE/RTEMS_BASE =
\/home\/mritunjay\/development\/rtems/\$\(RTEMS_VERSION\)-arm\/g’
configure/os/CONFIG_SITE.Common.RTEMS
oder so ;-)
Viele Grüße
Heinz Junkes
Hello, Chris,
with libbsd I also realized this with the concept you suggested (still beta
development):
...
sc = rtems_bsd_initialize();
assert(sc == RTEMS_SUCCESSFUL);
/* Let the callout timer allocate its resources */
sc = rtems_task_wake_after(2);
assert(sc ==
Hallo Mritunjay,
everything looks pretty good. I'm commenting on the text. I also send this mail
to two EPICS experts (Andrew Johnson and Michael Davidsaver). Maybe they also
have some ideas.
>
> Current Status:
>
> 1) Successfully built EPICS7 with RTEMS5 by hand for pc-386
> 2) Worked for
)
rtems_bsd_ifconfig_lo0();
/* lookup primary network interface */
char ifnamebuf[IF_NAMESIZE];
char *prim_ifname;
prim_ifname = if_indextoname(1, [0]);
assert(prim_ifname != NULL);
…
Heinz
> On 8. Aug 2020, at 03:50, Chris Johns wrote:
>
> On 8/8/20 5:12 am, Heinz Junkes wrote:
>&g
020, at 14:17, Sebastian Huber
> wrote:
>
> On 07/08/2020 13:39, Heinz Junkes wrote:
>
>> Can I get the name of the primary network interface from the header files of
>> a target-bsp?
>
> Some BSPs have an RTEMS_BSP_NETWORK_DRIVER_NAME define.
>
>
Can I get the name of the primary network interface from the header files of a
target-bsp?
Danke
Heinz
smime.p7s
Description: S/MIME cryptographic signature
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
Because the libbsd stack does not support some things yet (e.g. ntp) I have to
call different
functions at rtems_init in EPICS. Therefore, when building EPICS for a target,
I need
to know which stack the target was built with.
Viele Grüße
Heinz Junkes
--
Experience directly varies
I'm trying to figure out when compiling a third party software (EPICS),
whether the RTEMS for a target bsp was created with the legacy stack or
uses the libbsd stack.
Unfortunately I have found some different definitions:
in target.cfg : RTEMS_HAS_NETWORKING
in bsp.cfg : HAS_NETWORKING
in
I will be back online next weekend. Just a short note:
Mritunjay, please have a look on github epics-base in the directory ci-scripts
Here you should find automated tests etc. used by the epics development team.
Heinz
> On 30.07.2020, at 01:33, Chris Johns wrote:
>
>> On 30/7/20 9:11 am,
It uses the legacy-stack.
When I am back I will adapt rtems_init to use libbsd.
You should proceed to write rsb recipes.
Heinz
FHI, Heinz Junkes
> On 19. Jul 2020, at 16:03, Mritunjay Sharma
> wrote:
>
>
>
>
>> On Sun, Jul 19, 2020 at 4:28 AM Gedare Bloom wrote:
Mritunjay,
can you try to use the commit 3afec267ab08568ea454789e562450b00feea5c0
Dated 25.9. 2019
From Heinz
> On 17.07.2020, at 20:23, Mritunjay Sharma
> wrote:
>
>
>
>> On Fri, Jul 17, 2020 at 12:53 PM Heinz Junkes
>> wrote:
>> You are right. I was n
a mess of things here.
In the "official" epics repo, you can read
https://github.com/epics-base/epics-base/blob/7.0/modules/libcom/RTEMS/rtems_init.c
:
…
#include
#include
#include
#include
#include
…
Here the definition of the legacy stack will be included
#include
Viele G
It's not my experience.
I made my first attempts with RTEMS5 for a beatnik-board (MVME6100).
For this I created the BSP like this:
cd build/b-beatnik
../../rtems/configure --enable-maintainer-mode --prefix=$HOME/RTEMS/rtems-5
--target=powerpc-rtems5 --enable-rtemsbsp="beatnik"
Sorry for the long delay.
Yes, this Epics version still uses the rtems-libbsd.
The bsp must be built with --enable-network.
I'm trying to create an Epics version over the weekend that recognizes from
the configuration which libbsd version should be used.
Viele Grüße
Heinz Junkes
I’m away from my keyboard. If you use the epics Adaption to rtems from my
github “playground?” and bsp’s with —enable-networks should compile.
Heinz
FHI, Heinz Junkes
> On 7. Jul 2020, at 18:14, Mritunjay Sharma
> wrote:
>
>
> [UPDATE]: I tried building EPICS with RTEMS5 fo
Thank you, this is exactly where I was unsure.
@Chris: Can you give a recommendation here?
Danke Heinz
--
Fritz-Haber-Institut| Phone: (+49 30) 8413-4270
Heinz Junkes | Fax (G3+G4): (+49 30) 8413
Hello, Mritunjay,
that's good news. Don't you want to try to develop a rsb-set for exactly this
combination of RTEMS4.10 and EPICS7?
Then it should be no problem to do it with RTEMS5 in the same way.
Did you also run the tests on Epics and also tried the pc386-qemu?
Greetings Heinz
> On 3. Jul
gt; > resolved.
> >> > I have attached the config log as well.
> >> >
> >> > Thanks
> >> > Mritunjay
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > On Wed, Jul 1, 2020 at 12:27 AM Mritunjay Sh
I forgot to send it to rtems-devel...
> Begin forwarded message:
>
> From: junkes
> Subject: Re: Release snapshot 5.0.0-m2006-2 available
> Date: 21. June 2020 at 13:53:35 CEST
> To: Chris Johns
>
> Hello Chris,
> thanks for the release snapshot. It all looks very good already.
> I have
I can agree with Cedric.
I use rtems5 with rtems-libbsd. I initialize the network interfaces of my
target via dhcpcd
and the interfaces are automatically multicast capable.
This works without creating a route:
if (setsockopt(conf->udp, IPPROTO_IP, IP_ADD_MEMBERSHIP,
If you want to get ahead, just make a version that already has a configure, then
you can save yourself the trouble with autoconf. I'd put that in the back.
Heinz
> On 15. Jun 2020, at 20:46, Mritunjay Sharma
> wrote:
>
> Hello everyone,
>
> The latest update is that by changing a couple of
I can't find configure in the zip-file (master.zip) which you are loading..
ptpd-master still needs to be reconfigured (autoreconf -vi)
This reconfigure is missing in the cfg file.
It only works the second time and therefore cannot really be used at the
moment.
Unfortunately I don't know why it
Thanks for the good ideas.
I have now replaced the accesses to the internal thread structure
(real_priority, current_priority) with API - calls.
One of the calls is from the pthread-library and therefore needs --enable-posix
when creating the BSP.
Calls used
pthread_getschedparam
The Priority_node structure was committed to the 4.10 branch of RTEMS in
December
2017 (78b867e26d score: replace current and real priority with priority node).
Do I have a possibility to know at compile time (in our case EPICS) if it is
present or not.
Background:
We had received the
> On 18. Mar 2020, at 22:17, Joel Sherrill wrote:
>
> We have had good experiences with RTEMS+libbsd with the Qemu ARM Zynq.
> We have been able to telnet to the RTEMS target from Linux and use the RTEMS
> NFS client to mount Linux files plus dynamic loading works. Personally I
> would
>
it is anymore.
More tomorrow.
Many greetings and stay healthy,
Heinz
--
Fritz-Haber-Institut| Phone: (+49 30) 8413-4270
Heinz Junkes | Fax (G3+G4): (+49 30) 8413-5900
Faradayweg 4-6| VC
79 matches
Mail list logo
