Statically allocated build

Hello everyone! I am currently creating a aerial robot application upon the arm/stm32f4 bsp (extending it, possibly will contribute soon) I have just moved from RTEMS5 to RTEMS6 and have a few questions. 1. I don't understand how to build a system fully statically allocated. For safety reasons I

Re: Virtual UART

Hi! > Can anyone point us to documentation on how to do this for a generic non-console UART? The simplest way is to disable compilation of the console from your bsp build settings or switch console-mapped uart to another one. Best regards. Peter Borisenko Awesome Technologies, Ltd.

Re: Statically allocated build

No. there is no filesystem. The application is build upon the stm32f4 bsp, and linker script's kept unchanged. On Tue, Sep 28, 2021, 8:28 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > Hello, > > On 24/09/2021 20:08, Петр Борисенко wrote: > > Hel

Re: Statically allocated build

Oh, I got it. Does FS enabled by default and I am supposed to disable it during the build process? On Tue, Sep 28, 2021, 2:52 PM Петр Борисенко wrote: > No. there is no filesystem. > The application is build upon the stm32f4 bsp, and linker script's kept > unchanged. > > > On

Static allocation

Hello! Is it possible to compile Rtems statically and disable memory allocation routines and heap? ___ users mailing list users@rtems.org http://lists.rtems.org/mailman/listinfo/users

Re: Static allocation

Sherrill wrote: > > > On Tue, Sep 28, 2021, 6:43 AM Петр Борисенко wrote: > >> Hello! >> Is it possible to compile Rtems statically and disable memory allocation >> routines and heap? >> > > No. You have to restrict your application use of APIs and se

Re: Static allocation

ote: > > > > On Tue, Sep 28, 2021, 10:05 AM Петр Борисенко wrote: > >> Seems pretty obvious, but I mean kernel. When I define a queue or a task, >> will it compile statically or it will get memory from heap during the >> initialization? @Sebastian Huber >

RTEMS_FATAL_SOURCE_EXCEPTION during startup

Hello and Happy new year! I am getting an error during startup: RTEMS_FATAL_SOURCE_EXCEPTION Catching it in _ARM_Exception_default. The bsp is `arm/stm32f4`. Here is contains of CPU_Exception_frame: register_r0 uint32_t 0x80139bc register_r1 uint32_t 0 register_r2 uint32_t 0 register_r3 uint32_t

Re: RTEMS_FATAL_SOURCE_EXCEPTION during startup

“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 anything explisitly. > Here is call stack

Re: RTEMS_FATAL_SOURCE_EXCEPTION during startup

is going on wrong! Best regards. Peter Borisenko Awesome Technologies, Ltd. http://awsmtek.com hardw...@awsmtek.com +79062165482 On Sun, Jan 2, 2022 at 1:25 AM Joel Sherrill wrote: > > > On Sat, Jan 1, 2022, 4:02 PM Петр Борисенко wrote: > >> Ok I see. >> The master bra

Re: RTEMS_FATAL_SOURCE_EXCEPTION during startup

e > > > > and make sure that all of the functions have the same architecture > > specified. Mine had a mix of -mcpu=cortex-m4 and -mcpu=arm7tdmi which are > > incompatible. > > > > > > > > Andrei Chichak > > (from The Great White North) >

Re: Want to add RISC-V-based PolarFire SoC support to RTEMS

Wow, I thought I will do it alone soon. Also interested Best regards. Peter Borisenko Awesome Technologies, Ltd. http://awsmtek.com hardw...@awsmtek.com +66826684211 On Wed, Aug 24, 2022 at 2:14 PM wrote: > Hi, > > I want to add a new BSP for RISC-V-based Microchip PolarFire SoC(MPFS) > to