Erratic BLE, pairing problematic, connection flakey

Renate · ‎Oct 05, 2021

I've been working on this for a week, learned some, so let me restate my case. I'm using brand new, US big-name distributor, sealed CYBLE-012011-00 modules on two different perfboarded prototypes of different layouts.

I can program them with the downloaded hex file of EZ-Serial and they behave properly, visible under any OS, pair instantly. I have tried three different examples (only modified for switch/LED pin assignments) BLE_HID_Keyboard, BLE_HID_Mouse, BLE_Heart_Monitor. All of them program and verify correctly. All of them only pair with difficulty (hitting pair 50 times). All of the HID examples are not even visible under Windows. On the occasions that I have got the Keyboard to pair with Android it has worked functionally correct, but balky, with latency problems and the connection dropping. The power is good (batteries, different power supplies) and the layout keeps out of the antenna area. The distance is two feet.

What is going on? Could somebody post a hex file (with BLE) for the CYBLE-012011-00 so I can have a reality check? I'm running on the 3.66 BLE version, although I have tried 3.50 also. When I have added user parts to the code those parts have operated correctly within the constraints of the BLE part flakey.

Renate · ‎Oct 11, 2021

With all the trademark names flying around it's easy to overlook that a CYBLE-012011-00 is not just a PSoC4BLE but is also an EZ-BLE.

Since PSoC Creator knows the target that I am using, why can't it set this properly itself? Why is this critical info in an add-on KBA? I haven't run into anywhere where they spell out the exact meaning of "ECO".

So, I get it. The master 24 MHz crystal oscillator needs trimming of the parallel caps for startup, stability and frequency accuracy. I don't see any procedure for verification/testing of these values.

Finally, the clock dialog uses a setting in picofarads. That's hard to correlate with the suggested hex values. Do I have to adjust in pF, build, check what hex values it's using then circle back until I get it right? Apparently.

Edit: For the CYBLE-012011-00 suggested value of 0xbcbc, use 17.8 pF, 17.8 pF

The conversion uses two overlapping ranges depending on the MSB. The lower range is pf = hex/10+3.7 The upper range is pf = hex/10-1.0

View solution in original post

Erratic BLE, pairing problematic, connection flakey

Erratic BLE, pairing problematic, connection flakey

Re: Erratic BLE, pairing problematic, connection flakey