• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 50 subscribers
  • Views 377 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.

HCI messages through a "null" UART

bob frankel
Expert 2460 points

as i understand it, the hci_ext_app.c file in the HostTestRelease project basically handles/dispatches *all* of the TI HCI extension messages....  as configured, these command/event messages are received-from/sent-ti my host PC via the physical UART....

for reasons a little complex to explain, i would like to consider a case where my PC-based host application (which is send/receiving these HCI extension messages) is written in portable C such that it can *also* execute (with little/no code change) on the CC25450 itself....

said another way, i would like to use the HCI message set (with the TI extensions) as my "standard" interface to the BLE stack....  my application would send/recv messages in lieu of making direct calls to GATT/GAP APIs....  in the case where the app is executing on the controller itself, i would  implement some sort "null" UART (essentially, a message queue) that would carry the HCI messages between my application and the dispatcher logic in hci_ext_app.c

does this make sense???  and can anyone spot any serious drawbacks with this approach??

thanks in advance....

 

  • 0
    TI__Genius 17975 points

    I believe your approach would work, though it probably would require some modification of the HAL UART drivers in order to implement the "null" interface. The HCI vendor specific commands basically just map to the stack API functions, so even if you are not directly calling the API functions they are still getting called when you use the HCI commands.