On 23/06/2021 17:51, jan.som...@dlr.de wrote:
You probably have a general memory corruption issue. As a first step I would
enable RTEMS_DEBUG = True to enable the heap protection. This could help
to debug the issue.
With this enabled a few asserts failed during early system initialization
On Wed, Jun 23, 2021 at 9:52 AM wrote:
>
>
>
> > -Original Message-
> > From: Sebastian Huber
> > Sent: Wednesday, June 23, 2021 11:47 AM
> > To: Sommer, Jan ; users@rtems.org
> > Subject: Re: Heap allocation for libbsd overwrites IMFS
> >
> >
> >
> > On 23/06/2021 10:32,
> -Original Message-
> From: Sebastian Huber
> Sent: Wednesday, June 23, 2021 11:47 AM
> To: Sommer, Jan ; users@rtems.org
> Subject: Re: Heap allocation for libbsd overwrites IMFS
>
>
>
> On 23/06/2021 10:32, jan.som...@dlr.de wrote:
> > One of our applications for the Zedboard
On Wed, Jun 23, 2021, 4:47 AM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
>
>
> On 23/06/2021 10:32, jan.som...@dlr.de wrote:
> > One of our applications for the Zedboard fails with fatal error after
> the setup of the network stack in libbsd.
> > So far I traced it down to the
On 23/06/2021 10:32, jan.som...@dlr.de wrote:
One of our applications for the Zedboard fails with fatal error after the setup
of the network stack in libbsd.
So far I traced it down to the point that the memory allocation for libbsd
overwrites parts of the IMFS of rtems.
When opening device
