Thank you for the clarification.
On Thu, Jul 23, 2020 at 12:25 PM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
> On 23/07/2020 08:12, Richi Dubey wrote:
>
> > I am still having a hard time understanding this. What do you mean by
> > no code which blocks? Does the thread which exec
On 23/07/2020 08:12, Richi Dubey wrote:
I am still having a hard time understanding this. What do you mean by
no code which blocks? Does the thread which executes our task (Say a
function Loop with 30k loops) block? What does block mean here?
Block means here that the thread calls _Scheduler_
Thank you for the clarification.
I am still having a hard time understanding this. What do you mean by no
code which blocks? Does the thread which executes our task (Say a
function Loop with 30k loops) block? What does block mean here?
On Wed, Jul 22, 2020 at 7:46 PM Sebastian Huber <
sebastian.h
On 22/07/2020 15:36, Richi Dubey wrote:
Threads that get created automatically when a CPU starts have their
scheduler nodes with node->idle set to the thread itself, while the
nodes that are created due to a task being created have NULL in their
node->idle (If not using helper function atm).
Hi,
Please clear a doubt of mine.
Threads that get created automatically when a CPU starts have their
scheduler nodes with node->idle set to the thread itself, while the nodes
that are created due to a task being created have NULL in their node->idle
(If not using helper function atm). Am I righ
This helps. Thanks a lot.
On Tue, Jul 21, 2020 at 6:55 PM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
> On 21/07/2020 14:36, Richi Dubey wrote:
>
> > Could you please explain what _User_extensions_Thread_start does? It's
> > hard to understand it all by myself since it has a lot
On 21/07/2020 14:36, Richi Dubey wrote:
Could you please explain what _User_extensions_Thread_start does? It's
hard to understand it all by myself since it has a lot of other
information related to objects.
The brief for it says:
/**
* @brief Starts a thread.
*
* @param created The thread
Hi,
Could you please explain what _User_extensions_Thread_start does? It's hard
to understand it all by myself since it has a lot of other information
related to objects.
The brief for it says:
/**
* @brief Starts a thread.
*
* @param created The thread to start.
*/
This is exactly what my d
Hi,
_Thread_Clear_state_locked( the_thread, STATES_ALL_SET );
I did have a look at it, it unblocks the node belonging to the_thread, I'll
go through everything again.
When you use the debugger to figure out what is going on I would step in
> to each function you don't know.
Got it. Thank you.
On 20/07/2020 17:16, Richi Dubey wrote:
Hi,
I am trying to map out how a task gets scheduled according to a
scheduling algorithm once a user writes rtems_task_create() and later
rtems_task_start() in the source file.
On debugging with gdb, I came to realize that the
rtems_task_start() func
10 matches
Mail list logo
