What I think is there is issue with PSoC Creator installation in your system. The CYBLE-212020 module works with PSoC Creator 4.3 without any issues.
If you are using PC CySmart tool please install latest CySmart tool i.e CySmart1.3 and check once.
If you are using mobile CySmart tool, please check with different mobiles.
Also, please debug the application and check if CyBLE_Start() is SUCCESS or not.
>>"What if the device under the hood for this module? The datasheet has plenty of dead links. Is it PSOC or PROC?"
--> This module uses PSoC 4 BLE device.
This link give me access denied.
I will look into the return value from CyBLE_Start next, as 4.3 decided it did not like the miniprog3, even though 3.3 had just been using it.
CYBLE_ERROR_OK is the return value from CyBLE_Start()
Please refer to the PSoC4: 4200_BLE Family Datasheet from this link. Please check if you are getting the CYBLE_EVT_STACK_ON event or not. If yes, then check the api result of CyBle_GappStartAdvertisement() API.
Please send your project so that we can check at our end.
That link worked. Thanks.
I will check the other return values and reply with the project files as well.
CYBLE_ERROR_OK is returned for CyBle_GappStartAdvertisement(CYBLE_ADVERTISING_FAST) inside of the event CYBLE_EVT_STACK_ON.
I have attached the project archive.
I have not tried another phone yet, but this one sees the advertisement from the Creator 3.3 build.
I have the PC CYSmart 1.3 installed, the dongle reports as firmware 126.96.36.199, hardware 188.8.131.52
This tool does discover the advertisment, but after about 30 seconds of scanning. The phone app seems to scan for only a few seconds.
Just tried another android device with a fresh install of CYSmart. Exactly the same.
Tried an iPhone and that was slightly different in that upon the app starting up, it saw the Alert Handler broadcast, yet failed to find it again after a refresh.
So after sending the app and trying different phones, do you have an idea why I am seeing this behaviour?
ECO capacitance trim is required to supply the correct capacitance load to achive 0 ppm for the ECO. By default, the ECO capacitance trim values are set to the trim values of PSoC 4 BLE / PRoC 4 BLE modules. If any other BLE module is used (such as, EZ-BLE module), the trim values should be changed to the values provided by that module’s datasheet. Please refer to this KBA ECO Capacitance Trim Values for EZ-BLE™ Modules - KBA218990 for the CAPTRIM Register value.
Please let me know your observations after adding the Cap trim value.
This has confused me.
You are suggesting that I have to re trim the cyble-212020 module when using an app created in PSOC creator 4.3, but PSOC creator 3.3 does not need the module to be trimmed?
OK, I have not seen this in any of the materials read so far.
I will give this a go and report back. Fingers crossed.
Brilliant, thank you. It now creates advertisements that I can see on the phone.
Not sure I understand whey Creator 3.3 works with or without this addition configuration, but i'll take it as a win and move on.