Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
The trace output comes out of the HCI UART right? It always comes out of the HCI UART irrespective of what's attached to those pins? Is there a way to turn off all trace output or disable the HCI UART so the pins tri-state? (after boot up when the 20737 checks to see if it's meant to go into programming mode.)
With SDK 2.1, we implemented an encoded tracing mechanism in the ROM to reduce the ROM foot print and to make logging a bit faster. You cannot use a hyperterm like application any more because these traces are encoded. The SDK comes with its own trace parsing plugin that can decode these traces. Use the Trace -> Start Debug Traces menu item in Eclipse to capture traces on the same uart you used to download the application (or use Trace -> Setup COM Port menu to manually set it). Note that you have to Stop Debug Traces before you download the app again or the download will fail.
I've a 20737on a board with another micro. I'll program the 20737 via the other micro. Once the 20737 is programmed the pins from the micro that are attached to the HCI Uart are also connected to a different device on the board.
I should be able to control everything so that at turn on the 20737 doesn't go into programming mode, but, when in application mode, if the 20737 automatically outputstrace data from the HCI Uart pins it'll interfere with the operation of the other device.
If I'm understanding you correctly, in application mode, the UCI Uart doesn't drive any trace data out unless it's instructed to.