• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 51 subscribers
  • Views 434 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

another way fall into sdk_error_handler()

shali lv
Intellectual 360 points

I have made a blue tooth modul using BT5190 and PAN1325. It's program is based on ez430-accl program with some modifications. Now it works as a brige transfering data to my desk PC. The problem is: It's program will fall into sdk_error_handler() if I take it away from my desk PC and out of range of  blue tooth signal when it is transfering data. That is to say: it will stop work and fall into dead loop in sdk_error_handler().  I don't hope it falling into dead loop, It can stop work when out range and should rebuild link and work again when it is back into the range of  blue tooth.

  • 0
    Intellectual 360 points

    ...continued

    the call tack is like this when it falls into sdk_error_handler()

    sdk_error_handler()
    BT_alloc_mem()
    rfcomm_transmit_data()
    rfcomm_write_bh()
    wt_service_queue()
    write_task_start_routine()
    [PC=Memory:0x2FE]

    who can tell me what's  wrong with BT_alloc_mem()? how can I avoid fall into adk_error_handler()? I just want my blue tooth modul disconnects with desk PC when it is far away from PC and reconnects with PC when it comes back into the range of blue tooth distance.

     

  • 0 in reply to Miguel
    Intellectual 360 points

    Thank Miguel,

    I have read those posts you mentioned. sdk_error_handler() is really has relationship with how many bytes BT_spp_send() send. generally to say, 110 bytes is up limit. But I just let BT_spp_send()  send 32 bytes data onec a time. and my problem is happend at the condition of in range working well and then out of range working fault. Now I cut down bytes to 16 once a time BT_spp_send() called. Though the  problem of BT_alloc_mem() is solved, but  new problem of  hci_hardware_error_event() happend.  the call stack like this:

    sdk_error_handler()

    hci_hardware_error_event()

    hci_transport_read_data()

    ht_read_task_start_routine()

    What's the error of hci_hardware?