Re: INTERNAL_ERROR_BAD_THREAD_DISPATCH_ENVIRONMENT

2018-02-19 Thread Joel Sherrill
On Feb 19, 2018 6:55 PM, "Chris Johns" wrote: On 20/02/2018 00:13, Matthew J Fletcher wrote: > All, > > Replying to my own post, with CPU_ENABLE_ROBUST_THREAD_DISPATCH set FALSE i get > a fatal exception, this on a Cortex-M7, rtems 5.0.0 from git. > > I think i will have to

Re: RTEMS Toolchain building failed for ARM

2018-02-19 Thread Chris Johns
On 19/02/2018 17:11, zhang heng wrote: > Dear, >    I am busy in doing my homework some days ago,so I have no time to respond > your letter.  >    I have updated mingw-w64-x86_64-gcc to 7.3.0 and have installed all > packages > according to the manual >

Re: INTERNAL_ERROR_BAD_THREAD_DISPATCH_ENVIRONMENT

2018-02-19 Thread Chris Johns
On 20/02/2018 00:13, Matthew J Fletcher wrote: > All, > > Replying to my own post, with CPU_ENABLE_ROBUST_THREAD_DISPATCH set FALSE i > get > a fatal exception, this on a Cortex-M7, rtems 5.0.0 from git. > > I think i will have to work around the new behavior somehow. > I would view this as

INTERNAL_ERROR_BAD_THREAD_DISPATCH_ENVIRONMENT

2018-02-19 Thread Matthew J Fletcher
Hi, I've seen this in our application in certain use cases, if my understanding is correct (an it might not be), it comes from RTEMS_SCORE_ROBUST_THREAD_DISPATCH, via CPU_ENABLE_ROBUST_THREAD_DISPATCH. It only seems to be TRUE for Arm, which seems a bit inconstant. However i dont really

Re: INTERNAL_ERROR_BAD_THREAD_DISPATCH_ENVIRONMENT

2018-02-19 Thread Matthew J Fletcher
All, Replying to my own post, with CPU_ENABLE_ROBUST_THREAD_DISPATCH set FALSE i get a fatal exception, this on a Cortex-M7, rtems 5.0.0 from git. I think i will have to work around the new behavior somehow. -- regards --- Matthew J Fletcher ___

Re: INTERNAL_ERROR_BAD_THREAD_DISPATCH_ENVIRONMENT

2018-02-19 Thread Matthew J Fletcher
For those interested the callstack looks like this; bsp_fatal_extension() at bspclean.c:32 0x700d42ba _User_extensions_Iterate() at userextiterate.c:175 0x700ef42a _User_extensions_Fatal() at userextimpl.h:307 0x700eb9b2 _Terminate() at interr.c:35 0x700eb9b2 _Internal_error() at interr.c:52

Re: INTERNAL_ERROR_BAD_THREAD_DISPATCH_ENVIRONMENT

2018-02-19 Thread Matthew J Fletcher
Hi Joel, Its possible interrupts are disabled. I am using the termios RTEMS_IO_RCVWAKEUP callback to get chars from console input. I accumulate them for a timer tick or two, then in a timer callback do rtems_message_queue_send() The callstack above this from the rtems_message_queue_receive() in

Re: INTERNAL_ERROR_BAD_THREAD_DISPATCH_ENVIRONMENT

2018-02-19 Thread Joel Sherrill
On Mon, Feb 19, 2018 at 10:20 AM, Matthew J Fletcher wrote: > Hi Joel, > > Its possible interrupts are disabled. I am using the > termios RTEMS_IO_RCVWAKEUP callback to get chars from console input. I > accumulate them for a timer tick or two, then in a timer callback > do

Re: INTERNAL_ERROR_BAD_THREAD_DISPATCH_ENVIRONMENT

2018-02-19 Thread Joel Sherrill
Based on the code, it looks like you have interrupts disabled when you are making the call to rtems_region_get_segment(). For sure, you shouldn't free memory from an ISR though. On Mon, Feb 19, 2018 at 9:33 AM, Matthew J Fletcher wrote: > For those interested the callstack