- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I found today that if I don't call wiced_transport_init() right away in APPLICATION_START() and wait till BTM_ENABLED_EVT, the wiced_transport_tx_complete_t callback stops getting triggered.
Is wiced_transport_init() required to be called only in APPLICATION_START()?
The reason why I wanted to call wiced_transport_init() in BTM_ENABLED_EVT is in APPLICATION_START() I'm not ready to receive data yet.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have created a simple snippet for WICED UART raw mode. I am calling the init() function in BTM_ENABLED_EVT and not in application start. It works fine. You can test too.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You should be able to call wiced_transport_init after the BTM_ENABLED_EVT. I tried the same and the wiced_transport_tx_complete_t callback was triggered. By the way, I performed the test using WICED 6.0.
Is the callback never triggered or does it stop randomly after some time?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
wiced_transport_tx_complete_t callback never triggered if I don't call transport init in application start. I am using WICED studio 6.0 and WICED_TRANSPORT_UART_RAW_MODE.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content