Re: Building RTEMS tools using Source Builder fails

2017-10-12 Thread groups
I was building the 4.12 tools for ARM using RSB yesterday and the build would randomly fail. Unfortunately, to fix it, I’d delete everything and try again. Trying again is a very unsatisfying solution. I passed it off as a git repository inconsistency. On the other hand, doing a git checkout

dead servers

2017-10-18 Thread groups
I was trying to get the 4.12 tools working but some of the rtems.org servers used for git in RSB are giving 503s. Andrei___ users mailing list users@rtems.org http://lists.rtems.org/mailman/listinfo/users

Re: dead servers

2017-10-18 Thread groups
devel.rtems.org is dead and the ones that are referred to in source builder. A > On 2017-October-18, at 23:10, Chris Johns wrote: > > On 19/10/2017 15:55, gro...@chichak.ca wrote: >> I was trying to get the 4.12 tools working but some of the rtems.org >>

Re: I've got a problem compiling the 4.11 tools for ARM (fancy_abort)

2017-10-24 Thread groups
I was hoping to go there later but, this is the script that I am using to build the BSP for 4.12: cd cd development/rtems mkdir kernel cd kernel git clone git://git.rtems.org/rtems.git rtems cd rtems ./bootstrap -c && ./bootstrap -p && $HOME/development/rtems/rsb/source-builder/sb-bootstrap cd

Re: I've got a problem compiling the 4.11 tools for ARM (fancy_abort)

2017-10-24 Thread groups
Same thing, I tried that too. I can’t make up that syntax, I do embedded applications not obscure UNIX hieroglyphics. I got it out of a quick start guide from RTEMS.org somewhere. Andrei > On 2017-October-24, at 01:01, Sebastian Huber >

I've got a problem compiling the 4.11 tools for ARM (fancy_abort)

2017-10-24 Thread groups
Hello, I’m attempting to get a BSP rolling for STM32F767 and 4.12 is going reasonably poorly, so I am trying to regress back to a BSP for stm32f4 on 4.11. Now, when putting together the tools for 4.11, I use the script: cd mkdir -p development/rtems cd development/rtems git clone

Re: I've got a problem compiling the 4.11 tools for ARM (fancy_abort)

2017-10-24 Thread groups
Okay, here is the 4.12 build for stm32f4 (it’s something different today): Generating ./c/src/lib/libcpu/m68k/preinstall.am Generating ./c/src/lib/libcpu/powerpc/preinstall.am Generating ./c/src/lib/libcpu/lm32/preinstall.am Generating ./c/src/lib/libcpu/or1k/preinstall.am Generating

An issue with ARM interrupts revisits.

2017-11-21 Thread groups
Back in June 2015 I reported an issue where my program would crash after a very predictable period when working with rtems_event_receive. Sebastian and I tracked the problem down to an issue with the priorities of my interrupts causing an infinite loop in the dealings with “Watchdog” values in

Re: Stack_check_Dump_threads_usage printing out the wrong values

2017-11-16 Thread groups
> On 2017-November-15, at 16:10, Chris Johns wrote: > > On 16/11/2017 09:50, Mr. Andrei Chichak wrote: >> I’m working with 4.12 for ARM (cortex M7) >> >> I’m tracing down an issue and figured it smelled like a stack problem, so I >> got >> my command line interpreter to

Re: Stack_check_Dump_threads_usage printing out the wrong values

2017-11-16 Thread groups
I fear blowing up builds all over the world, but I’ll give it a try. A > On 2017-November-16, at 21:21, Chris Johns wrote: > > On 17/11/2017 15:05, gro...@chichak.ca wrote: >> >> (I don’t know how to proceed with getting this reported/fixed.) >> > > Please head to the wiki

Re: I've got a problem compiling the 4.11 tools for ARM (fancy_abort)

2017-10-24 Thread groups
> > TypeError: cannot concatenate 'str' and 'general' objects > ./getRTEMS: line 18: > /Users/andreichichak/development/rtems/kernel/rtems/configure: No such file > or directory > make: *** No targets specified and no makefile found. Stop. > make: *** No rule to make target `install'. Stop. >

Re: Stitching in another BSP into V5

2018-09-05 Thread groups
Of course. I should have looked in there. Thank you for your help. A > On 2018-September-04, at 23:55, Sebastian Huber > wrote: > > Hello Andrei, > > you still need the BSP build files in "c", e.g. > > https://git.rtems.org/rtems/tree/c/src/lib/libbsp/arm/stm32f4 > > Build system

does RTEMS use libssh?

2018-10-16 Thread groups
Hi, there seems to be a protocol issue with libssh that allows the bypass of credentials. I was wondering if there are any parts of RTEMS that use libssh? Instead of butchering the explanation of a protocol that I don’t know, see CVE-2018-10933. I couldn’t find libssh on my RTEMS distro, but I

Re: RTEMS 5 build on a Mac with the latest compilers?

2018-09-19 Thread groups
My initial tests look very promising. I did a clean pull and build and the ARM tools built without complaint. I need to do more work on my STM32F767 BSP to get it into the new format, but the compile went through the motions well enough. Andrei > On 2018-September-18, at 19:08, Chris Johns

Re: RTEMS scheduler bug ?

2019-04-03 Thread groups
This sounds like a problem I had in 2015 on an STM32 that Sebastian helped me get around. At the end of the ordeal I wrote: "A bit of review to begin with; I am working with an STM32F4 ARM Cortex M4F processor’s ADC section. A feature of this ADC is the ability to have conversions triggered by

Re: stm32f4 __wfi

2019-06-21 Thread groups
Jython, You may have better luck asking on the ST support forums. Your questions relate more to the inner workings of the STM32 sleep and interrupt facilities and less about RTEMS. A > On 2019-June-20, at 18:58, Jython wrote: > > > handler

Re: function declare

2019-06-27 Thread groups
No, it has nothing to do with RTEMS in particular. Any C program will do this. > On 2019-June-27, at 21:17, Jython wrote: > > so it is rtems build requirement? > > On Thu, Jun 27, 2019 at 2:53 AM Mr. Andrei Chichak > wrote: > Assume that you are using C and C has a

Tick interrupt priority?

2019-09-18 Thread groups
I was reviewing the interrupt priorities on a project where I’m using FreeRTOS and they want the tick interrupt priority to be very low. I found this to be not obvious, then started wondering what the elders of the RTEMS suggest for use with RTEMS. Should the tick interrupt be high priority or

Re: Tick interrupt priority?

2019-09-18 Thread groups
Super, I’ll have to review my projects to see if I did it right. Granted, it should only come into play when there is interrupt contention, but these are the sorts of things that cause subtle issues. Thanks Chris, A > On 2019-September-18, at 22:32, Chris Johns wrote: > > On 19/9/19 2:16

RTEMS C++ examples?

2019-07-22 Thread groups
I’m trying to figure out how to get started with using C++ with RTEMS. Mostly as an academic endeavour to figure out what people are talking about when they say that C++ is so much better than C. Can anybody point me at any C++ sample code to create a couple of tasks, pass a message back and

Re: RTEMS C++ examples?

2019-07-24 Thread groups
I’m working on a bit of a hobby project right now and someone bullied me into trying C++. Fine. Plus I did say that I’d try it in anger at some point. So far I’ve managed to get a simple Init going that creates two tasks. I haven’t tried it yet, since it was 2AM when I finally got the right

Re: Link errors with an install using quick-start guide

2019-07-22 Thread groups
Thank you. Thank you. Thank you. Yes, of course, once I added the configuration section and changed main into an appropriately formatted Init, it compiles nicely. Thanks again, Andrei > On 2019-July-22, at 00:05, Sebastian Huber > wrote: > > On 22/07/2019 07:58, Mr. Andrei Chichak wrote:

Re: Issue with configure on MacOS

2021-01-05 Thread groups
> Any ideas or pointers? > > Did you forget to add something to c/src/libbsp? The autoconf builds system > files are under the old tree while all the code is under bsps/. This makes it > easier to remove the old build system when all is done. > > likely. In c/src/lib/libbsp/arm I created a

Segmentation fault 11 issue with gdb

2021-04-26 Thread groups
In my ongoing quest to bring up libbsd, I ran into an issue with gdb as built for RTEMS5. gdb 9.1 immediately gives a segmentation fault 11 as it has a fight with python3 version 3.9.2. I managed to find a good explanation of the problem at

Re: Pleiades Neo and RTEMS?

2021-08-16 Thread groups
https://www.youtube.com/watch?v=onGXURpR1bM_channel=RawSpace > On 2021-August-16, at 10:13, Joel Sherrill wrote: > > Hi > > I noticed that another Pleiades Neo satellite was launching later today. > > https://directory.eoportal.org/web/eoportal/satellite-missions/p/pleiades-neo > > My quick

Re: RTEMS_FATAL_SOURCE_EXCEPTION during startup

2022-01-01 Thread groups
(sorry, I accidentally sent this to the dev list instead of users. too much cheer) It’s bombing in printf. It’s so early that the stack hasn’t been set up yet, and it’s found an error and it’s trying to poot a message out on the console, which is also not set up yet. Umm, what could be wrong?

Re: RTEMS_FATAL_SOURCE_EXCEPTION during startup

2022-01-01 Thread groups
I reported this, Set fixed it, and the report was closed. Either someone said “multilib, multilib, multilib” and it came back, Peter needs to do a pull, or something has reverted. https://devel.rtems.org/ticket/4504 A > On 2022-January-01, at 13:56, Петр Борисенко wrote: > > I didn't print

Re: Question on rtems printf problem

2022-12-19 Thread groups
> On 2022-December-19, at 19:59, tia...@sugon.com > wrote: > > Hi: > I have a testcode, it will lead to uart print space forever. > > Demo code like this: > Init() > { > create a task; > start this task; >

Re: Question on rtems printf problem

2022-12-19 Thread groups
On 2022-December-19, at 19:59, tia...@sugon.com wrote: > > Hi: > I have a testcode, it will lead to uart print space forever. > > Demo code like this: > Init() > { > create a task; > start this task; >

Hands up, do you use the Mini Robomind BSP (MRM332)?

2022-12-01 Thread groups
Hi all, The Mini Robomind is a board that was available through the Seattle Robotics Society that used the Motorola MC68332 processor. The BSP is called MRM332. I was wondering if anybody uses this BSP, either for a Mini Robomind or as a basis for some other MC68332 board? Why? I was talking