Re: GSoC'18-Introduction

Am 02.03.2018 um 07:43 schrieb Chris Johns: > On 02/03/2018 17:12, Christian Mauderer wrote: >> Am 02.03.2018 um 00:53 schrieb Chris Johns: I think it would be a good idea to take a look at the boot process first: We have two situations: 1. U-Boot does loads a FDT at a spec

Re: GSoC'18-Introduction

On Thu, Mar 1, 2018 at 10:12 PM, Christian Mauderer wrote: > Am 02.03.2018 um 00:53 schrieb Chris Johns: >> On 01/03/2018 18:42, Christian Mauderer wrote: >>> Am 01.03.2018 um 08:07 schrieb Russell Haley: On Wed, Feb 28, 2018 at 3:24 AM, Udit agarwal wrote: > Hi, > Sorry for la

Re: GSoC'18-Introduction

On 02/03/2018 17:12, Christian Mauderer wrote: > Am 02.03.2018 um 00:53 schrieb Chris Johns: >>> >>> I think it would be a good idea to take a look at the boot process >>> first: We have two situations: >>> >>> 1. U-Boot does loads a FDT at a specified address and provides that >>> address to the R

Re: INTERNAL_ERROR_THREAD_EXITTED, but what thread ?

Am 02.03.2018 um 02:59 schrieb Joel Sherrill: > > > On Mar 1, 2018 11:03 AM, "Matthew J Fletcher" > wrote: > > Hi, > > So if a thread returns without deleting itself you get the following > error,.. but may i make the observation that it might be more >

Re: INTERNAL_ERROR_THREAD_EXITTED, but what thread ?

Ok I will do, I've got a breakpoint in bsp_fatal_exception and I can see up the callstack there are lots of contexts and structures, does one of them already hold the previously executing task ? On 2 Mar 2018 01:59, "Joel Sherrill" wrote: On Mar 1, 2018 11:03 AM, "Matthew J Fletcher" wrote:

Re: GSoC'18-Introduction

Am 02.03.2018 um 00:53 schrieb Chris Johns: > On 01/03/2018 18:42, Christian Mauderer wrote: >> Am 01.03.2018 um 08:07 schrieb Russell Haley: >>> On Wed, Feb 28, 2018 at 3:24 AM, Udit agarwal wrote: Hi, Sorry for late reply, i am having my mid term examinations ongoing. So as o

Re: INTERNAL_ERROR_THREAD_EXITTED, but what thread ?

On Mar 1, 2018 11:03 AM, "Matthew J Fletcher" wrote: Hi, So if a thread returns without deleting itself you get the following error,.. but may i make the observation that it might be more helpful print the rtems_name of said thread ? *** FATAL *** fatal source: 0 (INTERNAL_ERROR_CORE) fatal cod

Re: error: checksum failure file: sources/expat-2.1.0.tar.gz

I see expat is now hosted on github. I will update the RSB https://devel.rtems.org/ticket/3315 Chris ___ users mailing list users@rtems.org http://lists.rtems.org/mailman/listinfo/users

Re: error: checksum failure file: sources/expat-2.1.0.tar.gz

On 02/03/2018 01:53, leonardo wrote: > > I am try to download RTEMS source builder and build a tool chain following the > instruction in this page > . The problem > that > I have seems to be a package download automatically through /so

Re: GSoC'18-Introduction

On 01/03/2018 18:42, Christian Mauderer wrote: > Am 01.03.2018 um 08:07 schrieb Russell Haley: >> On Wed, Feb 28, 2018 at 3:24 AM, Udit agarwal wrote: >>> Hi, >>> Sorry for late reply, i am having my mid term examinations ongoing. >>> >>> So as of now, I'm having following two short term tasks: >>

INTERNAL_ERROR_THREAD_EXITTED, but what thread ?

Hi, So if a thread returns without deleting itself you get the following error,.. but may i make the observation that it might be more helpful print the rtems_name of said thread ? *** FATAL *** fatal source: 0 (INTERNAL_ERROR_CORE) fatal code: 5 (INTERNAL_ERROR_THREAD_EXITTED) RTEMS version: 5.0

error: checksum failure file: sources/expat-2.1.0.tar.gz

Dear all, I am try to download RTEMS source builder and build a tool chain following the instruction in this page . The problem that I have seems to be a package download automatically through /sourceforge.net/: it seems that the