Using HCI for debug

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
Anonymous
Not applicable

Hello,

I would like to use the HCI for debug and I've seen many posts in the past discussing the same thing, but they are confusing.

1) On the one hand there is a document MMPWICED-Smart-QSG203-R.pdf (and posts on this site) which suggest calling BLE_APP_ENABLE_TRACING_ON_HCI_UART will work, as long as the UART_RX pin is disconnected once the application is running. The procedure is given in pages 19/20 of the above document (Viewing Traces from the WICED Smart Tag).

2) In WICED-Smart-Hardware-Interfaces.pdf, page 16 says:

The BCM20732 has two UART interfaces. One is the factory or HCI UART that is used for programming and factory testing. The other is the peripheral UART, which is available for application use to output debug messages/tracing or to interface with a peripheral device/microcontroller. The following sections describe the peripheral UART only. The HCI UART is not available for application use.

The two seem to contradict each other. Does anyone know?

Thanks.

0 Likes
1 Solution

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.

View solution in original post

0 Likes
4 Replies