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)
To conduct regulatory testing on a device containing a WICED chip I've used two different methods in the past
1. Expose the HCI UART outside the device and use CyBlueTool
2. Make API calls to blecm_StartTransmitterTest(). I then have the device's normal external pushbuttons cycle through the tests.
For my latest project I'm using a 20719-B1 based CYBT-413034-02.
From my reading of Putting 2073x, 2070x, and 20719 Based Devices or Modules in HCI Mode – KBA225450 it appears the only way to put the device into HCI mode is to erase the bluetooth code and put in some non-bluetooth code. This defeats the purpose of testing, as the device also needs to be able to operate normally (with bluetooth code). Is there any way to put the 20719-B1 in HCI mode without erasing the bluetooth code?
This leads me to want to call regulatory tests from the API, and control them from within the device, but I can't find blecm_StartTransmitterTest() or equivalents in WICED 6.2. What are the regulatory API calls in WICED 6.2?
So from your answer "Its recommended to use non BT application to make reliable communication with HCI host and CY20XX devices" I can infer that there is no way to issue HCI test commands programmatically? and also that I need to remove my bluetooth application code before sending my device for regulatory testing?