Re: Console driver not working?

Doing a bit more investigation this evening and it appears that the console driver for the Beaglebone BSP isn't really implemented properly. Comparing it with the raspraspberrypi and other bsps the console/console-config.c file looks very different and doesn't implement the POSIX Termios support pe

Re: Console driver not working?

Hi Chris, Thanks for your reply. On Mon, Apr 28, 2025, 09:50 Chris Johns wrote: > I suggest you see if the `hello.exe` sample program runs? It would check > the low > level hardware interface. > The helloworld example works as expected. I actually have a fair amount of tracing data printing to

Re: Console driver not working?

On 27/4/2025 4:18 pm, James Fitzsimons wrote: > Hi all, > > I'm trying to get back into some embedded development using RTEMS after a > number > of years away and have resurrected an old project using the Beaglebone black > as > a starting point. Welcome back. > I have built the latest RTEMS a

Re: BSP Nomenclature

On Fri, Jan 31, 2025 at 2:11 PM Robert W wrote: > > This sounds like you might be using the BSP build sets in the RSB. It > might > > be better for you to build just the tools with the bset 6/rtems-m68k and > then > > build and test BSPs individually. That way you can test, tweak, debug, > test,

Re: BSP Nomenclature

On Fri, Jan 31, 2025 at 6:10 AM Robert W wrote: > This might seem like a noob question but I keep running into this > issue when building rtems tools. > > Is there some master list of the *explicit* bsp option to pass to > "--with-rtems-bsp"? > I remember not having the *exact* bsp expression be

Re: rsb failure on rtems-m68k target

I think you are missing the Python development package for your host. It should be named something like: sudo apt-get install python3-dev --joel On Thu, Jan 23, 2025 at 1:09 PM Robert W wrote: > Sorry, forgot to add host info: > > Ubuntu 22.04, on an aspire e 15 laptop. > > Robert W. > > On

Re: rsb failure on rtems-m68k target

Sorry, forgot to add host info: Ubuntu 22.04, on an aspire e 15 laptop. Robert W. On Thu, Jan 23, 2025 at 11:50 AM Robert W wrote: > > Returning to the RTEMS world after many years of being distracted elsewhere: > > rtems 5.3: > > My notes for this attempt: > > " > package: expat-2.1.0-x86_64-l

Re: Evaluating RTEMS performances (jitter)

Hi, Thx a lot for the reference. Le ven. 29 nov. 2024 à 10:45, Sebastian Huber < sebastian.hu...@embedded-brains.de> a écrit : > Hello, > > Björn B. Brandenburg has done a lot work in this area: > > https://people.mpi-sws.org/~bbb/papers/ > > Maybe he has some tooling available. > > -- > embedde

Re: Evaluating RTEMS performances (jitter)

Hello, Björn B. Brandenburg has done a lot work in this area: https://people.mpi-sws.org/~bbb/papers/ Maybe he has some tooling available. -- embedded brains GmbH & Co. KG Herr Sebastian HUBER Dornierstr. 4 82178 Puchheim Germany email: sebastian.hu...@embedded-brains.de phone: +49-89-18 94 74

Re: PowerPC/e500: how is FDT access supposed to work?

Hello Chris, apologies for the (very) late response, however, I was able to make a lot of progress in the meantime and can now comment on this matter with much more confidence. Yes, do believe that amendents to the user manual would be helpful.  Before that, let me give you a little overview

RE: aarch64 curr_el_sp0_irq/_AArch64_Exception_interrupt_nest use Incorrect sp

Thanks for bringing this up. I couldn’t find the exact wording you mentioned, but I think this is what you’re referring to in the current (K.a) revision of the ARM Architecture reference manual for ARMv8: D1.3.2 Exception entry When an exception is taken to an Exception level, ELx, that is using

Re: Deprecating Architectures and BSPs after 6 Branches

A minor update, we have added several more m68k boards to the mrm332 board for deprecation in 6 and removal in 7: m68k/csb360 m68k/gen68340 m68k/gen68360 m68k/gen68360_040 m68k/pgh360 m68k/mcf5206elite m68k/mcf52235 m68k/mcf5225x m68k/mrm332 m68k/mvme147 m68k/mvme147s m68k/mvme162 m68k/mvme162lx m6

Re: PowerPC/e500: how is FDT access supposed to work?

On 7/7/2024 6:41 pm, Daniel Wohllebe wrote: > Hello Sebastian, > > thank you for your response. I found out that the problem was me including the > FDT-address incorrectly in the boot-command. > > For anybody who may also stumble upon this future, I will give a small outline > of what to check fo

Re: PowerPC/e500: how is FDT access supposed to work?

Hello Sebastian, thank you for your response. I found out that the problem was me including the FDT-address incorrectly in the boot-command. For anybody who may also stumble upon this future, I will give a small outline of what to check for: On the U-Boot commandline, we can see the environ

Re: PowerPC/e500: how is FDT access supposed to work?

Hello Daniel, the QorIQ BSPs assume that they are started by U-Boot with a device tree provided: https://docs.rtems.org/branches/master/user/bsps/bsps-powerpc.html#qoriq-qoriq -- embedded brains GmbH & Co. KG Herr Sebastian HUBER Dornierstr. 4 82178 Puchheim Germany email: sebastian.hu...@emb

Re: ARINC 653

hi,Thx for your advice, I will try it.--PierreLe 26 juin 2024 à 14:27, Jacques Seronie-Vivien a écrit :Hi,Seems to me that GMV is the right place to look for access to AIR code. In this PDF (https://www.gmv.com/sites/default/files/content/file/2023/10/31/111/sp_br1_air_final.pdf) I found the foll

Re: ATSAMV71 / ATSAMRH71 ethernet POC with RTEMS-LIBBSD

Hello Darius, On 2024-06-27 13:31, Matthew J Fletcher wrote: Hi Darius, The if_atsam driver is used extensively on industrial / custom ATSAME71 boards with external SDRAM with LibBSD. The reliability has been very good, you can see in the LibBSD change log for if_atsam some changes a coupl

Re: ATSAMV71 / ATSAMRH71 ethernet POC with RTEMS-LIBBSD

Hi Darius, The if_atsam driver is used extensively on industrial / custom ATSAME71 boards with external SDRAM with LibBSD. The reliability has been very good, you can see in the LibBSD change log for if_atsam some changes a couple of years back that resolved the last issues. regards, Matthew.

Re: How to get a stack trace in RTEMS

On 27.06.24 10:27, Stanislav Pankevich wrote: A small further update here to support the discussion further. It turns out that there is an undocumented function that, in contrast to _Unwind_Backtrace, allows passing a given stack: /    In my practice standard _Unwind_Backtrace failed to switch

Re: How to get a stack trace in RTEMS

A small further update here to support the discussion further. It turns out that there is an undocumented function that, in contrast to _Unwind_Backtrace, allows passing a given stack: *In my practice standard _Unwind_Backtrace failed to switch to pre-signal stack. I've managed to get some bef

Re: How to get a stack trace in RTEMS

Hi Sebastian, We had to add -funwind-tables to have this trace() called, and we can now see the function names as follows. The challenge is that the functions of the exception handler are printed, not the code that led to the exception. Now we need to figure out how to switch this code to print ou

Re: ARINC 653

Hi, Seems to me that GMV is the right place to look for access to AIR code. In this PDF ( https://www.gmv.com/sites/default/files/content/file/2023/10/31/111/sp_br1_air_final.pdf) I found the following sentence: "For further information: AIR is running under the GPL v2 license and can be accesse

Re: How to get a stack trace in RTEMS

Hello Stanislav, On 26.06.24 11:15, Stanislav Pankevich wrote: Dear RTEMS community, My colleague George cannot register to post to this forum, getting 403 when subscribing at https://lists.rtems.org/mailman/listinfo/users . I am posting this q

Re: Unfortunately, I still can't use rsb on a Mac (M2).

gdb simulators need to be built only for powerpc and mips AFAIK. I also just had an MR merged for missing an update to the checksum for rtems-tools Hopefully things are improving. Lots of small issues from the GitLab transition. URL changes hit a surprising number of places. On Mon, Jun 10, 2024

Re: waf in gitlab rtems-net-legacy still linked to git.rtems.org

Hi, Thank you very much for this, unfortunately there is still a problem with the 'tar’: + cd rtems-net-legacy-74a7abc2d41209c9f667fb6cbffbd05cedf88977 + /bin/chmod -R a+rX,g-w,o-w . + cd /Volumes/Epics/LONG_ISLAND/RTEMS_FOR_EPICS/rsb/rtems/build/rtems-net-legacy-74a7abc2d41209c9f667fb6cbffbd05c

Re: waf in gitlab rtems-net-legacy still linked to git.rtems.org

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: > > git clone https://gitlab.rtems.org/rtems/pkg/rtems-net-legacy.git > cd rtems-net-legacy > > junkes@Zarquon rtems-net-l

Re: compiling rtems-net-services fail

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'... > remote: Enumerating objects: 806, d

Re: rtems-net-legacy.bset failure

On 12/6/2024 5:26 am, Heinz Junkes wrote: > 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-68654b4f995382765605dc16917baad

Re: rtems-net-legacy.bset failure

Hi, the same with other bset like rtems-libbsd.bset /Volumes/Epics/LONG_ISLAND/RTEMS_ARM_libBsd_stack/rsb/rtems/build/rtems-libbsd-388d46bb1b3080402c68ae11d14b2b36c3138952-powerp-rtems6-1/do-build: line 99: %/usr/bin/tar: No such file or directory shell cmd failed: /bin/sh -ex /Volumes/Epics

Re: Unfortunately, I still can't use rsb on a Mac (M2).

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

Re: Unfortunately, I still can't use rsb on a Mac (M2).

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, thanks for the report. Chris ___ users mailing list users@rtems.org http://lists.rtems.org/m

Re: Unfortunately, I still can't use rsb on a Mac (M2).

On 11/6/2024 2:13 pm, Joel Sherrill wrote: > On Mon, Jun 10, 2024, 10:57 PM Chris Johns > wrote: > > On 11/6/2024 1:29 pm, Heinz Junkes wrote: > > Hi, > > > > All the stuff seems to be there: > > > > > > junkes@Zarquon ~ % ls -l  >  /Librar

Re: Unfortunately, I still can't use rsb on a Mac (M2).

On Mon, Jun 10, 2024, 10:57 PM Chris Johns wrote: > On 11/6/2024 1:29 pm, Heinz Junkes wrote: > > Hi, > > > > All the stuff seems to be there: > > > > > > junkes@Zarquon ~ % ls -l > /Library/Frameworks/Python.framework/Versions/3.12/ > > total 31296 > > lrwxrwxr-x 1 root admin18 Mar 1

Re: Unfortunately, I still can't use rsb on a Mac (M2).

On 11/6/2024 1:29 pm, Heinz Junkes wrote: > Hi, > > All the stuff seems to be there: > > > junkes@Zarquon ~ % ls -l > /Library/Frameworks/Python.framework/Versions/3.12/ > total 31296 > lrwxrwxr-x 1 root admin18 Mar 12 09:09 Headers -> > include/python3.12 > -

Re: Unfortunately, I still can't use rsb on a Mac (M2).

Hi, All the stuff seems to be there: junkes@Zarquon ~ % ls -l /Library/Frameworks/Python.framework/Versions/3.12/ total 31296 lrwxrwxr-x 1 root admin18 Mar 12 09:09 Headers -> include/python3.12 -rwxrwxr-x 1 root admin 16020240 Feb 6 23:15 Python drwxrwxr-x 5 root admin

Re: Unfortunately, I still can't use rsb on a Mac (M2).

On 11/6/2024 10:39 am, 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 seems to be the root cause of the problem: > > > > > > configure:21663: ch

Re: Unfortunately, I still can't use rsb on a Mac (M2).

On Mon, Jun 10, 2024, 7:26 PM Chris Johns wrote: > On 11/6/2024 7:00 am, Heinz Junkes wrote: > > Hi. > > > > That seems to be the root cause of the problem: > > > > > > configure:21663: checking whether to use python > > configure:21665: result: /usr/local/bin/python3.12 > > configure:21869: chec

Re: Unfortunately, I still can't use rsb on a Mac (M2).

On 11/6/2024 7:00 am, Heinz Junkes wrote: > Hi. > > That seems to be the root cause of the problem: > > > configure:21663: checking whether to use python > configure:21665: result: /usr/local/bin/python3.12 > configure:21869: checking for python > configure:21892: /usr/bin/cc -O2 -pipe -fbracket

Re: Unfortunately, I still can't use rsb on a Mac (M2).

Hi. That seems to be the root cause of the problem: configure:21663: checking whether to use python configure:21665: result: /usr/local/bin/python3.12 configure:21869: checking for python configure:21892: /usr/bin/cc -O2 -pipe -fbracket-depth24 -I/Volumes/Epics/LONG_ISLAND/RTEMS_ARM_libBsd_sta

Re: disable DCache on RTEMS SMP

On 22.05.24 17:53, Sebastian Huber wrote: On 19.04.24 08:45, Sebastian Huber wrote: Hello Stéphane, the rtems_cache_disable_data() has no real use case. It is quite difficult to implement and it is not unusual that its implementation is broken. I think on RTEMS 6 it should work for this BSP.

Re: Classic API - Are there incompatibilites between schedulers and rtems_task_set_priority()?

Hello Ingolf, changing the priority through rtems_task_set_priority() of running tasks is supported by all current schedulers. However, this function changes only the priority of the task itself. The actual priority of the task depends also on locking protocols and periods (EDF scheduler). -

Re: building rtems-net-legacy failed

On 30/5/2024 6:44 am, Miroslaw Dach wrote: > Hi John and Joel, > >> It is enable/disable networking (e.g. --enable-networking when you configure > RTEMS itself) and then do not reference the legacy repository at all. > I built RTEMS 5 with  --enable-networking >>and then do not reference the legac

Re: building rtems-net-legacy failed

Hi John and Joel, > It is enable/disable networking (e.g. --enable-networking when you configure RTEMS itself) and then do not reference the legacy repository at all. I built RTEMS 5 with --enable-networking >and then do not reference the legacy repository at all. How to build then rtems-net-ser

Re: building rtems-net-legacy failed

Hi rtems-net-legacy only works with 6+. It was still included in the rtems source tree in versions 5 and earlier. It is enable/disable networking (e.g. --enable-networking when you configure RTEMS itself) and then do not reference the legacy repository at all. For 6, there is waf and no network s

Re: building rtems-net-legacy failed

Hello. Thanks for the example configuring waf. I built v5.3 for Raspberry Pi using RSB after failing with waf. Legacy components are more likely to build using “legacy” RSB instead of WAF. I don’t know where you can find that missing test-info.h file. But you probably don’t need it at first bu

Re: RTEMS Project Repos in GitLab

On Mon, May 13, 2024 at 10:46 AM Frank Kühndel wrote: > > Hello Chris, > > I just did not managed to find git://git.rtems.org/rtems_waf.git on > gitlab. Has been moved too or will it stay were it was? > Thanks for bringing this up. https://gitlab.rtems.org/rtems/tools/rtems-waf It should work che

Re: RTEMS Project Repos in GitLab

Hello Chris, I just did not managed to find git://git.rtems.org/rtems_waf.git on gitlab. Has been moved too or will it stay were it was? Thanks, Frank On 5/1/24 08:46, Chris Johns wrote: Hi RTEMS Community. This email explains the RTEMS Project and Repos in GitLab. GitLab is will be open a

Re: Introducing myself to the community

Hi Purva, Congratulations and welcome aboard! On Fri, May 3, 2024 at 4:10 AM Purva Yeshi wrote: > Hello everyone, > I'm Purva Yeshi, a pre-final year Electronics and Telecommunication > undergraduate from VJTI, Mumbai. I've decent exposure to working with > Embedded systems and system software,

Re: Contributor Introduction

Hey there! I am Suraj Kumar, a 19 year old guy from India. Super excited to work with all of you :) I am a Computer Science student, currently in my 2nd year, and very passionate about Cyber Security and Open Source. I am an active member of team bi0s, and my current area of focus is Reverse Engin

Re: How can I use --with-rtems-bspopts properly?

Dear Y. HB, On Friday 16 of September 2022 11:45:05 Y. HB wrote: > I am working on tms570 bsp > > I want to change some bspopts , but I cannot get the default value > overridden via --with-rtems-bspopts, what correct way should I do? > > I used following command to configure RTEMS bsp > > ../../rt

Re: disable DCache on RTEMS SMP

Hello Stéphane, the rtems_cache_disable_data() has no real use case. It is quite difficult to implement and it is not unusual that its implementation is broken. I think on RTEMS 6 it should work for this BSP. However, I am not sure if the atomic operations work, if you disable the data cache.

Re: multiple definition of `_Semaphore_Wait', multiple definition of `_Semaphore_Post' , undefined reference to `__dso_handle'

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/6/bin/powerpc-rtems6-g++ -o >> libCom

Re: multiple definition of `_Semaphore_Wait', multiple definition of `_Semaphore_Post' , undefined reference to `__dso_handle'

Hello Heinz, On 20.03.24 16:31, Heinz Junkes wrote: /home/rtems/MVME2500_PCI/rtems/6/bin/powerpc-rtems6-g++ -o libComTestHarness -static -L/home/rtems/MVME2500_PCI/EPICS/epics-base/lib/RTEMS-qoriq_e500 -L/home/rtems/MVME2500_PCI/rtems/6/powerpc-rtems6/qoriq_e500/lib -mcpu=8540 -msoft-float -mea

Re: rosetta error: Unimplemented syscall number 282 Trace/breakpoint trap

Great! It worked! Thank you very much Gedare! On Monday, March 18, 2024 at 10:05:39 PM GMT+1, Gedare Bloom wrote: On Mon, Mar 4, 2024 at 6:39 AM Volkan SALMA wrote: > > Dear Rtems users, > > Newbie here.. > > I compiled a basic i386 project using the docker image of > juanmagomez/

Re: rosetta error: Unimplemented syscall number 282 Trace/breakpoint trap

On Mon, Mar 4, 2024 at 6:39 AM Volkan SALMA wrote: > > Dear Rtems users, > > Newbie here.. > > I compiled a basic i386 project using the docker image of > juanmagomez/rtems-dev. > > The generated binary works fine on the real target. However I would like to > run it on qemu > to speed up my deve

Re: MicroZed PHY timeout

Hey Kinsey, Thanks for the response. Yes, I am using the 6-freebsd-12 branch of rtems-libbsd. This doesn’t make any sense to me, but i get the error when I build everything (rsb, rtems, libbsd) on Redhat Enterprise Linux 8. If I build everything on Ubuntu 22.04, everything works fine. -Ric

Re: MicroZed PHY timeout

On 14/3/2024 2:00 am, Kinsey Moore wrote: > As far as I know, the Zynq LibBSD CGEM support hasn't changed much beyond the > updates to support ZynqMP variants of the peripheral. Are you building LibBSD > master or 6-freebsd-12? > > Kinsey > > -Original Message- > From: users On Behalf

RE: MicroZed PHY timeout

As far as I know, the Zynq LibBSD CGEM support hasn't changed much beyond the updates to support ZynqMP variants of the peripheral. Are you building LibBSD master or 6-freebsd-12? Kinsey -Original Message- From: users On Behalf Of Richard VanderWal Sent: Tuesday, March 12, 2024 11:34 A

Re: EPICS and tftp file system

Hi Michael, I tried to read and write to/from the tftp server using the command line tftp on my linux computer and all of that works fine so it looks to me to be an issue with the RTEMS/EPICS setup. Best Regards Mirek ___ users mailing list users@rtems.

Re: EPICS and tftp file system

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

Re: EPICS and tftp file system

Hi Frank, Thank you for your feedback on that. It might be then the setup in EPICS. Best Regards Mirek czw., 15 lut 2024 o 02:26 Frank Kühndel napisał(a): > Hello Miroslaw, > > On 2/14/24 21:54, Miroslaw Dach wrote: > > Thanks for your e-mail. > >> TFTP is normally only used for reading, and

Re: “AW:” ?

It seems another pedantic expresion of fascism from redmond software... Regards RMD On 2/1/24 05:51, jan.som...@dlr.de wrote: -Original Message- From: users On Behalf Of Sebastian Huber Sent: Donnerstag, 1. Februar 2024 07:48 To: John Howard ; users@rtems.org Subject: Re: “AW

Re: EPICS and tftp file system

Hello Miroslaw, On 2/14/24 21:54, Miroslaw Dach wrote: Thanks for your e-mail. TFTP is normally only used for reading, and it doesn’t surprise me if writing isn’t supported since there is no user authentication involved. I thought that setting the parameter RTEMS_FILESYSTEM_READ_WRITE in the f

Re: EPICS and tftp file system

Hi Andrew, Thanks for your e-mail. >TFTP is normally only used for reading, and it doesn’t surprise me if writing isn’t supported since there is no user authentication involved. I thought that setting the parameter RTEMS_FILESYSTEM_READ_WRITE in the function call below would do the job: if (moun

Re: EPICS and tftp file system

Hi Mirek, TFTP is normally only used for reading, and it doesn’t surprise me if writing isn’t supported since there is no user authentication involved. It should be possible to enable NFSv2 in Rocky Linux 8, it still works on RHEL-8 but you do have to change one or two files in the server’s /et

RE: “AW:” ?

> -Original Message- > From: users On Behalf Of Sebastian Huber > Sent: Donnerstag, 1. Februar 2024 07:48 > To: John Howard ; users@rtems.org > Subject: Re: “AW:” ? > > On 31.01.24 18:20, John Howard wrote: > > Lost in translation. > > > > Anyb

Re: “AW:” ?

On 31.01.24 18:20, John Howard wrote: Lost in translation. Anybody here know what “AW:” in the Subject means? At first, I took it to mean a comical expression of sarcasm because of an accident. Ironically, that’s not it. It is an abbreviation of Antwort (answer) and was probably produced by

Re: “AW:” ?

On Wed, Jan 31, 2024 at 11:20 AM John Howard wrote: > Lost in translation. > > Anybody here know what “AW:” in the Subject means? > Should be German version of "RE: " > > At first, I took it to mean a comical expression of sarcasm because of an > accident

Re: “AW:” ?

I believe it's the German equivalent of "Re:" - Andrew On 1/31/24, 11:20 AM, "users" wrote: Lost in translation. Anybody here know what “AW:” in the Subject means? At first, I took it to mean a comical expression of sarcasm because of an accident. Ironically

Re: AW: Rust on RTEMS

Hello Jan, cool progress! Looking forward to test once things settles a bit, although I'm more of thumb person in arm world. :-) Thanks for sharing! Karel On 1/30/24 11:03, Frank Kühndel wrote: On 1/29/24 19:27, jan.som...@dlr.de wrote: Hi everyone, Sorry for the delayed response. Yes, th

Re: Rust on RTEMS

On 1/30/24 14:08, jan.som...@dlr.de wrote: -Ursprüngliche Nachricht- Von: Frank Kühndel Gesendet: Dienstag, 30. Januar 2024 11:03 An: Sommer, Jan;j...@rtems.org Cc:dwaine.s.mol...@nasa.gov;users@rtems.org Betreff: Re: AW: Rust on RTEMS Hello Jan, thanks for the info and all your

Re: AW: Rust on RTEMS

Jan Von: Joel Sherrill Gesendet: Mittwoch, 20. Dezember 2023 23:38 An: Frank Kühndel Cc: Molock, Dwaine S. (GSFC-5820);rtems-us...@rtems.org ; Sommer, Jan Betreff: Re: Rust on RTEMS Karel Gardas posted in February that he has Rust on RTEMS on an arm. Frank. Are there instructions on building th

RE: RTEMS 5.0.0 GR712RC SMP Occasional Dropped Messages

Hi Sebastian, Thanks for your reply! OK, we will investigate an update to RTEMS 6. Regards, Don -Original Message- From: Sebastian Huber Sent: Monday, January 22, 2024 11:06 PM To: Don Oliver Cc: users Subject: Re: RTEMS 5.0.0 GR712RC SMP Occasional Dropped Messages [You don&#

Re: RTEMS 5.0.0 GR712RC SMP Occasional Dropped Messages

Hello Don Oliver, with the information you provided it is hard to figure out what is going on. RTEMS 5.0.0 is not an RTEMS release. The problem you described could be caused by an operating system bug or an application issue. I recommend to first update to the current RTEMS master branch (RTEMS

Re: riscv target spec for newlib and rtems

On Sat, Dec 30, 2023, 9:45 AM Matt Wette wrote: > The build from git master worked (but first try I ran out of disk space: > needs > 10 G for the build. > That's good news that it built. We need to check the Users Guide to see if it has disk space recommendations. Did you see any? Personally,

Re: Rust on RTEMS

On Sun, Jan 7, 2024 at 2:22 AM Karel Gardas wrote: > > On 12/22/23 18:36, Joel Sherrill wrote: > > It's not a huge secret. :) > > > > https://activities.esa.int/4000140242 > > shows an ~EU175 project was awarded > > to DLR. From there, Jan Sommer is the on

Re: riscv target spec for newlib and rtems

On 30/12/2023 1:05 pm, Joel Sherrill wrote: > Chris... I thought the RSB was ok for Python 3 for RTEMS 5? Is it just on the > branch?  Sorry I am not sure what the status is. > Matt..can you try the tip of the 5 branch? Looking at the log, I see commit > messages about Python 3. This is the way

modular networking Was: Re:

Hi Shreyas Udaya, That ticket work has been "completed" but there remains quite a lot of interesting work to be done on the networking stack improvements especially for lwIP integration and the new rtems-net-services repo. Feel free to drop by Discord and see if you can find anyone to chat about i

Re: Rust on RTEMS

On 12/22/23 18:36, Joel Sherrill wrote: It's not a huge secret. :) https://activities.esa.int/4000140242 shows an ~EU175 project was awarded to DLR.   From there, Jan Sommer is the only person at DLR who has mentioned this. I understand wanting someone

Re: riscv target spec for newlib and rtems

The v5 source-builder does not work on python3 machines and current RTEMS release is 5.2 (or 5.1 if you go to www.rtems.org.   I did find v6.1-rc1  by guessing the path based on the 5.1 release path. I decided to take a shot at building on my own.   I've done this sort of thing before (e.g., bu

Re: riscv target spec for newlib and rtems

Sounds like you are trying to do this by hand. The RTEMS Source Builder (RSB) is the recommended way to build tools. See https://docs.rtems.org/branches/master/user/index.html for detailed instructions on the required packages on your host and how to use the RSB. The RSB fetches, patches, and buil

Re: Rust on RTEMS

On 12/22/23 18:36, Joel Sherrill wrote: It's not a huge secret. :) https://activities.esa.int/4000140242 shows an ~EU175 project was awarded to DLR.   From there, Jan Sommer is the only person at DLR who has mentioned this. Wow! So we may finally get s

Re: Rust on RTEMS

On Fri, Dec 22, 2023 at 7:40 AM Frank Kühndel < frank.kuehn...@embedded-brains.de> wrote: > Hello Joel, > > On 12/20/23 23:37, Joel Sherrill wrote: > > Karel Gardas posted in February that he has Rust on RTEMS on an arm. > > This is one email from that thread: > https://lists.rtems.org/pipermail/d

Re: Rust on RTEMS

Hello Joel, On 12/20/23 23:37, Joel Sherrill wrote: Karel Gardas posted in February that he has Rust on RTEMS on an arm. This is one email from that thread: https://lists.rtems.org/pipermail/devel/2023-March/074532.html Frank. Are there instructions on building the tools chain somewhere? I

Re: Rust on RTEMS

Karel Gardas posted in February that he has Rust on RTEMS on an arm. Frank. Are there instructions on building the tools chain somewhere? And is Jan Sommer part of the DLR Rust on RTEMS project? --joel On Wed, Dec 20, 2023, 3:59 PM Frank Kühndel < frank.kuehn...@embedded-brains.de> wrote: > He

Re: Rust on RTEMS

Hello Dwaine, On 12/20/23 20:41, Molock, Dwaine S. (GSFC-5820) wrote: > Hello, > > Has anyone been able to execute Rust on RTEMS? Yes – to use RTEMS from within a Rust application, with #![no_std] #![no_main] > > If so, is there a how to guide and what architecture and development hardware wa

Re: rtems6 master on darwin-x86_64 fails building: arm-rtems6-gcc-814ec21-newlib-fbc5496-x86_64-apple-darwin22.6.0-1

On 19/10/2023 6:25 am, 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 configuration still the same error: >>> nclude -g -O2 -mthumb -O2 >>> -I../../../../gcc-13.2.0/libgcc/../newlib/libc/sys/rtems

Re: RTEMS Development on Zynq 7000 Board

Dear Florian, we are using Zynq 7000 as the base for our projects, education, motion control and CAN/CAN FD development. For Linux and RTEMS now. We are starting RTEMS CAN/CAN FD revwrite/bring-up project. I am actually preparing some initial steps progress report for RTEMS devel list now. We us

Re: RTEMS Development on Zynq 7000 Board

Hi Florian, Thanks for asking. I am not working on that project anymore. We definitely brought up RTEMS to run on ARTY with some tinkering behind it, but we could not open-source our setup due to lack of time. I am most certain that we used the xilinx_zynq_zc702 configuration as a base. Now I don'

Re: rtems6 master on darwin-x86_64 fails building: arm-rtems6-gcc-814ec21-newlib-fbc5496-x86_64-apple-darwin22.6.0-1

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 configuration still the same error: >>> nc

Re: rtems6 master on darwin-x86_64 fails building: arm-rtems6-gcc-814ec21-newlib-fbc5496-x86_64-apple-darwin22.6.0-1

Good morning Sebastian, when I use 7/rtems-arm it does not get better unfortunately : [junkes@h XILINX_ZYNQ_A9_QEMU]$ tail -1000 ./rsb/rtems/rsb-report-arm-rtems7-gdb-29736fc-x86_64-apple-darwin22.6.0-1.txt RTEMS Tools Project - Source Builder Error Report Build: error: building arm-rtems7-gdb-

Re: rtems6 master on darwin-x86_64 fails building: arm-rtems6-gcc-814ec21-newlib-fbc5496-x86_64-apple-darwin22.6.0-1

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 configuration still the same error: >> nclude -g -O2 -mthumb -O2 >> -I../../../../gcc-13.2.0/libgcc/../newlib/libc/sys/rtems/include -g -O2 >> -DIN_GCC -DCROSS_DIRECTORY_ST

Re: rtems6 master on darwin-x86_64 fails building: arm-rtems6-gcc-814ec21-newlib-fbc5496-x86_64-apple-darwin22.6.0-1

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: ../source-builder/sb-set-builder --prefix=${RTEMS_ROOT} --with-rtems-gcc=tools/rtems-gcc-10-newlib-head.cfg 6/rtems-arm ... /bin/sh ../../libtool --tag CXX --t

Re: rtems6 master on darwin-x86_64 fails building: arm-rtems6-gcc-814ec21-newlib-fbc5496-x86_64-apple-darwin22.6.0-1

Leider gibt es da noch andere Probleme? I have now tried to build with gcc-10 and rsb-master: ../source-builder/sb-set-builder --prefix=${RTEMS_ROOT} --with-rtems-gcc=tools/rtems-gcc-10-newlib-head.cfg 6/rtems-arm ... /bin/sh ../../libtool --tag CXX --tag disable-shared --mode=compile /Volu

Re: rtems6 master on darwin-x86_64 fails building: arm-rtems6-gcc-814ec21-newlib-fbc5496-x86_64-apple-darwin22.6.0-1

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 -I../../../../gcc-13.2.0/libgcc/../newlib/libc/sys/rtems/include -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-

Re: rtems6 master on darwin-x86_64 fails building: arm-rtems6-gcc-814ec21-newlib-fbc5496-x86_64-apple-darwin22.6.0-1

Hello Sebastian, unfortunately also with the GCC 13.2 configuration still the same error: nclude-g -O2 -mthumb -O2 -I../../../../gcc-13.2.0/libgcc/../newlib/libc/sys/rtems/include -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wstrict-prot

Re: rtems6 master on darwin-x86_64 fails building: arm-rtems6-gcc-814ec21-newlib-fbc5496-x86_64-apple-darwin22.6.0-1

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-arm On 18.10.23 09:44, Heinz Junkes wrote: Hello Sebastian, thank you for your answer. Unfortunately, it seems to ha

Re: rtems6 master on darwin-x86_64 fails building: arm-rtems6-gcc-814ec21-newlib-fbc5496-x86_64-apple-darwin22.6.0-1

Hello Sebastian, thank you for your answer. Unfortunately, it seems to have nothing to do with it: [junkes@h rsb ((a536dfe...))]$ git status HEAD detached at a536dfe U/rsb/rtems/build/arm-rtems6-gcc-506cb58-newlib-fbc5496-x86_64-apple-darwin22.6.0-1/gnu-mirror-gcc-506cb58/newlib/libc/include -

Re: rtems6 master on darwin-x86_64 fails building: arm-rtems6-gcc-814ec21-newlib-fbc5496-x86_64-apple-darwin22.6.0-1

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-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 -

RE: Windows 11 - Compiling toolchain (5.3 and 6)

that PC. Thanks, Chris Thomas -Original Message- From: Sebastian Huber Sent: Thursday, October 12, 2023 11:21 AM To: Chris Thomas ; users@rtems.org Subject: Re: Windows 11 - Compiling toolchain (5.3 and 6) Hello Chris, some of our customers use WSL2 with Ubuntu, they reported no issues

  1   2   3   4   5   6   7   8   9   10   >