On 23/11/17 18:25, Mr. Andrei Chichak wrote:
One question though, where can I tap into the OS to figure out what priorities
my ISRs are actually using?
If there is something odd with the encoding that ST uses for priorities, I
could actually be fighting an issue with CubeMX for F7 that is caus
One question though, where can I tap into the OS to figure out what priorities
my ISRs are actually using?
If there is something odd with the encoding that ST uses for priorities, I
could actually be fighting an issue with CubeMX for F7 that is causing my ISRs
to be interpreted as NMIs again.
On 22/11/17 07:33, Sebastian Huber wrote:
I have absolutely no idea how you can end up in
_ARMV7M_Thread_dispatch() with an unexpected interrupt level.
I think if you call an operating system service which leads to a thread
dispatch in a NMI handler, then you could end up with this situation.
On 22/11/17 05:41, gro...@chichak.ca wrote:
Here is the situation, I have my ADCs set up to deliver results using
DMA 200 times per second using two interrupt routines. One routine is
called when the ADC buffer is half full, the other when the ADC buffer
is full. The interrupt routines execute
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 e
