I have followed those directions as I stated earlier but I see no activity on the bluetooth module gci out Pin. i thought the protocol is bidirectional. Also this is for the 20707 which uses a different api than the 20719.
Just to prove this out, I used my 20719 devboard and sending the following commands before initializing the bluetooth system does enable the bt board to send gci data. I am just using the ibeacon demo.
wiced_hal_gpio_select_function(WICED_P10 , WICED_GCI_SECI_OUT);
wiced_hal_gpio_select_function(WICED_P06 ,WICED_GCI_SECI_IN );
/* Register the dynamic configurations and */
/* initialize the stack */
For the 20707, I am using the mybeacon snip and this does not work
wiced_bt_stack_init(mybeacon_management_cback, &my_beacon_cfg_settings, my_beacon_cfg_buf_pools);
I have the same question.
The datasheet here https://www.cypress.com/file/298056/download says this:
■ Enhanced coexistence data can be exchanged over GCI_SECI_IN and GCI_SECI_OUT a two-wire interface, one serial input (GCI_SECI_IN), and one serial output (GCI_SECI_OUT). The pad configuration registers must be programmed to choose the digital I/O pins that serve the GCI_SECI_IN and GCI_SECI_OUT function.
So, looks like pad configuration is the must, but I don't see any API to configure GCI or SECI on API manual. How can I configure that?
This still has not been answered. The coexistence interface api does not let you choose a pin for this module. I have been told that it defaults to gpio 6 and gpio 7 for the 20707, but the cybt353027 wants to use gpio 5 and gpio 6. Is it a problem with the platform files? There is a bug somewhere in the wiced code or platform files supplied.
I thought this may have been fixed in wiced 6.4 but it still doesn't work. How do you enable coexistence on the CYBT_353027-eval?
I tried calling wiced_bt_coex_enable() but still nothing comes out. How do we select the pin function?