Dynamically allocate a RTX mailbox

No it is still is just as incorrect. The box allocated mailbox will be valid no longer than the stack allocated mailbox. If the os_mbx_wait times out after 10 OS_TMR_TICKS, you are hosed both ways.

The only reason I showed how to dynamically allocate a mailbox was because that is what the OP asked, not because I would use the feature. It is VERY hard to make correct code that provides something usefull with a dynamic mailbox. It is better to use something that is actually helps you to create correct code. You would much better off using either a single static mailbox per task or a event. I would probably use the event, because it could be "hidden" (i.e the task calling the CommFunc does not need to have any prior knowledge of the Event use - which was the benefit you were trying to gain by using the dynamic mailbox in the first place)

No it is still is just as incorrect. The box allocated mailbox will be valid no longer than the stack allocated mailbox. If the os_mbx_wait times out after 10 OS_TMR_TICKS, you are hosed both ways.

The only reason I showed how to dynamically allocate a mailbox was because that is what the OP asked, not because I would use the feature. It is VERY hard to make correct code that provides something usefull with a dynamic mailbox. It is better to use something that is actually helps you to create correct code. You would much better off using either a single static mailbox per task or a event. I would probably use the event, because it could be "hidden" (i.e the task calling the CommFunc does not need to have any prior knowledge of the Event use - which was the benefit you were trying to gain by using the dynamic mailbox in the first place)

I have posted to this thread as i think its of the same vain!

I have a multiple (4of)task application passing messages via mailbox's (2of). I have one mailbox and its associated tasks works fine, i have a second task the call to the mail box works fine, however refuses to call the function within the task. See code below

this task works fine

void tcp_task (void) __task {

U8 *ptr_tcp_task_msg;

while (1) {

 if(os_mbx_wait(TCP_task_msg_box, (void**)&ptr_tcp_task_msg, 0x0000) == OS_R_OK ){
/* if we have received a message decided what action to take */
   switch(*ptr_tcp_task_msg){
       case TCPTASK_DNS_ROUTINE:
       start_DNS_resolve((dns_struct*)tcp_task_msg);
       break;

    default:
       start_DNS_resolve((dns_struct*)tcp_task_msg);
       break;
    }
}

                        /* DNS routine */
 if ( dns_resolve.DNS_active == __TRUE){
  get_host_by_name((U8*)dns_resolve.ptr_dns_task_data->name, dns_cbfunc);
  }

  main_TcpNet();
  os_tsk_pass();
  }
}

This mailbox functions fine however,

The one below fails the message arrives will break on UARTSend function can see data in via message pointer but, fails to call function moves to os_tsk_pass.

void communication_task (void) __task{

global_msg_struct *ptr_global_msg;

   while (1) {

    if(os_mbx_wait(communication_task_msg_box,void**&ptr_global_msg, 0xFFFF) == OS_R_OK ){
/* if we have received a message decided what action to take */
    //init_serial_port0();
    UARTSend((U8*) ptr_global_msg->tx_data );

    }
  os_tsk_pass();
  }
}

Any comments welcome on the topic, tried calling a simpler function init_serial_port() this fails in same way. Though when called from init_task at start functioned ok.

The mailbox in the second case is external linked using OS_MBX as its in included file, but the mail box itself seems to work fine.

Obviously issue with the boxes i guess any pointers? excuse the pun, or similar issues in the past.

regards
Darren