Smart Bluetooth Forum Discussions
We're preparing a device using CYW20736S (actual part is BCM20736) and need a way to attach a coax connector to the antenna.
The module comes with an embedded antenna only but some info on the forums suggest that similar parts use the pin 10 as external antenna access. The datasheet for this part shows pin 10 as Reserved without suggesting antenna access.
Can I assume that we can use pin 10 to connect to an external antenna?
Also, pin 26 is described as test mode control. Does that mean the pin needs pulled up in order to use external antenna for testing purposes?
Is it possible to provision a device for a Mesh Network if that device does NOT have a GATT PROXY running?
If it’s possible to provision a device, (without a Proxy on the target device), through a Mesh Network, does Cypress have any examples of this "Remote Provisioning"?
If it’s NOT possible to provision a device through a Mesh Network, must every device initially have a GATT Proxy to enable provisioning?
Aside: I did find the “low_power_led” example on GitHub. After enabling low power mode by adding “#define LOW_POWER_NODE 1”, it appears the only way to provision the device is provision shortly after Power On or press Reset then SW3 which appears to enable a GATT PROXY. I'm inferring there's a GATT Proxy running as I have no other BLE-MESH devices powered-on in the near vicinity and I’m able to see the low power device on my smartphone only after pressing Reset and SW3, I can provision the Low Power Node from my smartphone if I'm quick before it goes to sleep.
The Low Power Node doesn't show up after provisioning on a Mesh Network without a Friend Node existing first.
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?Show Less
For developing a device that can be working very long with a coin cell, I am looking for a BLE with the lowest energy consumption.
I will be very thankful to your help.Show Less
We can't use the chipload binaries as our manufacturing computers run on ARM.
- Would it be possible to get the source-code of chipload?
- is the UART protocol for the bootloader documented somewhere?
- are there any other existing tools or implementations (like openocd) out there that can be used that doesn't rely on chipload
where is the function in the peripheral ble ?
The peripheral ble let the central ble to launch a BTM_SECURITY_REQUEST_EVT .
Thank you.Show Less
We're looking into sending a permissive change request for the BCM20736S BLE module. I can't find any references or documentation on the website, what's the best way to approach this?
I was skimming through the documentation about EZBLE (EZ-Serial BLE Firmware Platform User Guide, Doc. No. 002-11259 Rev. *A, https://www.cypress.com/file/285326/download ), and came across lot f acronyms that I haven't any idea, such as CYSPP, GATT, GAP etc. Would it be better to include expansion of these acronyms and/or a few words or references to these inside the documents itself? I couldn't understand what they are?Show Less
I would like to change the BLE address of the device but directly from the device running itself.
I know that the address is stored in the EEPROM in the DS1 at offset 0xFF000015 to 0xFF00001b and I can change it directly via bleappfwu_writeMem and when I reboot I indeed get the desired address.
But is there a better way to change the value of the BLE address stored in the EEPROM ? I found blecm_set_static_random_bd_addr but once again, the address must be set to 0xffffffffffff in the EEPROM before calling it.Show Less