Substituting IDLE task

[John Pickwick]

Not exactly ... I was expecting a simple macro that would have overriden the default Idle thread without having to recompile the BSP.

Thanx anyway :=)

John
  ----- Original Message ----- 
  From: Manuel Coutinho 
  To: 'John Pickwick' ; rtems-users at rtems.org 
  Sent: Friday, October 19, 2007 12:57 PM
  Subject: RE: Substituting IDLE task


  Hi

   

  I'm not sure I understood your question. Are you trying to replace the idle task of the Leon2 BSP?

  If so, you can found the body of the idle task on the setvec.c file. 

  This is the default idle task implemented on Leon2:

   

  /* LEON specific power-down function */

   

  void _CPU_Thread_Idle_body( void )

  {

    while (1) {

      LEON_REG.Power_Down = LEON_REG.Power_Down;   /* make sure on load follows store to power-down reg */

    }

  }

   

  If you want, you can change it any way you like, but you have to recompile RTEMS. A simple "make all install" is sufficient.

   

  Hope this answers your question.

   

  Regards

  Manuel Coutinho

  Edisoft 

   


------------------------------------------------------------------------------

  From: rtems-users-bounces+manuel.coutinho=edisoft.pt at rtems.org [mailto:rtems-users-bounces+manuel.coutinho=edisoft.pt at rtems.org] On Behalf Of John Pickwick
  Sent: Thursday, October 18, 2007 10:43 PM
  To: rtems-users at rtems.org
  Subject: Substituting IDLE task

   

  Hi,

   

  is it possible to substitute a task to the default IDLE task in the LEON2 BSP ?

  I found the CPU_IDLE_TASK macro that goes in the CPU_Table structure but I don't know if I need to recompile my BSP if I use it.

   

  Regards,

   

  John



------------------------------------------------------------------------------


  _______________________________________________
  rtems-users mailing list
  rtems-users at rtems.com
  http://rtems.rtems.org/mailman/listinfo/rtems-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20071019/9c0dc4b7/attachment-0001.html>