...@rtems.org
Original-Recipient: rfc822;u...@rtems.org
Action: failed
Status: 5.1.1
Remote-MTA: dns; mx.rtems.org
Diagnostic-Code: smtp; 550 5.1.1 : Recipient address rejected:
User unknown in local recipient table
From: "Heinz Junkes (FHI)"
Subject: Typo in RTEMS 6.1 'quick guide to
88977-powerp-rtems6-1
Heinz
> On 13. Jun 2024, at 04:16, Chris Johns wrote:
>
> On 13/6/2024 12:01 am, Heinz Junkes wrote:
>> Hi,
>> I'm trying to install the network stacks manually as rsb is having a problem
>> and I've encountered the following problem:
>
ok, should be
#include
Works with both stacks.
Heinz
> On 12. Jun 2024, at 22:12, Heinz Junkes wrote:
>
> Hi,
>
> junkes@Zarquon RTEMS_FOR_EPICS % git clone \
> https://gitlab.rtems.org/rtems/pkg/rtems-net-services.git
> Cloning into 'rtems-net-services'...
>
Hi,
junkes@Zarquon RTEMS_FOR_EPICS % git clone \
https://gitlab.rtems.org/rtems/pkg/rtems-net-services.git
Cloning into 'rtems-net-services'...
remote: Enumerating objects: 806, done.
remote: Counting objects: 100% (31/31), done.
remote: Compressing objects: 100% (26/26), done.
remote: Total 806 (
Hi,
I'm trying to install the network stacks manually as rsb is having a problem
and I've encountered the following problem:
git clone https://gitlab.rtems.org/rtems/pkg/rtems-net-legacy.git
cd rtems-net-legacy
junkes@Zarquon rtems-net-legacy % git submodule init
git submodule update
Submodule '
/Epics/LONG_ISLAND/RTEMS_ARM_libBsd_stack/rsb/rtems/build/rtems-libbsd-388d46bb1b3080402c68ae11d14b2b36c3138952-powerp-rtems6-1/do-build
Heinz
> On 11. Jun 2024, at 21:26, Heinz Junkes wrote:
>
> Hi,
>
> There is a small error in rtems-net-legacy.bset.
>
> in the do-build s
Hi,
There is a small error in rtems-net-legacy.bset.
in the do-build script in line 99 is a '%' too much ...
/usr/bin/bzip2 -dc
/Volumes/Epics/LONG_ISLAND/RTEMS_ARM_libBsd_stack/rsb/rtems/sources/rtems_waf-68654b4f995382765605dc16917baad4bdbf7f7c.tar.bz2
| %/usr/bin/tar -x --strip-components 1
Thanks for the quick repair, it works and we are moving forward.
Heinz
> On 11. Jun 2024, at 06:50, Chris Johns wrote:
>
> On 11/6/2024 2:15 pm, Chris Johns wrote:
>> I will create an MR. I need to figure out the arm sim failure and how we
>> handle
>> this error.
>
> Fixes merged. Heinz, thank
152 Mar 12 09:09 lib
drwxrwxr-x 4 root admin 128 Feb 6 23:10 share
Heinz
> On 11. Jun 2024, at 02:39, Joel Sherrill wrote:
>
>
>
> On Mon, Jun 10, 2024, 7:26 PM Chris Johns wrote:
> On 11/6/2024 7:00 am, Heinz Junkes wrote:
> > Hi.
> >
> > That se
on.framework/Versions/3.12/Python'
configure:21892: $? = 1
configure: failed program was:
--
Fritz-Haber-Institut| Phone: (+49 30) 8413-4270
Heinz Junkes | Fax (G3+G4): (+49 30) 8413-5900
Faradaywe
Hi,
when trying to build the arm-tools with the Rtems Source Builder on osX and I
get this error:
It starts with Python 3.12.3
RTEMS Tools Project - Source Builder Error Report
Build: error: building arm-rtems6-gdb-14.2-arm64-apple-darwin23.5.0-1
Command Line: ../source-builder/sb-set-build
Thanks, that's it, with -qrtems it works. I am now trying to use pkg-config as
you recommended.
Danke Heinz
> On 20. Mar 2024, at 16:41, Sebastian Huber
> wrote:
>
> Hello Heinz,
>
> On 20.03.24 16:31, Heinz Junkes wrote:
>> /home/rtems/MVME2500_PCI/rtems
ory '/home/rtems/MVME2500_PCI/EPICS/epics-base/modules'
make: *** [configure/RULES_DIRS:85: modules.install] Error 2
Danke Heinz
----------
Fritz-Haber-Institut| Phone: (+49 30) 8413-4270
Heinz Junkes
Hi,
I would like to use the ADC inputs on the Beaglebone BSP. Unfortunately, I
can't find any support in the BSP.
Danke Heinz
smime.p7s
Description: S/MIME cryptographic signature
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/
I can confirm that it also works flawlessly on my MacBook with M2.
Heinz
> On 18. Oct 2023, at 21:25, Chris Johns wrote:
>
> On 18/10/2023 8:48 pm, Sebastian Huber wrote:
>> On 18.10.23 12:29, Heinz Junkes wrote:
>>> unfortunately also with the GCC 13.2 configurat
/build/arm-rtems7-gdb-29736fc-x86_64-apple-darwin22.6.0-1/do-build
Heinz
> On 18. Oct 2023, at 15:23, Sebastian Huber
> wrote:
>
> On 18.10.23 14:31, Heinz Junkes wrote:
>> Leider gibt es da noch andere Probleme?
>> I have now tried to build with gcc-10 and rsb-master:
//gcc.gnu.org/bugs/> for instructions.
Sorry,
Heinz
> On 18. Oct 2023, at 12:48, Sebastian Huber
> wrote:
>
> On 18.10.23 12:29, Heinz Junkes wrote:
>> unfortunately also with the GCC 13.2 configuration still the same error:
>> nclude -g -O2 -mthumb -O2
>> -
.o] Error 1
Heinz
> On 18. Oct 2023, at 10:13, Sebastian Huber
> wrote:
>
> Hello Heinz,
>
> I added a GCC 13.2 configuration. Maybe it works. You can test it with:
>
> ../source-builder/sb-set-builder
> --with-rtems-gcc=tools/rtems-gcc-13.2-newlib-head 6/rtems-
Heinz
> On 18. Oct 2023, at 07:39, Sebastian Huber
> wrote:
>
> On 17.10.23 21:52, Heinz Junkes wrote:
>> Hi, unfortunately i can't build RTEMS6 on the Intel-Mac (darwin-x86_64) at
>> the moment. it fails here: ... downloading:
>> patches/fix-mac-ar
Hi,
unfortunately i can't build RTEMS6 on the Intel-Mac (darwin-x86_64) at the
moment.
it fails here:
...
downloading: patches/fix-mac-arm64-mpc-config.patch - 347.0 bytes of 347.0
bytes (100%)
download: https://www.mpfr.org/mpfr-4.2.0/mpfr-4.2.0.tar.bz2 ->
sources/mpfr-4.2.0.tar.bz2
downloadin
It was a mess with homebrew and python versions on my system.
Rsb works well ;-)
Heinz
> On 27. Sep 2023, at 20:26, Heinz Junkes wrote:
>
> Hallo,
>
> I'm trying to build RTEMS on a MAC (M2) and I'm getting the following error:
>
>
> config: tools/rtems-gdb-1
Hallo,
I'm trying to build RTEMS on a MAC (M2) and I'm getting the following error:
config: tools/rtems-gdb-13.2.cfg
error: config error: gdb-common-1.cfg:127: "gdb: python: library file not
found: libpython3.11.*, please install"
Build FAILED
Build Set: Time 0:02:09.754310
error: config error:
I see exact the same behavior as in the ticket 4273.
Thanks for looking into….
Heinz
> On 13. Jul 2023, at 09:33, Chris Johns wrote:
>
>
>
> On 11/7/2023 7:32 pm, Heinz Junkes wrote:
>> Hallo,
>>
>> I am observing a strange problem with an NFS(v4) moun
Hallo,
I am observing a strange problem with an NFS(v4) mounted filesystem and path
usage.
I have mounted a filesystem via NFSv4 (/Volumes):
loc = 0x00820a20
node_access = 0x007c2378, node_access_2 = 0x, handler = 0x005c3474
type = nfs, mounted, read-write, target = /Volumes, dev =
For the Legacy stack you have to define MBUFS in rtems_bsdnet_config.
Example from EPICS:
os/CONFIG.Common.RTEMS-mvme3100:ARCH_DEP_CFLAGS +=
-DRTEMS_NETWORK_CONFIG_MBUF_SPACE=2048
struct rtems_bsdnet_config rtems_bsdnet_config = {
FIRST_DRIVER_CONFIG, /* Link to next interface */
MY
.com/system-emulation-using-qemu-raspberry-pi-3-4973260ffb3e
>
>
> Hope that helps,
> Jacob
>
> On Fri, Mar 17, 2023 at 9:49 AM Heinz Junkes wrote:
> Hi,
>
> I've been trying again for some time to get RTEMS (version 5 or 6) for
> raspberryPi2 to work on a
>
>> python shows:
>> mac07:VE_RTEMS_INST hjunkes$ python
>> Python 3.11.2 (main, Feb 16 2023, 02:55:59) [Clang 14.0.0
>> (clang-1400.0.29.202)] on darwin
>
> Where is this python from?
It’s from homebrew
>>
>>
>> on CLANG 10.0.0 and python 3.8.5
>>
>> Ok with RTEMS 5.2 (and rtems6)
>
> On whic
Hi,
I have, once again, a problem with building RTEMS on OS X.
It works fine with rtems6/master
with clang 10.0.0 , python 3.8.5 on
Darwin Judiciary-Pag.fritz.box 22.2.0 Darwin Kernel Version 22.2.0: Fri Nov 11
02:04:44 PST 2022; root:xnu-8792.61.2~4/RELEASE_ARM64_T8103 arm64
python shows:
(b
Hi,
I've been trying again for some time to get RTEMS (version 5 or 6) for
raspberryPi2 to work on a qemu.
There is a lot of documentation about it. To those I have tried it there are
always some 'fuzzies’ and I
unfortunately get never any output message when starting
qemu-system-arm -M raspi2
)
executing thread ID: 0x089010001
executing thread name: IDLE
I have no idea if this is a bug in the U-boot:
U-Boot 2018.09-2-g0b54a51eee (Sep 10 2018 - 19:41:39 -0500), Build:
jenkins-github_Bootloader-Builder-65
Heinz
> On 2. Jun 2022, at 18:00, Heinz Junkes wrote:
>
> Yes, I c
available.
So I can't use Ethernet here.
So I have to switch to libbsd. I will now try again with RTEMS-master (6).
Viele Grüße
Heinz Junkes
--
Experience directly varies with equipment ruined.
> On 1. Jun 2022, at 22:37, Alan Cudmore wrote:
>
> I see you are trying RTEMS 5.1. I
ewlib 7947581)
executing thread ID: 0x08b010001
executing thread name:
Viele Grüße
Heinz Junkes
--
Experience directly varies with equipment ruined.
> On 1. Jun 2022, at 15:30, Heinz Junkes wrote:
>
> Hi Alan,
> Thanks for the feedback. Did you also use the Ethernet of the beaglebon
Hi Alan,
Thanks for the feedback. Did you also use the Ethernet of the beagleboneblack
in your demo. I can't see which if is implemented in the BSP.
Danke Heinz
> On 31. May 2022, at 14:43, Alan Cudmore wrote:
>
> If it helps, I have a demo where I built and ran RTEMS 6 with libbsd on the
>
)
RTEMS version: 5.1.0
RTEMS tools: 7.5.0 20191114 (RTEMS 5, RSB 5.1, Newlib 7947581)
executing thread ID: 0x08b010001
executing thread name:
U-Boot SPL 2018.09-2-g0b54a51eee (Sep 10 2018 - 19:41:39 -0500)
Trying to boot from MMC2
Viele Grüße
Heinz Junkes
--
Experience directly varies with
Hi Chris,
I am trying to understand the problems my student is having with the Cora-z7-10.
I am trying my hand at a beaglebone black and RTEMS6 (master).
Unfortunately I have similar problems.
I built the rtems-examples.
rtems/6/bin/arm-rtems6-objcopy -R -S --strip-debug -O binary posix_hello.e
Hi Mirek,
You can find the configuration of the RTEMS at EPICS here:
epics-base/modules/libcom/RTEMS/posix/rtems_config.c
There for example
...
#define CONFIGURE_EXTRA_TASK_STACKS (4000 * RTEMS_MINIMUM_STACK_SIZE)
#define CONFIGURE_UNLIMITED_ALLOCATION_SIZE 32
#define CONFIGURE_UNLIMITED
I think I slept through the latest development. Sorry about that.
Where can I get the rtems sources (c/src)?
$: git clone git://git.rtems.org/rtems.git kernel
$: cd kernel
$: ls c
ACKNOWLEDGEMENTS
$: git checkout 5
Switched to branch '5'
Your branch is up to date with 'origin/5’.
$: ls c
acinclu
Yes, Andrew is absolutely right. I unfortunately got the two things mutex vs.
event
mixed up in the rush. Sorry for that.
Viele Grüße
Heinz
> On 28. Sep 2021, at 17:11, Johnson, Andrew N. wrote:
>
> On Sep 28, 2021, at 5:02 AM, Sebastian Huber
> wrote:
>>
>> On
d Danke
Heinz
> On 28. Sep 2021, at 12:02, Sebastian Huber
> wrote:
>
> On 28/09/2021 11:46, Heinz Junkes wrote:
>> Unfortunately we found out that EPICS uses the mutex handling also in the
>> interrupt context
>> and this leads to core-dumps in RTEMS :-(
Can the rtems_semaphore_*() routines be used on SMP systems?
Viele Grüße
Heinz
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users
intitialization? Translated
with www.DeepL.com/Translator (free version)
Gruss Heinz
--
Fritz-Haber-Institut| Phone: (+49 30) 8413-4270
Heinz Junkes | Fax (G3+G4): (+49 30) 8413-5900
Faradayweg 4-6| VC
Some RTEMS tests (capture, fileio, ...) respond to an input from the keyboard.
Thereby the function rtems_shell_wait_for_explicit_input is called.
(file: cpukit/libmisc/shell-wait-for-input.c)
In it change_serial_settings is called. There then
rv = tcsetattr(fd, TCSANOW, &new_term);
If you now u
:
>
> Hi Heinz,
>
> On Tue, Apr 13, 2021 at 7:02 AM Heinz Junkes wrote:
>>
>> Unfortunately I still do not understand it. Under Unix it runs perfectly and
>> also the
>> values are displayed correctly.
>>
>
> #include
>
> [...]
, Joel Sherrill wrote:
>
>
>
> On Tue, Apr 13, 2021 at 8:02 AM Heinz Junkes wrote:
> Unfortunately I still do not understand it. Under Unix it runs perfectly and
> also the
> values are displayed correctly.
>
> In the debugger, the contents of the structure ti
cond, &mutex, &timeout) returns "1" and
does not wait for the timeout.
This return value should not exist at all?
Under Unix, as expected, "110" is returned. ETIMOUT.
Heinz
> On 12. Apr 2021, at 20:38, Gedare Bloom wrote:
>
> On Fri, Apr 9, 2021 at 11:45
In rtems-examples/posix_api the examples
psx_example_[123] do not work as they should (especially timing).
E.g. in psx_example_1 the sleep(1) is ignored by sparc-rtems6-sis -rt … .
With qemu-system-arm -M xilinx-zynq-a9 the "sleep" at least works.
With both simulators/emulators psx_example_2 get
or bigger examples, I prefer the RTEMS
> configuration and Init thread to be in a separate file. I think the psx
> reporting
> examples do that.
>
> --joel
>
> On Fri, Apr 9, 2021 at 12:45 PM Heinz Junkes wrote:
> Jiri, Joel, thanks for your answers.
>
> @Joel: I
Jiri, Joel, thanks for your answers.
@Joel: I was wondering that rtems-examples in psx_example_3 does not wait 3
seconds.
I made a curious observation:
in the original code:
clock_gettime( CLOCK_REALTIME, &timeout );
timeout.tv_sec += 3;
timeout.tv_nsec = 0;
printf("The task is com
Danke,
that worked.
Heinz
> On 9. Apr 2021, at 14:35, Sebastian Huber
> wrote:
>
> On 09/04/2021 09:20, junkes wrote:
>
>> can not build examples (https://github.com/RTEMS/rtems-examples.git) for
>> sparc/erc32.
>> Seems to related to missing run time linker lib.
> I updated the RSB. I hope
Can the SIS Simple Instruction Simulator run in "real time"?
I.e. a sleep of 3 seconds should also last 3 seconds?
Thanks Heinz
smime.p7s
Description: S/MIME cryptographic signature
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman
If I use e.g. sparc6-rtems-sis and query the terminal window
size within rtems_task_Init, the output for winsize.ws_row and winsize.ws_col
is "0”.
/*
* get winsize example
*/
#include
#include
#include
#include
#include
rtems_task Init(
rtems_task_argument ignored
)
{
struct winsize
Ok, whenever you wrote to the Maillist, you find the solution ;-)
It's too easy …
…
bld(features = 'c cprogram',
target = 'till.exe',
cflags = '-g -O2',
source = ['rtems_config.c',
'rtems_netconfig.c',
'rtems_init.c’]
lib =[ ‘bsd’, ‘m’] )
I was able to build my application with the legacy stack (nfs, telnet, etc)
using waf.
“my" wscript file:
from __future__ import print_function
rtems_version = "5"
try:
import rtems_waf.rtems as rtems
except:
print('error: no rtems_waf git submodule')
import sys
sys.exit(1)
def in
it works with the Ubuntu package : qemu-system-arm 1:4.2-3ubuntu6.14
Heinz
> On 19. Feb 2021, at 22:46, Chris Johns wrote:
>
> On 20/2/21 7:10 am, junkes wrote:
>> running test programs with keyboard input. Is ignored on xilinx_zynq_a9_qemu
>
> This is a known issue with qemu, well the one the
I was totally happy with the Makefile provided by Christian.
It saved me a lot of typing and made it possible for me to play
through different variants in a really structured and consistent way
without "forgetting something every now and then".
Such help is very important for people like me who a
When I use the kernel from RTEMS6 my MVME2500 (qoriq_e500)
does not boot anymore and hangs:
VME2500=> run rtems_myTests
reading mvme2500.dtb
12363 bytes read in 13 ms (928.7 KiB/s)
Speed: 1000, full duplex
Using eTSEC1 device
TFTP from server 141.14.128.9; our IP address is 141.14.128.89
Filename
Sorry. The settings for several targets are in the defaults.
and for ARM-Cortex-A9 the default value is
CLOCK_DRIVER_USE_FAST_IDLE = True
Sorry for the noise ….
Heinz
> On 19. Feb 2021, at 09:45, Christian MAUDERER
> wrote:
>
> I think some of the simulator BSPs have an option that enable s
Unfortunately, the option is set to "False" by default.
CLOCK_DRIVER_USE_FAST_IDLE = False
Heinz
> On 19. Feb 2021, at 09:45, Christian MAUDERER
> wrote:
>
> I think some of the simulator BSPs have an option that enable some kind of
> time laps as soon as the idle routine is reached.
>
> I
Sorry, I should have seen…
Yes, it works as you wrote.
Now I just need to clarify the timing problem with fileio keyboard input
Vielen, vielen Dank für Deine Hilfe,
Heinz
> On 19. Feb 2021, at 09:45, Christian MAUDERER
> wrote:
>
>
> If you start the script just like it is, it assumes
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 Berlin| E-Mail:jun...@fhi-berlin.m
Harness
Viele Grüße
Heinz Junkes
--
Experience directly varies with equipment ruined.
> On 2. Oct 2020, at 08:15, Chris Johns wrote:
>
> On 2/10/20 2:48 pm, Heinz Junkes wrote:
>> init01.exe does not initialize the network interface.
>
> Yes. It splits the problem.
>
init01.exe does not initialize the network interface.
I see the same delay with dhcpcd01.exe
Heinz
> On 2. Oct 2020, at 01:08, Chris Johns wrote:
>
> On 2/10/20 5:34 am, Heinz Junkes wrote:
>> I have finally managed to apply the patch. Unfortunately it didn't lead to
Dear Karel,
I have finally managed to apply the patch. Unfortunately it didn't lead to a
change in the behaviour of qemu. The delay of about 45 seconds is still there.
Thanks anyway!
Heinz
> On 28. Sep 2020, at 21:53, Karel Gardas wrote:
>
>
> Could you be so kind and test attached patch? It
> On 7. Sep 2020, at 21:53, Joel Sherrill wrote:
>
> i386-rtems5-ar dv librtemscpu.a dummy.o
That was really the trick and helped.
Danke Heinz
smime.p7s
Description: S/MIME cryptographic signature
___
users mailing list
users@rtems.org
http://lists.
> On 7. Sep 2020, at 21:18, Joel Sherrill wrote:
>
>
> It needs to be in an object file defined between rtemsTestData.o and
> -lCom. Otherwise, there are configuration symbols lacking and the dummy
> configuration will get pulled in.
>
>
Unfortunately I do not understand that. These a
ibrtemscpu.a(dummy.o):(.bss+0x58):
first defined here
collect2: ld returned 1 exit status
../../../../configure/RULES_BUILD:212: recipe for target 'libComTestHarness'
failed
--
Fritz-Haber-Institut| Phone:
rtems 4.10 —with-network —with-posix
Unfortunately I cannot resolve a reference:
source/rtems-source-builder/rtems/build/i386-rtems4.10-kernel-4.10-1/i386-rtems4.10-kernel-4.10-1-4.10/build/i386-rtems4.10/c/pc686/cpukit/libblock/../../../../../../rtems-4.10/c/src/../../cpukit/libblock/src/bdbuf.c
Arghhh,
as so often, if you are looking for a problem for a long time, then send the
request to the list and
then read the ticket again, you can "see" the cause.
Adding “-Wl,—gc-sections” to the LD_FLAGS solved the issue.
Sorry for the disturbance ...
Viele Grüße
Heinz Junkes
--
Is there a BSP for the Zynq-7000 based board cora-z7?
Should the image of the zedboard be bootable on the cora z7-10 ?
Danke Heinz
smime.p7s
Description: S/MIME cryptographic signature
___
users mailing list
users@rtems.org
http://lists.rtems.org/
Hallo,
i just can't get it to load and start a rtems-exe via tftp in u-boot.
I have tried many variations now. Without success. This one should work, right?
pwd:
build/b-xilinx_zynq_zedboard/arm-rtems5/c/xilinx_zynq_zedboard/testsuites/samples
ls -l ticker*
-rwxr-xr-x 1 junkes staff 2822792
to configure and forgot to append the existing
flags ${CFLAGS} :-(
Heinz
> On 30. Apr 2020, at 01:33, Chris Johns wrote:
>
> On 29/4/20 8:03 pm, Heinz Junkes wrote:
>> unfortunately i can't really get along with the
>> source-builder/sb-set-builder.
>
> Can y
Hello,
unfortunately i can't really get along with the source-builder/sb-set-builder.
For example, I want to build ntp for xilinx_zynq_a9_qemu using the command line:
(in rtems-source-builder-5.0.0-m2003/rtems)
../source-builder/sb-set-builder —log=log_ntp_arm.txt
—prefix=/home/h1/GSOC/RTEMS/5.
Great, thanks. Now I have a new error, but the setting of CFLAG worked.
I had always done "something" wrong and then didn't even look at the examples
anymore.
Danke Heinz
> On 24. Apr 2020, at 16:47, Gedare Bloom wrote:
>
> Heinz,
>
> Did you try to modify the source-builder/config/ntp-4-1.cf
clock_settime was not initialized ;-)
Viele Grüße
Heinz Junkes
--
Experience directly varies with equipment ruined.
> On 13. Apr 2020, at 19:04, Sebastian Huber
> wrote:
>
> Hello Heinz,
>
> this assertion is definitely an error (clock_settime should return EINVAL
> instead)
When calling clock_settime(CLOCK_REALTIME, &now)
under qemu (arm-rtems5-xilinx_zynq_a9_qemu) I get an error:
assertion "!_Watchdog_Is_far_future_timespec( ts )" failed:
file
"/home/h1/GSOC/RTEMS_DEV/rtems-5.0.0-m2003/cpukit/include/rtems/score/watchdogimpl.h”,
line 530, function: _Watchdog_Ti
quot;ntp_servers" and for the dhcp-servers I know (e.g.
isc-dhcpd-server)
the option "ntp-servers" is designated.
But I did not manage to define the option in dhcpcd.conf itself.
Viele Grüße
Heinz Junkes
--
Experience directly varies with equipment ruined.
> On 21. Jan 2020, at
In the current files "Makefile.inc" you can find a comment :
“
# This support will be removed from RTEMS. Please consider other
# ways to build applications.
“
How is this to be interpreted?
Danke,
Viele Grüße
Heinz Junkes
--
Experience directly varies with equipment ruined.
p without waiter
test wakeup one
slave[2]: 4
slave[2]: 5
test waassertion "rtems_resource_snapshot_check(&snapshot)" failed: file
"../../testsuite/sleep01/test_main.c", line 229, function: test_main
*** FATAL ***
fatal source: 7 (RTEMS_FATAL_SOURCE_ASSERT)
fatal code: 33917016 (0x02058858
lob at 2000
Booting using the fdt blob at 0x2000
Uncompressing Kernel Image ... OK
Loading Device Tree to 03ff9000, end 03fff04a ... OK
WARNING: OS Clock time was read before being set.
Using 1990-01-02 00:00:00.00 UTC
initConsole --- Info ---
> On 13. Feb 2020, at 17:
Using qoriq_e500 BSP
if configured with --enable-rtems-debug :
../../rtems-5.0.0-m1912/configure --enable-maintainer-mode
--prefix=/home/epics/MVME2500/RTEMS/5.0.0-m1912 --target=powerpc-rtems5
--enable-rtemsbsp=qoriq_e500 --enable-posix --enable-cxx --disable-networking
--enable-pci --enable-r
is assigned to
“new_rtems_cmdline"?
Danke Heinz
--
Fritz-Haber-Institut | Phone: (+49 30) 8413-4270
Heinz Junkes | VC: 1022 2018 1216 @ bjn.vc
Faradayweg 4-6| Fax (G3+G4): (+49 30) 841
I can confirm that this one quickly solved the problem.
Sorry I didn't look for a fix.
Viele Grüße
Heinz Junkes
--
Experience directly varies with equipment ruined.
> On 18. Dec 2019, at 05:49, Chris Johns wrote:
>
> On 17/12/19 11:59 pm, Heinz Junkes wrote:
>> Wh
c-rtems5/c/qoriq_e500'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/home/epics/MVME2500/RTEMS_DEV/build/b-qoriq_e500/powerpc-rtems5/c'
make: *** [all-recursive] Error 1
I guess the expansion of RTEMS_REVISION doesn't work with the "-".
Viele Grüße
H
Yeah, that fixed it.
Danke
Viele Grüße
Heinz Junkes
--
Experience directly varies with equipment ruined.
> On 10. Sep 2019, at 12:13, Sebastian Huber
> wrote:
>
> Hello Heinz,
>
> would you mind testing the attached patch.
>
> --
> Sebastian Huber, embedd
s/usr/include/c++/v1/algorithm:2586:1: note:
candidate function template not viable: requires single argument '__t', but 2
arguments were provided
min(initializer_list<_Tp> __t)
^
1 error generated.
Waf: Leaving directory `/Users/junkes/MVME2500/RTEMS_DEV/rtems-tools/build'
I use the posix implementation in RTEMS5.
How can I start telnetd in POSIX_Init?
Is there an example/manual?
Very concretely:
Which priority do I have to choose in the
rtems_telnetd_config_table
the Posix Prio or the rtems Prio?
Danke,
Heinz
smime.p7s
Description: S/MIME cryptographic sign
Is it foreseeable when RTEMS5 will get a release?
Danke,
Heinz
smime.p7s
Description: S/MIME cryptographic signature
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users
Danke,
can’t find beaglebone = “machine” with qemu-system-arm
Heinz
> On 19. Mar 2019, at 12:08, Sebastian Huber
> wrote:
>
> Hello Heinz,
>
> there is no network support for the RPI2. I think the RPIs use an USB
> Ethernet device on the board. This could be supported via the FreeBSD USB
can not find any definitions for
e.g. RTEMS_BSP_NETWORK_DRIVER_NAME
in the raspberrypi2 bsp.h file.
Is there no support for network devices with this bsp?
Danke,
Heinz
smime.p7s
Description: S/MIME cryptographic signature
___
users mailing list
user
../../rtems/configure --enable-maintainer-mode --prefix=$HOME/.rtems
--target=x86_64-rtems5 --enable-rtemsbsp="amd64" --enable-posix --enable-cxx
--enable-networking
make all
...
Making all-am in amd64
make[6]: Entering directory
`/home/travis/RTEMS_DEV/build/b-x86_64/x86_64-rtems5/c/amd64/lib/
The porting of Epics-7 to RTEMS 5 is almost finished.
To run our tests we use Travis-Ci where we run qemu-i386.
(I couldn't find a suitable emulator for the PowerPC, beatnik board. I do the
tests on the hardware.)
Unfortunately our tests get stuck with one of the tests. This is because
>> http
With the actual rtems-master I can not load anymore programs on beatnik board
(MVME6100)
[junkes@h rtems-source-builder (master)]$ ls rtems/sources/
autoconf-2.69.tar.gz
automake-1.12.6.tar.gz
binutils-2.32.tar.bz2
expat-2.1.0.tar.gz
gcc-7.4.0.tar.xz
gdb-8.2.1.tar.xz
gmp-6.1.0.tar.bz2
isl-0.16.1.
To boot rtems code within qemu we used bin2boot in 4.10 like
i386-rtems4.10/pc386/build-tools/bin2boot dbScanTest.boot 0x00097E00
/home/travis/.rtems/i386-rtems4.10/pc386/lib/start16.bin 0x00097C00 0
dbScanTest.bin 0x0010 0
With RTEMS 5.1 this command disappeared with #3410. What can be u
Hello Sebastian,
it worked with the patch. Thank you.
What I don't understand is why I could build the gcc-7.3 under linux (with the
rtems-source-builder) and
not with the Mac (darvin)?
Shouldn't the same gcc tarball be loaded when downloading?
Heinz
> On 31. Oct 2018, at 08:23, Sebastian H
linking /usr/bin/python to python3 it works.
Heinz
> On 31. Oct 2018, at 02:20, Chris Johns wrote:
>
> On 31/10/2018 02:39, Heinz P. Junkes wrote:
>> How can I fix this in after download (tried to run builder with
>> --no-downloads
>> after download all sources)
>>
>> After the software down
found:
/Users/junkes/RTEMS_PRE_AUSTRALIA/RTEMS_DEV/rtems-source-builder/rtems/sources/gcc-7.3.0.tar.xz
Build FAILED
How to prevent checksum checking/ cleanup with the source builder?
Danke,
Heinz
> On 30. Oct 2018, at 12:08, Sebastian Huber
> wrote:
>
> On 30/10/2018 09:47,
The patch from Amar works for me.
This is quick since it's late but the issue I ran into is in
rtemstoolkit/version.py
In line 174: -- if that's the latest
_revision = int(''.join(itertools.takewhile(str.isdigit, rev)))
Depending on the version of Python you are running 'rev' can be unicode
Building rtems on Darwin (10.13.6, High Sierra) with Homebrew 1.8.0
Homebrew 1.8.0-74-g2b3f855
Homebrew/homebrew-core (git revision 4961b; last commit 2018-10-30)
Homebrew/homebrew-cask (git revision 2b5ad; last commit 2018-10-30)
failed.
[junkes@h rtems (master)]$ more
rsb-report-powerpc-rtem
A lot of enhancements to rtems took place in the past.
E.g. https://devel.rtems.org/ticket/3243 which is crucial for the EPICS
project.
Will there be a new release available soon?
Danke Heinz
--
Das FHI verarbeitet, speichert und
There is RTEMS 5 support for the MVME2500 made by Sebastian Huber.
Unfortunately, I have not been able to test it properly with EPICS7.
I will try it after the Epics meeting and will report.
Heinz
> On 6. Jun 2018, at 23:24, Matt Rippa wrote:
>
> Thanks for the fast reply. Of all the mvme boar
1 - 100 of 102 matches
Mail list logo
