Differences between CYBLE-214015-01 and CYBLE-214009

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
DaZh_1276586
Level 2
Level 2
5 sign-ins First solution authored 10 replies posted

Hi:

I just want to ask more information about the differences between CYBLE-214015-01 and CYBLE-214009.

I recently changed from CYBLE-214009 to CYBLE-214015-01 because the 214009 is discontinued. But I found the throughput of 214015 is flipping, reducing upto 40%, while the 214009 module fairly stable.

I think it might because the changes on the silicon. Is there any information can provide?

Thanks.

Dayi,

0 Likes
1 Solution
Yugandhar
Moderator
Moderator
Moderator
500 solutions authored 1000 replies posted 5 likes given

Hello,

CYBLE-214015-01 is a PSoC 4 BLE with BLE version 4.2 where as CYBLE-214009-00 is a PSoC 4 BLE with BLE version 4.1. In Bluetooth 4.1, the payload size is 27 bytes and the total time taken for single transaction is 708 µs that gives the theoretical throughput of 298 kbps. In Bluetooth 4.2, the payload size is 251 bytes (2008 bits) and the total time is 2500 µs that gives the theoretical throughput of 784 kbps. This gives approximately 2.6 times throughput for a Bluetooth 4.2 device as compared to a Bluetooth 4.1 device. Please refer to the section 5 LE Data Packet Length Extension in the datasheet for more information. Could you please let me know how you configured the payload values in CYBLE-214015-01 ?
Please refer to the page no.6 in AN96841 GETTING STARTED WITH EZ-BLE CREATOR MODULES datasheet for different EZ-BLE Modules Features.


Thanks,
P Yugandhar.

View solution in original post

0 Likes
5 Replies
wcc3
Level 4
Level 4
10 likes received 10 replies posted 5 replies posted

I notice that the recommended settings of the CAPTRIM register for these two modules are radically different.  See the specification ECOtrim on the respective datasheets.

Setting CAPTRIM wrong pulls the high-speed crystal frequency and plays hob with BLE timing.

The '214009 module recommends a CAPTRIM value of 0x2D6A while the '214015 module recommends 0x9595.

If you're setting this with an API call in your code, you just change the number.

If you're relying upon the clock editor in the design-wide resource file configurator, you change the capacitances in the oscillator configuration block from 8.25pF and 14.3 pF to 13.896 pF for both.

0 Likes

According to the datasheets, 214009 and 214015 recommend CAPTRIM are the same, 0x9595.

And this is the value I put in the firmware.

0 Likes

Ah.  They changed that at '241009 datasheet rev C.  When I did my '214009 design, rev B was current.

This has tripped me up at least twice retargeting designs onto different modules.  Was worth a shot.

Hope you get this fixed soon!

0 Likes
Yugandhar
Moderator
Moderator
Moderator
500 solutions authored 1000 replies posted 5 likes given

Hello,

CYBLE-214015-01 is a PSoC 4 BLE with BLE version 4.2 where as CYBLE-214009-00 is a PSoC 4 BLE with BLE version 4.1. In Bluetooth 4.1, the payload size is 27 bytes and the total time taken for single transaction is 708 µs that gives the theoretical throughput of 298 kbps. In Bluetooth 4.2, the payload size is 251 bytes (2008 bits) and the total time is 2500 µs that gives the theoretical throughput of 784 kbps. This gives approximately 2.6 times throughput for a Bluetooth 4.2 device as compared to a Bluetooth 4.1 device. Please refer to the section 5 LE Data Packet Length Extension in the datasheet for more information. Could you please let me know how you configured the payload values in CYBLE-214015-01 ?
Please refer to the page no.6 in AN96841 GETTING STARTED WITH EZ-BLE CREATOR MODULES datasheet for different EZ-BLE Modules Features.


Thanks,
P Yugandhar.

0 Likes

Thanks.

I use the same firmware code, just recompile the project with 214009 and 214015 without any changes. But I see the throughput is different. 214015 is obviously lower than 214009.

It might be a small settings error. Could you open a tech support for me so I can send the project file to you?

0 Likes