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 <[email protected]> wrote: > > > On Fri, Nov 1, 2019, 11:24 AM Mathew Benson <[email protected]> > 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 know where it would be pending. The task is accessing >> NOR drivers. But just by running the shell command, releases that priority >> 235 task. In fact, any command releases it. Whether its a valid command >> or not. But if I remove the shell from the build, everything is fine. The >> task doesn't pend. It executes as it should. Did I miss something in the >> documentation regarding integration of the shell? Is there something we >> are or are not supposed to do when the shell is integrated? >> > > I'm off today and this is from my phone. > > TIME should indicate that the task is sleeping. Assuming these are not > POSIX thread priority The priority 235 task has to be blocked or the shell > task won't run at all. So anytime your shell task runs, the others should > be blocked. > > --joel > >> >> -- >> *Mathew Benson* >> CEO | Chief Engineer >> Windhover Labs, LLC >> 832-640-4018 >> >> >> www.windhoverlabs.com >> >> _______________________________________________ >> users mailing list >> [email protected] >> http://lists.rtems.org/mailman/listinfo/users > > -- *Mathew Benson* CEO | Chief Engineer Windhover Labs, LLC 832-640-4018 www.windhoverlabs.com
_______________________________________________ users mailing list [email protected] http://lists.rtems.org/mailman/listinfo/users
