I2C Component - Max supported by BCP

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

cross mob
anlec_1602741
Level 1
Level 1

Good morning everyone,

   

 

   

I have a problem concerning the component I2C in PSoC Creator 3.3.

   

I have download the example "I2C BLE bridge" here:

   

https://github.com/cypresssemiconductorco/PSoC-4-BLE/tree/master/100_Projects_in_100_Days/Day035_I2C...

   

 

   

In the file "app_I2C.h", there is two line code that i don't understand:

   

#define I2C_READ_BUFFER_SIZE    (61) /* Max supported by BCP */
#define I2C_WRITE_BUFFER_SIZE    (61) /* Max supported by BCP */

   

 

   

What means "Max supported by BCP"? There is a way to improve this value?

   

 

   

Thank you for your answer.

0 Likes
1 Solution
HeLi_263931
Level 8
Level 8
100 solutions authored 50 solutions authored 25 solutions authored

BSP is the "bridge control panel" - the software that connects to the I2C BLE bridge (on the PC side). Why do you want to increase that - 61 seems quite plenty?

View solution in original post

0 Likes
3 Replies
HeLi_263931
Level 8
Level 8
100 solutions authored 50 solutions authored 25 solutions authored

BSP is the "bridge control panel" - the software that connects to the I2C BLE bridge (on the PC side). Why do you want to increase that - 61 seems quite plenty?

0 Likes

Thank you for your reply.

   

In fact i would like to increase this value because on some frames i will use sometimes 200 bytes. So if i understand why 61 is the maximum, i can maybe increase this value to 256 or 512 for example. I have seen maybe there is a link betweek this value and "Attribute MTU size"?

0 Likes
HeLi_263931
Level 8
Level 8
100 solutions authored 50 solutions authored 25 solutions authored

I think you should be able to send larger packets still (but I have never used the BSP or the I2C bridge). But since this is a limitation of the BSP, you should raise a support case with Cypress and ask them directly.

0 Likes