[PSoC62]I2C state keep busy and cannot communicate any more

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

cross mob
lock attach
Attachments are accessible only for community members.
xubo_2592826
Level 2
Level 2
5 replies posted 5 questions asked First question asked

Hi,

I found 1 issue on PSoC62(CY8C6247BZI-D54),

after long time I2C communication(Long than 1 hour),

I2C comunication stop and cannot continue.

please refer to attached file(PSoC62_I2C_Issue.xlsx) for detail information,

Is above symptom known issue? Would you like to share some information to me?

It is very helpful if you can provide some advice about counter measure.

0 Likes
1 Solution

Hi fddl_xubo_2592826​,

One of our customers recently faced a issue just like yours. The I2C bus busy flag is set whenever a start condition is detected on the bus. This flag is cleared on detecting a stop condition and it assumes that another master is sending the data. But due to noise, a false start condition may be detected on the I2C bus and the I2C bus can get stuck in the busy state.

Regards,

Bragadeesh

Regards,
Bragadeesh

View solution in original post

0 Likes
8 Replies
BragadeeshV
Moderator
Moderator
Moderator
First question asked 1000 replies posted 750 replies posted

Hello fddl_xubo_2592826​,

This is not a known issue. Could you please share the project file focusing on the issue? We will try to reproduce the issue and let you know the cause.

Regards,

Bragadeesh

Regards,
Bragadeesh
0 Likes

Hi BragadeeshV_41

>Could you please share the project file focusing on the issue?

->I am sorry that I cannot share the project to you due to information security.

and PSoC62(CY8C6247BZI-D54) statr kit has been connected to user set,

and PSoC62 does not run alone.

So I think you cannot run the project even you got the project.

would you like to share some hint for studying this issue?

Best regards,

Xu Bo

0 Likes

Hi fddl_xubo_2592826​,

Thanks for the update. Instead of using the user's slave device, can you try using a I2C slave emulator such as Aadvark and check if you still face this issue? This is discard any possible effects the slave can have on this issue.

Try loading any I2C master code example into your device, run it for more than an hour and check if you still face this issue.

If I have your project I can use the Aadvark I2C slave emulator and check your code. Is it possible to share the PSoC 6 part alone?

Regards,

Bragadeesh

Regards,
Bragadeesh
0 Likes

Hi BragadeeshV_41

I am so sorry that reply too late.

This issue cannot be reproduced at new prototype set,

maybe this issue relate with noise on old prototype set made by manually.

Best regards,

Xu Bo

0 Likes

Hi fddl_xubo_2592826​,

Thanks for the update. Could you please let us know the rev of the old and new kit that you used. Also please let us know the PDL version and Creator version.

Regards,

Bragadeesh

Regards,
Bragadeesh
0 Likes

Hi BragadeeshV_41

>Could you please let us know the rev of the old and new kit that you used.

->Old prototype set use PSoC62 Wifi rev10.

    New prototype set mounts PSoC61 on board.

>Also please let us know the PDL version and Creator version.

->PDL version:3.0.1

    Creator version:4.2

Best regards,

Xu Bo

0 Likes

Hi fddl_xubo_2592826​,

One of our customers recently faced a issue just like yours. The I2C bus busy flag is set whenever a start condition is detected on the bus. This flag is cleared on detecting a stop condition and it assumes that another master is sending the data. But due to noise, a false start condition may be detected on the I2C bus and the I2C bus can get stuck in the busy state.

Regards,

Bragadeesh

Regards,
Bragadeesh
0 Likes

Hi BragadeeshV_41

Thank you for sharing new information to me!

>But due to noise, a false start condition may be detected on the I2C bus

>and the I2C bus can get stuck in the busy state.

->Maybe the issue that I found has the same root cause as above.

Best regards,

Xu Bo

0 Likes