The HCI UART for all intents and purposes is a programming interface only. You can also route debug traces to the HCI UART per the instructions in the WICED Smart Quick Start Guide (SDK 2.x and TAG4 Board), but again, if you application requires some form of UART access, only the peripheral UART is available to the application.
Thanks for the answer. However I don't think I fully understood. While you said that "You can also route debug traces to the HCI UART per the instructions .." you also said "if you application requires some form of UART access, only the peripheral UART is available to the application". Could you explain a little on what the difference is that you are making?
i.e. when can we use the debug traces using HCI UART and when will we necessarily have to use P UART?
Is it that with HCI UART we can only output debug strings / traces whereas for a full-fledged bi-directional data transfer then P UART is the only option?
If you confirm this, thanks, I've understood fully.
The PUART can be used for bidirectional communications with an outside entity via control provided within your bluetooth application.
PUART or HCI UART can be used to display trace output.
The HCI UART is only used for programming the device, and your bluetooth application cannot require services from this port, other than the redirection of traces for debug.
I am able to follow the instructions in the manual to display traces over HCI UART on the IDE debug console window.