The question is whether your driver is actually pending indefinitely as you
think, or just the shell is running during the small sleeps.
On Sat, Nov 2, 2019, 9:06 AM Joel Sherrill wrote:
>
>
> On Sat, Nov 2, 2019, 12:03 AM wrote:
>
>> That’s kind of my point. The low priority shell task is
On Sat, Nov 2, 2019, 12:03 AM wrote:
> That’s kind of my point. The low priority shell task is working
> perfectly. The higher priority task is pended by time. I do have some
> sleep functions in the driver code but they are short sleeps. They
> shouldn’t just pens indefinitely until a run
That’s kind of my point. The low priority shell task is working perfectly.
The higher priority task is pended by time. I do have some sleep functions in
the driver code but they are short sleeps. They shouldn’t just pens
indefinitely until a run any random command in the shell. Unless I’m
On Fri, Nov 1, 2019 at 12:33 PM Gedare Bloom wrote:
>
> On Fri, Nov 1, 2019 at 10:52 AM Mathew Benson
> wrote:
>
>> So no matter what priority the shell task is initialized as, it preempts
>> all other tasks?
>>
>> No.
>
But an odd artifact of looking at the status of threads in the shell is
On Fri, Nov 1, 2019 at 10:52 AM Mathew Benson
wrote:
> So no matter what priority the shell task is initialized as, it preempts
> all other tasks?
>
> No.
With low priority (250) under the default scheduling (fixed priority
round-robin), the shell would only run when higher priority tasks are
So no matter what priority the shell task is initialized as, it preempts
all other tasks?
On Fri, Nov 1, 2019 at 11:36 AM Joel Sherrill wrote:
>
>
> On Fri, Nov 1, 2019, 11:24 AM Mathew Benson
> wrote:
>
>> My shell task is set to priority 250. I have another task that I've set
>> to a
On Fri, Nov 1, 2019, 11:24 AM Mathew Benson
wrote:
> My shell task is set to priority 250. I have another task that I've set
> to a priority of 235. When I have the shell in the build, that priority
> 235 task appears to pend indefinitely with the shell reporting state =
> "TIME" and I don't
My shell task is set to priority 250. I have another task that I've set to
a priority of 235. When I have the shell in the build, that priority 235
task appears to pend indefinitely with the shell reporting state = "TIME"
and I don't know where it would be pending. The task is accessing NOR
