5 Replies Latest reply on Mar 25, 2015 7:38 AM by MichaelF_56

    puart_control with BLE_APP_DISABLE_TRACING()  will have some problem

    RuCh_2181101

      Hi Sir,

         This situation is hard to describe. First, we observe one case. If we show up too much message in HCI UART, the device will reboot.

      So we want to use BLE_APP_DISABLE_TRACING() to disable console output. But we found that other case.

      if the puart_control.exe send the command to WICED (20736), it will no response to send information back to puart_control.exe.

      But if we add some code in puart_control_rx_callback. Like .

       

      test_puart_write(PUART_CONTROL_EVENT_CONTINUE);

      test_puart_write(PUART_CONTROL_EVENT_CONTINUE);

      test_puart_write(PUART_CONTROL_EVENT_CONTINUE);

      test_puart_write(PUART_CONTROL_EVENT_CONTINUE);

      test_puart_write(PUART_CONTROL_EVENT_CONTINUE);

      test_puart_write(PUART_CONTROL_EVENT_CONTINUE);

      test_puart_write(PUART_CONTROL_EVENT_CONTINUE);

      test_puart_write(PUART_CONTROL_EVENT_CONTINUE);

      test_puart_write(PUART_CONTROL_EVENT_CONTINUE);

      test_puart_write(PUART_CONTROL_EVENT_CONTINUE);


         It will back to normal. It is very strange.


        Do you know the way to close HCI UART safely ?


      Best Regards,

      Rush Chen