Hi Petersen,
we are still facing issue for thread not working . we want to know how
the task get schedule and how it find the task_func entry point and
also how is switching happen.
please help on this.
Thanks
Shishir
On Wed, Jan 14, 2015 at 3:44 PM, Joakim Gebart joakim.geb...@eistec.se
Hi Shishir,
the scheduler is deciding which task is run next. During normal
operation, the behavior is intended as this:
- save the current context (register contents to the current stacks thread)
- run scheduler to determine the thread with the highest priority
- point a global variable
You can look at the startup files for other CPUs for a proper way of
doing initialization e.g. cpu/stm32f1/startup.c
Note that you must also make sure that your linker script provides the
correct symbols at the beginning and end of .data and .bss.
Best regards,
Joakim Gebart
Eistec AB
Hi Shishir,
when RIOT initially starts up, the CPU is normally running in interrupt
mode (using the interrupt mode stack). After creating the stacks for the
main and the idle threads, the CPU must be put into thread-mode. This
means the main threads initial context needs to put into the CPUs
